Trust center
Mission Control holds the work your organization runs on. Here is exactly how we protect it, in plain words. If something you need isn't here, ask us and we'll answer in writing.
See Go / No-go in action
Your data stays yours
- Separated in the database. Row-level security is on for every table, so access is checked by the database on every read and write, not just by the app.
- Secrets in a vault. Tokens for connected apps and any AI key you bring are stored encrypted in a vault, never in ordinary tables.
- No training on your content. We don't use your organization's content to train AI models, and our AI provider doesn't train on it either.
- Nothing sold. We don't sell personal information or use it for ads.
The right people, the right access
- Four roles. Flight director, admin, member and viewer. Viewers can see but never change anything, enforced in the database.
- Per add-on access. Admins can give each person edit, view or no access to each add-on.
- Sign-in rules. Require Google single sign-on, and require two-step sign-in with an authenticator app for admins or for everyone.
- Session control. Anyone can see their active sessions and sign out everywhere else. Admins can sign out a member.
Every change on the record
The Mission Log records what people and agents do, including deletes, restores and support access. Each entry is chained to the one before it with a cryptographic hash, so a missing or edited entry shows. Deleted records sit in Trash for 30 days and come back with their links intact.
AI with a person in charge
- The crew works only on what you ask, and only sees the content that task needs.
- Anything that sends, charges, signs, publishes or deletes waits in Go / No-go for a person to approve.
- AI spend has an org-wide hard stop, and you can bring your own Anthropic key instead.
Connected apps
An admin chooses each connection and sees what it can read before approving it. We never read source code, environment variables or database table data through a connection. Google data is used under the Google API Services User Data Policy, including its Limited Use rules. Disconnecting an app deletes its stored token. How connections work.
Where your data lives
Your organization's data is stored in the United States. These companies process it for us, each only to provide its service:
| Company | What for | Where |
|---|---|---|
| Supabase | Database, file storage and sign-in | United States (AWS us-east-1) |
| Vercel | Hosting and scheduled jobs | United States |
| Anthropic | AI for the crew, only when you ask it to work | United States |
| Stripe | Subscription billing and payments on your sites | United States |
| Resend | Sign-in links and the emails you approve | United States |
Apps you connect (for example Google, Microsoft or Slack) process data under your own agreements with them. We'll update this list before adding a new company.
Your choices
- Ask for a full export of your organization's data, or for it to be deleted. We do either within 30 days.
- When you close your account we delete your data within 90 days, except records the law requires us to keep.
- See, correct or delete your personal information on request.
Where we are today
We're a new product and we'd rather be clear than impressive. We don't have a SOC 2 report yet. If your review needs a security questionnaire filled in, send it over and we'll answer it honestly.
Report a security issue
Email hello@joineta.org with “Security report” in the subject. We'll confirm we got it within two business days. Please give us a fair chance to fix an issue before you share it.