Team data isolated in the database
Postgres row-level security sits on every multi-tenant table. The app connects as a restricted role that cannot bypass it, so a missing check in code still can’t leak another team’s data.
Isolation between teams is enforced by the database itself, not only by application code. Here is what protects your data today — and what we don’t offer yet.
Postgres row-level security sits on every multi-tenant table. The app connects as a restricted role that cannot bypass it, so a missing check in code still can’t leak another team’s data.
Passwords are hashed with argon2id. Turn on two-factor sign-in with an authenticator app, and team owners can require it for everyone. Sessions use httpOnly cookies.
Files are never in a public bucket. They are served through signed links that expire after minutes, and only to people allowed to see them.
We don’t train models on your content. Your AI key is stored encrypted and never sent to the browser. AI only sees what the person using it may see.
Review the team’s activity — approvals, role changes, agent runs — and export it as CSV or JSON.
Your account shows a log of any time Projoint staff accessed it for support, so nothing happens out of sight.
We’d rather say it plainly than imply it. If one of these is a requirement for you, tell us — it helps us decide what to build next.
You can delete your account from Account settings at any time. For a copy of your data or a deletion request, email privacy@projoint.tech.
Email security@projoint.tech with a description and steps to reproduce. We read every report and will credit you, with your permission, once a fix ships.
Free for up to 10 members. No card required. Add AI with your own key when you’re ready.