Privacy policy

Last updated 2026-10-29. This policy covers the apps at sheetsa.com, which are provided by Sheetsa LLC, a New York limited liability company ("Sheetsa", "we"). It is written to be read; the terms of use are the agreement.

The short version

• Specs never sends your files, and without a plan neither do the other tools. Specs runs in your browser and needs no account. Split, Archive's scan tools, Triage and Convert need you to sign in; when your organization has no plan they run in your browser and the file you open is not sent to us. When your organization has a plan, what you drop into Split, Archive or Triage is saved to its Library, described next.
• Each run sends a short usage report: which tool ran, how long it took, how many pages, how it went, and counts of what the engine found. Never the drawing, its name, or anything read from it. Every field is listed below, with the switch to turn it off.
• When you correct a value in Split or Archive's scan tools on a set that is not saved to your Library, the correction is shared with us together with the titleblock crop it came from, so the engine can be fixed where it misread. On by default; untick the box to stop. Never from the Library, or from a set saved to it. What is sent.
• Signing in collects your email address. The Library keeps what your organization puts in it: its members and invitations, its drawing sets, spec books and other files, what Sheetsa reads from them, your team's corrections, the packages it sends and who opened them, and an activity log of who did what. The full list is below.
• The notify-me box on the front page keeps the email address you type there, so we can tell you when Archive launches. Only if you use it. What we keep.
• No advertising, no third-party tracking, no selling data. There is no third-party analytics script or tracker on this site. The usage report, and a correction you choose to share, are the only things this site records about a run of the tools when nothing is saved to the Library, and they go to our own database.
• You can have it all deleted by writing to support@sheetsa.com.

1. What we collect, and why

The tools that run in your browser: Specs, and Split, Archive's scan tools, Triage and Convert when nothing is saved to the Library. The file you open is processed on your device and is not transmitted to us. Specs needs no account; the others need you to be signed in (what signing in collects), and when your organization has a plan, what you drop into Split, Archive or Triage is saved to its Library instead. Split and Archive's scan tools keep your current project in your browser's own storage on your device so you can resume it; that copy never leaves your browser, and clearing this site's data removes it. After each run, the tool sends us a usage report, described next.

Usage reports

We collect them so we can see how the reading engine does on real sets it has never seen, and improve it. One report is sent when a run of Split, Specs, Convert or Archive's scan tools (restore, optimize, the PDF/A check, or the fixed copy the PDF/A check can make) finishes or fails, and one more each time you correct a value in Split or Archive's scan tools. A report contains:

• which tool ran, and whether it ran in your browser or on a local server you run yourself;
• how long it took, and the size of the file in pages and bytes;
• whether it finished or failed, and if it failed, the kind of failure (for example, out of memory or not a PDF), not the error text;
• the options you ticked, such as the quality setting or the PDF/A level;
• counts of what the engine produced: how many sheets were matched, which titleblock positions matched how often, how many pages were scans, how many read states of each kind, how many PDF/A findings of each rule, which PDF/A rules a fixed copy repaired or could not, how many images were recompressed;
• for a correction: which field you corrected (sheet number, title, date, revision, or another field, recorded only as "other") and what state the engine had it in;
• your browser's family and version, your operating system, and your machine's processor count and memory class, because "ran out of memory at this many pages" means nothing without them;
• a random id for the browser tab, discarded when you close it, so two runs in one sitting can be told from two visitors.

A report never contains your file, its name, any page image or text, any sheet number, title, date, revision or section number, any recognized line, or anything you typed. It carries no cookie, no account and no persistent identifier, and it is sent anonymously even when you are signed in. We do not keep the network address it came from with it.

Corrections you choose to share

