Privacy policy

Purrsave helps you organise personal money and a small shop. This notice explains what the app stores, which choices are optional and where to ask for help. Purrsave does not sell your data or use advertising trackers.

What you provide, and why

• Your account: an email and sign-in information let you access and recover your account. Your chosen display name, avatar and preferences personalise the app. A photo is optional; you can choose an icon instead.
• Your records: transactions, accounts, bills, budgets, goals, debts, notes and shop records provide the tracking and calculations you request. Enter only the customer or other personal details your own records need. Purrsave does not ask for your bank-login password.
• Support: submitting Contact sends your message, optional reply email and a contact-specific random identifier together to Purrsave’s database. The identifier limits repeated submissions and is separate from analytics. A reply email is needed if you want a response; do not send passwords, full card numbers or unnecessary documents.
• Public contributions: posts, comments and images you choose to submit to the ideas board are public. Do not put private financial records or somebody else’s personal information in them.

Account storage and access

Supabase provides the hosted database, sign-in and file storage. Your records are not kept only on your device. Requests use HTTPS. Database access rules separate private account records from other users; this is not a promise that every upload or public post is private, or that any system is immune to a security incident.

The operator can technically access database records. The existing commitment is to inspect your private financial records only for support or debugging and with your consent. Routine automated processing is still needed to save, sync and calculate the records you ask the app to handle.

Images, receipts and backups

Profile photos and custom logos use public image links. Choosing a file uploads it before you save the surrounding form. Anyone with its link can view it. Resetting an avatar or cancelling a form does not delete that upload. Use an icon if you do not want to upload an image. Ideas-board images are public too.

Receipt images and automatic CSV backups use private storage. Downloads use time-limited links; someone you share a valid link with may be able to open it. The app can create a monthly transaction backup when you open it. Deleting or editing a transaction does not rewrite older backup files. Keep downloaded exports secure: the app cannot remove copies from your files or another person’s device.

Your browser and offline work

Browser storage remembers your session and preferences. While signed in, IndexedDB can hold a copy of your own records and pending changes so you can work offline. Those changes are sent to your account when syncing succeeds. Signing out runs local offline cleanup; if the browser prevents it, clear site data after checking that your work has synced. Clearing storage first can lose unsynced work.

Sample mode does not create this signed-in financial snapshot. App files are cached for offline loading. Read Cookies & browser storage for the storage keys, their purposes and how to remove them.

Optional reminders

If you enable push notifications, Purrsave stores the subscription endpoint, delivery keys, account association, language and timezone to send reminders. Your browser’s push service delivers the messages. Bill reminders can include bill names, amounts and currencies; weekly recaps can include entry counts. These notifications may appear on your device’s lock screen. You can turn reminders off in Settings and manage notification permission in your browser.

Optional usage counts

Purrsave’s own usage counts stay off until you allow them in Privacy choices. They help understand first visits, later returns, sample use, signup and setup, a first saved transaction, and first use of adding, one-tap or planner tools. Stored markers avoid repeatedly counting the same step while those markers remain.

An event contains its action name, a random browser identifier, hour-rounded time, screen-size group and referring site name. The analytics payload does not include your account ID, email, typed content or money amounts. A persistent random identifier is not a guarantee of anonymity, and rounding the time does not make correlation impossible.

Do Not Track and Global Privacy Control signals stop these optional counts. Turning them off stops future events and removes their browser keys, not past server events or financial records. The choice applies to this browser, not every device. Service providers still receive connection information such as IP addresses when handling requests.

Services the app connects to

• Supabase: account, records, uploads, contact messages and permitted usage events.
• Cloudflare: website delivery and security. Production also has a separate Web Analytics script for page and performance statistics; the app’s Privacy choices currently controls its own counts, not this hosting script.
• jsDelivr: code libraries. Fonts are served from purrsave.com itself.
• Simple Icons: brand images. An image URL you supply also connects your browser to that image’s host.
• ExchangeRate-API and Frankfurter: exchange rates. These requests include a base currency code, not a list of your transactions.
• Your browser’s push service: delivery of notifications you enable.

External-resource requests can disclose an IP address, browser headers and the requested resource to its host. Providers may process technical logs under their own terms, potentially outside your country. This notice does not promise that they keep no logs. Links you follow to other websites are covered by those sites’ notices.

Keeping and deleting information

Account records are stored so you can return to them until you remove them or successfully delete the account. Account deletion removes the sign-in account and linked private records. File cleanup can fail, and deletion does not automatically remove public posts, comments, support messages, previously received usage events or copies already downloaded or shared.

No automatic expiry is currently configured by the app for retained support messages, public contributions or usage events. Monthly backups are separate snapshots, not live mirrors of the transaction list. For removal of a public contribution, an old upload or other retained information, contact support and identify the item without sending unrelated financial records.

Your controls and questions

You can edit records, export account data, change optional choices and start account deletion from Profile and Settings. Exporting account data is not a complete export of support messages, public contributions or provider logs. Where applicable law provides rights of access, correction, deletion, restriction, objection or portability, use the contact form to make a request. Include a reply email so the request can be discussed and, when needed, your account ownership verified.

You may also have a right to complain to your relevant data-protection authority. No wording here removes rights that apply by law.