The Android privacy policy in full
ARHAS INDIA (OPC) PRIVATE LIMITED, Hyderabad, Telangana, India. Last updated 2026-09-18.
This policy is about the Android application and nothing else. The Windows application has its own, at creasepoint.com/privacy, and the two products are genuinely different: the Windows one makes one network request and only if you switch it on, and this one makes several without asking. Carrying a sentence from that policy onto this page would be the specific mistake docs/DECISIONS.md #115 records, so nothing here is inherited — every sentence is written from what this application does.
There are two builds and they do not have the same privacy properties. §1 is the difference, and it is the first thing on the page because it decides which of the rest applies to you.
0. The uncomfortable things first
Four things are true that a privacy policy would normally bury.
- One feature sends the text of your document to a third party. It is called Summarise, it is in the Google Play build only, it does nothing until you press it, and it asks you before the first time. §4 is the whole of it. Everything else this application does — opening, editing, merging, splitting, compressing, recognising text, redacting, signing, saving — happens on your phone.
- Advertising is in the Play build, and the advertising SDK collects things we never see. Google's Mobile Ads SDK collects an IP-derived approximate location, interactions with the advertisements, and diagnostics. It does not get an advertising identifier — the Play build removes that permission and we checked the merged package to be sure. That is Google's collection, not ours, and it is still our declaration to make. §3.
- A summary can be wrong, and being wrong is not rare. We measured it. §4.4 gives a real example from the model we ship, because a policy that describes a feature without describing how it fails is describing something else.
- We are an Indian company and Indian obligations follow us, not you. Where you are decides which of your rights apply; where we are registered decides who you complain to. §8 names a person.
1. Which build you have, and how to tell
You can check this yourself without running it. An APK's permission list is a static property of the file: aapt dump permissions prints it. The plain build prints one permission, which the application defines for itself and which grants access to nothing.
What that means is narrower than it sounds, and here is the narrow version: it stops this application opening a network connection. It does not stop a document leaving your phone. When you save to Google Drive, this application hands the file to Google Drive's own app, and that app does the networking — which is exactly how saving to a cloud drive works here without a permission.
2. What the application collects about you
Nothing. There is no CreasePoint account, no sign-in, no profile, no sync, no licence check, no analytics, no usage counter and no crash reporting of our own. We do not know how many people use this application, which features they use, or that any particular installation exists.
What it stores on your phone, in its own private storage:
- a list of documents you recently opened — names and locations, not contents;
- folders you connected, so it can save to them again;
- which recognition languages you last used;
- whether you have a subscription, as Google Play last reported it;
- whether you agreed to Summarise;
- a random identifier with no meaning outside our own summarising service, used to count your daily free summaries. It is not a device identifier, not an advertising identifier, and it follows you nowhere.
Clearing the application's data erases all of it. Uninstalling erases all of it.
3. Advertising (Play build, free tier)
The free Play build shows a banner, and Premium removes it.
Where it appears: the Files and Tools screens, and at the end of a document you have scrolled to the end of. Never over a page you are reading, and never in the position your first file should be in.
What Google's Mobile Ads SDK collects: approximate location derived from your IP address, interactions with the advertisements, and diagnostics. We do not receive this, cannot query it, and cannot switch it off while showing advertisements at all. Google's own policies govern it.
What it does not get is the advertising identifier. This build removes the AD_ID permission outright, so the SDK cannot read the one Android holds for you — and because the SDK asks for that permission itself, we verified the removal survived on the merged package rather than trusting our own manifest. The advertisements are not personalised either: the application disables personalisation on every request, everywhere, for everyone, whether or not any privacy law applies to you. You can still reset or delete your advertising ID in Android's settings, under Privacy → Ads; it makes no difference to this application, which never sees it.
Your documents are not given to it. No advertisement request carries anything from a file you opened.
4. Summarise (Play build, and only when you press it)
4.1 What is sent
The text of the document you have open. Not the file.
The application extracts the text with the same code that powers Find, and sends only that string over an encrypted connection to a small service we operate on Cloudflare, which passes it to a language model running on Cloudflare's own network. The model writes the summary and the summary comes back.
Not sent: the file itself, images, attachments, embedded files, digital signatures, document metadata, the filename, or where the document is stored.
One thing you cannot see for yourself, so we tell you. If a form was filled in and then flattened, what was typed becomes part of the page's text, and is therefore part of what is sent. Nothing distinguishes a flattened form from an ordinary paragraph — not for us and not for you. If a document has a live form in it, the consent sheet says so.
4.2 What is kept
Nothing, by us. There is no cache and no request log, deliberately and at a cost — caching would have cut our bill by about a third. The usual way to get both is Cloudflare's AI Gateway, and the reason we run none is that its cache and its logs work by keeping your text, so the feature we would be switching off is the one that stores the thing this page is about. Our service keeps counters and a random identifier; it never writes your text to storage or to a log.
Cloudflare processes it to produce the summary. Their terms govern what they do with it, and we link them rather than paraphrase them.
4.3 When it happens
Never, unless you press Summarise. The first time you press it you are shown exactly what is sent and asked. You are asked once in the life of the installation — whichever way you answer, you will not be asked again. You can change your answer at any time in Settings → Summarise, and turning it off is one tap with no confirmation.
Refusing costs you nothing but the feature. Every other part of the application is unchanged.
4.4 It can be wrong, and here is a real one
A model writes fluent prose and sometimes states something the document does not say. This is not a theoretical caution. On a logistics report we tested with, the model wrote that a fuel surcharge was "up 11.2% year-over-year" — but 11.2% was the surcharge's share of unit cost, not a rate of change, and the real change of +6.8% was in the same table. On another run it said "three structural risks" where the document's own heading said two.
We tightened the instructions we give the model, measured it again, and the same class of error still occurred. So we do not claim to have fixed it. Every summary carries a permanent note saying it can be wrong, and that note cannot be dismissed, because it is a description of the feature rather than a disclaimer about it.
Do not rely on a summary for anything that matters without reading the document.
5. Buying Premium (Play build)
The subscription is sold and processed by Google Play. We never see your payment details, your card, or your billing address. What we receive is Google's answer to one question — whether this Google account has an active subscription — and that answer is what removes the advertising and raises your daily summary allowance.
There is nothing to log into and nothing to restore manually. Play ties the subscription to the Google account your device is signed into, so reinstalling or changing phone restores it by itself. Settings has a Check my subscription row for when you want to make it ask again.
To cancel, use the Play Store's own subscription settings. We cannot cancel it for you and have no control over it.
6. Cloud folders you connect
If you connect a folder — Google Drive, OneDrive, Dropbox, or somewhere on your phone — Android grants this application access to that folder only, and you can take it back in Android's own settings at any time. There is no account of ours involved, no OAuth token held by us, and no sign-in.
When you save a document to a connected folder, it goes to your drive, not to us.
7. What we declare on Google Play
Play's Data safety section is generated from a form we complete. What we say there:
- Files and docs — collected, and shared with a third party, for app functionality. This is Summarise, and only Summarise. It is processed and not retained.
- Device or other IDs — collected, for app functionality. This is the random per-install identifier in §2 that counts your free summaries. It is not Google's advertising identifier. The Play build removes the
AD_ID permission outright, we checked the merged package rather than the source to be sure the removal survives the SDK asking for it back, and Play Console's separate advertising-ID declaration is therefore answered no. - Approximate location — collected, for advertising. Google's Mobile Ads SDK may estimate it from your IP address. We declare it because the SDK can do it, not because we receive it; we derive no location ourselves and the application holds no location permission.
- App interactions and diagnostics — collected, for advertising and analytics by that SDK.
- Purchase history — collected by Google Play, to tell us whether you are a subscriber.
If what we declare and what this page says ever differ, the difference is a mistake and we want to know. §8.
8. Your rights, and who to write to
Whoever you are, you can ask what we hold about you (the answer is: nothing tied to you), ask for it to be deleted (clearing app data does it immediately and without asking us), and withdraw consent for Summarise in Settings.
If India's Digital Personal Data Protection Act 2023 applies to you, you have rights of access, correction, erasure, grievance redressal and nomination, and the contact below is the grievance channel the Act requires.
If the GDPR applies to you, your legal bases are: consent for Summarise, which is the only thing this application asks you for; contract for the subscription; and legitimate interests for the advertising, which is not personalised — the application tells Google's SDK to disable personalisation on every request, unconditionally and everywhere, so there is no personalised advertising to consent to and we never ask you to.
Contact and grievances: [email protected] ARHAS INDIA (OPC) PRIVATE LIMITED, Hyderabad, Telangana, India. We answer within 30 days, and sooner if we can.
9. Children
This application is rated 3+ and is not directed at children. It collects nothing that identifies anyone. The free Play build shows advertising, and Google's SDK is configured for the rating the listing carries.
10. Changes
The version of this page on creasepoint.com is always the current one. A copy ships inside the application, and that copy is the text as at your version's release. Where they differ, the website is right and the difference is written at the top of the page rather than left for you to find.