1. Who we are
Purrse is run by Abbas Anandwala, an individual developer in India ("Purrse", "we", "us"). We make the Purrse expense tracking app for iOS and Android and runs the website at purrse.in. This policy explains what personal data we process when you use the app or the website, why, and the choices you have. It is written to meet India's Digital Personal Data Protection Act, 2023 and, where it applies to you, the EU and UK General Data Protection Regulation.
2. What we collect
Free plan and Purrse Plus
What we collect depends on your plan.
- Free plan, no account. You don't need an account. Your accounts, entries, people, categories and settings are kept only on your phone, and we never receive them. If you never sign in, none of your entries, balances, notes, name or email address is sent to our servers.
- Purrse Plus. Plus (a subscription or the Lifetime plan) adds sign-in with Google or an email code (Sign in with Apple comes with the iPhone app), and cloud backup and sync. When you sign in, the information in the table below is stored on our servers so it can be backed up and synced between your devices.
A few things reach us whatever your plan, because the app needs them to work or to be fixed: crash reports, the anonymous once-per-install pings, exchange-rate requests, and the purchase check, each described below.
Information you give us
Except for messages you send us, the information below reaches us only if you sign in, which needs Purrse Plus.
| Data | Examples |
|---|---|
| Sign-in details | Your email address. If you use Google or Apple, the account identifier and email address they share with us (Apple may give us a private relay address). We never receive your Google or Apple password, and Purrse never asks you for a password. |
| Profile | Your display name, the cat you pick as your avatar, and your base currency. |
| Accounts | Names and types of the accounts you add (cash, bank, credit card, wallet), currency, opening balance, and optional details such as a card limit, bill and due day, payment methods, a UPI ID, or the last 4 digits of a card. |
| Entries | Expenses, income, transfers, loans and repayments: amount, date and time, account, category, payment method and any note you write. |
| People | Names you enter for people you lend to or borrow from. |
| Categories | The categories you turn on, rename or create. |
| Where you heard about Purrse | The app may ask you once, after you've added a few entries. If you answer, we store the one-word answer (for example “friend” or “instagram”) with your account. You can dismiss the question. |
| Messages to us | Anything you send us by email, such as a support request, or with Me → Report a problem in the app. |
Please don't store full card numbers, CVVs, PINs, bank passwords or anyone's sensitive information in notes. Purrse never asks for them. When you add people to track IOUs, only enter what you're comfortable storing about them, such as a first name.
Information collected automatically
To keep the service running and secure, our hosting provider records basic technical logs when the app talks to our servers, such as IP address, request time, and device and app version. These logs are used only for security and troubleshooting.
If you're signed in, our server keeps a few timestamps for your account: when you last opened the app, when you last signed out, when your last entry reached the server, when you finished setting up the app, and when you logged your first entry. The last two are recorded once, on any plan, even if your entries stay only on your phone: we receive the time, never the entry itself. We use these timestamps to remind you to come back if you go quiet, and to understand how many people get started with Purrse. Apart from the crash reports and anonymous counts described below and the sign-in time our login service keeps for every account, nothing else about how you use the app is recorded, and these timestamps are deleted with your account.
When the app crashes or hits an error, it sends a crash report to Sentry: what went wrong in the code, your device model, operating system and app version, the screens you opened and buttons you tapped just before, and, if you're signed in, your Purrse user ID (a random code, not your email). Crash reports never include your entries, balances, notes or email address, and the app records no video of your screen. They're used only to find and fix bugs.
Before we email you a sign-in code, in the app or on the account deletion page, Cloudflare Turnstile checks that the request comes from a person and not a bot. Cloudflare receives your IP address and technical signals from your device and browser to do this. It doesn't receive your email address or any of your Purrse data, and the check isn't used for advertising.
Anonymous counts
We keep two counts, and neither is tied to you. First, links like purrse.in/go/instagram pass through our website on the way to the app or the waitlist, and we add one to the count for that link name, along with whether the visitor was on Android, iPhone or something else. Second, the app sends an anonymous ping to purrse.in the first time it is opened after you install it, the first time each setup screen is shown, when you finish setting it up, when you log your first entry, and the first time you open it again on a later day and a week or more later. Each is sent at most once per install. It also sends a ping the first time you open it each day, each week and each month, and the first time each day and each month you use each part of the app (for example, open Stats or set a budget), so we can count how many phones use Purrse and each of its features, without knowing which ones. These say only which part it was, never what you entered. A ping carries only which of those steps it is, your platform (Android or iOS) and the app version. It sends no email, account ID, advertising ID or device ID, and nothing about your entries. Both counts are stored as aggregate numbers in Cloudflare Analytics Engine. We don't store your IP address with them.
The iPhone waitlist
If you join the iPhone waitlist on purrse.in, we store your email address, your platform and the link you came from (for example, the instagram in purrse.in/go/instagram, or “direct”). Cloudflare Turnstile checks the form to keep bots out. We use Resend to send you one confirmation email when you join and one email on the day Purrse launches on iPhone. Every one of these emails has an unsubscribe link, and using it removes you from the list.
Emails we send
Besides sign-in codes and exports you ask for, we send a few account emails through Resend: a note if a payment fails, a note when you cancel, and a monthly spending recap. You can switch these off from the unsubscribe link at the bottom of any of them, and we keep a record of what we sent you and when so we never send the same note twice. Emails from Purrse include a postal address for Abbas Anandwala, Baramati, India, because anti-spam law requires one.
Purchases
Subscriptions and the Lifetime plan are sold through the Apple App Store or Google Play and managed with RevenueCat. We receive your purchase status (for example, active plan, trial and renewal dates). Before you sign in, the app checks it with RevenueCat using a random anonymous ID that has no email address or name. Once you sign in, your status is linked to your Purrse account, and RevenueCat also holds your email address and display name next to your Purrse account ID, so we can find your subscription when you contact us. We never see your card or payment details; Apple or Google handles payment.
What we don't collect
We don't access your bank accounts, SMS, contacts, photos, location, microphone or camera. The app contains no advertising identifiers, ad networks or behaviour-tracking SDKs. The only analytics are the anonymous counts described above.
The website
purrse.in is a static website. It sets no cookies and runs no advertising or behaviour-tracking scripts. To see which pages are read, which sites send visitors and how fast pages load, it uses Cloudflare Web Analytics, which counts page views without cookies, without fingerprinting and without following you across sites or visits. Fonts are loaded from Google Fonts, which receives your IP address to deliver them. Our web host keeps standard server logs.
3. How we use your data
- To provide the app: on your phone, run Purrse with the data you enter. If you have Purrse Plus and sign in, also sign you in, back up your data, sync it between your devices and restore it when you change phones.
- To manage your plan: check whether you have an active subscription, trial or Lifetime plan.
- To keep Purrse secure: prevent abuse, fix bugs and protect accounts.
- To talk to you: send one-time sign-in codes, answer support requests, email you about a failed payment, a cancellation or your monthly recap, email you about the iPhone launch if you joined the waitlist and, rarely, tell you about important changes to the service or this policy.
- To see what's working: use the anonymous counts and your where-you-heard answer to learn which links bring people to Purrse, so we know where to spend our time.
- To meet legal obligations, such as tax and accounting records for purchases, and lawful requests from authorities.
We process your data because you asked us to provide the app (performance of our agreement with you, and your consent when you sign up), because of our legitimate interest in keeping the service secure, and to meet legal obligations. We do not sell your personal data, share it for advertising, or use your financial entries to profile you or train AI models.
4. Who we share it with
We share data only with service providers who help us run Purrse, under contracts that limit their use of it to providing their service to us:
| Provider | What for |
|---|---|
| Supabase | Database, sign-in and hosting for your account and, with Purrse Plus, your backed-up and synced data. Not used for your entries if you never sign in. |
| Google and Apple | "Continue with Google" and "Sign in with Apple", if you use them. App distribution and payment. |
| RevenueCat | Checking and managing your subscription status. Receives your Purrse account ID, email address and display name. |
| Sentry | Crash and error reports, and problem reports you send from the app, so we can fix bugs. |
| Frankfurter and ExchangeRate-API | Daily currency exchange rates for multi-currency totals. They receive an ordinary web request from your device (including its IP address) and none of your Purrse data. |
| Cloudflare Turnstile | A bot check before sign-in codes are sent and on the waitlist form, to stop abuse. |
| Cloudflare Analytics Engine | Stores the anonymous link-click and once-per-install app counts. No names, emails or identifiers. |
| Cloudflare Web Analytics | Cookieless page-view counts for purrse.in: which page, the referring site, country, browser type and page load speed. No cookies and no cross-site tracking. |
| Resend | Sending your 6-digit sign-in codes, an export of your entries to your account email when you ask for it in the app, the account emails described above, and the iPhone waitlist emails. It receives the recipient address and the email itself. |
| Cloudflare R2 and GitHub | Storing our encrypted daily database backups. They hold only encrypted files and can't read your data. |
| Web host | Serving the purrse.in website. |
We may also disclose data if required by law, to protect the rights and safety of our users or the public, or as part of a merger or acquisition, in which case this policy will continue to protect your data.
Some of these providers process data outside India. When they do, we rely on their contractual commitments and security measures to keep your data protected, and we only transfer data to countries that Indian law permits.
5. Storage and security
- On your phone. Purrse stores your data on your device first so it works offline. On the free plan this is the only place it is stored. Your sign-in session is encrypted with a key kept in the iOS Keychain or Android Keystore. Android cloud backup of app data is turned off.
- On our servers. Only if you sign in with Purrse Plus (or still have an account from before). Data is sent over encrypted connections (HTTPS) and stored with our database provider. Every table is protected by row-level security, so the server only lets you read and change your own rows.
- Backups. Once a day we take an encrypted snapshot of the database so your data can be recovered if something goes wrong. Snapshots are encrypted before they leave the database, with a key only we hold, and are stored in Cloudflare R2 for up to 180 days and as GitHub Actions run files for up to 90 days. Neither provider can read them.
- On sign-out. If your plan is syncing, pending changes are uploaded, then your data is removed from the device.
No system is perfectly secure, but we work to protect your data and will notify you and the relevant authorities of a personal data breach as the law requires.
6. Retention and deletion
Free plan. Your data lives only on your phone and is never sent to our servers. Purrse keeps all of your entries on the phone. The free plan shows the last 30 days; older entries remain stored on the phone and become visible again with Purrse Plus. Entries that versions 2.3 and earlier cleared automatically cannot be restored. Past months are a Purrse Plus feature. We hold no copy, so uninstalling the app removes it, and you can export it first under Me → Export.
When Plus ends. If your subscription is cancelled or expires, or a free trial ends without payment, sync stops. We keep your cloud copy for 30 days, so if you subscribe again everything is restored. After 30 days we automatically delete the cloud copy of your entries, accounts, people, categories, recurring items, streak days and wardrobe, and clear the app settings stored in your account. Accounts that existed before the free plan and have no plan get 30 days from the release of the update that introduced it. Copies of the deleted data stay in our encrypted daily backups until they expire, at most 180 days later. Your account itself (your name, email address and plan history) stays until you delete it.
Deleting your account. You can delete your account at any time in the app under Me → Delete account. This permanently deletes your profile, accounts, entries, people and categories from our servers immediately. If you no longer have the app, request deletion at purrse.in/delete-account: we confirm the request is yours with a code sent to your account email, then delete your account and data within 30 days. Your data stays in our encrypted daily backups until they expire, at most 180 days after the deletion. Copies in our providers' own encrypted backups are overwritten on their normal backup cycle. We may keep limited purchase records where the law requires, such as for tax. You can also email us and we'll delete your account for you. We keep a short record of each deletion request (the email address, dates and outcome) to show it was handled.
When you delete a single entry, we clear its note, category, person and payment method straight away, and keep only its amount, account and date, marked as deleted, so your other devices know to remove it too. That marker goes when you delete your account. Crash reports and problem reports are deleted automatically within 90 days. Your where-you-heard answer and our record of which emails we've sent you go when you delete your account. To leave the iPhone waitlist, use the unsubscribe link in any waitlist email and your row is deleted. The anonymous counts hold no personal data, and Cloudflare keeps them for about three months. Uninstalling the app removes data from your phone but does not delete your cloud account or any cloud copy that is still within its 30 days.
7. Your rights
Depending on where you live, you have the right to:
- access the personal data we hold about you and get a summary of how it's processed;
- correct or update it (most of it you can edit directly in the app);
- delete it, or withdraw your consent, which you can do by deleting your account;
- get a copy of your data in a portable format (you can do this yourself at any time in the app under Me → Export, as a CSV or PDF, saved to your phone, or with Purrse Plus emailed to your account address);
- nominate someone to exercise your rights if you die or become unable to;
- raise a grievance with us, and if you're not satisfied, complain to the Data Protection Board of India or your local data protection authority.
To use any of these rights, email privacy@purrse.in from the address linked to your account. We'll reply within 30 days.
8. Children
Purrse is intended for people aged 18 and over. We don't knowingly collect data from children. If you believe a child has created an account, contact us and we'll delete it.
9. Changes to this policy
We may update this policy as Purrse changes. We'll change the date at the top, and if the changes are significant we'll tell you in the app or by email before they take effect.
10. Contact and grievances
Questions, requests or complaints about privacy: privacy@purrse.in. Our grievance officer can be reached at the same address. For anything else: hello@purrse.in.