This is the one case where part of a drawing leaves your browser from a set that is not saved to the Library. On the Split page and in Archive's scan tools there is a box, "Help improve the engine: share my corrections with Sheetsa", which starts ticked. It starts unticked if your browser sends a Do Not Track or Global Privacy Control signal, and nothing is sent from such a browser in any case. Only a correction you make is shared; opening, reading and splitting a set sends nothing. While it is ticked, each value you correct also sends us: the small image of the titleblock the engine read that sheet from (the same crop the page shows you), the value the engine had and the value you typed, which field it was, and what state and confidence the engine had it in. Nothing else from the set is sent: not the file, not its name, not the rest of the page, not the other sheets. We use these to see exactly where the engine misreads titleblocks and to fix it. They are stored with the usage reports, are anonymous in the same way, and are read only by us. Untick the box to stop, before or after you correct anything; it stays off in this browser. Turning usage reports off in this browser (above) stops shared corrections too. The Library, where your organization keeps its sets, has no such box and never shares anything with us; once Split or Archive has saved a set to your Library, the box is hidden and nothing from that set is shared. If you shared something by mistake, write to support@sheetsa.com with roughly when, and we will delete it.

Your account, and your organization's Library

Signing in. Split, Archive's scan tools, Triage, Convert and the Library need you to sign in, and we collect your email address because that is how sign-in works: we email you a link, or, for an account that has a password, you use it. We keep the email address, when you signed in, and the organization you belong to.

The Library (early access). When your organization has a plan, the Library keeps what your organization puts in it, because that is the product: an archive that remembers. Specifically:

• Your organization and its people: the organization's name; each member's email address and role (owner, admin, member or viewer); invitations, each with the invited email address, its role and who sent it, until it is accepted or withdrawn (Sheetsa sends no invitation email; the person who invites sends the link themselves); and when each member last visited the Library.
• Drawing sets and sheets: the files added from Split, Archive, Triage or the Library itself, the per-sheet PDFs made from them (and, beside a sheet's original, a restored copy of a scanned sheet; a sheet's file can also be replaced by its PDF/A version if an owner or admin chose that), what Sheetsa read from them (sheet numbers, titles, dates, revisions, the site and building, and the evidence for each), and the text printed on each sheet and the rows of its schedules, for search.
• Spec books, with each section's PDF and its CSI number and title.
• A building's other files (CAD drawings, building models, photos, reports, contracts and the like), with the name, kind and note your team gives each. Sheetsa keeps these files and never opens them, except photos.
• Site photos are kept as they were taken, with the data the photo itself carries. When a photo is added or first opened in Sheetsa Photos, your browser reads from it when it was taken, where (its GPS location, if the phone recorded one), which way the camera faced and the phone's make and model, and makes two smaller copies for previews; those, and the building and set your team confirms for it, are kept with the photo. A package can leave a photo's location out when it is sent; the stored photo is not changed.
• Corrections your team makes, with who made them and when.
• The activity log: who indexed or attached a set, spec book or file, corrected a value, exported, sent a package, deleted something, changed a retention period or reviewed a flagged record, and whom they invited (the invited address included), with when. It cannot be edited. It is read by your organization's owners and admins, and by Sheetsa's operators.
• Retention settings: the period your organization sets for each kind of record, and each review of a record flagged past its date, with who made it.
• Packages you send and what their recipients did (below), and AI keys with the log of what each was asked (below).
• Your plan: which plan the organization is on and its sheet allowance. Payment is handled by Stripe: your card details stay with Stripe, and Sheetsa keeps only the plan, the allowance and Stripe's references to the customer and subscription.
• If your organization connects SharePoint: which site and library it chose, and when the connection was last checked. Its files then live in its own SharePoint, not with us, and the Microsoft sign-in used for it stays in that browser tab; it is never stored by Sheetsa.

The notify-me box. If you leave your email address in the "get notified" box on the front page, we keep the address, the time, and that it came from that page, so we can send you one email when Sheetsa Archive launches and, now and then, news about it. It goes to the same database as everything above, is not added to any other list, and is not shared. Write to support@sheetsa.com, or reply to any email we send, to be taken off; we delete the row.

Project requests. If you use "Start with one project" on the design review or owners' pages, we keep what you type (your name, work email, organization and the line about your project), when you sent it and which page it came from, so we can write back and set the project up with you. It goes to the same database as everything above, is not added to any other list, and is not shared. Write to support@sheetsa.com to have it deleted.

