Last updated 2026-09-26
What Groundline stores, where it goes, and how to delete it
Short version: Groundline keeps your email address, the documents you upload, and the questions and answers from your account. Document text is sent to external models to answer questions. Deleting your account removes all of it immediately.
What is collected
- Your email address - the only account identifier. There is no password, no profile and no tracking of you across other sites.
- Documents you upload - stored as extracted text, split into fragments, each with a numeric representation of its meaning used for search.
- Your questions and answers - kept as history and as cache entries, so a repeated question can be answered without paying for it again.
- Technical records - timing and token counts per request, the IP address of login-code requests (to rate-limit abuse), and server logs.
Where it is stored
In a single Postgres database hosted by Supabase in the EU. Every row is tied to an account, and the database itself enforces that one account cannot read another’s rows - not just the application code.
Which services receive what
| Service | What it receives |
|---|---|
| Render | Runs the backend, so every request passes through it: your questions, your uploads and your email address. Its logs keep the technical records above. |
| Vercel | Serves the pages, so it sees the IP address and browser of every visit. No document text and no email address. |
| Groq | Your question and the document fragments chosen to answer it. Used to write the answer. |
| OpenRouter and TypeSafe | Your question, the document fragments chosen to answer it, the answer, and the earlier question a cached answer belongs to. OpenRouter passes them to TypeSafe’s Jev model, which checks whether the fragments are enough to answer, whether a cached question asks the same thing, and whether the sources back the answer. Jev returns probabilities, not text. |
| DeepInfra | The text of your document fragments and of your questions. Used to turn text into the vectors that make search work. |
| Pinecone | Your question and the candidate fragments. Used to rank which fragments actually answer it. |
| LangFuse | A trace of each request: the question, the answer and the fragments used, for debugging and cost analysis. |
| Resend | Your email address and the six-digit login code. |
| Cloudflare Turnstile | A challenge token and your IP address, to keep bots from requesting login codes. |
| Upstash | Counters only - how many login codes an IP requested, how many streams an account holds. No document text. |
| Vercel Analytics and Speed Insights | Page views and page-load timings, aggregated. Cookieless, no identifier that follows you to other sites, no document text and no email address. |
Running Groundline yourself with local models keeps document text inside your own infrastructure; the hosted demo does not.
How long it is kept
Documents, history and cached answers stay until you delete them or delete your account. Login codes expire after 10 minutes, and the record of a code request (address and IP) is deleted after seven days. Sessions last seven days; logging out ends every session of the account. LangFuse keeps traces for 30 days on its free plan.
How to delete it
The Documents screen has two buttons: one clears documents, cache and history; the other deletes the account entirely. Deletion is immediate and cascades to every table - there is no soft delete and no recovery. The same is available over the API as DELETE /me.
What is not done
- No advertising and no third-party trackers - the landing page and the app measure page views and load times through Vercel, which sets no cookies and builds no cross-site profile. Nothing else is loaded.
- No selling or sharing - data goes only to the services listed above, and only to answer your questions.
- No training on your documents - the providers are used through their APIs; check their own terms for their retention policies.
Contact
Data controller: Anton Minin Baranovskii (a private individual). Enquiries about personal data: hi@antonmb.com.
Write if you want to talk about the product, an engineering problem, a consultation or working together. Open to conversations about the book as well: interviews, publications, talks.