Privacy

Your book is stored under your account so it survives a lost phone. It is not sold, not shared with advertisers, and not used to build a profile of you. You can export everything as plain text at any time, and deleting your account deletes the contents with it.

PrendzBook is run by an independent developer. For anything on this page, including any request about your data, write to prendzbook@gmail.com.

Your account

An email address and a password. The password is stored only as a salted hash by our authentication provider — it is never readable, by us or anyone else. We also keep the date the account was created and when it last signed in.

Your profile

Whatever you choose to put on your card: name, an optional nickname, city, phone numbers, email addresses and social handles. Gender is optional and has an “undisclosed” option. Your profile also holds a share token, which is the random value behind your QR code, and your per-field sharing preferences.

Your date of birth. Onboarding asks for it, and it is optional — the year especially, which you can leave out. It is stored so friends who scan your code can be reminded of your birthday. It is shared on your card by default. A date of birth is also half of what some organisations use to verify identity, so if you would rather not hand it out, turn it off under What’s on my card. Every other field on the card works the same way.

The people you add

For each person in your book: their name and nickname, phone numbers, emails and social handles, city, where you knew them from, dates you have noted, tags, and whatever you write in the notes and “how we met” fields.

What is never stored

• Photographs. There are none anywhere in the app, of you or of anyone in your book. Everyone is shown as initials on a colour derived from their name.
• Your phone’s contact list. Importing contacts reads them on your device so you can pick people from a list. Only the ones you actually select are saved, and nothing is uploaded in the background.
• Location. The app never asks for it. “City” is a text field you type.
• Payment details. The app is free and takes no payments.

Most of what PrendzBook stores is information about other people, entered by you. That is the point of the product, and it carries a responsibility: you are the one deciding what to record about someone, and you should only keep details they would reasonably expect a friend to keep. If someone asks you to remove them from your book, please do — and if they contact us directly, we will help you act on it, but their entry is yours and we do not edit it on anyone else’s behalf.

Your QR code contains only the fields you have chosen to share. Scanning it opens a pre-filled form on the other person’s phone — nothing is saved until they save it, and what they then write about you belongs to their book, not yours.

If someone added you by scanning your code, the two entries stay linked. When you change your details you can offer the update to those people; each of them chooses whether to accept it. Your notes about them, and their notes about you, are never part of that exchange.

You can regenerate your share token at any time from the app. Every code you have previously shown or that has been screenshotted immediately stops resolving.

• Camera — only to scan a QR code. Nothing is recorded or uploaded, and the scanner reads QR codes only, never other barcode formats.
• Photos — only if you scan a code from a picture you already saved, such as one a friend sent you. The picture you pick is read on your device to find the code in it, and is not uploaded or kept.
• Contacts — only when you open the import screen, and only to show you a list to choose from.
• Notifications, and alarms on Android — only for birthday reminders. The app schedules them on your device, and reschedules them after a restart, which is why Android asks about exact alarms. No reminder data leaves your phone to make them work.

Every one of these is optional. Declining any of them leaves the rest of the app working.

Your book is stored on your device and in a hosted Postgres database, with per-account isolation enforced by the database itself. We use a small number of service providers, none of which receive your data for their own purposes:

• Supabase — hosts the database and handles sign-in.
• Brevo — sends verification and password-reset emails. It receives your email address and nothing from your book.
• Sentry — receives a crash report if the app fails, and only in builds where crash reporting is switched on. Personal data is disabled at the source, network request details are stripped before a report is sent, and passwords are never included.
• Vercel — hosts this website. Its analytics are cookieless and count page views, not people. They do not run inside the app.

These providers operate servers in several countries, so your data may be stored or processed outside the country you live in. They act on our instructions and may not use your data for their own purposes.

We do not sell your data, share it with advertisers, or use it to train anything. There is no advertising in the app and no third-party analytics inside it.

Your book is kept as long as your account exists — that is the promise the product is built on. When you delete your account, the account and everything attached to it is removed from the live database straight away.

Entries you delete inside the app are marked as deleted first, so the deletion reaches your other devices, and are then cleared.

Our hosting provider keeps routine backups of the database for its own disaster recovery. Deleted data can persist in those until they are overwritten on the provider’s normal cycle. We do not restore deleted accounts from them.

• See everything. The app shows you the whole book; there is no hidden record beyond what is described here.
• Take it with you. You → Export, as CSV or vCard, any time.
• Correct it. Every field is editable in the app.
• Delete it. From inside the app, or see deleting your account.

Depending on where you live you may have further rights over your data. Write to prendzbook@gmail.com and we will help.

Traffic between the app and our servers is encrypted in transit, and the database is encrypted at rest by the provider. Passwords are stored only as salted hashes. Access to the account that administers the database is limited to the developer and protected by two-factor authentication.

No system is perfect. If a breach ever affects your data, we will tell affected users and the relevant authority as quickly as we can, and say plainly what happened and what to do about it.

PrendzBook is not intended for children under 13, and the app should not be used by anyone under that age. If you believe a child has created an account, write to us and we will remove it.

If this policy changes in a way that affects what is stored or who can see it, the date at the top changes and the app will tell you. Small corrections happen without notice.

For anything about your data — a question, a correction, a deletion, or a complaint about how it has been handled — write to prendzbook@gmail.com.

The same address reaches the person responsible for grievances, who is the developer of the app. We aim to acknowledge within 48 hours and resolve within 30 days. If you are not satisfied with the outcome, you may raise it with the data protection authority where you live.