Email you send us. If you write to support@sheetsa.com we keep the email to answer it.

Server logs. Our hosting providers keep standard request logs (the address a request came from, the page requested, the time) for a short period to run and secure the service. We do not use them to profile anyone.

Questions you ask the archive

The Library can answer a question about your organization's sheets ("Ask the archive"). To do that, Sheetsa reads the text printed on each sheet in your browser when a set is added and stores it for your organization, next to the sheet's index. A question is a search over that text and index inside your organization's own rows in our database, and the answer is composed in your browser from the sheets it found, each cited. No AI company receives your drawings or your questions. Today no language model is involved at all. When one is added it will run in your browser or on servers Sheetsa operates, it will receive only the index rows and text snippets that matched, never a drawing, and this policy will say so before it happens.

An AI of your own, connected to your archive

An owner or admin of your organization can make a key that lets an AI your organization already trusts (for example one running in your own Microsoft tenant, or a workspace under your own agreement with its provider) search your sheet index and the text printed on your sheets through Sheetsa's server. That AI receives only records: sheet numbers, titles, disciplines, revisions, dates, how each was read, and text snippets. It never receives a drawing or a link to one, and never another organization's records. Nothing is connected until you make a key; revoking every key closes the door. Every request is recorded, with what was asked, by which key and when, for your organization's members to see. What that AI's provider does with what it receives is governed by your agreement with them, not by this policy.

Packages you send to others

A member of an organization can send sheets, spec sections and files from the Library to someone by a link ("Send"). The package holds copies of the chosen files, their index, a manifest and a transmittal that records what was sent; it is stored for your organization and opens for anyone who has the link, without an account, until the date you chose (7, 30 or 90 days) or until a member of your organization closes it. The sender chooses whether the link allows printing and downloading as well as viewing; nothing can be edited from it. We keep the package's title and message, the addresses the sender entered, and the sender's email address, which the recipient's page shows with your organization's name. The email itself opens in the sender's own mail program, so we never send it or see it. Before the files show, the recipient gives a name and an email address, and we record that, together with when they opened the package and what they viewed, printed and downloaded, and show it to the sending organization's members. Recipients' names and addresses are kept with that record and used for nothing else. If you received a package and want your name removed from its record, write to the address below.

On the Archive plans, an owner or admin can add the organization's logo (a PNG or JPEG image) and a brand colour. They are kept on the organization's record and shown, with its name, to anyone who opens one of its package links, and on each package's transmittal; they are shown only while the plan includes them, and an owner or admin can change or remove them at any time. So that the next send can suggest them, the Library also keeps a contact list for the sending organization: each address it has sent to, with the name and company the sender typed, when it was last sent to and how often. The organization's members can see the list, and members who can edit can change or remove an entry; nothing in it is sent anywhere, and it goes with the organization.

2. What we do not do

• We do not sell, rent or share your data with anyone for their own purposes.
• We do not use your files, or what Sheetsa reads from them, to train any model or to improve the product for other customers, unless you have expressly agreed to that in writing. The one exception is corrections shared from the "share my corrections" box in Split and Archive's scan tools, for a set not saved to the Library, which we use to fix the reading engine; it starts ticked and you can untick it (what is sent). Nothing is ever shared from the Library.
• We do not run advertising or third-party analytics or tracking scripts on this site. The usage report described above is ours, and stays with us.
• We do not read your files except to run the service, to fix a problem you have reported, or where the law requires it.

3. Where data is stored, and who processes it

The Library's data, accounts, the usage reports and shared corrections, and the notify-me list live on servers run by Supabase (the database, file storage, sign-in and Sheetsa's few server functions, such as the one your connected AI calls) in the us-east-2 region (Ohio, United States), on Amazon Web Services. The website itself is served by Vercel. Sign-in emails are sent through Supabase's email service. These providers process data on our behalf under their own terms and security programs; they do not get to use your data for themselves.

