Jalees

Privacy Policy

Effective date:

1. About this policy

This policy explains what personal information Jalees ("we", "us") collects when you use the Jalees website and application (the "Service"), how we use that information, who we share it with, and the choices and rights you have.

The Service is operated by Jalees LLC, a Wyoming limited liability company with a mailing address at 30 N Gould St Ste 7128, Sheridan, WY 82801, USA. Jalees LLC is the controller of personal information processed through the Service. Where we use third-party providers to process information on our behalf, they act as processors and are listed in section 5.

2. Information we collect

We collect the following categories of information:

2.1 Account information

  • Your email address.
  • If you sign up with a password: a salted Argon2id hash of your password. We never store your password in clear text and cannot recover it for you.
  • If you sign in with Google: your Google account identifier (the OAuth "sub" claim), your email address as reported by Google, and your display name and avatar URL if you provide them.
  • An optional display name.

2.2 Content you upload and create

  • Files you upload (typically PDFs of books or other study materials), their original filenames, MIME types, and sizes.
  • The Markdown text that our optical-character-recognition ("OCR") worker extracts from each upload, used to ground chat responses in the page you are reading.
  • Your chat conversations with the assistant: the prompts you send, the streamed responses you receive, any image attachments captured from your current reader viewport, and the titles you assign to chats.

2.3 Billing information

  • Your Stripe customer identifier, subscription identifier, plan, status, current period end, cancellation flag, and trial-used flag.
  • A token-usage ledger recording, for each chat exchange, the number of input and output tokens, the underlying model used, and a pointer back to the chat message that consumed them. We use this ledger to enforce per-plan rate and volume quotas and to support billing analytics.
  • We do not store your card number, CVV, or any other payment-card data. Payment data is collected directly by Stripe under their privacy policy. We only ever see your Stripe customer identifier.

2.4 Technical information

  • The IP address, user-agent string, and timestamps of your requests, used for abuse prevention, rate limiting, and security investigations. These appear in server logs.
  • Authenticated session cookies (see our Cookie Policy for the complete list).
  • If you accept analytics cookies, a randomly-generated PostHog "distinct id" and session identifier; PostHog also records its standard properties (page URL, referrer, viewport, device class, web vitals) and, where session replay is enabled, a masked screen recording of your interactions. Sensitive inputs (passwords, email fields, anything inside our [data-ph-mask] attribute) are masked at the source before upload.
  • If something goes wrong on our backend or in your browser, our error-monitoring provider captures the exception, a stack trace, the URL, your IP, and limited request metadata. We strip request and response bodies before upload to avoid leaking your content.

2.5 Record of your consent choices

When you answer the cookie banner while signed in, we keep a copy of that answer on your account as well as in your browser. We are required to be able to demonstrate that consent was given (GDPR Art. 7(1)), and a setting stored only in one browser cannot show that. It also means you are not asked again on every device you sign in on.

Each entry holds:

  • Which categories you chose — essential (always on, and recorded as such so an old entry stays readable), analytics, and marketing.
  • The policy version you were shown, so the record identifies the text you agreed to rather than whichever text is current now.
  • The consent schema the choice was made under (for example jalees:consent:v1). If we ever change the categories we re-ask, and this keeps the old answers distinguishable from the new ones instead of silently merging them.
  • The date and time, taken from our database's clock rather than from your browser or our application.
  • Your IP address and user-agent string at that moment, as corroboration. Both may be absent — a missing one never blocks recording the choice itself, because the choice is the evidence and these only support it.

The record is append-only: changing your mind writes a new entry and withdrawing consent writes an entry with the categories switched off. Nothing is edited or removed, because the obligation is to show what was agreed at a given moment, not to report what is set today. If you are not signed in, your choice stays in your browser only, and is added to your account the first time you sign in afterwards.

3. How we use your information

