Privacy policy
How Q19 processes personal data: on this website, in your account, in Ask Q19, for payments and emails, and in cookies and device storage.
This English text is provided for convenience. If it differs from the German version, the German version prevails.
1. Who is responsible, and how to contact us
Loading the operator's details…
Seller information (Impressum)The controller responsible for the processing described in this policy (Art. 4(7) GDPR) is the operator of Q19 named above. The same details appear on the seller information page (Impressum).
For questions about your data or to exercise your rights, contact support@q19.ai.
Privacy contact: Privacy requests are handled by the operator at support@q19.ai; no separate data protection officer contact is published.
2. Overview
Q19 is a website for studying the Qur'an: a reader, search, subject pages, a research canvas, a Research Hub, and Ask Q19, which writes answers with AI models from Q19's library and index. Without an account you can see Q19's public pages and a short demo; the platform itself needs a free account, and some features need a paid plan.
This policy covers these kinds of personal data:
- Connection data: IP address, browser and device details, time and requested address.
- Account data: email address, password hash or sign-in provider identity, display name, settings and plan.
- Research data: bookmarks, notes, annotations, collections, canvases, reading history and Ask Q19 conversations.
- Usage and billing data: AI usage counts and costs, subscription status and Stripe references.
- Communication data: emails Q19 sends you, and withdrawal or cancellation declarations you submit.
- Device storage: cookies and browser storage, described in section 13.
3. Hosting and server logs
Q19 runs on a server rented from netcup GmbH, Karlsruhe, Germany, on a European hosting plan. The precise data-centre country has not yet been independently verified. The databases that hold accounts, research and temporary data run on that server and are not reachable from the internet; only Q19's web server accepts connections. The hosting provider processes data on Q19's behalf under a data processing agreement (Art. 28 GDPR).
For each request, Q19's server records only the time, the method (for example GET), the general route that was called (for example /api/v1/verses/:id, not which verse), the response status and how long it took. It does not record your IP address, your search terms or any other part of the address after "?", or what you send. Q19's web server (reverse proxy) keeps no access log. Q19 also records technical errors, and in some events your account id (for example when a password reset or an email confirmation is completed, or when a digest is sent).
If Q19's safety filter removes text that looks like an attempt to manipulate the AI from a question to Ask Q19, only the kind of text removed and the length are logged, never the question.
Purpose and legal basis: running Q19 securely, finding and fixing errors, and detecting attacks. This is Q19's legitimate interest (Art. 6(1)(f) GDPR). You can object to it (section 19).
Retention of server logs: 7 days at the latest.
4. Your account
You need an account to use the Q19 platform (the reader, search, research tools and Ask Q19). Q19's public pages and the demo work without one.
Registration with email and password
Q19 stores your email address, your password as a bcrypt hash (never the password itself; at least 12 characters), a display name (by default the part of your email address before the @, which you can change), default language and display settings, your plan (Reader at first), whether your email address is confirmed, and the date you registered. If you came through an invitation link, Q19 also stores who invited you (section 10).
The interface language you use when signing up only chooses the language of the confirmation email; it is not stored.
Legal basis: providing the account you ask for (Art. 6(1)(b) GDPR). An email address and a password, or a sign-in provider, are required; without them Q19 cannot create an account.
Signing in and staying signed in
When you sign in, Q19 issues a short-lived access token (15 minutes) and a refresh_token cookie that keeps you signed in on this device for up to 7 days. Your browser keeps the access token and your profile (including your email address and plan) in the q19-auth storage entry until you sign out.
For each signed-in device Q19 stores a session record: a hash of the refresh token, when it was created, when it expires, and when it was ended. Signing out ends the session. A session record is deleted 30 days after it expires or is ended.
Legal basis: Art. 6(1)(b) GDPR, and Q19's legitimate interest in secure sign-in (Art. 6(1)(f) GDPR).
Signing in with Google, Microsoft or Apple
If you choose a sign-in provider, your browser goes to that provider. The provider receives your IP address and browser details and processes your sign-in under its own privacy policy, as a separate controller. Q19 never receives your provider password. Provider tokens are exchanged and checked on the server during sign-in; Q19 does not retain the provider access token or request access to your mail, files or contacts. A short-lived security code is kept on Q19's server for 10 minutes while you sign in, together with the inviter's code if you came through an invitation link (section 10).
What Q19 receives and stores:
- Google: your Google account id, email address, whether Google has verified it, your name, and the address of your Google profile picture. Q19 stores the picture address but does not display it.
- Microsoft: your Microsoft account and organisation ids, email address and name. Q19 treats the email address as confirmed only when Microsoft states it is verified; otherwise it sends you a confirmation email.
- Apple: your Apple account id and email address (which may be an Apple relay address). Q19 does not read the name Apple offers, so your display name is the part of your email address before the @.
If you sign in with Google using a Gmail or Google Workspace address that already has a Q19 password account, the two are linked: the password is removed (you can set one again through a password reset) and any API keys are revoked.
Legal basis: Art. 6(1)(b) GDPR.
Age confirmation and your research-data choices
When you create an account you must confirm that you are 16 or older. Q19 stores the time of this confirmation. If you sign up with Google, Microsoft or Apple, Q19 asks for this confirmation on a one-time screen at your first sign-in.
Q19 also stores your choices about research data (section 5): whether and when you gave consent, the version of the consent text, and your reading-history and chat-history settings. These records are kept as long as your account exists, are included in your data download, and are deleted with the account.
Legal basis: providing the account, which is for people aged 16 or older (Art. 6(1)(b) GDPR), and Q19's legal duty to be able to demonstrate your consent (Art. 6(1)(c) GDPR with Art. 7(1) GDPR).
Email confirmation
After you register, Q19 emails you a confirmation link. The link carries your account id, an expiry time and a signature, but not your email address, and it is valid for 24 hours. It is not stored. You can ask for a new link up to 3 times an hour. Confirming your address unlocks the free AI answers of the Reader plan.
Legal basis: Art. 6(1)(b) GDPR (proving that the address is yours before AI answers are unlocked).
Password reset
Anyone can ask for a reset link for an email address; the reply is the same whether or not an account exists, and each IP address can ask 5 times a minute. Q19 stores only a hash of the reset code and its expiry. The link is valid for 1 hour; an unused code is deleted 7 days after the link expired. When you set a new password, every session and every API key of the account is ended and the email address is marked as confirmed.
Legal basis: Art. 6(1)(b) GDPR, and Q19's legitimate interest in protecting accounts (Art. 6(1)(f) GDPR).
Profile and settings
Q19 stores your display name, reading persona, interface and content language, script and text settings, Simple or Deep mode, and whether you subscribed to the weekly digest, so that they follow you across devices. Legal basis: Art. 6(1)(b) GDPR.
Downloading and deleting your data
In Account › Your data you can download your profile, saved research, conversations, reading history, subscriptions and AI usage as a JSON file. Q19 prepares it in a temporary file that is deleted as soon as the download is sent.
In Account › Delete account you can delete your account. Your account and the data linked to it in Q19's database are deleted immediately, and any active subscription is cancelled. Data kept in your browser (section 13) is not erased by this; you can delete it in your browser settings. What remains for a limited time, and why, is listed in section 18.
5. Saved research, reading history and conversations
If you have given your explicit consent (see the box below), Q19 keeps in your account:
- Bookmarks (verse, tags, your note), annotations (verse, your text, tags, colour), collections (name, colour, description), research notes (title, your text, verse reference, pinned) and canvases (name, the verses and links on it, whether it is shared), each with the time it was created or changed. You can delete each of them yourself, or all of them at once in Account › Privacy.
- Reading history: each time a verse stays in view for about 1.5 seconds, Q19 records the surah and verse and the time. It powers Continue reading and the history in the Research Hub. Reading history is recorded only if you have given consent and reading history is switched on in Account › Privacy. It is on by default once you consent, you can switch it off at any time, and you can delete it in Account › Privacy.
- Ask Q19 conversations are saved to your account only if you have given consent and chat history is switched on (on by default once you consent; you can switch it off in Account › Privacy). A saved conversation has a title (the first 60 characters of your first question), the verse it refers to if any, every question and answer, and details of each answer such as its sources and the model that wrote it. You can delete a conversation in Ask Q19. Answers work either way.
Without consent you can still read, search, study subjects, use the analysis tools and ask Q19, and you can save bookmarks, notes, collections and canvases on your device. Q19's server then stores none of this research data, and Ask Q19 conversations are answered but not saved.
If you share a canvas, other signed-in members whose plan includes canvas sharing can open it through its link. Your name and account id are not shown with it.
Some of your work is also kept in your browser (section 13).
6. Ask Q19 and other AI features
Ask Q19 is available to signed-in members whose plan includes AI answers; on the free Reader plan your email address must be confirmed first. Answers are written by an AI model, can be wrong, and are labelled with the model that wrote them.
What is sent, and to whom
When you ask a question, Q19 searches its library and sends the AI provider: your question, the earlier messages of the conversation (up to 20 messages), and the Qur'an verses, source passages and facts Q19 retrieved for it. Q19 does not send your name, email address, account id or IP address; the provider sees only Q19's server.
- Standard answers: Together AI (Together Computer, Inc., United States (Together AI)), model DeepSeek V4 Pro.
- Deeper answers, only when you choose Deeper: Anthropic (Anthropic Ireland, Limited, Ireland), model Claude Sonnet 4.6.
- Finding related passages: the text of your question, or of a meaning-based search, is sent to OpenAI (OpenAI Ireland Ltd., Ireland), which turns it into a numerical representation (an embedding). No identifiers are sent with it.
Other AI features, such as explanations of a connection or a summary of a canvas, are built from Q19's own data (verse text, roots, cross-references and the verses you put on a canvas). They contain no text you typed and no identifiers, and are sent to Together AI, or to Anthropic if Together AI does not respond.
Please do not put personal details about yourself or other people into questions.
What the providers keep
As Q19's processors, the providers may process the text only on Q19's instructions (Art. 28 GDPR). What they keep beyond that, for example for abuse monitoring, and for how long:
- Together AI: Storage of prompts and responses and use for training were disabled at the account check on 3 October 2026. Q19 does not claim a separately verified zero-retention agreement for every model route.
- Anthropic: API inputs and outputs are normally deleted within 30 days. Suspected policy violations may be kept for up to 2 years, with safety classification scores for up to 7 years; legal requirements can also extend retention. No zero-retention agreement is claimed.
- OpenAI: Embeddings have no stored application state. Abuse-monitoring logs may include submitted text for up to 30 days, or longer when required by law or needed to protect services or third parties. API data is not used for training unless the customer opts in; disabling request logging is not a zero-retention agreement.
They are in the USA; the safeguards for these transfers are listed in sections 16 and 17.
What Q19 keeps
Your conversations are saved only as described in section 5 (with your consent and while chat history is on). An answer is also kept for 1 hour in a temporary cache that is not linked to your account, so that an identical conversation, from anyone, gets the same answer without a new paid call. Search results are cached for 10 to 30 minutes under the search text, without any account link.
For every AI call Q19 records your account id, a request id, the time, the feature, the model and provider, the number of tokens, the cost and the duration, but never the text; for each Ask Q19 answer it also records the time, whether it was Standard or Deeper, and whether it was delivered or refunded to your allowance. Q19 uses these records to apply your plan's answer allowance and spending limits, and for cost accounting. Per-call records are kept for 12 full calendar months; afterwards only monthly totals per feature, model and provider are kept, without any link to an account or request. When you delete your account, the answer records are deleted and your account id and the request id are removed from the call records at once; each call's time, feature, model, token count and cost remain for cost accounting until they are added to the monthly totals.
Legal basis: Art. 6(1)(b) GDPR (the service you request). Questions revealing personal beliefs or other sensitive information require additional protection under Art. 9 GDPR. Q19 does not treat a request for an answer as explicit consent to process sensitive personal information. QI is intended for research about the text: do not include personal religious beliefs, health information or other sensitive details about yourself or other people in a question. Saving the conversation in your account needs your consent as described in section 5. The usage records also serve Q19's legitimate interest in controlling costs and preventing misuse (Art. 6(1)(f) GDPR).
7. Payments
Paid plans are sold through Stripe Checkout and managed in Stripe's billing portal. Q19 sends Stripe your email address and your Q19 account id as a reference. On Stripe's page you enter your payment method, your name and a billing address (required), and a tax ID if you wish. Q19 never receives your card or bank details.
Q19 stores your Stripe customer id, your subscription (id, plan, status, current period, cancellation), and each checkout you start (its id, the price and Stripe's session id, with the time). Stripe tells Q19 when a subscription changes, and Q19 then reads its current state from Stripe. Q19 keeps the id and type of each such notification for 90 days, so that it processes each one only once.
Stripe: Stripe Payments Europe, Limited and Stripe Technology Europe, Limited, Ireland. Stripe processes payment data on Q19's behalf to provide the payment service. For fraud prevention, anti-money-laundering and identity checks and its own billing, Stripe acts as an independent controller under its own privacy policy. Stripe keeps invoices and payment records as tax and commercial law require.
Legal basis: performing your subscription contract (Art. 6(1)(b) GDPR) and Q19's legal duties to keep invoices and accounting records (Art. 6(1)(c) GDPR with § 147 AO and § 14b UStG and, where Q19 is a merchant (Kaufmann), § 257 HGB).
8. Emails
Q19 sends emails through Resend (Plus Five Five, Inc., San Francisco, USA), which receives the recipient address and the content of each email as Q19's processor. Q19 sends:
- Account emails: the confirmation link and password reset links (section 4). Legal basis: Art. 6(1)(b) GDPR.
- Receipts and outcome notices for withdrawal and cancellation declarations, to the address you give in the form (section 9). Legal basis: Art. 6(1)(c) GDPR.
- The weekly digest, only if you switch it on in Account and your email address is confirmed. It contains a featured verse, how many bookmarks you have (not which verses) and the newest topic. Every digest has an unsubscribe link, which does not expire; you can also switch it off in Account. The unsubscribe page does not show your address. Q19's operator can send a single test digest to check how the email looks, but only to the operator's own address or to an account that has switched the digest on and confirmed its email address. When a digest is sent or you unsubscribe, Q19's server log records only your account id, not your email address; these entries are deleted after 7 days at the latest (section 3). Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time.
- Operational alerts to Q19's operator, which contain no visitor data.
Q19 does not send newsletters or advertising other than the weekly digest you choose.
9. Withdrawal and cancellation declarations
The withdrawal form (/v3/withdrawal) and the cancellation form (/v3/cancel-subscription) work without signing in. Q19 stores what you enter (name, email address, contract reference, type of cancellation, requested end date and reasons where needed), your language, the time it was received, a fingerprint (hash) of the declaration and the receipt text, which repeats these details. The receipt is emailed to the address you give; Q19 retries the delivery if it fails. When Q19 has processed your declaration, it records the outcome, the time and the person who handled it, and emails you the outcome.
To prevent misuse, at most 3 receipts a day are emailed to the same address automatically (counted under a keyed hash of the address, not the address itself); further receipts, and receipts above an overall hourly limit, are held until Q19 has checked them. Each IP address can submit 10 forms an hour.
These records are not linked to your account and are kept after an account is deleted, because they prove your declaration. Legal basis: Art. 6(1)(c) GDPR with §§ 312k and 356a BGB, and the establishment or defence of legal claims (Art. 6(1)(f) and 17(3)(e) GDPR). Retention: 3 years from the end of the year in which Q19 received them (the limitation period, §§ 195, 199 BGB), together with the emails sent about them; longer only while a declaration is still being handled or an email about it has not been sent.
10. Invitations (referrals)
Members can share a personal invitation link. Opening one sets no cookie and stores nothing on your device: the link opens the registration page with the inviter's code in the web address, and the page removes the code from the address bar straight away, so it is not passed to analytics. If you then create an account, with email and password or with Google, Apple or Microsoft, Q19 records who invited you. When you use Google, Apple or Microsoft, the code is kept only on Q19's server during that sign-in (at most 10 minutes) and is not sent to the provider.
The inviter sees only how many people created an account through their link, and only once at least 3 have; never who they are, which plan they have or whether they pay. Q19's operator sees inviters' email addresses and how many of the people they invited have a paid plan, and grants rewards (a free month of the Study plan for every 3 invited people with a paid plan) by hand as Stripe discount codes sent by email. A reward therefore tells the inviter that at least 3 of the people they invited pay for Q19; if exactly that many joined through the link, the inviter can infer that each of them pays.
If the inviter deletes their account, the link to them is removed. Legal basis: Q19's legitimate interest in crediting the member who invited you (Art. 6(1)(f) GDPR). Q19 sets no cookie for invitations.
11. API keys
API access is not part of any current plan. If you have an API key, Q19 stores its name, a hash of the key, its first 12 characters, when it was created and last used, and when it was revoked. The key itself is shown only once. Revoked keys stay listed until your account is deleted. A password reset, or linking a Google sign-in, revokes all keys. Legal basis: Art. 6(1)(b) and (f) GDPR.
12. Security and abuse protection
Q19 uses encrypted connections (TLS). Passwords are stored only as bcrypt hashes; refresh tokens, reset codes and API keys only as hashes. The sign-in cookie cannot be read by page scripts. The databases are not reachable from the internet.
To protect Q19 against overload, abuse and runaway costs, Q19 counts requests per IP address and, for signed-in members, per account id. Each counter is deleted when its time window ends: 60 seconds for most requests, 1 hour for withdrawal and cancellation forms, account deletion and data downloads. Plan allowance and spending counters per account are kept for up to 40 days and are deleted when you delete your account. These counters are held in a fast data store that is also written to disk.
Q19's operator, and administrators the operator names, can see for support, billing and misuse: the email addresses of the accounts with the highest AI costs, the email addresses of inviters, and cost and quality dashboards. The server operator has technical access to the databases and logs.
Q19 makes nightly backups of its whole database, stores them on the same server and keeps them for up to about 4 months. Data you delete stays in older backups until they are removed in rotation, and is not restored into the live service.
Legal basis: Q19's legitimate interest in a secure, available and affordable service (Art. 6(1)(f) GDPR); the measures also serve Q19's duty to keep data secure under Art. 32 GDPR (Art. 6(1)(c) GDPR). You can object (section 19).
14. Analytics with Google Analytics (optional)
Google Analytics is currently disabled on q19.ai. The following describes the optional analytics functionality, which requires both configuration by Q19 and your consent before it can operate. Google Analytics is not active on the public website; no acceptance of Analytics processing terms is claimed here.
Data: the type of page you visit (the address reduced to its template, for example /v3/read/:surah/:ayah or /v3/subject/:slug, with the page type as title; never which verse, surah, subject, lecture or source), the Q19 features you use and their outcome (for example "search", "verse read" or "added to canvas", with counts, the search mode and whether it worked), device type, browser, screen size, language, the region Google derives from your IP address, the referring website (reduced to its domain), and a random identifier in the _ga cookie. Your IP address is transmitted to Google for this; according to Google, Google Analytics 4 does not store it. Of what you type into a search box, only its writing system (Arabic, Latin, digits), a length range (for example 3 to 5 characters) and the kind of query (for example a verse reference or a root) are sent; never the text itself.
Also sent: your plan (visitor, free, a paid plan, or operator), whether you are signed in, your reading persona, interface and content language and theme, and, when you buy a plan, the plan, billing interval, price, currency and a one-way hash of the payment session (never the payment details).
Never sent: which verses, surahs, roots or words you read or search for, which subjects, topics, scholars, lectures, claims or sources you open, your name, email, user id, questions, notes or any search text. Google signals and ad personalisation are off.
Retention in Google Analytics: Not applicable to the current public website: Google Analytics is disabled and Q19 sends it no analytics events.
Legal basis: your consent, § 25(1) TDDDG and Art. 6(1)(a) GDPR. Q19 sends Google Analytics nothing about which verses, roots, subjects, scholars, lectures or sources you study.
Google LLC (USA) may process this data. Safeguard: No Google Analytics transfer takes place on the current public website. Optional Google sign-in is separate and follows Google’s privacy policy.
15. External content and embeds
Fonts are served from Q19's own server; your browser does not contact a font service.
Recitation audio and manuscript photographs are loaded from Q19's own servers. When you play a recitation (Q19 also loads the next three verses in advance so that playback continues smoothly) or view a manuscript photograph, your browser requests the file only from Q19. Q19's server fetches the file from its source the first time it is needed and keeps a copy in a size-limited cache on Q19's server, removing the least recently used files first. The sources are:
- Recitations: everyayah.com.
- Manuscript photographs: Corpus Coranicum (Berlin-Brandenburg Academy of Sciences and Humanities, Germany), the Staatsbibliothek zu Berlin (Germany), OPenn (University of Pennsylvania Libraries, USA) and The Metropolitan Museum of Art (USA).
These sources receive only Q19's server request: the server's IP address, a fixed Q19 user agent and the file's path, which names the reciter and verse, or the photograph. They do not receive your IP address, cookies, browser details, the page you were reading or anything about your account. Because cached copies are reused, a source learns at most that a file was needed, not by whom or how often.
Your request to Q19 for these files is handled like any other request to Q19 (server logs, section 3). The file address carries a time-limited signature (valid for 12 to 18 hours) that is the same for every reader and does not identify you. To stop abuse, Q19 counts these requests per IP address in a counter that expires after 60 seconds. Legal basis: Art. 6(1)(b) GDPR (providing the reader and manuscript features you use); for the request counter, Q19's legitimate interest in protecting the service (Art. 6(1)(f) GDPR, section 12).
The citation links on manuscript cards (the original catalogue record and the licence) are ordinary links to the institutions' websites. They open only if you click them; the website then receives your IP address and browser details, but not the address of the Q19 page (no referring address is sent).
External reference links open third-party websites. Their privacy policies apply when you visit them.
Verse cards embedded on other websites load from Q19's server in an isolated frame, without cookies, device storage or analytics. Q19's server receives the visitor's IP address, browser details and the embedding site's address, and uses them only to deliver the card; its logs keep only what section 3 describes. Legal basis: Art. 6(1)(f) GDPR.
16. Recipients and processors
Q19 does not sell personal data and does not share it for advertising. Data goes only to the recipients below, and to authorities where the law requires it (Art. 6(1)(c) GDPR). The sources of recitation audio and manuscript photographs receive no personal data about you (section 15).
| Recipient | Role | Purpose | Transfer safeguard |
|---|---|---|---|
| Hosting: netcup GmbH, Karlsruhe, Germany, on a European hosting plan. The precise data-centre country has not yet been independently verified | Processor | Runs Q19's servers and databases | Not needed inside the EU |
| Email: Resend (Plus Five Five, Inc., San Francisco, USA) | Processor | Delivers Q19's emails | Resend is certified under the EU-U.S. Data Privacy Framework (Art. 45 GDPR); EU Standard Contractual Clauses also apply (Art. 46(2)(c) GDPR) |
| Together AI: Together Computer, Inc., United States (Together AI) | Processor | Standard answers and other AI features | Together describes EU Standard Contractual Clauses in its published privacy policy. An executed Q19-specific data processing agreement has not yet been recorded |
| Anthropic: Anthropic Ireland, Limited, Ireland | Processor | Deeper answers; fallback for other AI features | EU Standard Contractual Clauses (Art. 46(2)(c) GDPR) for transfers to Anthropic in the USA |
| OpenAI: OpenAI Ireland Ltd., Ireland | Processor | Embeddings of question and search text | EU Standard Contractual Clauses or an adequacy decision (Art. 45, 46(2)(c) GDPR) for transfers outside the EEA |
| Stripe: Stripe Payments Europe, Limited and Stripe Technology Europe, Limited, Ireland | See section 7 | Payments and subscriptions | Stripe’s data processing agreement and Data Transfers Addendum provide EU Standard Contractual Clauses; eligible transfers to certified US entities may rely on the EU–US Data Privacy Framework |
| Google Ireland Limited (Ireland); Google LLC (USA) | Processor, with your consent | Google Analytics | No Google Analytics transfer takes place on the current public website. Optional Google sign-in is separate and follows Google’s privacy policy |
| Google: Google Ireland Limited, Ireland (EEA and Switzerland); Google LLC, USA for most other regions | Separate controller | Sign-in with Google, if you choose it | Provider's own terms |
| Microsoft: Microsoft Corporation, USA, and Microsoft Ireland Operations Limited for the EEA, UK and Switzerland; an organisation may also control a work or school account | Separate controller | Sign-in with Microsoft, if you choose it | Provider's own terms |
| Apple: Apple Distribution International Ltd., Ireland, for EEA users | Separate controller | Sign in with Apple, if you choose it | Provider's own terms |
- Recipient
- Hosting: netcup GmbH, Karlsruhe, Germany, on a European hosting plan. The precise data-centre country has not yet been independently verified
- Role
- Processor
- Purpose
- Runs Q19's servers and databases
- Transfer safeguard
- Not needed inside the EU
- Recipient
- Email: Resend (Plus Five Five, Inc., San Francisco, USA)
- Role
- Processor
- Purpose
- Delivers Q19's emails
- Transfer safeguard
- Resend is certified under the EU-U.S. Data Privacy Framework (Art. 45 GDPR); EU Standard Contractual Clauses also apply (Art. 46(2)(c) GDPR)
- Recipient
- Together AI: Together Computer, Inc., United States (Together AI)
- Role
- Processor
- Purpose
- Standard answers and other AI features
- Transfer safeguard
- Together describes EU Standard Contractual Clauses in its published privacy policy. An executed Q19-specific data processing agreement has not yet been recorded
- Recipient
- Anthropic: Anthropic Ireland, Limited, Ireland
- Role
- Processor
- Purpose
- Deeper answers; fallback for other AI features
- Transfer safeguard
- EU Standard Contractual Clauses (Art. 46(2)(c) GDPR) for transfers to Anthropic in the USA
- Recipient
- OpenAI: OpenAI Ireland Ltd., Ireland
- Role
- Processor
- Purpose
- Embeddings of question and search text
- Transfer safeguard
- EU Standard Contractual Clauses or an adequacy decision (Art. 45, 46(2)(c) GDPR) for transfers outside the EEA
- Recipient
- Stripe: Stripe Payments Europe, Limited and Stripe Technology Europe, Limited, Ireland
- Role
- See section 7
- Purpose
- Payments and subscriptions
- Transfer safeguard
- Stripe’s data processing agreement and Data Transfers Addendum provide EU Standard Contractual Clauses; eligible transfers to certified US entities may rely on the EU–US Data Privacy Framework
- Recipient
- Google Ireland Limited (Ireland); Google LLC (USA)
- Role
- Processor, with your consent
- Purpose
- Google Analytics
- Transfer safeguard
- No Google Analytics transfer takes place on the current public website. Optional Google sign-in is separate and follows Google’s privacy policy
- Recipient
- Google: Google Ireland Limited, Ireland (EEA and Switzerland); Google LLC, USA for most other regions
- Role
- Separate controller
- Purpose
- Sign-in with Google, if you choose it
- Transfer safeguard
- Provider's own terms
- Recipient
- Microsoft: Microsoft Corporation, USA, and Microsoft Ireland Operations Limited for the EEA, UK and Switzerland; an organisation may also control a work or school account
- Role
- Separate controller
- Purpose
- Sign-in with Microsoft, if you choose it
- Transfer safeguard
- Provider's own terms
- Recipient
- Apple: Apple Distribution International Ltd., Ireland, for EEA users
- Role
- Separate controller
- Purpose
- Sign in with Apple, if you choose it
- Transfer safeguard
- Provider's own terms
17. Transfers outside the EU
Q19's own servers are at netcup GmbH, Karlsruhe, Germany, on a European hosting plan. The precise data-centre country has not yet been independently verified. Some recipients are in the USA or belong to US groups: Together AI, Anthropic, OpenAI, Google, and possibly Stripe, the email provider, Microsoft and Apple. The sources of recitation audio and manuscript photographs, some of them in the USA, receive no data about you, because Q19's server fetches those files (section 15).
For the recipients in section 16 to which Q19 itself sends data (its processors and Stripe), Q19 relies on a safeguard under Chapter V GDPR: either the recipient is certified under the EU-U.S. Data Privacy Framework, for which the European Commission adopted an adequacy decision on 10 July 2023 (Art. 45 GDPR), or Q19 has agreed the European Commission's standard contractual clauses with it (Art. 46(2)(c) GDPR). The safeguard for each recipient is in the table in section 16. You can ask for a copy of the standard contractual clauses at the contact address in section 1.
18. How long data is kept
The table below lists the current retention periods. Where no fixed period is given, data stays until you delete it or your account.
| Data | How long |
|---|---|
| Account, profile and settings | Until you delete your account |
| Age confirmation and research-data consent record (time, consent text version, history settings) | As long as your account exists |
| Bookmarks, notes, annotations, collections, canvases | Until you delete them (one by one, or all at once in Account › Privacy) or your account |
| Reading history | Until you delete it in Account › Privacy, or delete your account |
| Ask Q19 conversations | Until you delete the conversation (or all saved research in Account › Privacy) or your account |
| Sign-in session records | Deleted 30 days after the session expires or is ended (a sign-in itself lasts at most 7 days) |
| Password reset code (hash) | Valid 1 hour; removed when used or replaced, otherwise deleted 7 days after the link expired |
| Email confirmation link | Valid 24 hours; not stored |
| AI answer cache and search caches | 1 hour; 10 to 30 minutes |
| AI usage records (one per AI call) | Per call for 12 full calendar months; afterwards only monthly totals per feature, model and provider are kept, without any link to an account or request. When you delete your account, your account id and the request id are removed from them at once |
| AI answer ledger (time, Standard or Deeper, delivered or refunded, for each answer) | Until you delete your account |
| Allowance and spending counters | Deleted when you delete your account; otherwise they expire after 40 days |
| Request counters (abuse protection) | 60 seconds to 1 hour |
| Server logs | 7 days at the latest |
| Database backups | Up to about 4 months |
| Subscription records at Q19 | Until you delete your account |
| Records of Stripe notifications (event id and type) | 90 days |
| Stripe customer reference after account deletion | The minimum Stripe customer reference is retained to recognise late payment events after account deletion. It is not linked back to a Q19 account. No automatic expiry is currently configured; requests for deletion are reviewed by the operator |
| Invoices and payment records at Stripe | 8 years from the end of the calendar year in which the invoice was issued (§ 147(1) No. 4 and (3) AO, § 14b(1) UStG) |
| Withdrawal and cancellation declarations, and the emails about them | 3 years from the end of the year in which Q19 received them (the limitation period, §§ 195, 199 BGB), together with the emails sent about them; longer only while a declaration is still being handled or an email about it has not been sent |
| Consent cookie q19_consent | 12 months |
| Cached recitation and photograph files (no personal data) | Until the cache's size limit removes them |
| Google Analytics data | Not applicable to the current public website: Google Analytics is disabled and Q19 sends it no analytics events |
| Revoked API keys | Until you delete your account |
| Data download file | Deleted as soon as it is sent |
- Data
- Account, profile and settings
- How long
- Until you delete your account
- Data
- Age confirmation and research-data consent record (time, consent text version, history settings)
- How long
- As long as your account exists
- Data
- Bookmarks, notes, annotations, collections, canvases
- How long
- Until you delete them (one by one, or all at once in Account › Privacy) or your account
- Data
- Reading history
- How long
- Until you delete it in Account › Privacy, or delete your account
- Data
- Ask Q19 conversations
- How long
- Until you delete the conversation (or all saved research in Account › Privacy) or your account
- Data
- Sign-in session records
- How long
- Deleted 30 days after the session expires or is ended (a sign-in itself lasts at most 7 days)
- Data
- Password reset code (hash)
- How long
- Valid 1 hour; removed when used or replaced, otherwise deleted 7 days after the link expired
- Data
- Email confirmation link
- How long
- Valid 24 hours; not stored
- Data
- AI answer cache and search caches
- How long
- 1 hour; 10 to 30 minutes
- Data
- AI usage records (one per AI call)
- How long
- Per call for 12 full calendar months; afterwards only monthly totals per feature, model and provider are kept, without any link to an account or request. When you delete your account, your account id and the request id are removed from them at once
- Data
- AI answer ledger (time, Standard or Deeper, delivered or refunded, for each answer)
- How long
- Until you delete your account
- Data
- Allowance and spending counters
- How long
- Deleted when you delete your account; otherwise they expire after 40 days
- Data
- Request counters (abuse protection)
- How long
- 60 seconds to 1 hour
- Data
- Server logs
- How long
- 7 days at the latest
- Data
- Database backups
- How long
- Up to about 4 months
- Data
- Subscription records at Q19
- How long
- Until you delete your account
- Data
- Records of Stripe notifications (event id and type)
- How long
- 90 days
- Data
- Stripe customer reference after account deletion
- How long
- The minimum Stripe customer reference is retained to recognise late payment events after account deletion. It is not linked back to a Q19 account. No automatic expiry is currently configured; requests for deletion are reviewed by the operator
- Data
- Invoices and payment records at Stripe
- How long
- 8 years from the end of the calendar year in which the invoice was issued (§ 147(1) No. 4 and (3) AO, § 14b(1) UStG)
- Data
- Withdrawal and cancellation declarations, and the emails about them
- How long
- 3 years from the end of the year in which Q19 received them (the limitation period, §§ 195, 199 BGB), together with the emails sent about them; longer only while a declaration is still being handled or an email about it has not been sent
- Data
- Consent cookie q19_consent
- How long
- 12 months
- Data
- Cached recitation and photograph files (no personal data)
- How long
- Until the cache's size limit removes them
- Data
- Google Analytics data
- How long
- Not applicable to the current public website: Google Analytics is disabled and Q19 sends it no analytics events
- Data
- Revoked API keys
- How long
- Until you delete your account
- Data
- Data download file
- How long
- Deleted as soon as it is sent
Expired data is deleted in a monthly clean-up, so deletion can happen up to one month after a period ends. Database backups contain deleted data for up to about 4 months, until they are overwritten.
Q19 does not currently delete inactive accounts automatically.
19. Your rights
Under the GDPR you have the right to:
- access the data Q19 holds about you and receive a copy (Art. 15);
- have incorrect data corrected (Art. 16);
- have your data erased (Art. 17);
- have its processing restricted (Art. 18);
- receive the data you provided in a common machine-readable format, or have it sent to another provider (Art. 20);
- withdraw any consent at any time, with effect for the future (Art. 7(3)).
In Account you can download your data and delete your account yourself, and in Account › Privacy you can withdraw your research-data consent, switch reading or chat history off, and delete your reading history or all your saved research. For anything else, write to the contact address in section 1. Q19 answers within one month (Art. 12(3) GDPR) and may ask you to confirm your identity first.
20. Complaint to a supervisory authority
You can lodge a complaint with a data protection supervisory authority, in particular in the EU member state where you live, work or where the alleged infringement took place (Art. 77 GDPR). The authority responsible for Q19 is the State Commissioner for Data Protection and Freedom of Information of Baden-Württemberg (Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg, LfDI BW), Lautenschlagerstraße 20, 70173 Stuttgart, Germany, www.baden-wuerttemberg.datenschutz.de.
21. Children
Q19 is for people aged 16 or older. When you create an account, or first sign in with Google, Microsoft or Apple, you must confirm that you are 16 or older; Q19 does not verify this further. Visitors under 16 cannot themselves consent to Analytics (Art. 8 GDPR) and should not switch it on. If Q19 learns that an account belongs to someone under 16, it deletes the account.
22. Automated decisions
Q19 makes no decisions based solely on automated processing that have legal effects on you or similarly significantly affect you (Art. 22 GDPR). AI answers are generated content, not decisions about you. Your plan's limits on answers and requests are applied automatically, exactly as the plan describes.
23. Changes to this policy
This policy is dated 15 October 2026. When Q19 changes how it processes personal data, it updates this page and its date. If a change affects your cookie choices, Q19 asks for your choice again; if the research-data consent text changes in substance, Q19 asks for your consent again (section 5).
This policy is available in German, English and Arabic. If the versions differ, the German version prevails.