Two others appear only in particular cases. Microsoft, only when your organization connects its SharePoint library: its files then live in its own Microsoft 365 tenant, under its own agreement with Microsoft, and your browser talks to Microsoft directly. Stripe, only when your organization pays for a plan: card details stay with Stripe, and Sheetsa keeps only the plan and Stripe's references to the customer and subscription. No other provider receives your data. If we add or change a provider, this policy will say so. The security page has a table of what is kept, where, for how long and by whom.

4. Who can see your data

Files and records you put in the Library are visible to the members of your organization (a viewer can read them but change nothing). Beyond them, they reach only: the people you send a package link to, and only what that package holds, while its link is live; an AI your organization connects with a key, and only records, never files; and, if your organization connects SharePoint, whoever your own SharePoint permissions allow. The activity log is read only by your organization's owners and admins, and pending invitations only by them and the invited address. That is enforced in the database, not only in the app: every row is tied to an organization, and the database refuses queries from anyone who is not a member. See Security and data handling for how. We, as the operator, can access data when needed to run the service or to fix a problem you report, and where the law requires. What our operators change for your organization from Sheetsa's console is logged, and your members can read those entries.

5. How long we keep it

For as long as your organization uses the Library, plus a short period afterwards to allow for mistakes. When an owner or admin deletes a set, spec book or file, it is removed from the live system, and the activity log keeps the record that it was deleted; backups taken by our hosting provider expire on their own schedule (currently days, not months). A package's link stops opening on its date, and its files stay until a member of your organization deletes them; the record of what was sent and who opened it stays with your organization. Retention periods your organization sets only flag a record for review; Sheetsa never deletes a record because of its date. When an organization closes its account, we delete its files and records, its activity log included. During early access the Library's features may still change, and if the system ever had to be reset we would give notice first. Usage reports, and any corrections you chose to share, are kept for two years from the day we receive them and then deleted automatically. They contain nothing that identifies you, so there is nothing in them to delete on request; a shared correction you sent by mistake can still be removed, as described above.

6. Your choices and rights

• Access and export. Everything Sheetsa read from your sets can be exported from the Library as JSON and CSV at any time, and any selection of sheets, spec sections and files can be packaged with its index and sent by link.
• Correction. Every value Sheetsa reads can be corrected in the Library; the correction is kept with the record.
• Deletion. An owner or admin can delete a set, spec book or file in the Library. Or write to support@sheetsa.com to have your account, your organization's data, or a specific file removed. We will confirm when it is done.
• Where the law gives you more (for example under the GDPR or the California privacy laws), you have those rights too; write to the same address and we will act on them.

7. Children

Sheetsa is a tool for professional work and is not directed at children. We do not knowingly collect data from anyone under 16.

8. Changes

If this policy changes in a way that matters, we will list it here and update the date at the top. Continuing to use the Library after a change means you accept the updated policy.

• 2026-10-03: an owner or admin can replace a sheet's file in the Library with the PDF/A check's fixed version, or do that for every sheet of a set. The old file is deleted (the file uploaded for the set is kept as uploaded), packages send the new one, and each replacement is logged in the Library's activity. Nothing is replaced unless they ask, and nothing kept in SharePoint is changed (what the Library keeps).
• 2026-10-03: the PDF/A check can now make a fixed copy of a file, and that sends one more usage report: the PDF/A level, which rules it repaired or could not (rule names only), the file's size, how long it took and how it ended. Nothing about the file's contents, name or details (usage reports).
• 2026-10-03: the organization's logo and brand colour, shown on its packages, and the contact list kept from each send are added to packages you send.
• 2026-10-01: changes to this policy are now listed here rather than on the What's new page.
• 2026-09-30: the policy is rewritten to describe the Sheetsa Library as it is today.
• 2026-09-26: sharing corrections from Split and Archive's scan tools is now on by default (it was off). It still starts off in a browser that sends Do Not Track or Global Privacy Control, and the Library never shares. What is sent.
• 2026-09-23: usage reports from the browser tools are added, with every field listed and a switch to turn them off (usage reports). The sections on questions you ask the archive, an AI of your own, and packages you send are added.
• 2026-09-22: this privacy policy is first published.

9. Contact

Questions about privacy, or a request to access or delete your data: support@sheetsa.com.