Legal

Privacy Policy

Effective 1 October 2026  ·  Last updated 9 October 2026

The short version

  • Your library is yours. What you read, your progress, streaks, notes and highlights are stored so the app can show them back to you — not sold, not rented, and never handed to advertisers. If the free plan ever carries ads, they will not be targeted using your library.
  • We never see your card. Subscriptions are billed by Apple and Google. They tell us whether you are subscribed; they do not give us your payment details.
  • Two features send data out of the app. Personal summaries and narrated audio are produced by outside providers. Section 5 says exactly what reaches them.
  • The waitlist is one email. If you gave us an address before launch, it is used to tell you Pensovo has launched, and for nothing else.
  • This summary is here to be readable. The sections below are the part that binds us.
Section 1

Who we are

Pensovo is a reading tracker for iOS, operated by Snakescript Solutions LLP, registered in India at E-91, Phase 8, Industrial Area, Sector 73, Sahibzada Ajit Singh Nagar (Mohali), Punjab 160071, LLPIN AAO-0202.

In this policy, "we", "us" and "Pensovo" mean that entity. "You" means the person using the app. Under India's Digital Personal Data Protection Act, 2023, we are the Data Fiduciary for the data described here; under the GDPR, where it applies to you, we are the controller.

You can reach us at [email protected] about anything in this document.

Section 2

What we collect

Things you give us

  • Your account. Email address, and a sign-in through Apple or Google if you use one. There is no password: you sign in with a one-time code sent to your email, so there is nothing for us to store and nothing to be stolen. Optionally a display name.
  • Your library. The books you add and their titles and authors, whether each is unread, in progress or finished, your page or chapter position, the dates you marked things read, your collections, and any notes and highlights you write.
  • Your streak history. Which days you logged reading, and any streak saves used.
  • Your reader profile. The handful of details you set so personal summaries can be written for your situation — see section 5.
  • Anything you send us. Emails, bug reports, and what you write in them.

Things the app records as you use it

  • Subscription status. Whether you have an active Premium subscription, when it renews or lapses, and the store it came from.
  • Diagnostics. Crash reports and error logs, which include your device model, operating system version, app version and the state the app was in when it failed. These are sent to Sentry (see section 6). We have turned off the options that would attach your IP address, a screenshot of the screen you were on, or a copy of what was rendered — any of which could carry your own notes and highlights.
  • Product analytics. Events such as opening a screen, logging a reading session, seeing the paywall or completing a purchase. Each event records a random identifier for your installation and, when you are signed in, your account ID — so these are linked to you, not anonymous. They also record which book an event relates to, where one applies. We use them to see which parts of the app are used and where people stop, not to target advertising. You can turn them off at any time in Settings → Legal → “Share usage data”; nothing else in the app changes when you do.
  • Technical connection data. IP address and timestamps, recorded by our hosting provider as part of serving requests.

Things we do not collect

  • Card numbers, bank details or billing addresses. Apple and Google handle payment; that data never reaches us.
  • Your contacts, photos, microphone, precise location, or anything else behind a device permission we do not ask for.
  • Advertising identifiers — for now. Pensovo currently shows no ads and includes no advertising SDK. We may introduce ads on the free plan in future. If we do, we will update this policy before they appear to name the ad provider and what it collects (typically your device’s advertising identifier, IP address and coarse location, used by the provider to serve and count ads), and the app will let you limit personalised ads where your device or the law provides for it. Premium will stay free of advertising. Your library, notes and reading history will never be used to target ads.
Section 3

Why we hold it

WhatWhat it is for
AccountTo let you sign in, and to reach the same library from a second device.
Library, notes, streaksThis is the product. Without it there is nothing to show you.
Reader profileTo write personal summaries that fit your situation rather than a generic one.
Subscription statusTo unlock Premium features, and to stop unlocking them when a subscription ends.
Crash reportsTo find and fix the failures you hit.
AnalyticsTo see which features get used, so we know what to keep and what to cut.
EmailTo send your sign-in codes, to answer you, and to tell you about changes that affect your account.

We do not sell personal data, and we do not share your library, notes, photos or reading history with anyone for their own advertising or marketing. Should the free plan carry ads one day, the ad provider will receive only what it needs to serve and count ads, as section 2 will then set out — never your library.

Section 4

Our legal basis

Under the DPDP Act (India). We process your data on the consent you give when you create an account and when you turn on a feature, and for the certain legitimate uses the Act allows — such as responding to you when you write to us. You can withdraw consent at any time, as easily as you gave it, by deleting your account or writing to us; withdrawing it does not undo what was lawfully done beforehand.

