Can't reach the server
It may be waking up after sitting idle. Nothing you have saved is lost.
If the server answers on its own, this page will load by itself.
Legal notice
Privacy Policy
What is collected, where it is kept, who can read it, and how to get it back out.
The short version
- Your records are read by you and nobody else. Every query is filtered by your account at the database layer.
- Nothing about you is sold, shared or profiled. There is no advertising here and nothing to advertise with.
- There is no analytics, telemetry or crash-reporting code in either app. No third party is told you opened it.
- Your password is never stored — only a one-way hash of it.
- You can export everything, whenever you like, without asking.
Who holds your data
Personal Manager is maintained by Divyaprakash. On the copy run by the author, he is the one responsible for the data it holds, and the contact for any question about it.
The app is also built to be self-hosted. If you are using a copy installed by somebody else, your records sit on their server and they are the ones holding them — this page describes what the software does with your data, which is the same everywhere, but it cannot speak for how any particular operator runs their machine.
What is collected
Only what the app needs to be the app. There is no profile of you assembled from anything else.
Because you have an account
- Your email address — your sign-in id, and where account mail is sent.
- A display name — what the app calls you. It need not be your real name.
- A one-way hash of your password — never the password itself.
Because you entered it
- Transactions, transfers, accounts, categories, tags, budgets and recurring entries, with any notes and attachments you add.
- Notes, diary entries, tasks and their checklists and reminders.
- Vault items — stored only as ciphertext, as set out below.
- Your settings: theme, time zone, the day your week starts on, and so on.
Because a server has to run
- Ordinary technical logs, which can include your IP address, the time of a request and what went wrong. They exist to find faults and are not used to build any picture of you.
- An authentication cookie or token, so the app knows it is still you between one screen and the next.
No advertising identifiers, no device fingerprinting, no location, no contacts, and no tracking cookies. The app sets no cookie whose purpose is to watch you.
What it is used for
Showing your records back to you and doing the sums you asked for. That is the whole of it. Specifically, your data is used to run your account, to total and chart what you entered, to sync between your devices, to send the account mail listed below, and to produce the exports and backups you ask for.
It is not used to train anything, not sold, not rented, not shared with advertisers or data brokers, and not handed to anyone else except where the law actually compels it.
What is encrypted, and what is not
Sealed. Vault entries and exported backup archives are encrypted with AES-256-GCM under a key derived from your passphrase using PBKDF2-HMAC-SHA256. A backup file that leaks is a blob of ciphertext, not a readable list of your accounts.
Not sealed. Everything else — your transactions, notes, diary and tasks included — is stored as ordinary rows that only your account can query. They are protected by that boundary and by HTTPS in transit, not by a second passphrase. The vault is the place for secrets.
On Android and Windows the app's own copy of the database sits inside the operating system's private storage for the app, and the whole file is encrypted with SQLCipher.
Who can read it
Only you
Every query the server runs is filtered by the signed-in account at the database layer, not by the screen you happen to be on. A request that asks for someone else's transaction gets nothing back, whoever sends it.
Not even the author, for your vault
Vault items are sealed before they reach the server, under secrets that are never sent to it. Somebody holding the database sees ciphertext and nothing else.
An administrator, in the narrow sense
Whoever runs the server can see accounts exist and can reach the database the ordinary rows live in — that is true of every hosted app, and pretending otherwise would be the dishonest version. It is the reason the vault exists.
No third parties
Neither the website nor the Android app contains an analytics, telemetry, advertising or crash-reporting SDK. There is no profile of you anywhere to sell.
The few things outside the app
Three, and each is named rather than hidden behind “service providers”.
- Email. Account mail is sent over SMTP through the mailbox the server is configured with. It goes out when you verify an address, reset or change a password, change your email, or are issued a vault recovery code — and at no other time. There is no marketing mail, and there is no list to be on.
- Google Drive, only if you connect it. Backups stay on your own device or in your own downloads folder unless you link a Drive account yourself. When you do, the archive goes to your Drive, still encrypted, and the token that permits it is itself encrypted before being stored. Disconnect whenever you like.
- A payment provider, only if you choose to tip. If the copy you use offers the voluntary support page, any payment is handled by that provider under their own terms. The app is not told anything about you in return, and nothing in it behaves differently afterwards.
The offline vault lives behind your PIN
An encrypted copy of your vault is only ever kept on a device that has the app's PIN lock switched on, because a copy sitting on a phone cannot be locked out or wiped remotely the way the server can — the lock screen is what stands in front of it. Turn that PIN off and the copy is deleted in the same moment, before the lock goes. Not marked stale, not left for later: removed. Your vault on the server is untouched, and a new copy is one tap away whenever you set a PIN again.
How long it is kept
- Your records — for as long as your account exists. The app deletes nothing behind your back.
- Things you delete — removed when you remove them. Sync tells your other devices to do the same.
- Technical logs — kept only as long as they are useful for finding faults, then rotated away.
- Backups you made — yours, wherever you put them. The app cannot reach into your Drive or your downloads folder to tidy up after you.
Your rights, and the buttons that exercise them
Most of these are controls in the app rather than requests to a department, which is the point.
- See what is held — it is the app. Every record is on a screen you can already open.
- Take a copy — Import & Export for Excel, CSV or PDF; Backups for an encrypted archive of everything.
- Correct it — edit any record, and your email and display name in Profile settings.
- Delete it — delete any record at any time. For the whole account at once, see the note below.
- Object or ask a question — write to Prakash3300@gmail.com.
Account deletion is not yet self-service: the app has no button that erases an account and everything in it. Until it does, ask at Contact Us and it will be done by hand. Export anything you want to keep first — deletion is not reversible.
Children
The app is not aimed at children, and accounts are not knowingly created for them. If a child's account has been set up without a parent's involvement, write to the address above and it will be removed.
Changes to this policy
This page is updated when the app changes in a way that affects it, and the date at the top moves with it. No change will be made that starts selling, sharing or profiling your data — if that were ever on the table, the honest thing would be to stop running the app instead.
The rest of the small print
- Terms & Conditions The agreement between you and the app: what you may do with it, and what is asked of you.
- Copyright & Licences Who owns the app, and the open-source work it is built on.
- Disclaimer The limits of what the app promises, and what it is not a substitute for.
- Contact Us How to reach the person who maintains the app, and what to include.