Security
Your work stays yours.
Security isn't a feature added later: every request is checked against your organization and your role.
Organization isolation
Every request is checked against your organization, and the check is part of the database query itself, so other companies' data is never even loaded. A record from another organization looks exactly like one that doesn't exist.
Separate organizations
Products, stories, documents, teams, 1:1s and HR documents all belong to one organization.
Every id checked
Ids sent with a request (a story, a person, a team) must belong to your organization too.
Tested
Automated tests try to reach another organization's data through every part of the app.
Roles and the flow's rules
FlowGazer's server enforces the rules, not just the screens.
Four-eyes rule
Nobody reviews or approves their own work.
Admin protection
Product managers can manage people and teams, but can't edit organization admins or give anyone the admin or PM role.
The right people sign off
Only product managers promote stories to the backlog; only the assigned QA or Ops (or a manager) sign off releases.
Sessions and accounts
Hashed sessions
Sessions use random, high-entropy tokens stored only as hashes.
Automatic logout
You're logged out after 30 minutes of inactivity.
Who did what
Changes on the board are recorded with the person who made them.
Data, hosting and AI
Where your data lives
FlowGazer runs on DigitalOcean servers in Amsterdam, in the EU, and your data is stored there.
AI and your data
The AI features use Google Gemini. It only receives what you send it: a document you upload to be read, or the 1:1 sessions you select. Nothing is sent in the background.
Security questions: info@flowgazer.com