The short version
- You can use Scorby without an account. Scoring, your match history and your statistics work signed out and offline. None of it reaches us.
- Your history is yours. It lives on your device, backed up to your own iCloud or your own Google backup — never to a server of ours. We cannot read it.
- Your heart rate and calories never reach us. They stay between Scorby and your phone's own health record — Apple Health, or Health Connect on Android — and, as part of your match history, they are in your own phone backup. Never on a server of ours, and never used for advertising. Section 4.
- An account exists for one reason: playing a shared match with someone else. That is the only feature that needs one, and it is the only place your matches pass through our server, because two phones cannot follow the same score without something in the middle. Section 6 says exactly what that holds. On Android, one other small thing reaches us and it is not a match: a one-way hash that keeps the free trial to one per device (section 8).
- No advertising, no trackers, no data sales. We do not track you across other apps or sites, so Scorby never shows you Apple's tracking prompt. The app counts anonymous usage — which sports get played, whether matches get finished — with no advertising identifier and nothing that can be tied back to you. See section 10.
- The app store takes the payments — Apple on iPhone, Google on Android. We never see your card, your billing address or your store account details.
A summary, not the terms. The sections below are what actually applies.
Who is responsible
Scorby is developed and provided by Sofia Eirini Petaloti, a registered sole trader established in Limassol, Cyprus, VAT registration number CY08054271S (“we”, “us”).
For the personal data described on this page, we are the data controller within the meaning of Regulation (EU) 2016/679 (the “GDPR”), as applied in Cyprus by Law 125(I)/2018.
You can reach us at info@scorby.app. We are not required to appoint a Data Protection Officer and have not appointed one; your enquiries come to the address above.
What stays on your device
Scorby is built to work without a server. Unless you deliberately start a shared match, everything below is stored only on your own phone and watch — iPhone, Apple Watch or Android alike — and we have no access to any of it:
- Every match you score — the point-by-point record, the final score, the date and how long it took.
- The names you type for your opponents and partners.
- Your statistics, your record against each opponent, and your streaks.
- Your settings and preferences.
You can play, keep a full history and read your statistics indefinitely without ever creating an account or connecting to anything.
Your own backup
So that a new phone does not arrive with an empty history, Scorby keeps a copy of your matches somewhere outside the app. Where that is depends on the phone — and in neither case is it a server of ours.
On iPhone and Apple Watch
Scorby mirrors your matches to your own private iCloud database using Apple's CloudKit. This is storage inside your Apple Account. It is not our server, and the design of CloudKit's private database means we cannot read it — not the scores, not the names, not anything else.
Two things are mirrored:
- Match summaries — around a hundred bytes each: the final score, the date, the duration, the opponent's name as you typed it. Synced whenever iCloud is available, because this is the record a player expects to find on a new device.
- Detailed match archives — the full point-by-point log, only if you turn on detailed analytics in Settings. This is off by default and you can turn it off again at any time.
Apple's handling of your iCloud data is governed by Apple's Privacy Policy, not by this one. Turning off iCloud for Scorby in your iOS settings stops the mirroring; your matches stay on the device.
On Android
Your match history never reaches a server we control. The copy on the phone, in the app's own database, is the record, and there is no mirror of it pointed at us. Two things sit underneath it, both operated by Google as part of the phone rather than by us:
- Android's own backup carries the app's database and its settings into your Google account's backup, so a new phone can restore your history before Scorby is first opened. It is the same mechanism that restores the rest of your phone, and nothing in it passes through us. Your sign-in state is deliberately left out, so a restored copy never arrives already signed in.
Worth knowing what it does not promise. Android runs this backup roughly once a day, and only when the phone is charging on Wi-Fi. A match played this evening may not be in it yet, and the phone gives you no way to see whether a backup exists or how old it is. It is a safety net, not a sync. - Signing in does not bring your history back. On Android your account exists for shared matches and nothing else — there is no copy of your history on our side to restore from, deliberately. Reinstalling and signing in gives you an empty history unless Android's own backup restores it.
- Export, which is the one you control — and it is a paid feature. Settings → History → Export writes your whole history to a file you keep: every match, its statistics and its point-by-point record, including the heart rate and calories. Import adds back anything missing without disturbing what is already there. It is the reliable route when you are changing phones on purpose — export before you switch, because it works the moment you ask rather than whenever Android next decides to run.
It needs an active paid subscription, and the free trial does not include it. We would rather say so here than have you plan around a button you cannot press. Your data is still yours either way: it is on your phone and in your own backup, and you can ask us at any time for a copy of anything our servers hold, free — see section 17. - Device-to-device transfer. When you set up a new Android phone from your old one, the same data is included in that direct transfer. It goes from your old phone to your new one; it does not go through us, and on this route it does not go through Google's servers either.
What is carried on both routes is the app's match database and its settings — your matches, your statistics, your preferences and where you got to in setup. Google's handling of your device backup is governed by Google's Privacy Policy, not by this one, and you can turn Android's backup off in your phone's settings.
The same sentence is true on both platforms. Your history is held by Apple or by Google, in storage that belongs to your account, and we cannot read it. The provider could — it is their storage, under their policy. We could not, even if asked.
One thing this section does not cover, so that it cannot be read as a contradiction. "Your history never reaches our server" is about your history. A shared match is different: while it is running, the points are written to our database so that every device can follow the same score, and we can read those. They are deleted after about 90 days. Section 6 sets out exactly what a shared match holds, and section 16 how long.
Your health record and motion
Health data
Scorby connects to your phone's own health record — Apple Health on iPhone, Health Connect on Android. If you allow it, it writes each match there as a workout, with the active energy your watch measured, and it reads back two figures: your average heart rate and your active energy. That is how a match you scored on your phone can still show what a watch on your wrist recorded.
Health data moves between Scorby and your own health record. It is never transmitted to us, never shared with anyone, and — as both Apple's and Google's rules require, and as we would do regardless — never used for advertising or marketing of any kind. Scorby never puts it in iCloud or on any server of ours; the figures are stripped out before a match is copied anywhere, and what travels instead is a reference that lets a new device read the numbers back out of your own health record.
Reading and writing are asked separately, and you can refuse either without losing the ability to score. Refusing the read simply means a match shows no heart rate; refusing the write means nothing is filed to your health record at all.
The read is deliberately narrow. Scorby looks only when you open a match you have already played that has a health session and is missing a figure — never in the background, and never across your record generally. It reads only those two figures, and only over the minutes that one match ran. On Android it does not write heart rate at all: your watch's own app already records those readings, and filing a second copy would just duplicate them.
Average heart rate and calories for a finished match are stored alongside that match on your device so the summary screen can show them. Being part of your match history, they are included in your phone's own backup — your iCloud or Google backup, described in section 3 — and in a transfer to a new phone. That backup is yours: it goes to your own Apple or Google account, not to us, and we cannot read it. They can be removed by deleting the match.
Withdrawing access, on either platform:
- iPhone — Settings → Privacy & Security → Health.
- Android — the Health Connect settings on your phone, or the Health Connect row in Scorby's own Settings. Health Connect may also ask a second time before Scorby can read anything older than the last thirty days; refusing that leaves everything else working and simply means older matches show no figures.
Motion data
On Apple Watch, Scorby can use the motion sensors to recognise a serve, so the score can move on without you touching the screen. That processing happens entirely on the watch, in the moment. The raw motion signal is not recorded, not stored and not transmitted. What survives is a count — how many serves were detected, and an average peak — kept with the match on your device.
Your account
An account is optional and exists for exactly one purpose: a shared match, where two or more people follow the same live score on their own devices. That needs a server, and a server needs to know whose match it is. Nothing else in Scorby requires you to sign in.
We offer Sign in with Apple only. When you use it, we receive:
- A user identifier issued by Firebase Authentication, which is what our security rules use to decide what you may read and write.
- Your name, if you choose to share it — used as your display name so the other players know who is who.
- Your email address. If you use Apple's Hide My Email, this is a relay address ending in
privaterelay.appleid.comand we never learn your real one. We store the address so the account screen can show you which account you are signed in as.
Authentication is operated for us by Google (Firebase Authentication) as our processor. We never receive your Apple Account password, and we cannot use Sign in with Apple to learn anything you have not chosen to share.
You can delete your account from inside the app at any time. See section 16 for what that removes.
Other people's names
Scorby lets you type in a player who does not have the app, so a doubles match with three phones between four people still works properly. When you do that, you are entering someone else's personal data — usually just a first name.
Please only enter a name that person would be comfortable with, and prefer a first name or a nickname over a full one. If someone asks you to remove their name from your matches, you can edit or delete those matches yourself; if their name is in a shared match, tell us at info@scorby.app and we will remove it.
If you are named in someone else's Scorby match and want that dealt with, write to us — you do not need an account, and you do not need to be a Scorby user, to exercise your rights.
Subscriptions and payments
Apple is the seller. Every subscription is bought through the App Store, and Apple handles the payment entirely. We never receive your card number, your billing address, or your Apple Account credentials — Apple tells us only that a subscription is active.
On your device, Scorby stores which subscription is active and, for the free trial, the date it began. The trial has to start once — otherwise deleting and reinstalling the app would hand out a second free run of it, and then a third. Its length is set out in the Terms. How that is prevented differs by platform, and on Android it is the one thing about the trial that involves us at all.
On iPhone: the date stays on the phone
The trial start date is kept in your device's keychain, which survives the app being deleted. It is a single date, it never leaves the device, we never see it, and it is removed when you delete the app's data.
On Android: a one-way hash reaches our server
Android has no equivalent of the keychain — every store the app can write to is wiped on uninstall — so the same trick does not work, and the anchor has to be held somewhere the app can find again after a reinstall. That is our server. Apart from a shared match (section 6), this is the only part of Scorby on Android that stores anything about your device with us, and it works like this:
This is live. The Android app has sent this hash since 6 September 2026. Everything described below is what happens today, not a plan — if any of it changes, this section changes with it.
- What is sent. A one-way SHA-256 hash of your device's Android ID, combined with a fixed, app-specific value before hashing. That value is not a secret — it ships inside the app and anyone who unpacks it can read it — and its job is narrower than secrecy: it means a list of Android IDs cannot be matched against our records by someone who does not also have our app. The identifier itself is never sent.
- What that hash can and cannot do. It cannot be read back into your Android ID. It is not, however, a magic trapdoor: Android IDs are short, so a party who already holds both our salt and one particular device's identifier could confirm that the two correspond. We would rather write that down than imply a guarantee the maths does not give.
- What is stored. The hash and the date the trial began — that is the whole record. No name, no email, no account: the trial starts before you have signed in to anything, and we would like to keep it that way. A truncated fragment of the hash and the start date are also written to our server logs, which are a separate store with their own retention (see section 16).
- What it is honestly. A stable pseudonym, and it is worth being precise about what it identifies. Since Android 8 the Android ID is scoped to the app's signing key, the user and the device together — so it is not a device-wide identifier shared with other apps, and this pseudonym cannot be lined up against any other app's records, even in principle. It also changes on a factory reset. So "per device" is really per installation identity. It is not used for anything but the trial — not advertising, not analytics, not linking to an account you make later. It is still a per-installation value on our server, so we treat it as personal data and list it in the tables below like everything else.
- Where it is. The record stays in the EU: both the database holding it and the function that writes it are in Google Cloud's
europe-west8region, in Milan. One part of the surrounding check is not EU-only — the app proves it is genuine through Google's Play Integrity service, which runs on Google's own infrastructure — so we claim the record rather than the whole interaction. The app cannot read or change the record itself; only the function can, which is what stops a device awarding itself a fresh trial. - How long. Indefinitely, with no expiry. This is deliberate and it is the honest awkward part: an anchor that expired would hand out a second trial, which is the whole thing it exists to prevent. So it stays.
- Legal basis, and the limit on erasure. Our legitimate interest in offering a free trial once per installation rather than repeatedly — Art. 6(1)(f). You can object under Art. 21, and you can ask us to delete the anchor at info@scorby.app. Because the hash can only be recomputed on the device it came from, we need the request to come from that phone — and after a factory reset or a move to a new handset the old value cannot be recomputed at all, which means an anchor from a device you no longer have cannot be found and therefore cannot be deleted. That is a real limit, not a policy, and you should know about it rather than be told about a right that cannot always be exercised.
Apple's handling of your purchase is governed by Apple's Privacy Policy, and Google's by Google's.
This website
The website is a separate matter from the app. scorby.app sets no cookies, runs no analytics of any kind, and loads no advertising or tracking scripts. There is no consent banner because there is nothing to consent to. Web fonts are served by Google Fonts, which receives your IP address as part of that request; if you would rather avoid that, a content blocker will stop it and the page still reads correctly.
Our web server keeps ordinary access logs for security and troubleshooting, on the basis of our legitimate interest in keeping the site running.
The “Report a problem” form
If you send a bug report from this site, we receive what you typed, plus a short technical footer shown to you in the form before you send it: the page address, your browser's user-agent string, your screen size, your language and the time. If you give an email address, it is used to reply to you and for nothing else.
To stop the form being abused, our server keeps a one-way hash of your IP address for one hour, purely to count how many reports have come from one place. The address itself is not written down.
Anonymous usage counts
To know whether the app is any good, we count how it is used — how many matches get started and finished, in which sport, whether they were started on the phone or on the watch, and whether people get through setup. This is measured by Aptabase, an open-source analytics service, on servers in the European Union.
What the app sends. A short list of event names, with the app version, the operating system, the device model and your language attached, plus a session number that is generated fresh from the clock and a random value, and starts over after an hour of inactivity. No advertising identifier, no device identifier, no account, and nothing derived from any of them. No name, no score, no opponent, no match. The app is built so this cannot leak by accident: the only things it is able to send are a fixed list of events chosen in advance, and none of them has anywhere to put a name.
What we will not overclaim. Sending anything over the internet reveals your IP address to the server receiving it — that is true of every request your phone makes, and this one is no exception. Aptabase undertakes not to keep it: it uses the address only in the moment, combined with a salt it changes daily, and then discards it, which is what stops one day's activity being joined to the next. That is a commitment by the company processing the data, and we rely on it as their customer; it is not something the app itself can enforce.
Legal basis: our legitimate interest in knowing whether the app works and where it does not — Art. 6(1)(f). Because nothing here identifies you, there is no profile to object to and nothing to ask us for; if you would rather not send it at all, a content blocker or a firewall rule for eu.aptabase.com stops it and the app is unaffected.
When you contact us
If you email info@scorby.app or bug@scorby.app, we keep your message and address so we can answer, and so we can recognise a follow-up. We keep support correspondence for up to 24 months, then delete it.
If you sign up as a tester
Before Scorby can be published on Google Play, Google requires a closed test — a group of people who install the app and stay opted in for at least fourteen days. If you volunteer for that through the tester form, this section is what happens to what you typed. It applies to nobody else: if you have not filled that form in, none of this concerns you.
What we ask for, and why each one
- Your name, so we can tell one sign-up from another and write to you as a person.
- The Google account email signed in on your Android phone. This is the only way a Play closed test can work: Google sends the invitation to that account and to no other. It is passed to Google as part of the tester list — that is the whole point of collecting it, and it is the one piece of this that leaves us.
- Your phone's make, model and Android version, and whether you have a Wear OS watch, so we know which devices the app has actually run on.
- Which sports you play and how often, so we know which rulebooks are actually getting exercised and can ask the right people about the right things.
- Your club, or how you know about Scorby.
- A phone number or WhatsApp, only if you give one. It is used for a single reminder near the end of the test, so the free period is not held up. Nothing else, and never for marketing.
The form also records the date you submitted it and that you ticked the agreement box. That is our record that you consented, and we keep it for as long as we keep the rest.
Legal basis: your consent — Art. 6(1)(a). You gave it by ticking the box, and you can withdraw it at any time by writing to info@scorby.app. Withdrawing is not difficult and costs you nothing: we remove you from the tester list and delete the sign-up. It does not affect anything done before you withdrew, and it does not affect the app itself.
Who else sees it
Google, for the account email only, because a closed test is run through Google Play and the list of testers lives there. Google's handling of it is covered by Google's Privacy Policy, not by this one. Everything else you typed stays in our mailbox and goes to nobody.
How long
Until the closed test finishes and the free period that follows it has run out, and then no longer than three months. After that the sign-up is deleted and the address is removed from the tester list. If you ask for it sooner, sooner.
The feedback form
Twice during the test we will point you at a feedback form. It asks for the same Google account email, so we can tell whose answers are whose, and then for what you used, what broke, and what you would change. Everything on it except the email and two questions is free text, so what it holds is whatever you choose to type — please do not put anything in it you would not want us to read.
It runs on the same consent you gave at sign-up, it goes to the same mailbox, it goes to nobody else — not to Google; Google is told what we changed, not who said it — and it is deleted on the same schedule as the rest. Feedback you send us by email instead is covered by section 11, like any other message.
Legal bases
Under Article 6 of the GDPR, every processing activity needs a lawful basis. Ours are:
| What | Why | Legal basis |
|---|---|---|
| Your account | To let you use shared matches at all | Performance of a contract — Art. 6(1)(b) |
| Shared match records | To keep every device on the same score | Performance of a contract — Art. 6(1)(b) |
| Subscription status | To give you what you paid for | Performance of a contract — Art. 6(1)(b) |
| Trial anchor (Android only) | To offer the free trial once per device rather than repeatedly | Legitimate interests — Art. 6(1)(f). A one-way hash, never the identifier. See section 8 |
| Health and motion access | To show heart rate and recognise serves | Your explicit consent — Art. 6(1)(a) and Art. 9(2)(a), given through Apple's permission prompts and withdrawable at any time |
| Detailed match archives | To carry your full match logs between your own devices | Your consent — Art. 6(1)(a), given by turning the setting on |
| Anonymous usage counts | To know whether the app works and where it does not | Legitimate interests — Art. 6(1)(f). Nothing here identifies you. |
| Bug reports and support email | To answer you and fix what is broken | Legitimate interests — Art. 6(1)(f): running and improving the app |
| Rate limiting and server logs | To keep the service available and unabused | Legitimate interests — Art. 6(1)(f): security |
Where we rely on consent, you may withdraw it at any time — in your iPhone's privacy settings for Health and motion, or in Scorby's own settings for detailed archives. Withdrawing consent does not affect what was lawful before you withdrew it.
Who else is involved
We keep the list of companies touching your data as short as we can. It is:
| Who | What they do | Role |
|---|---|---|
| Apple | App Store distribution, payments, Sign in with Apple, iCloud, Apple Health | Independent controller for its own services |
| Google (Google Play, Android backup, Play Integrity, Health Connect) | Play distribution and payments, your own device backup on Android, the check that confirms the app is genuine, and your own on-device health record | Independent controller for its own services |
| Google (Firebase Authentication, Cloud Firestore, Cloud Functions) | Accounts and the shared-match relay | Our processor |
| Aptabase | Anonymous usage counts, on EU servers | Our processor |
| Our web host | Serves scorby.app and the bug-report form | Our processor |
We do not sell personal data, we do not share it with advertisers or data brokers, and we do not use it to build profiles or to make automated decisions with legal or similarly significant effects. We may disclose data if the law requires it, or to establish or defend legal claims.
Transfers outside the EEA
Shared match data stays in the European Union. Our Firestore database is hosted in Google Cloud region europe-west8, which is in Milan, Italy. The matches, the names and the point-by-point events described in section 6 are stored there and are not transferred out of the EEA.
Our server-side code runs in the same place: the function that erases an account when you ask us to is deployed to europe-west8 as well, so deleting your account is handled inside the EU too. The Android trial anchor described in section 8 is written and stored in the same region. The anonymous usage counts described in section 10 go to Aptabase's European servers and stay there.
One thing does leave the EEA. Firebase Authentication is operated by Google on infrastructure that includes the United States, so the identifier and email address described in section 5 may be processed there. That transfer is covered by the Standard Contractual Clauses adopted by the European Commission, incorporated into Google's Cloud Data Processing Addendum, together with Google's certification under the EU–US Data Privacy Framework.
Apple operates its own services globally under its own safeguards, described in its privacy policy.
You may ask us for a copy of the safeguards that apply, at info@scorby.app.
How long we keep things
| What | How long |
|---|---|
| Matches on your device | Until you delete them or remove the app. We are not involved. |
| Your own backup — your iCloud, or your Google account's backup | Until you delete the matches, turn the backup off, or remove Scorby's data from that account. Controlled by you, not by us. |
| Your account | Until you delete it in the app. |
| Shared match records | About 90 days from the start of the match, after which our server deletes the match and its point-by-point events automatically. Sooner if you delete your account or ask us to remove one. |
| Match invitations | The code stops working fifteen minutes after it is created — after that it cannot be used to join anything. The invitation record is deleted when the invitation closes or the match begins, and otherwise by our server's own deletion sweep, which runs on a best-effort basis and normally completes within a day of the code expiring. |
| Trial anchor (Android only) | Indefinitely. A hash that expired would hand out a second free trial, so it has no expiry. Ask us from the device and we will delete it — see section 8 for when that is not possible. |
| Server logs holding a truncated fragment of that hash | Kept with our other server logs on Google Cloud's own retention, and not used for anything but diagnosing the trial mechanism. |
| Support and bug-report email | Up to 24 months. |
| Hashed IP for rate limiting | One hour. |
| Anonymous usage counts | Kept as aggregates. They identify nobody, so there is nothing in them to delete on request. |
| Web server access logs | Up to 30 days. |
Deleting your account in the app removes your identifier, your entry and your name from every shared match you are in, and deletes any match where you were the last one left, together with its point-by-point events and any invitations you created. Your own history stays on your own device and in your own backup, because it is yours; delete the app, or the matches, to remove that too.
Expiry costs you nothing. The shared match record is a live channel between devices, not your record of the game. Every player's own app files the finished match into its own history when it ends — so when the server copy expires, your matches, your statistics and your record against each opponent are exactly as they were. The only thing that goes is a connection that closed months ago.
Because deletion is a background process, it usually happens within a day of the 90 days elapsing rather than at the exact moment.
Your rights
Under the GDPR you have the right to:
- Access the personal data we hold about you, and receive a copy.
- Rectify data that is wrong or incomplete.
- Erase your data — the app's own account deletion does most of this immediately.
- Restrict processing in certain circumstances.
- Object to processing based on our legitimate interests.
- Portability — receive your data in a structured, machine-readable format. Ask us and we will send you everything our servers hold about you, as a file, free of charge and whatever your subscription status. Exercising a right under the GDPR is never something we will charge for, and we will not ask you to subscribe in order to do it.
Separately, the app has an export feature that writes your whole match history to a JSON file without involving us at all. That one is a paid feature — see Terms, section 6. It is a convenience for moving your history between phones, not the mechanism by which you exercise this right, and it is not a substitute for it: your matches sit on your own device and in your own backup, where they are yours regardless, and the request route above is always open to you. - Withdraw consent at any time, where processing is based on it.
Write to info@scorby.app and we will answer within one month, as the GDPR requires. There is no charge unless a request is manifestly unfounded or excessive.
Complaints
If you think we have handled your data badly, please tell us first — it is usually the fastest way to fix it. You also have the right to complain to a supervisory authority, in the EU member state where you live, work, or where you believe the problem occurred. Ours is:
Office of the Commissioner for Personal Data Protection
15 Kypranoros Street, 1061 Nicosia, Cyprus
P.O. Box 23378, 1682 Nicosia, Cyprus
Telephone: +357 22 818 456
Email: commissioner@dataprotection.gov.cy
www.dataprotection.gov.cy
Security
Data in transit is encrypted with TLS. Shared match records are protected by server-side security rules that derive your identity from your authenticated session rather than from anything the app claims — a device cannot read a match it is not a participant in, and cannot add itself to one that is full. The raw motion signal never leaves your watch at all, and your heart rate and calories never reach any server of ours — the strongest protection available for them is that we do not hold them.
No system is perfectly secure. If a breach ever affects your rights, we will notify the Commissioner and, where the law requires it, you.
Age
Scorby is for people aged 16 and over, and we do not knowingly collect data from anyone younger. If you believe a child under 16 has given us personal data, write to info@scorby.app and we will delete it.
Changes
When this policy changes we will update the version and date at the top of the page. If a change materially affects how we use your data, we will tell you in the app before it takes effect, and where the law requires consent, we will ask for it rather than assume it.
Version history
- Version 1.5 — 28 September 2026
-
- A new section 12, for people who sign up as testers (section 12). Before Scorby can be published on Google Play, Google requires a closed test. If you volunteer for it, the form asks for your name, the Google account on your Android phone, your device, what you play, and optionally a phone number — so that section says what each is for, that the account email is passed to Google because a Play tester list is the only way a closed test works, that the basis is your consent and can be withdrawn by one email, and that it is all deleted within three months of the test ending. It applies to nobody who has not filled that form in. Sections that followed have moved up one number.
- The tester feedback form is named in the same section (section 12). Testers are asked for feedback twice during the test, on a form that repeats the Google account email so answers can be matched to a person and is otherwise free text. It runs on the same consent, is deleted on the same schedule, and — unlike the account email — none of it goes to Google: Google is told what we changed, not who said it.
- Version 1.4 — 11 September 2026
-
- Corrected what we said about export (section 17, section 3). Earlier versions said the app's export feature needed no subscription. That was wrong — export and import need an active paid subscription, and the 14-day trial does not include them. Your right to your data is unchanged and is not affected by this: ask us and we will send everything our servers hold, free, whatever your subscription status. The app's export is a convenience for moving history between phones, not the mechanism for exercising that right, and the two are now described separately.
- Version 1.3 — 9 September 2026
-
- Said what Android's backup does not promise (section 3). It runs about once a day, only on charge and Wi-Fi, and gives you no way to see whether a backup exists — so a match played this evening may not be in it. It is a safety net, not a sync. The section now also states plainly that signing in does not restore your history on Android: your account is for shared matches only and we hold no copy to restore from. And it points to Settings → History → Export, which is the route you control and the one to use before switching phones.
- Version 1.2 — 8 September 2026
-
- Said plainly that your heart rate and calories are in your own phone backup (section 4). Version 1.1 said they followed the same route as the rest of your history, which was true but easy to read past. They are part of your match history, so your iCloud or Google backup includes them, and so does a transfer to a new phone. That backup is yours and we cannot read it. The section now also states that Scorby never puts those figures in iCloud or on any server of ours — it strips them out and copies a reference instead, so a new device reads the numbers back from your own health record.
- Version 1.1 — 7 September 2026
-
- Health Connect named on Android (section 4). Scorby now also reads two figures — average heart rate and active energy — back from your phone's health record, so a match scored on the phone can show what a watch measured. The section says how narrow that read is: two figures, one already-played match at a time, over that match's own minutes, on your own device. Nothing about it is transmitted to us. The section was previously written in Apple terms only.
- The Android trial anchor is live (section 8). Version 1.0 described it as built but not switched on. It has been running since 6 September 2026.
- Version 1.0 — 4 September 2026
- First published.
Contact
Sofia Eirini Petaloti
Limassol, Cyprus
VAT CY08054271S
info@scorby.app