Privacy policy
In force from 10 October 2026
This is a translation. The Polish version is the binding one.
1. Controller and contact
The controller of your personal data (within the meaning of the GDPR) is:
- Trop Labs spółka z ograniczoną odpowiedzialnością
- Address: Rezydencka 11, 72-003 Grzepnica, Poland
- KRS: 0001270914 · Tax ID (NIP): 8513358509 · REGON: 545867719
- Registry court: Sąd Rejonowy Szczecin-Centrum w Szczecinie, XIII Wydział Gospodarczy Krajowego Rejestru Sądowego
- Share capital: 5 000,00 PLN
- Help: [email protected]
- Data protection matters: [email protected]
We have not appointed a data protection officer (we are not required to; we repeat this assessment as the service grows). For anything about your data, write to [email protected]. This policy covers gridhunt.app, the iPhone and Apple Watch apps, the Android and Wear OS apps, the Connect IQ apps (Garmin), the Karoo extension and the Integrations described in the terms.
2. What data we process
- Account: your name or display name, email address, profile picture (image address from the sign-in provider), language, the identifier from your sign-in provider (Strava, Apple, Google, Facebook), and your settings and consents (with dates). Others see the display name you set in Gridhunt (see Strava data and public features). We also store the date of your statement that you are at least 16 and, if you agree, the date and version of your consent to marketing emails.
- Activities: name, sport type, date, distance and GPS track. From the track we calculate claimed tiles and keep a simplified route to show you. We delete the raw GPS points of activities imported from other services after processing. For rides recorded in the Gridhunt iPhone app we keep the original file (GPX) so it can be reprocessed or sent to Strava. For each activity we record its source (e.g. the Strava API, an uploaded file, a recording in the Gridhunt app, a connected app), because the source decides where the activity may be shown.
- Heart rate and sensor data (only with consent): average and maximum heart rate, average cadence and power (if present), a downsampled heart-rate series for a chart, and the original ride file of rides recorded in a Gridhunt app (see Heart-rate data).
- Targets and routes: areas you want to claim and planned routes (GPX files).
- Integrations: your account ID and name in the connected service, the granted scope and access tokens (encrypted). We don’t know your passwords for these services.
- Devices: the name of a paired device (Garmin, Karoo, Wahoo), when it last connected and a hash of its token. During a ride the device sends its current position to fetch the tiles around you; we don’t store that position.
- Community: friendships, reports of “impossible” tiles, votes, comments and photos (we remove EXIF metadata, including where and when the photo was taken and the device model, on upload), and your leaderboard and public-link settings.
- Content reports and blocks: reports of content someone considers illegal or contrary to the terms (type and identifier of the content, reason, explanation, contact email, good-faith statement, decision, statement of reasons and dates), and the list of users you have blocked (see Content reports and blocking).
- Premium: your Stripe customer and subscription IDs, plan, status, period, country, amounts and receipts. We never see your card details.
- Technical and security data: event logs (sign-ins, settings changes, payments) with IP address, abuse-prevention counters (email address, IP) and server logs.
- Contact: the content of messages you send us (help, complaints, GDPR requests).
- Error reports and bug reports: when the Gridhunt app or website hits an error, we send a technical report with your consent: error type, stack trace, app version, device or browser model, OS version and your last steps in the app (e.g. screens opened). The report does not contain your email; we automatically remove email addresses, tokens and coordinates from it. Your ride’s position and state are included only if you tick “Include ride context”. You decide each time, or once for all in Settings → Privacy (“ask / always / never”). We link a report to your account only if you ask us to; you then see its status in “My reports”. Reports you submit yourself (description, device details, optional screenshot) are processed the same way; a screenshot is passed to the team as an attachment only with your consent. Legal basis for error reports: consent (Art. 6(1)(a) GDPR), which you can withdraw at any time in settings; for bug reports: performance of the contract (Art. 6(1)(b) GDPR).
- Reel texts (only with your consent to AI texts, “With humor” mode): the generated board texts and Instagram caption, together with the reel type (ride or season), its reference (the ride or the chosen years), style, language, model name, number of tokens used and the date, plus the date and text version of your consent. The texts are kept only so the same reel does not call the model twice; they are not added to your profile or statistics. In the event log we record when you give and withdraw consent and the generation event itself (style, language, outcome, model, token count), without the texts. Legal basis: consent (Art. 6(1)(a) GDPR), see Artificial intelligence.
3. Where the data comes from
Most data you provide yourself, or it is created when you use Gridhunt. Some comes from services you choose to connect:
- Sign-in: Strava, Apple, Google and Facebook give us your name, email (if they share it), profile picture and an identifier. Apple does the same for “Sign in with Apple” in the iPhone app (name only on the first sign-in; the address may be Apple’s private relay address).
- Activities: (1) your Strava connection via the Strava API (automatic import after you connect your account); (2) files and archives you upload (GPX, FIT, TCX, ZIP), including an account archive exported from Strava or Garmin Connect; (3) rides recorded in the Gridhunt apps (iPhone, Apple Watch, Android, Wear OS, Garmin Connect IQ); (4) other connected apps: Wahoo, Garmin Connect, Suunto, COROS, Polar, Ride with GPS, Hammerhead (some Integrations are in preparation). We delete uploaded files after processing, at the latest after 2 days; the activities and tiles calculated from them remain.
- iPhone and Apple Watch app: the GPS track of a recorded ride (also in the background while you record), and photos from the camera or library when you report a tile. The watch app reads your heart rate from Apple Health (HealthKit) to show it during the ride and saves the workout to Apple Health. Heart rate read during a ride goes into the ride file and, with your consent, into Gridhunt, as described in Heart-rate data. We do not send other HealthKit data (for example energy or workouts in Apple Health) to our servers. We do not use HealthKit data for advertising or marketing and we do not sell it.
- Android and Wear OS apps: the GPS track of a recorded ride (while recording, also with the screen off, as a service with a visible notification). The Android and Wear OS apps don’t read heart rate or other health data and don’t use the camera or gallery. A Wear OS watch exchanges data with the phone through Google Play services.
- Connect IQ apps on Garmin devices (the “Gridhunt” app and the “Gridhunt Live” data field): you link them to your account with a one-time pairing code; the device then gets a token, and we store a hash of it, the device name, the app type and version and when it last connected. The device downloads tiles, your target, the base map, your saved routes and your first name and last-name initial from Gridhunt; to fetch the tiles and map around you it sends its current position, which we don’t store. After you save a ride, the “Gridhunt” app uploads its GPS track (time, position, altitude) and a summary (sport, distance, times, ascent, device model). The app doesn’t upload heart rate, power or other sensor data. The ride goes to your account as a ride recorded in a Gridhunt app (source: Garmin device, Connect IQ). The “Gridhunt Live” data field doesn’t upload rides. Bike light control (ANT+ light network) and the wind forecast (from Garmin Connect) work only on the device and send us nothing; the apps don’t read radar data. A report about an unexpected app exit is sent only if you confirm it on the device.
- Karoo extension: it downloads data from Gridhunt (tiles, target, routes, your first name and last-name initial) and, when a recording ends, uploads the ride track to Gridhunt (position, elevation and time of each point). You can turn uploads off in the extension settings (“Send recorded rides to Gridhunt”). The extension doesn’t upload heart rate or power.
4. Purposes and legal bases
- Providing the Service (account, sign-in by email link or provider, tile counting, map, targets, planner, friends, devices, Integrations, data export and deletion, help): performance of a contract, Art. 6(1)(b) GDPR.
- Heart-rate data (health data) — your explicit consent, art. 9(2)(a) and art. 6(1)(a) GDPR; you withdraw it by turning off “Save heart rate in Gridhunt”.
- Passing heart rate to Strava — separate explicit consent, Art. 9(2)(a) and Art. 6(1)(a) GDPR; you withdraw it by turning off “Send heart rate to Strava”.
- Premium and payments (subscription, trial, entitlements): performance of a contract, Art. 6(1)(b). Complaints, withdrawals, tax and accounting duties: legal obligation, Art. 6(1)(c) GDPR.
- Square leaderboard and helping others in the planner: your consent (you turn them on in Settings), Art. 6(1)(a) GDPR; you withdraw it by turning the option off.
- Analytics with cookies (Google Analytics 4, Microsoft Clarity) and Google advertising signals: consent, Art. 6(1)(a) GDPR.
- Security, preventing abuse and leaderboard cheating, content moderation (DSA), cookieless statistics, establishing and defending legal claims: our legitimate interests, Art. 6(1)(f) GDPR.
- Age confirmation (your statement that you are at least 16, with its date) — legal obligation and our legitimate interest in showing that we don’t rely on children’s consent, Art. 6(1)(c) and (f) in conjunction with Art. 8 GDPR.
- Content reports (DSA), decisions and statements of reasons — legal obligation, Art. 6(1)(c) GDPR in conjunction with Arts. 16–18 of the Digital Services Act; blocking users and protecting the community — performance of the contract and our legitimate interest, Art. 6(1)(b) and (f) GDPR.
- Marketing emails (news, offers, surveys) — your consent, Art. 6(1)(a) GDPR and Art. 398 of the Polish Electronic Communications Law; you withdraw it with one click in any such email or in Settings.
- AI-assisted analysis of error reports, bug reports and logs (see Recipients) — our legitimate interest in fixing errors quickly and keeping the Service secure, Art. 6(1)(f) GDPR.
- Reel texts in “With humor” mode (see Artificial intelligence) — your explicit consent, Art. 6(1)(a) GDPR; you can withdraw it at any time in Settings, with immediate effect.
5. Who can see your data
By default, only you. We show your data to others only in the situations below, which you turn on yourself:
- Friends (after both sides accept): your claimed tiles (z14 and z17), your activity count, and your number of rides and kilometres per year. They don’t see routes, dates or targets. You can end a friendship at any time.
- Square leaderboard (“Show me on the leaderboard”): signed-in users see your display name (see below), avatar, the size and location of up to 10 of your squares and the tiles inside them. They don’t see routes or dates. They also see monthly and yearly numbers: the number of new tiles in the month, the year and in total, the growth of the side of your biggest square in the month, and your total number of tiles at the end of the month. This shows which month you were active in, but we don’t show routes, the dates of individual rides or individual rides. We store the results of a closed month as a snapshot that doesn’t change after a later import. We look up the place name for each square’s centre with OpenStreetMap Nominatim, sending only coordinates. Turning the option off removes you from the leaderboard immediately, and we delete your monthly leaderboard rows. Keep in mind that a square’s location may reveal the area where you live or train.
- Helping others in the planner: others learn only that “someone” rode through a tile that is an OpenStreetMap obstacle, never your name, routes or dates. Turning the option off removes your contribution.
- Public link (Settings → Sharing): anyone with the link sees your display name, your claimed z14 tiles by year and your targets (name and outline). They don’t see routes or z17 tiles. The link doesn’t expire on its own and isn’t indexed by search engines. Turning it off deletes it; regenerating it creates a new one.
- Reports of “impossible” tiles, comments and photos are visible to all signed-in users together with your name and avatar.
- Friend invitations: anyone with your invite link sees your display name.
- Track privacy (Settings → Privacy): you can hide the start and end of every ride, and privacy zones (a point on the map and a radius, which we store in your account), from other people. What others see then shows a trimmed track, and friends don’t see z17 tiles inside the zones or on hidden ride ends. Ride reels show the same trimmed track by default. z14 tiles, your square and stats don’t change, so their location may still point to your area. By default we hide 200 m at the start and 200 m at the end of every ride; you can change this or turn it off.
Only data from outside the Strava API. Everything described above is calculated only from activities that did not come through the Strava API. We never show data obtained through the Strava API to anyone else in any form, even when these options are on (see Strava data and public features). Others see the display name you set in Gridhunt, never the name or profile photo from your Strava account. Video reels are created by your browser or phone and never reach our servers.
Only the service provider has administrative access. We look at an activity’s GPS track only when the activity has been automatically flagged as passing through a tile reported as impossible, and every such view is logged. A person decides whether to exclude the activity.
Beta programme: the beta programme administrator can see participants’ activity — which platform you use (web, iOS, Android, watch, Garmin, Karoo) and when you were last seen, your last sign-in, the number and source of uploaded rides, your last route plan and your last sync with a connected service (no tokens, routes or coordinates). This is used to manage beta places: after 30 days without activity we send the participant one reminder email, and after another 7 days without activity their place may go back to the queue (terms, Beta programme); in case of a rule breach the administrator may also exclude a participant from the programme.
6. Strava data and public features
We record the source of every activity. The source decides who can see the tiles calculated from it.
- Strava API: for you only. Activities imported automatically after you connect your Strava account, and the tiles and routes calculated from them, are shown only to you: on your map, in your statistics, the planner, your rides and reels created on your device. We never use them in the square leaderboard, friends features, your public link, community aggregates (helping others in the planner) or marketing material. The Strava API rules require this.
- Public sources. Features that show anything to others use only files and archives you upload (including a ZIP archive exported from Strava or Garmin Connect), rides recorded in the Gridhunt apps, devices and other connected apps (e.g. Ride with GPS). They work only when you turn them on (see Who can see your data).
- One ride, one copy. When the same ride arrives from several sources, we keep one copy in this order: a recording in the Gridhunt app, a Garmin device (Connect IQ), an uploaded file or archive, other connected apps and, last, the Strava API. An activity from a Strava ZIP archive replaces the same activity obtained earlier through the Strava API.
- Strava API: 7 days at most. We keep an activity obtained through the Strava API, and the tiles and routes calculated from it, for at most 7 days after it was fetched. After that we delete it, unless you import the same activity yourself (a ZIP archive or a file) or record it in the Gridhunt app — then your copy from that source stays. Deleting an activity on Strava removes only the copy obtained through the Strava API, never a copy you uploaded yourself.
- Making your Strava history public. If you want your past Strava activities to count on the leaderboard and for friends, download your account archive from Strava and upload the ZIP file to Gridhunt. Step-by-step guide: Data sources.
- Public name. Others see the display name you set in Gridhunt. If you haven’t set one, we show the name from another sign-in method (email, Apple, Google, Facebook) only if you haven’t connected Strava; otherwise a neutral label with a number. We never show others the name or profile photo from your Strava account.
7. Garmin Connect
The Garmin Connect connection (Settings → Connections and data) uses Garmin’s official API (Garmin Connect Developer Program). You sign in and give consent on Garmin’s website; we never see your Garmin password.
- What we receive: your Garmin account identifier, access tokens (stored encrypted) and activity files from Garmin Connect (FIT). From each file we keep the route, ride statistics (time, distance, elevation gain, speed) and the device model. We do not store heart rate from these files, and we do not keep the file itself.
- Why: so that new rides from your Garmin devices reach Gridhunt automatically (performance of the contract, Art. 6(1)(b) GDPR). We show “Garmin [device model]” next to the ride because Garmin’s rules require it.
- Visibility: rides fetched from Garmin Connect count the same way as rides recorded in the Gridhunt apps: on the leaderboard, for friends, in your public link and in helping others in the planner, when you turn those features on (see Who can see your data). Wherever we show them to others (including images and reels), we label them “Garmin” with the device model, as Garmin’s rules require.
- History: the connection only fetches rides saved after you connect. You can upload earlier rides from your Garmin Connect data export (ZIP file), see help: Import.
- No sale, no AI: we do not sell data from Garmin Connect, do not share it with advertisers or other services, and do not use it to train, evaluate or improve AI models. We also do not pass it to any AI feature: rides from Garmin Connect and numbers derived from them never reach the model, including in “With humor” mode (see Artificial intelligence).
- Who processes this data: only we and our processors listed in Recipients, to the extent needed to run the service: Microsoft (Azure: servers and database in the EU, files, encryption keys, logs and monitoring, email delivery) and Cloudflare (network and protection of traffic to the service). Anthropic does not receive data from Garmin Connect. We do not pass rides or files from Garmin Connect to analytics providers (Google Analytics, Microsoft Clarity — only with your consent) or to Apple and Google (sign-in, app stores).
- Your rights: access and export — Settings → Connections and data → “Your data” (a JSON file, including rides from Garmin Connect); correction or deletion — single rides in Rides, the whole account in Settings → Profile & plan → “Delete account”; withdrawing consent to fetching data — “Disconnect” in Settings → Connections and data or in Garmin Connect (after that we fetch nothing more). Other rights and contact: Your rights.
- Sending to Garmin: we send a route to Garmin Connect only on your explicit request (once this feature is available). From then on Garmin processes it under its own terms: garmin.com/privacy/connect.
- Disconnecting: in Gridhunt Settings or in Garmin Connect. We then delete the tokens and stop fetching data. Imported rides stay in your account until you delete them (one by one in Rides or together with your account).
- Garmin (Garmin International, Inc. and its affiliates) is a separate controller of the data it holds.
8. Heart-rate data
During a ride the Apple Watch app records your heart rate (and cycling cadence and power from paired sensors, when available) into the ride file (GPX) that travels from the watch through the iPhone to Gridhunt. Ride files you upload (GPX, TCX, FIT) and Garmin rides may also contain heart rate. Heart rate is data concerning health, a special category of data (art. 9(1) GDPR).
- Only with consent. We store heart rate in Gridhunt only with your explicit, voluntary consent. You give it with the “Save heart rate in Gridhunt” toggle (web: Settings → Privacy; iPhone app: Settings) or in the one-time prompt after your first ride following the update. The toggle is off by default.
- What we store once you consent. For each ride: average and maximum heart rate, average cadence and average power (if present), and a downsampled heart-rate series (about one value per 10 seconds) for the chart in ride details. For rides recorded in Gridhunt apps we also keep the original ride file, which contains heart rate at each track point. The data sits in the database and file storage of our hosting provider (Microsoft Azure, EU; see Recipients).
- Purpose. We show you your heart-rate statistics and chart and, only if you separately agree (see below), pass your ride file with heart rate to your Strava account. We don’t use heart rate for advertising, profiling, leaderboards, community features or sharing. Other users never see it (it is not in the community, leaderboards, share pages or public profiles), and administrators reviewing flagged rides don’t see it either. We don’t sell this data.
- Legal basis: your explicit consent, art. 9(2)(a) and art. 6(1)(a) GDPR.
- Heart rate on Strava — separate consent. We send heart rate to Strava only if both options are on: “Save heart rate in Gridhunt” and “Send heart rate to Strava”. You give the second consent separately and freely, and you can withdraw it at any time without affecting heart-rate storage in Gridhunt. Strava processes the data it receives as a separate controller under its own rules (including in the USA).
- Without consent. Without consent to storing heart rate, the Gridhunt apps remove heart rate, cadence and power from the ride file on your device before uploading it, and the server removes them while processing files that reach us (including uploaded GPX, FIT and TCX files). We then store no heart-rate summary or series, and the stored ride file has no heart rate. If you consent to storage but not to sending it to Strava, the server strips heart rate, cadence and power from the copy of the file sent to Strava, so the ride reaches Strava without them.
- Retention and withdrawal. We keep heart-rate data as long as the ride exists in your account, until you withdraw consent or delete the account, whichever comes first. Turning off “Save heart rate in Gridhunt” deletes all stored heart-rate summaries and series and removes heart rate from stored ride files. Withdrawal does not affect the lawfulness of processing before withdrawal. Data already sent to Strava is governed by Strava; you can delete it there. Withdrawing “Send heart rate to Strava” stops heart rate being passed on with future uploads.
- Your rights. Access and export, deletion, and withdrawal of consent at any time in Settings (see also Your rights).
9. Content reports and blocking
Comments, photos, tile reports, ideas and profiles have a “Report” button. You can also send a notice by email (see the terms). We then process:
- the reporter’s data: account identifier (if you are signed in), name and contact email (not required when reporting child sexual abuse material), explanation and good-faith statement;
- the reported content and its author’s data;
- our decision, the statement of reasons (Art. 17 of the Digital Services Act), any appeal and the dates.
The author receives the statement of reasons without the reporter’s data unless it is necessary (e.g. for an infringement of the reporter’s copyright) — in that case we tell the reporter first. Information about a possible crime threatening someone’s life or safety is passed to law enforcement (Art. 18). Notices are handled by a person.
Blocking. You can block another user. We record who blocked whom and when. A block hides that person’s content in the community from you and limits their contact with you in Gridhunt; we don’t notify them. You can lift a block at any time.
10. Emails from us
- Service messages (sign-in links, confirmations, important changes to the service and documents, account reminders) are sent under the contract. You can unsubscribe from some of them (e.g. reports and reminders) in Settings or via the link in the email.
- Marketing emails (news, offers, surveys) are sent only with your separate consent. The consent box is never pre-ticked, and we record the date and version of your consent. The newsletter consent when signing up for the beta works the same way.
- You can unsubscribe with one click in any marketing email (including the “unsubscribe” button in your email app) or in Settings. After that we stop sending such messages; we keep the dates of consent and withdrawal as evidence until you delete your account.
11. Recipients of data
Processors acting on our behalf (under data processing agreements):
- Microsoft Ireland Operations Ltd. (Azure): servers, database, file storage, Key Vault (encryption keys), logs and monitoring (Application Insights), and sending sign-in link emails (Azure Communication Services). Region: West Europe (Netherlands); email data location: Europe.
- Cloudflare, Inc. (USA): DNS, CDN, attack protection (WAF) and Cloudflare Web Analytics. Traffic to the site, including your IP address, passes through Cloudflare. Cloudflare also tells us the approximate country derived from your IP address; we use it to pick the currency on the pricing page and store it with a beta sign-up. The beta sign-up and sign-in forms may be protected by Cloudflare Turnstile: Cloudflare then checks signals from your browser (e.g. IP address, browser and device characteristics) to tell people from bots. This is not used for advertising or tracking.
- Apple (TestFlight) and Google (Google Play): only if you ask for access to the test version of the app in Settings. We pass the Apple or Google account address you enter in the dialog to the provider solely so that it can send you the testing invitation (Android: we keep it on our testers list and add you in Google Play by hand), and we save it on your account so we can show the invitation status, let you change the address and revoke access (for example when you are excluded from the beta). We delete it together with your account.
- Google Ireland Ltd. (Google Analytics 4) and Microsoft Ireland Operations Ltd. (Clarity): only with your consent, see cookies.
- Microsoft Ireland Operations Ltd. (Azure DevOps): handling of errors and reports by the team. It receives the technical description of the error or the text of the report, the number of occurrences and an internal identifier, without your name, email or the raw error report.
- Anthropic (USA, Claude AI model): helps the team triage error reports and bug reports (e.g. assign a category, suggest a likely cause and duplicates) and review server logs. Before sending, we remove email addresses, tokens, coordinates and other identifiers, and the model never receives your name or email. We use the paid API under commercial terms that include a data processing agreement; Anthropic does not use this data to train models. For error reports, bug reports and logs, the model makes no decisions about you, and a person checks its output.
- Anthropic (USA, Claude AI model), reel texts: only with your explicit consent (“With humor” mode). It receives only numbers from the chosen period, without GPS tracks, names or identifying data, and without data from the Strava API or Garmin Connect. Full list of the data we send, retention and withdrawing consent: Artificial intelligence. We use the same paid API under commercial terms that include a data processing agreement; Anthropic does not use this data to train models.
Independent controllers (processing data under their own terms):
- Stripe: Stripe Payments Europe, Ltd. (Ireland) and Sold through Link, LLC (USA), under Stripe Managed Payments. They handle payment, taxes, receipts, fraud prevention and transaction support. We pass them your email, name, user ID and language; you give your card details directly to Stripe. Policies: stripe.com/privacy, link.com/privacy.
- Services you connect: Strava, Wahoo, Garmin, Suunto, COROS, Polar, Ride with GPS, Hammerhead (SRAM) and sign-in providers (Apple, Google, Meta/Facebook). At your request we send them data (e.g. a ride to Strava or a route to Wahoo) and fetch activities from them.
- Apple (App Store, Apple Health on your device) and Garmin (Connect IQ store): under their own terms. The same applies to Google (the Google Play store and Google Play services on your Android phone and Wear OS watch).
Map services: your browser loads map tiles from OpenFreeMap (tiles.openfreemap.org), which sees your IP address and the area you view. Our server asks OpenStreetMap Nominatim for place names and Overpass API servers for road data, sending only coordinates or an area and nothing about you. Routing (BRouter) runs on our own server. Your browser loads avatars from Google, Facebook or Strava directly from those companies’ servers. For navigation, our server gets wind direction and speed from Open-Meteo (open-meteo.com); it sends only coordinates rounded to about 5 km, without any data about you.
We may also disclose data to public authorities where the law requires it, and to advisers (accountants, lawyers) bound by professional secrecy.
12. Transfers outside the EEA
Our servers are in the EU. Data may reach countries outside the European Economic Area, mainly the USA, through Cloudflare, Google, Microsoft (Clarity), Anthropic, Stripe/Link and the services you connect. The legal basis is the European Commission’s adequacy decision (EU-US Data Privacy Framework, where the recipient is certified) or standard contractual clauses (Art. 46(2)(c) GDPR). We will send you information about the safeguards on request. When you connect a service based outside the EEA, the transfer happens at your request under your contract with that service. Anthropic receives only data from which identifiers have been removed (error reports, bug reports and logs) or plain numbers for a reel period (the “With humor” mode, which you turn on yourself); see Recipients.
13. How long we keep data
- Account, activities, tiles, targets, routes, friendships: until you delete your account. We delete accounts immediately, with no grace period. Database and file backups expire after 7 days.
- Heart-rate data: as long as the ride exists in your account, until you withdraw consent or delete the account, whichever comes first (see Heart-rate data).
- Strava data: when you disconnect Gridhunt (in Gridhunt Settings or on Strava), we delete all activities obtained through the Strava API and the data calculated from them (tiles, routes). Activities from files you uploaded yourself (including a Strava ZIP archive) and rides recorded in Gridhunt remain until you delete them or your account. Otherwise, activities obtained through the Strava API are deleted no later than 7 days after they were fetched, and an activity you delete on Strava is removed straight away (only the Strava API copy).
- Other Integrations: when you disconnect, we revoke access and delete the tokens; imported activities stay until you delete them or your account.
- Uploaded files: deleted after processing, at the latest after 2 days.
- Tile reports and comments: after account deletion they remain without your name and avatar; photos are deleted.
- Security logs with IP address: 12 months; abuse-prevention counters: up to 30 days; server logs: 30 days.
- Subscription data: with us until account deletion; Stripe/Link keeps receipts and transaction data for as long as tax law requires.
- Accounting records: payments are handled by Link as merchant of record (see the terms), so Link issues and keeps your receipts. We keep our own accounting records (e.g. settlements and invoices with Link, which may include a subscription identifier) for 5 years from the end of the calendar year in which the tax payment deadline passed (Art. 6(1)(c) GDPR in conjunction with Art. 74 of the Polish Accounting Act and Art. 86 of the Polish Tax Ordinance).
- Correspondence and complaints: up to 3 years after the matter is closed (defence of claims).
- Analytics: Google Analytics 14 months; Clarity: recordings up to 30 days, aggregated data up to 13 months.
- Error reports: raw reports for 90 days; all reports linked to your account are deleted together with it. Bug reports: while the case is open, then as correspondence; after account deletion they remain without any link to you.
- Content reports (DSA) and decisions: 6 months from the decision (time to appeal) or, if the matter is disputed, up to 3 years after it ends (defence of claims). Blocks: until you lift the block or delete your account.
- Age statement and consents (with date and version): until you delete your account; marketing consent applies until withdrawn, and we keep the record of giving and withdrawing it as evidence until you delete your account.
- Reel texts (“With humor” mode): in the reel’s memory until you withdraw consent to AI texts or delete your account; they are not added to your profile or statistics. We keep the date and version of your consent and the history of giving and withdrawing it until account deletion, as evidence.
14. Your rights
You have the right to access your data and get a copy, to rectification, erasure, restriction of processing and data portability, to object to processing based on our legitimate interests, and to withdraw consent at any time (without affecting the lawfulness of earlier processing).
- Yourself: in Settings you can download your data (a JSON file with your profile, activities, tiles, targets, friends and subscription), correct it, disconnect Integrations, turn off the leaderboard, planner help and public link, and delete your account.
- By email: to [email protected]; we reply within one month. We may ask you to confirm that the request comes from the account holder.
- Complaint: to the Polish supervisory authority, the President of the Personal Data Protection Office (UODO, ul. Stawki 2, 00-193 Warsaw, uodo.gov.pl), or to the data protection authority in your country.
Providing data is voluntary, but without an email address or a sign-in provider account you can’t create an account, and without activities we can’t count tiles.
16. Browser extension
The Gridhunt browser extension (Chrome, Edge, Brave, Opera) draws your tiles, current square, planned square and the new tiles of a planned route on the maps of Strava, Ride with GPS, MapMyRide/MapMyFitness, Hammerhead, Google Maps and other supported services. You install it and connect it to your account yourself; using it is optional.
- On your computer (in the extension’s storage in the browser) it keeps only: the device token and your account name, a copy of your tiles, square and target, your toggle and environment settings, and the panel position on the map. Your browser may sync the settings and panel position between your devices if you have browser sync turned on.
- To Gridhunt it sends only requests with the device token, to fetch your tiles, square and target. As with other devices, we store the browser name, the extension version and the time of the last connection.
- From the services’ pages it reads only the position and zoom of the visible map (to draw in the right place; it does not store or send it) and the page address (to recognise a route map page; on Google Maps also the map position, which is in the address). It also reads, only locally on your computer, the route you are planning or viewing on the map (the line the page already shows), to highlight the tiles that route would add; the route is not stored and is not sent to Gridhunt or anyone else. It does not read your activities, profile or any other page content.
- The extension contains no analytics, telemetry or ads and connects to nobody but Gridhunt.
- Revoking access: in Settings → Connections and data → Devices, click “Disconnect” next to the browser. The token stops working immediately; you remove the data stored in the extension by uninstalling it.
Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
17. Security
Connections are encrypted (HTTPS) and data is encrypted at rest. Tokens for Strava and other services are additionally encrypted (AES-256-GCM) with a key held in Azure Key Vault. Device tokens and pairing codes are stored only as hashes. There are no Gridhunt passwords, because you sign in with an email link or through a provider. Administrative access is restricted and logged. If a personal data breach puts you at risk, we will notify you and the supervisory authority as the GDPR requires.
18. Children
Gridhunt is for people aged 16 and over. We don’t knowingly collect data from younger children; if we find out, we delete the account. If you are a parent and think your child has created an account, write to [email protected]. When you create an account or sign up for the beta, you confirm that you are at least 16; we store the date of that statement.
19. Profiling, AI and selling data
- We don’t make decisions about you based solely on automated processing that produce legal effects or similarly significantly affect you (Art. 22 GDPR). The only automated step is flagging activities for review by a person (see above).
- We don’t use your data to train artificial intelligence models, and we don’t share it with others for that purpose.
- An AI model (Anthropic, see Recipients) helps the team sort error reports, bug reports and logs. It does not assess you or make decisions about you; in those matters a person approves every change and decision.
- Only with your explicit consent, an AI model (Anthropic) writes suggested board texts and a caption in “With humor” mode, based only on numbers from the chosen period. It does not assess you or make decisions about you. We label the text “Text by AI”; you see it before recording the reel and can edit or reject it, and you decide whether to publish the reel. The model never receives data from the Strava API or Garmin Connect (see Artificial intelligence).
- We don’t sell personal data or share it with advertisers or data brokers.
20. Artificial intelligence (AI Transparency Statement)
Gridhunt uses AI in two places. Neither makes decisions about you, and we do not use your data to train, evaluate or improve AI models or share it with others for that purpose.
- Reel texts (“With humor” mode), only with your consent. Model: Claude (claude-opus-5-5) by Anthropic PBC (USA), through its paid API. We send only numbers calculated by our server: the ride date or the season’s years, number of rides, distance, number of new and total tiles, the square’s side before and after, the size of the largest cluster before and after (if it grew), the season’s best day (date and number of new tiles), the period’s outcome, the season mode, and your chosen style, language and units. We do not send GPS tracks or coordinates, ride or place names, heart rate or other sensor data, your name, email address, or account and ride identifiers. Rides fetched through the Strava API and rides from Garmin Connect (including a Garmin personal key) are left out: neither they nor any numbers derived from them reach the model.
- Consent and withdrawal. We ask for consent, with this description, the first time you turn the mode on, and record its date and text version. You can withdraw it with one switch in Settings → Privacy & sharing (“AI texts in reels”), on the website and in the iPhone and Android apps. Withdrawal takes effect immediately: we send nothing more to the model and delete the stored AI texts. Without consent, regular reels work as before. Legal basis: consent (Art. 6(1)(a) GDPR).
- Retention. Anthropic does not use API data to train models and deletes inputs and outputs within 30 days (longer only for violations of its usage policy or where the law requires). We keep the generated texts in our database in the EU (the reel’s memory) so we don’t ask the model twice; we delete them when you withdraw consent or delete your account, and until then they are included in your data export. We label the text “Text by AI”; you see it before recording the reel and can edit or reject it.
- Sorting reports and logs. The Claude model (Anthropic) helps the team do a first analysis of error reports, reports you send and server logs after identifying data has been removed (see Recipients). We do not pass rides or files from Garmin Connect or the Strava API to this feature.
21. Changes to this policy
We will tell you about significant changes in the app or by email before they take effect. If a change requires your consent, we will ask for it.