Privacy Policy
Last updated: November 7, 2026
In short: your records are stored on your phone. In app versions with records on the server (currently the TestFlight beta), once you sign in with your email they are also stored on our server in Russia; until you sign in, they stay only on your phone. In versions without records on the server (currently the App Store version), your records do not reach the developer. We keep your records only for you: we do not use them for advertising and do not sell them. There are no ads in the app. Apart from your records and the details behind a client link, the only things that leave the app are anonymous usage statistics (you can turn them off in the app’s settings), crash reports and subscription information — never the names, phone numbers, notes or amounts in your records. An account is created when you sign in with your email: it holds your email and, if you pay on the website, payment details.
What you keep in the app
Clientberry is an app for tracking clients, sessions and payments. You enter the following yourself:
- clients: last name, first name, phone number and notes;
- price plans, session packages and their prices;
- sessions: dates, times, attendance and reschedules;
- payments and outstanding balances;
- expenses, calendar notes and workout programs.
Only you enter this data. The app does not read your contacts, photos, location, camera or microphone and does not ask for access to them.
Where the data is stored
- On your device. All records are kept in the app's storage on your iPhone.
- In your iPhone backup. Records are included in the regular device backup (to iCloud or to a computer), according to your iPhone settings.
- On our server. In versions with records on the server, your records are stored there once you sign in with your email, for as long as you have an account (see “Records on the server”).
The app makes no copies in iCloud Drive and no backup files. The developer has no access to your iPhone backups; storing them in iCloud is governed by Apple's Privacy Policy.
What the developer receives
Three kinds of anonymous information. None of them contains your records: no client names or phone numbers, no notes, no rate names, no prices or amounts. Separate from them are all your records, if you use a version with records on the server (see “Records on the server”), and the information about clients you sent a link to (see “Your clients' data”).
Usage statistics
Only while they are on (Settings → Usage statistics in the app). They help us see which screens people use and what to improve. The app sends to the PostHog analytics service (servers in the European Union):
- which screens are opened, and actions such as “onboarding finished”, “client added”, “rate added”;
- numbers about the size of your records: how many clients, sessions, rates and expenses;
- phone model, iOS and app version, language, and a random install ID that groups events from one phone together.
The app does not record the screen or collect text from it. The IP address is used only to determine the country and is not stored.
Crash reports
When the app crashes or runs into an error, it sends a report to the Sentry service (servers in the United States) so we can find and fix the cause. The report contains:
- the type of error and the place in the app’s code where it happened;
- the app version and build, phone model, iOS version and technical details about the device at the time (such as free memory).
The error text is erased before sending, because it could contain data from your records. The report has no screenshot, no history of taps or actions, no device name and nothing about you. Sentry does not store the IP address. Crash reports have no separate switch: without them we would not know that the app fails to open for someone.
Purchases
Clientberry sells its subscription through the App Store, and purchases are handled by the RevenueCat service (servers in the United States). Each time it starts, the app asks RevenueCat which subscriptions are available and whether yours is active. For this, the RevenueCat SDK creates a random install ID. It does not contain your Apple ID and is not the same as the ID used for statistics. If you subscribe, your App Store purchase history goes to RevenueCat: which subscription, the dates of purchase and renewal, and the store country. Payment is handled by Apple: neither we nor RevenueCat ever see your card details.
Like any internet request, requests to RevenueCat carry technical details: IP address, phone model, iOS and app version, language and region.
Email account
An account is needed for records on the server and for paying for Pro by card on our website. You sign in with your email: a sign-in code is sent to it. The account is created the first time you sign in with a code, whichever way you sign in (for example, through “Already have Pro? Sign in”). The account stores your email, the date it was created and fingerprints of your sign-in keys (the keys themselves cannot be recovered from them) and, if you pay on the website, the chosen plan, payment dates and the bank’s payment IDs — to know until when Pro is paid. It is stored in Yandex Cloud (Russia); code emails are sent by Yandex Cloud Postbox. Payments are processed by Tochka Bank: your card details never reach us.
If you sign in to the account in the app, it asks our server every few hours whether Pro is paid. This request carries only the sign-in key: it contains no records, clients or amounts.
Who else
PostHog, Sentry, RevenueCat, Yandex Cloud and Tochka Bank process this information on our behalf. We do not share it with anyone else, do not link it to your identity and do not use it for advertising. There is no cross-app tracking and no advertising identifier.
Records on the server are stored on our behalf by the hosting provider Webhost1 (Russia) and by Yandex Cloud (Russia), which holds the encrypted database backups. The server’s disk at Webhost1 is not encrypted, so Webhost1 also technically has access to your records. The database backups in Yandex Cloud are encrypted, and Yandex cannot read them. See “Records on the server” for details.
If you allowed “Share With App Developers” in your iPhone settings, Apple may provide us with anonymized crash reports and usage statistics. These are collected by Apple, not by the app, and contain none of your records. You can turn this off in Settings → Privacy & Security → Analytics & Improvements.
Records on the server
In app versions with records on the server (currently the TestFlight beta; the App Store version will get it in an update), your records are stored on our server once you sign in with your email — the same account as for paying on the website. The app offers to sign in when it starts; you can put this off, and until you sign in your records stay only on your phone and never reach us. After you sign in they are kept both on your phone and on the server, and this cannot be turned off separately. If you sign out, your records stay on the phone and stop going to the server.
Your phone stays the main copy. The app works without internet, and changes go to the server once you are back online. Records are sent over an encrypted connection (HTTPS). When you sign in with your email on a new phone, your records come back to it from the server.
What goes to the server
- all your records: clients (last name, first name, phone number, notes), rates and prices, packages, sessions and group sessions with attendance marks, payments and refunds, expenses, calendar notes, workout programs with their goals and comments, the workout log with the client’s wellbeing score (1 to 10) and comments, and the details of links you sent to clients;
- record settings: your name, currency, language, theme and tracking rules;
- your phone’s time zone, so the server knows what “today” is;
- the early access mark, if you have it;
- the phone’s platform (iOS or Android) and the data format version. The server gives the phone a random ID and a key to recognize it by, and remembers when the phone last connected;
- an upload log: when, from which phone and how many entries changed. The log does not contain the data itself;
- the history of moved and cancelled planned sessions: the date and time before and after. The server keeps it itself from the changes it receives, to show them in the client section.
Your records are linked to your email. The email itself is not in the records database: it holds a code derived from the email instead. The records server learns who is signed in from the account service in Yandex Cloud (see “Email account”).
Where and how it is stored
There is currently one records server: a virtual server at the hosting provider Webhost1 in Russia, running a PostgreSQL database. The database is closed to access from the internet, but it is not encrypted on disk: both the developer and the hosting provider Webhost1, where the server runs, are technically able to read your records. The server keeps no request log: neither request contents nor IP addresses are written to it.
Every hour the server makes a backup of the database, encrypts it and puts it in Yandex Cloud storage (Russia). The decryption key is not on the server; the developer keeps it separately. The server erases backups older than 7 days when it makes the next backup. If backups are failing, old ones are not erased and stay longer, until backups work again.
The server also keeps snapshots of your records so they can be restored as a whole: once a day if your records changed, and before each replacement of the records on the server. Snapshots are stored on the same server at Webhost1 and are not encrypted either. They are kept for 14 days. So if you replaced the records on the server with your phone’s, support can bring back the previous ones for 14 days.
A deleted client or other entry is kept on the server in full for 14 days so it can be restored. After that, the client’s name and phone number, notes, workout programs and logs are erased. In the database backups, the erased data stays for up to 7 more days (longer if backups are failing). What remains of deleted entries (dates, amounts, names of rates and expenses) and the upload log are deleted after about six months. The history of moved and cancelled sessions is kept for 90 days.
What we use it for
Only to store your records, deliver them to your phone, return them when you sign in with your email, and restore your previous records if you ask support to. Every night the server automatically checks your records for inconsistencies, such as more sessions used from a package than it had, and logs only the codes of any problems found, with no names or amounts.
We do not use your records for advertising, do not sell them, do not link them to usage statistics and do not share them with third parties. The exceptions are Webhost1 and Yandex Cloud, which store them on our behalf, and cases where the law requires it.
Deletion
Deleting your account — in the app or on the website’s payment page — immediately erases your records from the server, together with the snapshots, the upload log and the history of moves. They disappear from the encrypted database backups no earlier than 7 days later, when those backups are erased (later if backups are failing). If during those days the database has to be restored from a backup as a whole (this happens only after a server failure), your deleted records come back to the server with it. Write to us and we will erase them again. The records on your phone stay and no longer go to the server; if you sign in with your email again, they will be saved to the server again.
If you move from the beta to a version without records on the server, your records stay on the server until you delete your account. You can do that on the website’s payment page, whichever version of the app you have.
Your clients' data
You keep information about your clients yourself, for your own work: you are the controller of this data. The developer stores it only on your behalf — in records on the server — and does not use it for its own purposes. Apart from that and what is described below for the client link, the developer does not receive it. You are responsible for keeping this data lawfully (including obtaining your clients' consent where the law of your country requires it) — just as with a notebook or a spreadsheet. Please do not record diagnoses or other medical information about your clients — neither in notes nor in comments: Clientberry has no fields for it and will not add them.
You can send a client a link to their sessions. You send it yourself, through your own messenger or email. The link itself holds their first and last name and your signature, in the part a browser does not send to the website, so names do not reach the developer through the link. Anyone who has the link can see them.
So that the client's data updates by itself, the app sends our server (Yandex Cloud, Russia) information about the clients you sent a link to: a random record number, rate type, package size, sessions left, price, currency and session dates. It is stored as plain text, with no names, phone numbers or notes, and the developer does not link it to a specific person. Anyone who has the link can read the record. It is deleted with the client in the app, and deletes itself after 400 days without updates.
If your records are stored on the server, the records server also returns a summary of that client’s package and sessions for the random number in the link — again with no names, phone numbers or notes.
Deleting data
- You can delete a client from their card. Deleting the app erases all records from the device; records on our server stay.
- Copies that earlier versions of the app saved to iCloud Drive or as files stay where they are until you delete them: iCloud copies in the Files app (the “Clientberry” folder) or in Settings → [your name] → iCloud → Manage Storage, files wherever you keep them.
- Records on the server are erased when you delete your account: from the server itself immediately, and from the encrypted database backups no earlier than 7 days later (see “Deletion”). The records on your phone stay.
- The account is deleted in the app (Settings → Clientberry Pro → Delete account) or on the payment page. Deleting it turns off auto-renewal and erases the email, subscription history and records on the server.
Children
The app is intended for adult professionals — trainers, tutors, teachers — and is not directed at children. We do not collect information about children.
Changes to this policy
If the app ever starts sending anything beyond what is described here, we will update this page and the date above first, and ask for your consent in the app where the law requires it.
Contact us
Privacy questions: support@getclientberry.com
See also our Terms of Use.