Rook — Privacy Policy

Last updated: 23 August 2026

---

The short version

Rook keeps your training records on your device. There is no account, no sync, no advertising, and no analytics. GhostLabs cannot see your records and has no way to retrieve them.

Four optional features involve something outside the app, and each is off until you turn it on. Three of them send data off the device. The fourth — reading Apple Health or Health Connect — sends nothing anywhere; it reads into the app and stores no measurement. All four are described in full below, and two of them differ between Android and iPhone.

Who is responsible

GhostLabs (the "we" in this policy) is the controller for the processing described here.

• Address: Stuttgart-Ost, Stuttgart, Germany
• Email: ghostlabsoftware@gmail.com
• Web: https://ghostlabs.click

What stays on your device

Everything you enter: your profile, training schedule and attendance, journal entries and photos, techniques and game map, competitions, instructor questions, body measurements, coaching memories, and every app setting.

This data is stored in the app's private storage. It is not uploaded, backed up to us, or shared. On iPhone and iPad it is additionally marked as excluded from iCloud Backup, so Apple never carries a copy either — which also means a replaced device starts empty unless you exported a backup file yourself. We never receive it, so we cannot access, export or delete it on your behalf — you delete it by erasing your data in Settings or removing the app. A backup file you export yourself goes wherever you choose to put it, and from that point it is in your keeping.

The four optional features

Each is off until you turn it on, and each is described in full. The first three send something off your device. The fourth does not — it reads health records into the app and sends nothing anywhere; it is here because it is optional and because it touches sensitive data, not because it transmits.

1. Rook Live voice — off until you consent

While a Live session is open, your microphone audio is streamed through Firebase AI Logic to Google's Gemini service to produce the coach's spoken replies, together with a text briefing assembled from the minimum of your own records needed to answer — for example your next session, or the week you have just had.

• Nothing is sent when a session is not open. The microphone closes when you stop talking.
• Consent is explicit, is asked before the first session, and can be withdrawn in Settings at any time. Withdrawing ends any open session.
• Content is processed by Google under the terms attached to our Firebase and Gemini project. Under some no-cost Gemini terms Google may use submitted content to improve its products. Do not use Live voice for anything you would not want handled on those terms.
• Legal basis: your consent, Art. 6(1)(a) GDPR. Where you speak about injuries or health, that is health data and the basis is your explicit consent, Art. 9(2)(a) GDPR.

2. Reporting an AI response — Android only, and only when you send a report

If a generated reply is wrong or unsafe you can report it. A report sends the selected response, the model name, the reason you picked, an optional note you write, the app version, and timestamps to our Firebase project. This feature exists on Android only; the iPhone and iPad app has no equivalent and sends nothing to that project.

It does not attach microphone audio, your prompt, or your saved records. Because Rook has no account, a report is not linked to an identity; you receive a random reference you can quote if you later want it deleted.

• Purpose: reviewing safety and quality of generated replies.
• Legal basis: your consent, Art. 6(1)(a) GDPR, given by sending the report.
• Retention: 30 days, after which it is deleted.

3. Public competition calendar — only when you open that screen

Opening Rook's competition calendar makes one anonymous HTTPS request to Smoothcomp's public event listing so upcoming tournaments can be shown. No account, no identifier and no record of yours is sent, and cookies are disabled for the request. As with any web request, Smoothcomp's servers will see your device's IP address; we do not receive it, and Smoothcomp is not acting for us.

Nothing is kept until you pick a tournament as your own, which copies its name, dates and location into a competition record on your device.

• Legal basis: our legitimate interest in showing you a public calendar you asked to see, Art. 6(1)(f) GDPR.

4. Apple Health and Health Connect — off until you grant it

If you grant access, Rook reads a recent window of your own health records to show context beside your training, and to offer to mark a recorded workout as a session you attended. This reads only. Rook never writes to Apple Health or Health Connect, and it never sends a health measurement anywhere — not to us, not to Google, not to Gemini, not to anyone. Nothing here is used for advertising, profiling or any automated decision, and none of it is ever sold or shared.

