Flobit Privacy Policy
Last updated: 17 August 2026
This policy explains what personal data Flobit collects, why, who we share it with, and what you can do about it. We've tried to write it so you can actually read it.
Two things worth knowing up front:
- We don't track you. No analytics SDK, no crash reporting, no advertising, no third-party trackers, no data brokers. We don't have a business model that needs it.
- Your Apple Health data never leaves your phone. We read it on your device to show you a number, and that's where it stays.
And one thing we want to be straight about rather than bury: your messages are stored on our servers and we are technically able to read them. We don't do so routinely — §3 and §10 explain exactly when we do and why.
Languages. We publish this policy in English, Azerbaijani, Russian, Turkish and Spanish. If a translation and the English version ever disagree, the English version is the one that applies — translations are provided so the policy is readable, not to change what it says.
1. Who is responsible for your data
Flobit MMC, a limited liability company registered in the Republic of Azerbaijan, at 8 November 42, Baku AZ1000, Azerbaijan, is the data controller for the personal data described here.
Contact us about anything in this policy at [email protected].
This policy covers the Flobit iPhone app, the Apple Watch app, widgets and Live Activities, and the flobit.app website. Our Terms of Service govern your use of all of it.
2. The short version
| What | Why | Can you skip it? |
|---|---|---|
| Email, password or Apple/Google sign-in | To have an account | No |
| Username, name, photo, bio | To be recognisable to other players | Name and photo, yes |
| Gender | Match formats and fair pairing | No |
| Height and weight | Calorie estimates for your matches | Yes — both optional |
| Country and city | Finding players and venues near you | No |
| Your location, when you search nearby | To find venues close to you | Yes — search by city instead |
| Sports, skill level, ELO, match history | The core of the product | No |
| Sportsmanship ratings you give and receive | So players can see who is good to play with | Yes — you can hide yours |
| Messages | To deliver them and keep them across your devices | Don't send them |
| Community and tournament activity | To run them | Don't join |
| Push token | To send notifications | Yes — decline notifications |
| Reports you file | Keeping players safe | Don't file them |
| Apple Health data | Calorie figures. Stays on your device | Yes — decline Health access |
3. What we collect, and why we're allowed to
Under the GDPR we need a lawful basis for each use. Here they are, honestly labelled.
Your account — necessary to perform our contract with you
Email address, and either a password we store only as a hash, or an identifier from Sign in with Apple or Google. Account creation and last-activity timestamps.
If you use Sign in with Apple, Apple may give us a private relay email address instead of your real one. That works fine — we never need your real address.
Your profile — contract, and consent for the optional parts
Username, display name, first name and surname, bio, profile photo, country, city, and profile visibility setting.
Gender is required, because match formats and fair pairing depend on it.
Height and weight are optional. We use them only to estimate calories for your matches. Leave them blank and everything else works; you just won't see a calorie figure. You can remove them at any time in profile settings.
Your sport — contract
Sports you play, self-declared skill levels, ELO rating per sport, matches created, played, scored, or officiated, scores and per-period results, teams, communities, tournaments, registrations, and trophies.
Match records involve more than one person. A match you played is also part of your opponents' history. Section 9 explains what that means when you delete your account.
Sportsmanship ratings — legitimate interest in players being able to judge who to play with
After a match, you can rate the people you played against from one to five stars on sportsmanship — whether they were good to share a court with. It is not a rating of how well they play; ELO covers that.
We store who rated whom, for which match, the number of stars, and when. We show the person rated an average on their profile, alongside how many ratings it is based on.
Some specifics worth stating plainly, because this is data about a person written by another person:
- You can only rate opponents, never teammates or your doubles partner, and never a guest.
- Individual ratings are never shown to anyone, including the person rated. Only the average and the count are public. We do not disclose who gave which rating — see §11.
- The average is deliberately conservative. A single rating does not produce a 5.0 or a 1.0 profile; early ratings are weighted toward the overall average across Flobit and converge on the true figure as more arrive. Repeatedly rating the same person does not add weight — the people you play most often cannot dominate your number.
- You can hide yours. Profile settings has a switch that removes both the average and the count from everyone else's view. Yours stays visible to you.
- You have 48 hours to change a rating, then it is fixed. This exists so a rating given in frustration can be reconsidered, and so nobody can go back months later and rewrite the history of someone they have fallen out with.
If you don't want to be rated at all, you can hide the number, but we can't stop someone forming an opinion about a match you both played — the same way we can't remove the match itself from their history.
Your messages — contract, and legitimate interest in player safety
Direct messages and community or tournament group chats are encrypted in transit and encrypted at rest on our servers. They are stored on our servers so that your conversations follow you — sign out and back in, or set up a new phone, and your history is still there.
We are technically able to read message content. We do not do so routinely, and we do not sell it, use it for advertising, or share it with anyone for their own purposes. We access message content only when:
- someone reports a message and we need to review it;
- the law genuinely requires it; or
- it is necessary to protect someone from serious harm.
We also necessarily hold the surrounding information: who sent a message to whom, when, and delivery and read receipts.
If that trade-off isn't one you want, don't send it in a message.
A note on what changed. Earlier versions of Flobit encrypted direct messages end-to-end, which meant we could not read them — and also meant your messages were lost whenever you signed out or changed phone, and could not be moderated when reported. We changed it so your history follows you and so we can act on reports. We think that's the right trade for an app where people arrange to meet strangers, and we'd rather tell you plainly than not mention it.
Your location — consent
Two different things happen, and they're worth separating.
Setting your city. If you tap "Use my location", your device works out your country and city on the device itself and we keep only the country and city — never the coordinates.
Finding venues near you. When you search for courts or pitches nearby, your device sends your coordinates along with that search so we can return what's close. We use them to answer the search. We don't build a location history, we don't track your movement, and we never run location in the background.
Suggesting a venue. If you add a new venue, the venue's location is saved as part of that venue's listing — that's the point of it, and it stays with the venue, not with you.
You can decline location entirely and pick your city from a list instead.
Photos and images — contract, and consent for library access
Profile photos, community and tournament images, and share cards you build. Uploaded images get a content-hashed, immutable URL, so a given image address stays valid while it's cached or referenced.
Saving a share card to your photo library uses an add-only permission — we cannot see or read your photo library.
Apple Health — consent, and it stays on your device
Covered fully in section 8.
Your device — legitimate interest in delivering and securing the service
A push notification token from Apple and Firebase, a Firebase installation identifier, app version, OS version, device model, and language. Server logs including IP address and request timestamps, kept for security and debugging.
We do not collect an advertising identifier, and we do not ask for App Tracking Transparency permission, because we don't track.
Reports and moderation — legitimate interest in player safety
When you report a profile, message, community, or post, we receive what you reported, the reason, any detail you add, and your identity as the reporter.
Guest players — legitimate interest in recording a match honestly
Flobit lets you add a guest — someone who played but has no account. We store the name entered, attached to that match, and nothing else. No account, no profile, no contact details. Guests are never rated and never rate anyone.
If you add a guest, you're confirming you have their permission. If you're a guest and you'd rather not appear, email [email protected] and we'll remove or anonymise the name.
4. What we don't do
- No advertising, and no sale of personal data. Ever.
- No analytics or crash-reporting SDK. No PostHog, no Sentry, no Firebase Analytics, no Google Analytics, no Meta SDK, no attribution SDK.
- No tracking across apps or websites, and no data brokers.
- No reading your messages for advertising, training, or curiosity. See §3.
- No profiling with legal or similarly significant effects. Your ELO is a sports rating and your sportsmanship average is other players' opinion — neither is a decision about you, and neither is made automatically about anything that matters legally.
- No selling or sharing in the sense of the CCPA/CPRA.
5. Who we share data with
We share only what's needed to run Flobit, and only with these service providers, each bound by a data processing agreement.
| Provider | What it handles | Where |
|---|---|---|
| Railway | Our application servers, database, and self-hosted realtime service | EU region |
| Cloudflare (R2) | Stores and serves uploaded images | Global network |
| Resend | Sends transactional email — password resets, verification | United States |
| Google (Firebase Cloud Messaging) | Delivers push notifications | United States |
| Google (Sign-In) | Only if you choose Google to sign in | United States |
| Apple | App Store, Sign in with Apple, push delivery, Apple Health on your device | Global |
We also share data with other players — but only what you choose to show them, governed by your profile visibility setting, and with the people you play, message, or share a community with.
We may disclose data where the law genuinely requires it, or to protect someone from serious harm. We'll tell you when we're allowed to.
We do not sell your data, and we never will.
6. Where your data lives
Our servers, database, and realtime service run in Railway's EU region, so your core data stays in the European Economic Area.
Some providers in section 5 — Cloudflare, Resend, and Google — process data in or from the United States. For those transfers we rely on the European Commission's Standard Contractual Clauses, and on the EU–US Data Privacy Framework where a provider is certified under it.
If you'd like more detail on the safeguards for a specific provider, ask us at [email protected].
7. How long we keep it
| Data | Kept for |
|---|---|
| Account and profile | As long as your account exists |
| Match records | As long as your account exists — then anonymised, not deleted, because opponents share them |
| Sportsmanship ratings you received | As long as your account exists — deleted with it |
| Sportsmanship ratings you gave | Kept after your account is deleted, with your identity removed — see §9 |
| Messages | As long as your account exists, or until you or the recipient deletes them |
| Reports and moderation records | Up to 2 years after resolution, so repeat behaviour is visible |
| Server logs with IP addresses | Up to 90 days |
| Backups | Overwritten within 30 days |
When you delete your account, we remove or anonymise your personal data from live systems straight away. Backups are overwritten on their normal rotation and are fully purged within 30 days.
8. Apple Health
Your Apple Health data is the most sensitive thing Flobit touches, so this is spelled out.
What happens on your device. When a match ends, the Flobit app looks at Apple Health for that match's window: energy already recorded, your step count, and whether a workout was already saved. It uses that, plus your weight, height, and how the match went, to show a calorie figure and to avoid saving a duplicate workout.
What we save. Flobit saves an estimated workout to Apple Health only when your phone was actually on you during the match, so its step data reflects how you moved. It does not save a figure worked out from a phone left on the bench, and it does not save one when a workout for that time already exists — whether your watch recorded it or another app did. You can turn saving off entirely in Flobit's settings.
Because Apple Health totals energy from every app, workouts Flobit saves may count toward your Activity rings.
What never happens. Your health data is never sent to our servers. Not calories, not steps, not heart rate, not workouts. There is no field for it in our API. It is never used for advertising, never sold, never shared with any third party, and never used for anything but showing you your own number on your own device.
Estimates are estimates. They're calculated from published figures for how demanding each sport is. They'll be wrong for you by some margin. None of it is medical or fitness advice.
You're in control. Flobit's settings have a switch for saving match workouts, and you can revoke Flobit's access to Apple Health entirely at any time in Apple's Health app. Everything else keeps working — you'll still see an estimate based on how long you played, just a rougher one. Workouts already saved stay in Apple Health and you can delete them there yourself; deleting a match in Flobit does not remove a workout it already saved.
9. Deleting your account
Delete your account yourself, any time, in Settings → Account. No email, no waiting on us. It's permanent, and we say so before you confirm.
Three honest limits:
- Matches you played stay in your opponents' history, with your identity removed. We can't erase someone else's record of a game you both played.
- Messages you sent stay in the recipients' conversations. Deleting your account removes your side of it, not theirs — the same way an email you sent doesn't vanish from someone's inbox when you close your account.
- Sportsmanship ratings you gave stay, with your name removed. A rating you gave is information about the person you rated, not about you, and removing it would quietly change their public number because you left. The rating keeps counting toward their average; we detach it from you, so nobody can tell it was yours. Ratings you received are deleted along with your profile — they described you, and you're gone.
We may keep a minimal record that an account was removed, and moderation records where someone's safety depends on it.
10. Reporting and moderation
You can report a profile, a message, a community, or a post from inside the app, and you can block any player. Reports go to our moderation queue and we review them.
Where a report concerns a message, reviewing it means reading that message. That is the point of the report, and it's why §3 says we're able to.
Unfair ratings. If you believe a sportsmanship rating was given in bad faith — retaliation after an argument, or someone rating you for a match they weren't part of — report the player and say so. We can remove ratings and restrict a player's ability to give them. Blocking someone does not remove a rating they gave you: we deliberately don't let the person being rated delete ratings they dislike, because a number you can edit by blocking people isn't worth showing.
We may remove content, hide it, limit its reach, restrict features, suspend an account, or terminate it — where our Terms have been broken, where the law requires it, or where someone's safety is at stake.
11. Your rights
Wherever you live, you can ask us to:
- See the personal data we hold about you
- Correct anything wrong — most of it you can edit directly in the app
- Delete your data — you can do this yourself in Settings → Account
- Export your data in a portable format
- Restrict or object to how we use it, including anything we do on the basis of legitimate interests
- Withdraw consent you've given, such as location or Apple Health access — without affecting what we did lawfully beforehand
Email [email protected]. We'll respond within 30 days. We won't charge you, and we won't make the app worse for you because you asked.
One limit, stated in advance: sportsmanship ratings about you. If you ask what ratings you have received, we will tell you the average and how many — the same figures your profile shows — but not the individual ratings or who gave them. When only a few people have rated you, a single rating identifies its author, and that author's identity and opinion are their personal data too. We can't disclose one person's data to satisfy another's request. If you believe a rating was given in bad faith, §10 is the route.
Complaints. If you think we've handled your data badly, tell us first — most things are faster to fix by email. If you're in the European Economic Area or the United Kingdom, you also have the right to complain to your national data protection authority, wherever you live or work.
12. Security
- Everything in transit is encrypted with TLS.
- Message content is encrypted at rest on our servers.
- Passwords are stored as hashes, never as text.
- Access tokens live in the iOS Keychain, not in ordinary storage.
- Staff access is limited to what's needed for support and moderation, and reading message content is restricted to the situations in §3.
No system is perfectly secure. If we ever suffer a breach affecting your data, we'll tell you and the relevant authority as the law requires.
13. Children
Flobit is for players aged 13 and over. We don't knowingly collect data from anyone younger.
If you believe a child under 13 has an account, email [email protected] and we'll remove it.
14. Permissions Flobit asks for
Every one is optional, and every one is a genuine feature. Decline any of them and the rest of Flobit still works.
| Permission | What it's for |
|---|---|
| Notifications | Match invites, score updates, messages, tournament news |
| Camera | Scanning a match QR code to join |
| Location (while using) | Setting your country and city, and finding venues near you. Never in the background |
| Photo library (add only) | Saving a share card. We can't read your library |
| Calendar (write only) | Adding matches and tournaments. We never read your calendar |
| Apple Health | Calorie figures — see section 8 |
15. Marketing email
Right now we send transactional email only — password resets, verification, and account notices. You can't opt out of those, because they're how your account works.
If we ever send marketing or newsletter email, it will be opt-in, and every message will carry a one-click unsubscribe. We won't add you to a list because you signed up.
16. The flobit.app website
The website exists to host these legal pages and basic information about Flobit. It sets no analytics or tracking cookies, so there's no cookie banner. If that changes, we'll update this policy and add proper consent first.
17. Changes to this policy
When we make a material change, we'll tell you before it takes effect — in the app, by email, or both — and update the date at the top. Minor clarifications take effect when posted.
18. Contact us
Flobit MMC
8 November 42
Baku AZ1000
Azerbaijan
Email: [email protected]
Real questions get real answers. If something here is unclear or looks wrong, tell us.
Play more. Get better. A bit at a time.