How SetSnitch keeps data safe
A production trusts SetSnitch with its call sheets, its crew's phone numbers and its scripts. This page says how we look after them.
Who sees what
- Every request is checked on our servers, not in the app: who is asking, whether they are on that production, and what their role lets them see. A crew member sees their own production and their own days.
- The production decides who is on it. Removing someone closes every screen to them within a minute.
- Joining a production takes its invite link and the code the AD gives out, and repeated wrong codes are slowed down.
- Documents a production keeps private stay with the people it chooses, and crew can download a document the production uploaded only if the production allows it.
Documents and files
- Files are stored privately. They open only through links that stop working within an hour, made for the person who asked. The one public picture is a production's cover, which is shown like a poster.
- A PDF carries the reader's name across its pages, so a copy that travels says whose it was. The production can turn this off.
- Every opening and download in Documents is recorded with who and when.
Encryption and hosting
- Everything between your device and SetSnitch travels encrypted.
- The database and stored files are encrypted where they are kept.
- SetSnitch's servers run in Frankfurt on Vercel, and the database and stored files are kept by Supabase in Frankfurt. Sign-in is handled by Clerk.
- Vercel, Supabase, Clerk, Anthropic and OpenAI are each independently audited against SOC 2.
AI
- SetSnitch asks each person before it sends anything they give it to an AI model, and works without it if they say no.
- Documents, photos and questions go to Anthropic, which deletes them within 30 days unless its safety systems flag misuse, and never trains its models on them.
- Requests to the Snitch, spoken or typed, go as text to TypeSafe AI and OpenAI, each the other's backup, to work out what is being asked. The conversation before a request and details of the shooting days, such as dates, places, scene numbers and characters, go with it. No audio of them is sent to SetSnitch, TypeSafe AI or OpenAI.
- TypeSafe AI and OpenAI also answer short questions about a production's scripts, call sheets, crew list and files, and the emails sent to its call sheet address, such as what a scene needs or what kind of file a document is. For that they see the text, and sometimes a picture of a page or a photo.
- Storyboard sketches are drawn by OpenAI from a short description. SetSnitch takes every real name out of it first.
- Neither TypeSafe AI nor OpenAI trains its models on what we send. OpenAI deletes it within 30 days unless it is flagged as misuse or the law requires otherwise, and TypeSafe AI keeps it only as long as it needs to provide its service.
A record of what happened
Opening and downloading documents, removing, restoring and promoting people, leaving, handing over and deleting a production, and deleting an account are recorded with who did it and when. The record holds ids and short labels, such as the email a handover was offered to, never the contents of a document, and is kept 12 months.
Keeping and deleting
- A production's data stays until its owner deletes the production, or chooses deletion when cancelling their plan, or until 12 months after it locked without a plan. Then everything in it goes: days, crew list, documents, stored files and messages.
- Anyone can download their own data, and delete their account, from Your account.
- Backups expire within 30 days.
The fine print
How we handle personal data is in the privacy policy, and the terms we work under for a production are in the data processing agreement.
Found a problem?
If you think you have found a security issue in SetSnitch, write to support@setsnitch.com. We answer every report and fix what we find.