Citerra · on writingSubprocessors
Citerra markCiterra
productpricingupdates
FAQssecurity
contact
EnglishDeutsch
sign injoin the waitlist
productpricingupdatescontact
sign in
resources
FAQssecurity
Language
EnglishDeutsch

Last updated12 September 2026

Subprocessors

The register lists Citerra's providers, the data each receives and where it operates. Later sections explain what providers do not receive, custom model endpoints and changes to the register. A final section names the governing language.

On this page

  1. § 1Current subprocessors
  2. § 2What they do not receive
  3. § 3Your own model endpoint
  4. § 4Changes to this list
  5. § 5Governing language

Questions about a providersecurity@citerra.de

§ 1

Current subprocessors

Each provider below handles one slice of the data, and nothing beyond it. For a provider outside the EU, the last column also says whether the Standard Contractual Clauses of the European Commission (SCCs) are in force.

ProviderWhat it receivesWhere
ConvexApplication database and generated artifacts.EU (Ireland)
ResendEmail addresses on the waitlist and the newsletter, and the content of the messages Citerra sends to them. Also the copy of each contact form request sent to Citerra's own inbox.EU (Ireland) for delivery. Provider is US-based, SCCs in force.
ClerkSign-in identity: email address, name, and organization membership.United States. SCCs in force.
UploadThingUploaded PDF and image files.United States. No SCCs in force yet.
Fly.ioLaTeX sources during compilation, deleted after each job.EU (Frankfurt)
OpenAIText excerpts sent for AI assistance and search indexing. The provider's API terms exclude this content from training.United States. SCCs not yet signed.
VercelRequests to citerra.de and the application, and their server logs.Global edge, EU region for server rendering. SCCs in force.
SentryError reports with personal data removed.EU

§ 2

What they do not receive

No provider on this list receives your library in full. When the assistant answers a question, Citerra sends only the passages relevant to that question to the model provider. The rest of the document stays in Citerra.

Citerra queries public indexes: OpenAlex, arXiv, Europe PMC, Crossref, Semantic Scholar and Unpaywall. Searching the literature sends OpenAlex, arXiv, Europe PMC and Semantic Scholar the search terms. Importing or resolving a source sends Crossref, Semantic Scholar and Unpaywall that DOI or title. The assistant's web search sends Brave Search the terms it looks up. All of them are hosted in the United States, except Europe PMC in the United Kingdom. These receive the query, never the document. They are public indexes rather than subprocessors, because they process no personal data on Citerra's behalf.

§ 3

Your own model endpoint

An organization can point Citerra at its own model endpoint, in which case the assistant's answers are generated there instead of at OpenAI. Indexing a source and retrieving from it still reach OpenAI.

The API key for that endpoint is stored in Convex, readable only through an internal function, sent only to your own endpoint, and never logged. Deleting the override deletes the key.

§ 4

Changes to this list

Citerra updates this register when an integration is added or removed. Organizations with a data processing agreement in place are notified before a new subprocessor begins processing.

§ 5

Governing language

This register is published in English and in German, and both versions list the same providers.

The English version governs until counsel has reviewed both texts. Where the two differ before that review, the English wording applies.

Citerra markCiterra
Everything the paper needs.
resourcesproductpricingupdatesFAQs
companyaboutcontactsecuritystatus
toolsCiterra for web
legalimpressumtermsprivacysubprocessorscookiesdata processingopen source
communityXLinkedInInstagramDiscord
  • GDPR
  • EU hosted
  • No model training
  • Export anytime
  • English
  • Deutsch
© 2026 Citerra · made for academic writing