We use your information for the purposes below. Under the EU GDPR and the UK GDPR, each purpose has a corresponding lawful basis (Article 6).

  • To provide the Service — create your account, store and OCR your uploads, run your chats, persist conversation history. Lawful basis: performance of a contract with you (Art. 6(1)(b)).
  • To bill you and manage your subscription — create a Stripe customer, record your plan and status, enforce quotas, issue invoices. Lawful basis: contract (Art. 6(1)(b)); compliance with tax and accounting obligations (Art. 6(1)(c)).
  • To keep the Service secure — rate-limit abusive traffic, block bots, detect credential stuffing, investigate incidents. Lawful basis: our legitimate interest in operating a secure service (Art. 6(1)(f)).
  • To send service emails. We use your email address to send transactional messages — account verification, password reset, billing receipts — and important security notices. Lawful basis: contract (Art. 6(1)(b)). These emails are not marketing and you cannot unsubscribe from them while your account is active.
  • To measure how the Service is used — aggregate analytics on signup conversion, feature adoption, and performance. Lawful basis: your consent (Art. 6(1)(a)), which you can withdraw at any time via the cookie settings link in our footer.
  • To show that you consented — keep the record described in 2.5. Lawful basis: compliance with a legal obligation (Art. 6(1)(c)); Art. 7(1) requires a controller relying on consent to be able to demonstrate that it was given. Note the consequence: this record is not itself kept with your consent, so declining analytics does not remove it — declining is one of the things it exists to evidence.
  • To improve the Service — debug errors using captured stack traces, and review aggregated usage and answer-quality statistics: how many chat exchanges took place, how many named a source the assistant had actually retrieved, how often a request failed and with which error, and how these differ between the AI models we offer. These are counts. They are computed from your conversations, but they contain no part of them — no prompt, no reply, no document title, no page number, and no identifier for the account the exchange belonged to. Lawful basis: legitimate interests (Art. 6(1)(f)) in measuring and correcting the quality of the answers we give you.
  • We do not read your conversations. No member of our staff reviews the content of your chats, your uploads, or the text extracted from them as a matter of routine, and no internal tool exposes that content for review. We would access an individual conversation only where we are legally required to, or where you ask us to in order to resolve a support request you have raised. If we ever intend to review conversation content for quality purposes, we will change this policy and its effective date first, tell you as described in section 11, and give you a way to object.

We do not use your uploads or chat content to train any machine-learning model of ours, and we do not sell or licence it to anyone for that purpose. What an AI provider may do with a chat turn we forward to it is governed by that provider's own terms, which differ between them — section 4 sets out what each one commits to.

4. AI processing

When you send a chat message, we forward the message, the relevant excerpt of your book's OCR'd text, and any attached image to a large-language-model provider, which generates the response. Which provider receives it depends on the model you select in the chat model picker. Unless you change it, the turn goes to Google's Gemini API. Selecting one of the GPT-5.6 models sends that turn to OpenAI instead; selecting one of the DeepSeek models sends it to DeepSeek. Only the provider behind the model you selected receives that turn — we do not send a copy to the others. The streamed response is sent back to your browser and persisted with your chat history.

Each of these providers processes that content under its own terms and privacy policy, as our processor:

  • Google. Per its current Gemini API additional terms, paid-tier content is not used to train Google's models.
  • OpenAI. Per its current enterprise privacy commitments, API inputs and outputs are not used to train OpenAI's models by default, and may be retained for up to 30 days to detect abuse.
  • DeepSeek. Operated by Hangzhou DeepSeek Artificial Intelligence Co., Ltd., which states in its privacy policy that it processes and stores data in the People's Republic of China. Please read section 6 on international transfers before selecting one of its models.

Separately, when a guided-study lesson is read aloud, we send the text of that lesson to Google's Cloud Text-to-Speech API to synthesise the audio. Nothing else from your library is sent for synthesis.

5. Who we share information with

We share your information only with the processors below, and only to the extent each needs to perform the function listed.

Google (Gemini API)
Generating chat responses from your prompt, book excerpt, and viewport image — the default, and whenever you select a Gemini model.
OpenAI
The same, when you select one of the GPT-5.6 models in the chat model picker.
DeepSeek (Hangzhou DeepSeek Artificial Intelligence Co., Ltd., China)
The same, when you select one of the DeepSeek models in the chat model picker.
Google (Cloud Text-to-Speech)
Synthesising the spoken audio for a guided-study lesson.
Google (OAuth)
"Sign in with Google" authentication, when you choose it.
Google (Cloud Storage)
Storing the files you upload.
Stripe
Subscription billing, checkout, customer portal, webhook delivery.
Resend
Sending transactional email — account verification, password reset, and important security notices.
Cloudflare
Turnstile bot-mitigation challenge on signup, login, and other write endpoints.
PostHog (PostHog Inc., EU region)
Product analytics, session replay, and automatic capture of errors and crashes in the app — all three only after you accept analytics cookies.