Under the GDPR, where it applies. We rely on: performance of a contract for your account, library and subscription; legitimate interests for crash reporting, security and keeping the service working; consent for any marketing email; and legal obligation where a law requires us to keep something.

Product analytics. Under the GDPR we rely on consent, and under the DPDP Act on the consent you give when you create an account. That is a real basis here rather than a form of words, because the switch exists: the Share usage data switch in Settings turns it off, it takes effect on the very next event, and nothing is sent while it is off. The events themselves are first-party — written to our own database, not sent to an analytics company. As section 2 sets out, they carry a random installation identifier and, while you are signed in, your account ID, so they are linked to you rather than anonymous. They never carry your name, your email, or the text of anything you have read or written.

Section 5

What leaves the app

Two Premium features are produced by outside providers, which means something has to be sent to them. This section says what.

Summaries written for you

When you ask for a personal summary, we send the text extracted from the PDF you uploaded to our AI provider — OpenAI today; we may use Google's Gemini API as an alternative and will say so here if we switch — which generates the summary and returns it to us. We store the result against your account so you can read it again.

For this request we send only that extracted text. We do not send your highlights, your reading history or your email address.

Notes are a separate case. If you use the optional “refine” action on a note — to summarise a passage or restate it in plainer words — the text of that note is sent to the same AI provider to do it. That feature is off unless we switch it on, is available only on the paid plan, and is capped per month. If you never use it, nothing you have written leaves Pensovo.

Both providers process this on our instructions under their business API terms, which exclude submitted content from training their models. We use the OpenAI API and the paid Gemini API — not the consumer ChatGPT or Gemini apps, which are different services with different rules and not ones we send anything to.

Summaries are generated by a language model. They can be wrong, and the Terms say so plainly.

Narrated audio

Narration is produced by Google Cloud Text-to-Speech from the text of a summary. Only that text is sent — no account identifier and nothing you wrote. Narration for a title in the Pensovo catalogue is generated once and reused for every reader, so it is not tied to you or produced on your behalf.

If we change provider

The two above are who we use today, and this page names them rather than hiding behind “trusted partners” because knowing who holds your words is the point of telling you at all. We may change either one — for a better model, a better voice, or a provider whose terms suit this better — and if we do, we will update this page before the change ships, not after. What will not change without us saying so is the shape of it: only the text described above is ever sent, never your email, your highlights or your reading history, and any provider we use must be bound by terms that exclude what we send from training their models. A provider that would not agree to that is one we would not use.

Section 6

Who else touches it

We use a small number of providers to run the service. They act on our instructions, under contract, and may not use your data for their own purposes.

ProviderWhat it doesWhat it sees
Supabase Database, authentication and file storage Your account and everything in your library
Apple, Google App distribution and subscription billing Your purchase; they pass us only your subscription status
OpenAI (current); Google Gemini API (alternative)
language model, summaries
Generates personal summaries Only what section 5 lists
Google Cloud Text-to-Speech
speech synthesis
Generates narrated audio Summary text only
Brevo Holds the pre-launch waitlist and sends the launch email Your email address, and the date and page you joined from
Supabase Sign-in codes and service email Your email address and the message
Sentry Crash and error reporting Device model, OS and app version, and the stack trace of the failure. Not your IP address, not a screenshot, and not the contents of the screen.

Beyond those, we disclose personal data only where the law requires it — a valid order from a court or an authority with the power to compel it — or to establish or defend a legal claim. If Pensovo is ever sold or merged, your data may transfer to the buyer, who would be bound by this policy until they gave you notice of a different one.

Section 7

Where it is stored

Your library and account live in our Supabase project, hosted in Singapore (AWS ap-southeast-1) — that is, outside India. The providers in section 6 may process data in other countries: crash reports go to Sentry in the United States, and the other providers process in the United States or the European Union.

Where data leaves India or the European Economic Area, we rely on our providers' standard contractual clauses and equivalent safeguards. If you would like to know which apply to a particular provider, ask us and we will tell you.

Section 8

