Legal
Last updated: 28 October 2026
StirpeAI is developed under the Geyserich name. The legal operator, registration identifiers and public registered-office address have not yet been verified for publication. We will publish those details after verification. Do not submit confidential institutional documents or enter an institutional data-processing agreement until the operator and applicable data terms have been confirmed.
Questions, or to exercise any right below: [email protected].
You upload photographs or scans of historical documents. We use artificial intelligence to transcribe, translate and interpret them, and to extract the people, places, dates and relationships they record. Those extractions build into a research graph across everything you have uploaded.
Your account.Your email address, and your name and profile picture if you sign in with Google. Anything you add to your profile: display name, country, research focus, biography. If you enable two-factor authentication, an encrypted secret. If you add a passkey (Face ID, Touch ID, Windows Hello, or a security key), the public key it creates and a device name you choose — never a fingerprint, face scan, PIN, or any other biometric data, which never leaves your own device. If you set a password, a one-way cryptographic hash of it — we cannot read or recover your actual password, and check it against a public breached-password list before accepting it so you can’t set one already known to be compromised. Whether your email address has been verified. A log of significant actions on your account, with your IP address anonymised — we discard the final part of it before storing.
Your documents. The files you upload, and everything our analysis produces from them: transcriptions, translations, historical context, and the names, dates, places, relationships, occupations, social status, religious details and titles recorded in the document.
What you tell us. Corrections you submit, research notes, and messages you send us.
We do not collect payment information. We do not use advertising or tracking cookies.
| What we do | Why | Legal basis |
|---|---|---|
| Run your account and analyse your documents | To provide the service you signed up for | Performance of our contract with you |
| Keep security logs, apply rate limits, offer 2FA | To protect accounts and prevent abuse | Our legitimate interests |
| Retain transcriptions and extractions in a research corpus | To improve transcription of European archival handwriting — see below | Separate documented permission and the applicable basis for that agreed research use |
| Handle information in documents revealing religious belief or ethnicity | This is inherent in parish and colonial records | Article 9(2)(j) — archiving and historical research, with the safeguards Luxembourg law requires |
This part matters, so we state it plainly.
Document analysis does not automatically authorize a separate training or research use. Training capture, annotation and corpus exports require an explicit, recorded permission for the account. This permission is separate from processing your document to provide the analysis you requested.
Retention after account deletion is not automatic. It requires separate documented permission. Even with that permission, records must satisfy the historical-person safeguards described below. An expired or absent permission does not authorize retaining your historical analysis merely by removing your identity.
We do not sell this dataset, and we do not share it with third parties.
StirpeAI is for historical documents. Our Terms ask you not to upload documents about living people. If a document you upload does name a living person, we handle it under the historical-research provisions described above. Any living person named in our corpus can contact us at [email protected] to exercise their rights.
The service integrates the providers below. Deployment locations, applicable processing contracts and transfer arrangements still require verification for this service; this list does not establish that those checks have been completed.
| Provider | What for | Location evidence |
|---|---|---|
| Anthropic | AI analysis of your documents | Processing locations not yet verified |
| Supabase | Database and file storage | Database and storage region not yet verified |
| Vercel | Hosting | Processing locations not yet verified |
| Resend | Sign-in links and emails | Processing locations not yet verified |
| Cloudflare | Domain routing | Routing locations not yet verified |
| Sign-in, if you use it | Processing locations not yet verified | |
| OpenStreetMap | Turning place names into map coordinates — place names only | Endpoint location not yet verified |
The current list is always at stirpe.ai/subprocessors.
We have not yet verified the deployment-specific transfer arrangements. Before an institutional pilot, confirm the actual processing locations, applicable provider terms and any required transfer safeguards; do not infer them from a provider’s address.
We never sell your data, share it with advertisers, or disclose it to anyone else unless we are legally required to.
By default, your research is yours. Other users cannot see your documents, your analyses or your graph.
Two things are optional and off unless you turn them on:
Our administrator can access data in the course of operating and supporting the service. Administrator access is logged.
| Account details | While your account is open, and 30 days after you ask us to delete it |
| Uploaded files | Deleted when you delete your account |
| Transcriptions and extractions | Kept while your account exists. After you delete your account, kept only as described under “When you delete your account”; otherwise deleted. |
| Security logs | 12 months |
When you delete your account. We delete your account, your profile and your email address when the scheduled purge completes. Without separate retention permission, your attributed historical analyses and derived corpus records are selected for deletion as well. Where retention was separately authorized, a person record is kept only when the historical-person safeguards permit it; a transcription is kept only when every linked person passes those safeguards. Security and operator audit records have separate retention duties. We do not describe removing attribution as proof that all document content has been erased.
You can ask us to: give you a copy of your data; correct it; delete it; restrict or object to how we use it; or provide it in a portable format. You can withdraw consent at any time where we rely on it.
Write to [email protected]. We reply within one month.
Removing training or research permission stops future reuse under that permission; it does not itself execute deletion of copies already held. Contact us to arrange erasure and confirm the treatment of any earlier retained records or exported copies. We will explain any applicable retention duties and limitations rather than promise deletion that has not been verified.
If you are unhappy with how we handle your data, you can complain to the Commission nationale pour la protection des données (CNPD), 15 Boulevard du Jazz, L-4370 Belvaux, Luxembourg — cnpd.public.lu.
Encryption in transit and at rest. Uploaded files held in private storage. Optional two-factor authentication and passkey sign-in. Uploads validated against their actual file contents. Rate limiting. Access logging. No system is perfectly secure; if a breach affects you and poses a high risk, we will tell you.
Only what the service needs to work — keeping you signed in, and remembering your cookie choices. Analytics run only if you agree.
We will post any change here and, if it is significant, email you.
Questions? [email protected] · Terms of Service · Subprocessors