Security & IT overview
Last updated October 21, 2026
A summary for IT and security reviewers. Print or save it as a PDF for your records.
At a glance
| What it is | A planning tool. A manager keeps a ranked list of tasks, who is assigned, estimates, and team members' working schedules and time off. |
|---|---|
| Who uses it | The person who plans the work. Team members do not need accounts and are not contacted by the app. |
| Data stored | Account email address; names of team members as typed by the user; project names; task titles, notes, estimates, due dates and status; working-day patterns and time-off dates; photos the user chooses to attach to tasks. |
| Not collected | No passwords (sign-in is by one-time email code). No documents, payment card data, contacts, location, or device identifiers for advertising. Location metadata is removed from photos before upload. No advertising or third-party tracking scripts. |
| Integrations | None. The app does not connect to company email, calendars, directories, file storage, or project systems. All data is entered by the user. |
| Data location | United States. Database in Amazon Web Services us-east-1 (N. Virginia) via Supabase; web app served by Vercel. |
| Hosting vendors | Supabase (database and sign-in), Vercel (web hosting) and Resend (sign-in emails). Each publishes SOC 2 Type II reports; see the sub-processor list below. |
Protection of data
- In transit: all traffic between browsers or the iPhone app and the service uses HTTPS (TLS). Plain HTTP requests are redirected to HTTPS.
- At rest: the database and its backups are encrypted at rest by the hosting provider.
- Isolation between customers: every record belongs to a workspace, and the database enforces row-level security so an account can only read or change its own workspace's records. This is enforced in the database itself, not only in the app, and is covered by automated tests (for example: one account cannot read, edit, or insert into another account's workspace; read-only members cannot make changes).
- Photos: stored in private storage, never at public addresses. They are shown through links that expire after one hour and are issued only to members of the workspace. Photos are resized and re-encoded in the browser before upload, which removes location (GPS) and other embedded metadata.
- Backups: the database is backed up daily by the hosting provider, with backups kept for 7 days.
- Secrets: database administrator credentials are not stored in the app or its source code. The web app uses only the public client key, which is restricted by row-level security.
Sign-in and access
- Passwordless sign-in: users sign in with a one-time 6-digit code (or link) sent to their email. Codes expire after one hour and work once.
- Sessions: signed sessions with short-lived access tokens that refresh automatically; signing out ends the session on that device.
- Roles: each workspace has an owner. The data model supports read-only and editor members for future sharing; sharing is not yet available in the app.
- Operator access: the developer can access the production database for support and maintenance only. There is no sale or sharing of data.
Data retention and deletion
- Delete account: users can delete their account from inside the app. This immediately and permanently removes the account, all of its workspace data, and all photo files.
- Backups: deleted data ages out of backups within 7 days.
- Deleted tasks: tasks a user deletes go to "Recently deleted" so mistakes can be undone, until the user deletes them permanently or deletes the account.
Sub-processors
| Vendor | Purpose | Location |
|---|---|---|
| Supabase | Database, sign-in, and photo storage | US (AWS us-east-1) |
| Amazon Web Services | Infrastructure underlying Supabase | US (us-east-1) |
| Resend | Delivery of sign-in code emails (recipient address and code only) | US (us-east-1) |
| Vercel | Hosting of the web app | US, with global delivery of static files |
| Apple | iPhone app distribution (App Store / TestFlight) | Global |
Each vendor's security and compliance documentation, including SOC 2 reports, is available from the linked pages.
Current limitations
Stated plainly so they can be weighed in review:
- No single sign-on (SAML / Microsoft Entra ID / Okta) or SCIM provisioning yet.
- No customer-facing audit log yet.
- Data is hosted in the United States only.
- Team Priorities itself has not completed an independent audit such as SOC 2; it relies on the certified infrastructure of the vendors above.
Contact
Security questions or reports: contact the person who shared this app with you. See also the privacy policy.