Where your drawings go, and who can see them.

Free tools

• Your file never leaves the browser. Split and Specs process files on your device. There is no upload and no account.
• A usage report does leave it. After each run the tool sends counts (pages, time, sheets matched, the kind of failure if any) to our own database. Never the file, its name, or anything read from it; no cookie, no address kept. The privacy policy lists every field and has the switch to turn it off.
• Shared corrections are opt-in. A box on Split, off by default, sends the titleblock crop and the corrected values of a sheet when a person corrects it, and nothing else from the set. The privacy policy says exactly what.
• The pages load no third-party script, font or tracker; everything is served from sheetsa.com, and the usage report goes to the same database as Archive, not to a third party.
• The apps work offline after the first visit, which is a consequence of the same design. A usage report with no connection to send on is dropped, not queued.

Archive, early access

• Where: database and file storage on Supabase, in the us-east-2 region (Ohio, United States), on Amazon Web Services.
• Encrypted in transit (TLS everywhere) and at rest (the storage provider's disk encryption).
• Isolated by organisation in the database itself. Every row carries its organisation; row-level security policies refuse reads and writes from anyone who is not a member. An automated test checks that a member of one organisation cannot read or write another's rows.
• Sign-in by emailed link or password, through Supabase Auth. No passwords are stored by us in plain text; the auth service handles them.
• Files are in a private bucket. Nothing is publicly readable. Access is through short-lived signed links issued to signed-in members.
• Audit trail: every automatic read and every human correction is an append-only record with who and when.
• Deletion on request, confirmed in writing. See the privacy policy.

Not in place

• No SOC 2, ISO 27001 or similar certification. Sheetsa has not been audited. Our providers hold their own certifications; those cover their infrastructure, not our application.
• No single sign-on (SAML/SSO), no roles within an organisation beyond member and admin, no retention schedules, no legal holds.
• No storage region other than the one above; no choice of region yet.
• No penetration test report yet.

We would rather say this plainly than let a reviewer discover it. Each item is on the list for the owners-and-agencies tier when a contract asks for it.