We may also disclose information when required by law, to enforce our Terms of Service, or in connection with a merger or asset sale. We will tell you about a material change in control before your data is transferred.

6. International transfers

Some of our processors are based in the United States or operate globally. Where we transfer personal data of users in the European Economic Area, the United Kingdom, or Switzerland to a country that has not received an adequacy decision, we rely on the European Commission's Standard Contractual Clauses (and, where applicable, the UK International Data Transfer Addendum) plus supplementary measures appropriate to the transfer. You can request the relevant clauses from us using the contact below.

One transfer is under your control and worth calling out. DeepSeek states that it processes and stores data in the People's Republic of China, which has not received an adequacy decision from the European Commission, and which affords rights of access to state authorities that differ materially from those in the EEA and the UK. A chat turn reaches DeepSeek only if you select one of its models in the chat model picker; if you would rather no content leave for China, use the default Gemini model or one of the GPT-5.6 models, and no DeepSeek transfer takes place.

7. How long we keep information

  • Account, books, chats: for as long as your account is active.
  • Server logs: 30 days, then deleted.
  • Consent records (2.5): for as long as your account exists, and deleted with it. They are not pruned on a schedule: an entry proving what you agreed to is only useful for as long as we might be asked to produce it, which is for as long as we are processing on the strength of it.
  • Billing records: at least the period required by applicable tax and accounting law (typically 7 years), even after you close your account.
  • Backups: rolling encrypted backups are retained for up to 35 days after the originating record was deleted.
  • After you delete your account: we delete or anonymise your account, books, OCR text, chat history, and stored files within 30 days, except where we are required to retain billing records (see above) or limited information for security and abuse-prevention purposes.
  • Files stored once and shared: when two accounts upload the identical file, we store its contents once and each account holds a reference to it. Deleting your account removes your reference, and the stored copy is erased once no account references it any more. If another account independently uploaded the same file, their own copy of it continues to exist — it is their upload, not a retained copy of yours.

8. Your rights

If you are in the EEA, the UK, or Switzerland, you have the right under the GDPR / UK GDPR to:

  • access the personal data we hold about you;
  • correct inaccurate or incomplete data;
  • delete your data ("right to erasure");
  • restrict or object to certain processing;
  • port your data to another service in a structured, machine-readable format;
  • withdraw consent at any time where processing is based on consent;
  • lodge a complaint with your supervisory authority.

If you are a California resident, you have rights under the CCPA / CPRA to know, delete, correct, and (where applicable) opt out of "sale" or "sharing" of your personal information. We do not sell personal information and do not "share" it for cross-context behavioural advertising as those terms are defined under California law.

You can exercise most rights directly from your account settings: download your data, update your profile, and delete your account. For other requests, write to us using the address in section 12. We will respond within the time required by applicable law (one month for GDPR requests, 45 days for CCPA requests, extendable where permitted).

9. Children

Jalees is not directed to children. We do not knowingly collect personal information from anyone under 16 (or under 13, where that lower threshold applies). If you believe a child has provided us with personal information, contact us and we will delete it.

10. Security

We protect your account with industry-standard measures: TLS in transit, encrypted storage at rest, Argon2id password hashing, short-lived access tokens, rotation of long-lived refresh tokens, and audit logging of authentication events. No system is perfectly secure, and we cannot guarantee absolute security — if you believe your account has been compromised, change your password and contact us immediately.

11. Changes to this policy

We will update this policy from time to time. When we make a material change, we will update the effective date above and, where the change is significant, notify you by email or via an in-app banner. Continued use of the Service after a change takes effect means you accept the updated policy.

12. Contact

For privacy questions, requests, or complaints, write to [email protected], or by post to Jalees LLC, 30 N Gould St Ste 7128, Sheridan, WY 82801, USA.