Privacy and your data
What happens to your designs.
A lens design is somebody's work, sometimes somebody's patent. Here is what we do with yours, said plainly. This is the alpha version of this notice; a version reviewed by an attorney lands before public beta, and it will not quietly say less than this one does.
Our commitments
-
We do not train on your designs.
Your prescriptions, merit functions and analysis runs are not used to train any model, ours or anyone else's. VergenceAI reads your system to answer your question and for nothing else.
-
Your designs do not enter our corpus without your consent.
Vergence ships with a reference corpus used for testing and retrieval. Nothing you create joins it unless you explicitly say so, and if you change your mind afterwards, write to us and we will take it out.
What we store
Your account email address, the designs you save, their version history, any files you upload or export, the jobs you run, and how much VergenceAI usage you have spent. Designs are stored in a database where a row-level policy makes yours reachable only by you.
Error reports, when something breaks. A crash sends us a stack trace and the full URL that was being requested, so a failure reaches us instead of only you. Four separate mechanisms keep your design out of one: we send no variables from the stack frames, no request bodies, no client address and no session cookie, and design values are stripped by name out of the structured parts of the report.
One residual we know about, have measured, and have not closed: when a value is quoted into the text of an error message itself — a radius or a glass name written into the sentence the error is made of — it travels with that message, because there is no field name there to strip. Our own test suite asserts that this is still true, so that it cannot quietly stop being disclosed. We would rather name it than let the weakest of the four mechanisms take credit for a guarantee it cannot give.
Counts of a small, named set of product events, so we can tell what is actually used. Those are sent from our servers and record which of the actions happened. From the browser we also send a pageview each time you open a page. Both are tied to your account: once you sign in, your account identifier becomes the identifier the analytics service knows you by, so a pageview is not anonymous. A pageview carries which page you opened, its address, and the standard information any analytics library collects about a browser — its type and version, operating system, screen size, language, and the page that referred you. There is no session recording, and no automatic capture of what you click.
Who else handles it
These are every company that touches your data on our behalf, what each one does, and what each one can actually see. Each name links to that company's own privacy policy.
| Who | What they do for us | What they can see | Where they run |
|---|---|---|---|
| Supabase | the database, and the sign-in link that gets you into the app | your email address, the designs you save, their version history, your saved files, your jobs, and your VergenceAI usage totals | unconfirmed |
| Railway | runs the API, the background worker and the job queue | everything the API processes while it is running, held in memory rather than stored | US East (Virginia) |
| Anthropic | the model behind VergenceAI | the parts of your design relevant to the question you asked, and only while you are using VergenceAI | United States |
| Sentry | error reports, so a crash reaches us instead of only you | a stack trace and the request URL. No frame variables, no request bodies, no client address and no session cookie, and design values are stripped by name out of the structured parts of an event. One residual: a value quoted into an error message travels with the message | United States |
| PostHog | counts of seven named product events, and a pageview each time you open a page, so we know what is used | your account id, which of seven actions happened, and a pageview each time you open a page in the app: its address and the standard properties any analytics library reads from a browser. Signing in ties the pageviews to your account, so they are not anonymous. No design data — autocapture and session recording are both off, and the same denylist applies | United States |
| Vercel | serves this website and the app's front end | the ordinary request logs any web host keeps | United States |
| Loops | holds the waitlist and sends the invitation when a seat opens | the email address you type into the waitlist form, and nothing else | United States |
What we send to a model
When you use VergenceAI, the parts of your design relevant to your question go to Anthropic to produce a reply. Nothing is sent when you are not using it.
The analysis, tolerancing and optimization engines never call a model at all — they are ordinary deterministic code running on our servers. What VergenceAI can see, and what it can and cannot do with it, is set out in full on our AI page.
Where it runs
Our API, the background worker and the job queue run in US East (Virginia).
We are not yet stating a region for the database, because nobody here has confirmed it from the provider's console — and a commitment nobody verified is the kind of claim this product exists to avoid. It will be stated here once it is checked.
Cookies and other storage
Three things get stored in your browser. A session, so that you stay signed in. Your own interface preferences, so the app looks the way you left it. And an analytics identifier, which PostHog writes so that a series of pageviews reads as one visit rather than as strangers; it is cleared when you sign out.
That last one is the item a consent banner exists for, so here is the reasoning rather than the conclusion on its own. It is first-party product analytics: it tells us which parts of Vergence get used. There is no advertising, no ad network, no cross-site tracking, no session recording, no automatic capture of what you click, and nothing is sold or shared with anyone for advertising.
So we are not asking you to dismiss a banner, and the reason is that list rather than a shortcut around it. If Vergence ever stores something that is advertising or cross-site tracking, this section changes before it ships, and a banner comes with it.
Deleting your data
Ask, and we remove your account and everything attached to it: your designs, their versions, your files, your jobs and your usage records. During the alpha a person does this rather than a button, and it is not slower for that. At the outside it takes 30 days.
Two limits, said plainly rather than left for you to discover. We keep a record that a deletion happened, and when — with both the data it was about and the identity it belonged to taken out of it, so nothing in what survives points back at you. That makes it a deliberately weaker record than it could be: it shows that we do this, and when, rather than proving it about your account in particular.
And we cannot reach into Anthropic and erase what it holds under its own retention policy. What we can tell you is what went there in the first place: only the parts of a design relevant to a question you asked, only while you were asking it, and never for training.
Changes to this notice
We may update this notice. When a change is material we will say so on this page and give notice by email to alpha users before it takes effect, rather than moving the date and hoping nobody reads it.
Getting in touch
A person reads these. Write to ryan@artech-us.com, or find me on linkedin.com/in/ryanmm2002.