Privacy Policy
Last updated: November 16, 2026
1. Who this applies to
This Privacy Policy explains how Schema, operated by Edmon Jeiranian, collects and uses personal data when you use buildschema.app (the "Service"). It applies to everyone who visits the site or creates an account - and it's written to meet GDPR's requirements for anyone using the Service from the EU/UK, regardless of where you're located.
2. What we collect
- Account data. When you sign up, our authentication provider (Clerk) collects your email address and name, and issues the session that keeps you signed in. We receive your verified identity from Clerk; we don't separately collect or store your password.
- Diagram content. The diagrams you create - names, nodes, connections, and any text you put in them - including the earlier versions kept in a diagram's version history. Content is encrypted before it's stored (see Section 7) and only decrypted for you, for others you've shared an organization's diagrams with, or for someone opening a share link you created.
- Share links. If you create a read-only share link for a diagram, we store which diagram and view it covers, when it expires, and how many times and when it was last opened. We don't identify or track the people who open it.
- Security & activity logs. Who created, viewed, updated, or deleted a diagram and when; attempts to access a diagram without permission; and client-side errors (e.g. a failed save). These exist to secure the Service and diagnose problems, not to profile your behavior.
- Bug reports. If you send one from the app's "Report bug" button: what you wrote, technical details about your browser and editor (browser version, window size, settings, how large the diagram is, and recent error messages), and - unless you untick them before sending - a screenshot of the app and a copy of the diagram you had open. The screenshot and the diagram copy are encrypted the same way your saved diagrams are (see Section 7).
- Page-view statistics. When you open a page we count the visit using Vercel Web Analytics: the page's path (never the part of a share link that holds its secret), the referring site, your country, and your browser, operating system and device type. It sets no cookies and doesn't identify you or follow you across sites; visitors are counted using a hash that is discarded after 24 hours. We use it only to see how many people visit and which pages they use.
- Waitlist email. The homepage used to have a waitlist form (it no longer does). If you joined it, your email address was collected through a third-party form service (Formspree) so we could notify you about product updates.
Files you import (an asset spreadsheet, an Nmap scan) are read by your browser and are not uploaded; only the diagram you then choose to save reaches us. Diagrams you save as files on your own device never reach us at all.
We don't collect payment card details today - see Section 9.
3. Why we process it, and our legal basis
- To provide the Service (store and render your diagrams, keep you signed in, run the rule engine you configured) - basis: performance of our contract with you (GDPR Art. 6(1)(b)).
- To keep the Service secure (audit logs, denied-access logs, error logs) - basis: our legitimate interest in protecting the Service and your data from misuse (GDPR Art. 6(1)(f)).
- To fix problems you report (bug reports you choose to send) - basis: our legitimate interest in finding and fixing faults in the Service (GDPR Art. 6(1)(f)).
- To understand how the site is used (anonymous page-view statistics) - basis: our legitimate interest in knowing which pages people use so we can improve them (GDPR Art. 6(1)(f)).
- To send you product updates if you joined the earlier waitlist - basis: your consent, given when you submitted your email; you can withdraw it anytime by unsubscribing or emailing us.
4. Who we share it with
We don't sell your data. We share it only with the service providers ("sub-processors") that help us run Schema, each only for the purpose below:
- Clerk - authentication and account identity.
- Convex - stores your diagrams (encrypted), the logs described in Section 2, and any bug reports you send.
- Vercel - hosts the website and app, and provides the page-view statistics described in Section 2.
- Formspree - holds email addresses submitted to the earlier homepage waitlist.
These providers are based in the United States, so using the Service involves transferring data outside the EU/UK/EEA. Each of them publishes its own GDPR commitments and offers Standard Contractual Clauses or an equivalent transfer safeguard for exactly this situation. Contact us if you'd like details on the safeguard a specific provider uses.
We'll also disclose data if required by law, or to investigate a security incident affecting the Service.
5. How long we keep it
- Your diagrams: until you delete them, or your account.
- Version history: up to 50 earlier versions per diagram, removed when the diagram is deleted.
- Share links: until you turn them off, they expire, or the diagram is deleted; a record that a link existed is removed 30 days after it stops working.
- Security/activity logs: kept for up to 12 months, then deleted automatically on a rolling basis. Client error reports are kept for up to 90 days.
- Bug reports you send, including any screenshot or diagram copy attached: up to 90 days, then deleted automatically.
- Waitlist email: until you unsubscribe or ask us to remove it.
6. Your rights
If data protection law (such as GDPR) gives you these rights, you can ask us to:
- Give you a copy of the personal data we hold about you (access);
- Correct inaccurate data (rectification);
- Delete your account and associated data (erasure);
- Give you your diagram data in a portable format (portability);
- Stop or limit certain processing (restriction/objection);
- Withdraw consent, for anything based on consent (e.g. waitlist emails).
To exercise any of these, email admin@buildschema.app. We'll respond within 30 days. You can also do the most common ones yourself, without waiting on us: in the app, File → Your data & account exports every diagram in your account as one file, and permanently deletes everything stored in your account (diagrams, their version history and share links, your activity log, and any bug reports you've sent). Records of blocked access attempts are kept for their normal retention period, as part of keeping the Service secure. If you're in the EU/UK, you also have the right to complain to your local data protection authority.
7. How we protect your data
Diagram content is encrypted at rest (AES-256-GCM) before it's written to the database - the decryption key is never stored alongside the data itself. Access to diagrams is checked on every request against who owns them or which organization they're shared with; denied and unauthenticated attempts are logged. A share link's secret is stored only as a one-way hash. See our security overview for the details. This describes encryption in transit/at rest within our infrastructure, not end-to-end encryption - we are technically able to access diagram content if needed (e.g. to investigate abuse or respond to a valid legal request).
8. Cookies
We use only the session cookies our authentication provider (Clerk) sets to keep you signed in - these are strictly necessary for the Service to work and aren't used for advertising or cross-site tracking. We don't use analytics or advertising cookies: the page-view statistics in Section 2 work without any cookie, and the site loads no third-party trackers, fonts or scripts beyond what sign-in requires. The editor also keeps a few display preferences (such as whether the minimap is shown) in your browser's local storage; these stay on your device and aren't sent to us. If that changes, we'll update this section and add a cookie-consent banner before any non-essential cookie is set.
9. Payment data (future)
The Service doesn't process payments today. When paid plans launch, billing will be handled by a third-party payment processor (e.g. Stripe) - your card details will go directly to them, not to us, and will be covered by their own privacy policy. We'll update this section with specifics before that launches.
10. Children's privacy
The Service isn't directed at children, and you must be at least 16 to use it (see our Terms of Service). We don't knowingly collect personal data from anyone under 16.
11. Changes to this policy
We may update this policy as the Service changes. We'll post the update here with a new "Last updated" date, and let you know in-app or by email if the change is material.
12. Contact
Questions, or want to exercise a right from Section 6? Email admin@buildschema.app.