How long we keep it

  • Your library and account: for as long as your account exists. A reading tracker that forgets last year is not much use, so we do not expire old entries.
  • After you delete your account: we delete your personal data within 30 days. It may survive in encrypted backups for up to a further 30 days before those rotate out.
  • A count of the summaries a subscription has used: kept after you delete your account, with your name, the book, and the file's fingerprint removed. What remains records that a summary was made against a subscription on a date — no owner, no title, no content. It exists so the monthly allowance a subscription pays for cannot be refilled by deleting the account and signing up again, and it is not used for anything else.
  • Billing records: for as long as Indian tax and company law requires us to keep them.
  • Support email: 24 months after the conversation ends.
  • Crash reports: 90 days, after which Sentry deletes them.
  • Product analytics: 24 months from the day the event was recorded, after which it is deleted. Deleting your account unlinks the events recorded before that: your account ID is removed from them, leaving only the random installation identifier they were recorded against.
Section 9

Your rights

Whatever country you are in, you can:

  • See what we hold. Write to us and we will send you a copy of your data.
  • Correct it. Most of it you can edit directly; write to us for the rest.
  • Delete it. Delete your account in the app, or ask us to. Apple requires that in-app route to exist, and it does.
  • Withdraw consent to any processing that rests on it.
  • Complain if we get it wrong — see section 14.

If the DPDP Act applies to you, you also have the right to nominate someone to exercise these rights on your behalf if you die or become incapable of exercising them, and the right to a grievance redressal process — section 14.

If the GDPR applies to you, you also have the rights to restrict or object to processing, to data portability in a machine-readable format, and to complain to your national supervisory authority.

We answer requests within 30 days. We will ask you to confirm you control the account's email address before acting on one — not to obstruct you, but because "delete this person's account" is a request an attacker would also like to make.

Section 10

Children

Pensovo is for adults. You must be 18 or over to hold an account, which is also the age the Digital Personal Data Protection Act, 2023 uses to define a child in India. We do not knowingly collect data from anyone under 18. We do not sell data, serve targeted advertising, or build a profile to predict anything about you — but we do record how the app is used, and those records are linked to your account. Section 2 says exactly what is recorded.

If you believe a child has given us data without that consent, write to us and we will delete it.

Section 11

Security

  • Traffic between the app and our servers is encrypted in transit (TLS), and data is encrypted at rest by our hosting provider.
  • Database access is restricted per user by row-level security, so one account cannot read another's library.
  • There is no password to steal. Sign-in is a one-time code that expires, or Apple or Google, and we never see a credential of yours at all.
  • No card details are stored anywhere in our systems, because we never receive them.
  • Access to production data is limited to the people who need it to run the service.

No service is perfectly secure, and we will not pretend otherwise. If a breach affects your data, we will notify you and the Data Protection Board of India as the DPDP Act requires, and any other regulator we are obliged to tell.

Section 12

The waitlist

Before Pensovo launches, pensovo.com collects one thing: an email address, if you choose to give us one. We also record the date you joined and which page you came from, so we know which announcements worked.

We use it for exactly one message — telling you Pensovo has launched — and every email carries a one-click unsubscribe. We do not add waitlist addresses to any other list, and we do not share them.

The waitlist is held by Brevo, the email provider listed in section 6, and not in the Supabase project that holds accounts and libraries — until you create an account, we hold nothing about you beyond this address. Brevo processes it in the European Union; the safeguards in section 7 apply. Write to [email protected] at any time and we will remove you; you do not need an account for us to act on that.

After launch we delete addresses that never became accounts within 90 days of the launch email. A waitlist that outlives its purpose is just a mailing list nobody asked for.

Section 13

This website

The Pensovo marketing site runs no analytics and sets no cookies when you read it. Its two typefaces are served from pensovo.com itself. One exception: if you open the waitlist form, the page loads Google reCAPTCHA to tell people from bots, which sets a _GRECAPTCHA cookie and sends your IP address and browser details to Google under Google's privacy policy; your email address is sent to Brevo (EU), which stores it for the waitlist and sends the confirmation message. Nothing is loaded from either until you open that form.

Section 14

Changes

When we change this policy we will update the date at the top. If a change materially affects what we collect or what we do with it, we will tell you in the app or by email before it takes effect, rather than quietly swapping the page.

Section 15

Contact and grievances

For anything in this policy — a question, a request about your data, or a complaint — write to [email protected]. We aim to reply within three working days and to resolve grievances within 30 days.

Grievance Officer: Amol Bharmoria, Designated Partner, [email protected], E-91, Phase 8, Industrial Area, Sector 73, Sahibzada Ajit Singh Nagar (Mohali), Punjab 160071, India.

If you are in India and we have not resolved your complaint, you may take it to the Data Protection Board of India. If you are in the EEA or the UK, you may complain to your local supervisory authority.