What is read differs by platform, because the two systems hold different things:

Reading happens only while the relevant screen is open. Rook does not run in the background to collect anything, does not schedule reads, and asks for no background-delivery permission on either platform.

No measurement value is ever stored. What Rook reads lives in memory for as long as the screen is open and is gone when you leave it. It is not written to the app's database, does not appear in a backup file you export, and cannot be recovered afterwards — by you or by us.

There is exactly one exception, and it stores no measurement. If you confirm that a recorded workout was one of your planned sessions, Rook writes a small link record — which source the workout came from, its identifier, its start and end times, and which session you matched it to — so the link is visible and reversible. It stays on your device like any other record, is included when you erase your data, and carries no heart rate, no weight and no sleep figure.

Rook does not read reproductive or cycle health data. An earlier build could ask for it; that was removed on 23 August 2026 because Rook had nothing useful to do with it, and asking for a sensitive category in order to display it back unchanged is a cost to you with no benefit.

• Legal basis: your explicit consent, Art. 9(2)(a) GDPR — health data is a special category under Art. 9(1) — together with Art. 6(1)(a) GDPR. You are asked before anything is read, and no part of the app is withheld if you decline.
• Withdrawing: on Android, in the system's own Health Connect settings. On iPhone and iPad, in Settings ▸ Health ▸ Data Access & Devices ▸ Rook. You can also switch the feature off inside Rook, which stops reading immediately and drops what was on screen; note that this does not revoke the system permission, and Rook says so where you switch it off.
• One thing iOS will not tell us, and we will not guess. Apple deliberately does not report which health categories you allowed an app to read — only which you allowed it to write — because the refusal would itself reveal something about you. So on iPhone and iPad Rook genuinely cannot know what you granted, and no screen there claims a count. A category you refused and a quiet fortnight look identical to the app.

Who else processes data

Health data appears nowhere in this table, and that is the point. Nothing read from Apple Health or Health Connect is sent to any recipient, including as part of a Live session briefing.

Google acts as our processor for these services and may process data outside the EU/EEA, including in the United States. Those transfers rely on the European Commission's standard contractual clauses and Google's own transfer framework commitments.

We use no advertising network, no analytics SDK, no crash reporting service and no cloud sync. We do not sell or share data for advertising, and no automated decision-making with legal effect takes place.

How long we keep things

We hold nothing about you except AI-response reports, which are deleted after 30 days. Data on your device stays until you delete it. Health measurements are held by neither of us: they are not stored on your device either, and exist only for as long as the screen reading them is open.

Permissions

• Microphone — only during a Live session you start.
• Notifications — local training and recovery reminders; nothing leaves the device.
• Network — Live voice, the public competition calendar, and AI-response reports on Android.
• Apple Health (iPhone / iPad) — read-only, as described above. Rook requests no permission to write to Health and no background-delivery permission.
• Health Connect (Android) — read-only, as described above.
• Start after boot / package update (Android) — restoring reminders you enabled.

Rook does not request location, contacts, an advertising identifier, or access to your photo library beyond images you attach yourself.

Your rights

Under the GDPR you may request access, rectification, erasure, restriction, portability, or object to processing, and you may withdraw consent at any time without affecting what was lawful beforehand.

In practice, most of this you exercise directly: your records are on your device and Settings erases them. For AI-response reports, quote the reference you were shown to ghostlabsoftware@gmail.com. We respond within one month.

You may also complain to a supervisory authority, in your country of residence or place of work, or where you believe an infringement occurred.

Children

Rook is not directed to children under 13, and is not intended for anyone below the age of digital consent in their country without the consent of a parent or guardian.

Changes

If this policy changes materially we will update the date above and, where the change concerns a feature you have consented to, ask again in the app.

Contact

ghostlabsoftware@gmail.com