Current formal policy version: 12 July 2026
Material correction notice: 9 October 2026. This notice clarifies current weather, diagnostic and optional analytics handling. It introduces no additional use of your data and does not resume paused ingestion.
Current formal policy version: 12 July 2026. Proposed revised-policy version: 2026-10-24-current-disclosure-correction-v1, scheduled for 24 October 2026 at 00:00 UTC, after the required advance notice. The proposed version is not yet in force. If the required notice procedure is not completed in time, its effective date will be revised.
This clarification corrects descriptions of the current weather, diagnostic and analytics paths. It does not introduce additional uses of your data, resume paused ingestion or change health-data withdrawal processing.
If you allow location access, your device may obtain a precise location fix. For the weather preview, Bricko rounds latitude and longitude to two decimal places and sends those rounded coordinates directly to OpenWeather. This weather path does not send the unrounded fix to the Bricko backend. The app stores rounded coordinates in an account-tagged cache on your device. It attempts to remove that cache when account ownership changes or the applicable data is erased. Storage failures can leave a cached copy; owner checks prevent another account from using it. Forecasts are cached in memory and reused for up to one hour. The one-hour reuse limit does not itself remove expired entries from memory. You can disable location access in your device settings. OpenWeather receives the network information needed to handle your request, including your IP address.
We use Sentry for limited technical diagnosis of app crashes and faults under our legitimate interest in running a reliable service. Reports can contain error details, app and operating-system versions, technical device context and an identifier used to group recurring faults. Reports are not anonymous. The app filters listed contact and credential fields, but its filters can retain health fields or health information in error text if supplied. We have not established that such information was actually sent to or retained by Sentry. Sentry may process or store IP addresses; provider settings do not suppress their storage. This notice does not authorize a new health-data diagnostic purpose.
For the current beta, we have disabled the Sentry intake key used by the mobile app. The app can still attempt to send reports. The key change is subject to provider propagation; once it takes effect, the key no longer accepts new reports. We have not measured rejection of a report. This pause does not erase earlier reports or establish that no temporary processing occurs. The observed Sentry account stores data in the EU; we do not claim Germany-only storage or that all processing stays within the EU.
Our adopted report-handling procedure calls for access to be limited to people assigned to investigate faults. If unnecessary sensitive information enters a report, we will limit its circulation, arrange removal where possible, assess the incident and correct the sending path. Adopting this procedure does not establish that every access restriction has been implemented or every provider copy can be removed immediately.
Usage analytics are optional, opt-in and off by default. When enabled in Settings → Privacy & consent, the app associates usage events with your account identifier; the events are not anonymous. Current analytics code permits the event properties screen, surface, source, stage, code, status, error_name, intent and decision, plus a demo indicator. It does not forward the older effort, fuel, niggle, session-ID, discipline or rest-override-reason properties. Event names can still describe training or session activity, so property filtering alone does not establish that every health-related inference is excluded. You can switch analytics off in the same settings. For the current beta, a saved project-wide filter in PostHog drops all new events at ingestion, regardless of the app analytics setting. Requests can still reach PostHog and undergo temporary processing before they are dropped. The filter does not erase previously received data and is not a claim that events queued on your device have been erased. PostHog stores this project in EU Cloud. We do not use advertising trackers or sell or share usage data for marketing.
This Privacy Policy explains how BCKLE Ltd collects, uses, discloses, and protects personal data in connection with the Bricko adaptive training application and the website at getbricko.com. It is issued in accordance with the UK General Data Protection Regulation (the "UK GDPR"), the Data Protection Act 2018, and, where applicable, Regulation (EU) 2016/679 (the "EU GDPR").
Please read this Policy carefully. By creating an account you acknowledge that you have read and understood it. Where we process your health data, we do so only on the basis of your separate, explicit consent, as described in Section 6.
1.1 Bricko is an adaptive training application for runners and triathletes, operated by BCKLE Ltd. This Policy applies to all personal data processed through the Bricko mobile application (iOS and Android), the getbricko.com website, and the associated backend services (together, the "Service").
1.2 This Policy should be read together with our Terms of Service, which govern your use of the Service.
1.3 Bricko is currently available as an invite-only private beta. There is no public sign-up form on our website.
In this Policy, the following terms have the meanings set out below:
3.1 For the purposes of the UK GDPR (and the EU GDPR where it applies to you), BCKLE Ltd is the data controller in respect of personal data processed through the Service. We determine the purposes and means of that processing.
3.2 Our contact details are:
3.3 We have not appointed a statutory Data Protection Officer, as we are not required to do so. Data protection enquiries are handled by BCKLE Ltd at the contact address above.
We collect only the personal data that the Service actually uses. The categories of personal data we process are set out below.
The data in this section constitutes special category data (data concerning health) under Article 9 of the UK GDPR. We collect and process it only on the basis of your explicit consent, obtained separately and not bundled into our Terms of Service (see Section 6).
If you allow location access, your device may obtain a precise location fix. For the weather preview, Bricko rounds latitude and longitude to two decimal places and sends those rounded coordinates directly to OpenWeather. This weather path does not send the unrounded fix to the Bricko backend. The app stores rounded coordinates in an account-tagged cache on your device. It attempts to remove that cache when account ownership changes or the applicable data is erased. Storage failures can leave a cached copy; owner checks prevent another account from using it. Forecasts are cached in memory and reused for up to one hour. The one-hour reuse limit does not itself remove expired entries from memory. You can disable location access in your device settings. OpenWeather receives the network information needed to handle your request, including your IP address.
Usage analytics are optional, opt-in and off by default. When enabled in Settings → Privacy & consent, the app associates usage events with your account identifier; the events are not anonymous. Current analytics code permits the event properties screen, surface, source, stage, code, status, error_name, intent and decision, plus a demo indicator. It does not forward the older effort, fuel, niggle, session-ID, discipline or rest-override-reason properties. Event names can still describe training or session activity, so property filtering alone does not establish that every health-related inference is excluded. You can switch analytics off in the same settings. For the current beta, a saved project-wide filter in PostHog drops all new events at ingestion, regardless of the app analytics setting. Requests can still reach PostHog and undergo temporary processing before they are dropped. The filter does not erase previously received data and is not a claim that events queued on your device have been erased. PostHog stores this project in EU Cloud. We do not use advertising trackers or sell or share usage data for marketing.
Bricko is currently an invite-only private beta, and there is no public sign-up form on our website. If you contact us by email to enquire about access, we process that email in order to respond to you. Mail sent to our published address is redirected by Cloudflare into a Google Workspace mailbox, where it is received and stored (see Section 9).
We process your personal data only where we have a lawful basis to do so under Article 6 of the UK GDPR and, for special category data, a condition under Article 9. The purposes and corresponding legal bases are set out below.
| Purpose | Personal data used | Legal basis |
|---|---|---|
| Calculating your daily readiness and adapting your training plan | Wearable metrics, check-ins, session history, profile | Consent, Art. 6(1)(a), together with explicit consent, Art. 9(2)(a) |
| Safety features: under-fuelling (RED-S) signals, injury and niggle prompts, and suggestions to consult a professional | Weight trends, wellness and injury data, training load | Consent, Art. 6(1)(a), together with explicit consent, Art. 9(2)(a) |
| Generating your morning brief, your coaching explanations and your session content (AI-assisted, see Section 8) | First name and summarised recovery and training metrics | Consent, Art. 6(1)(a), together with explicit consent, Art. 9(2)(a) |
| Creating and operating your account; sending essential service emails (verification, password reset, data exports) | Email, name, account data | Performance of a contract, Art. 6(1)(b) |
| Responding to enquiries you send us by email, for example asking about beta access | Your email address and the content of your message | Legitimate interests, Art. 6(1)(f), in replying to correspondence you have chosen to send us |
| Sending push notifications (morning brief, night-before preview) | Push token, notification preferences, and the content of the notification | Performance of a contract, Art. 6(1)(b); each notification type may be disabled |
| Showing weather in the night-before preview (Section 4.4) | Coordinates rounded to two decimal places, sent from your device to OpenWeather; account-tagged coordinate cache on your device | Consent, Art. 6(1)(a); optional, and only where you allow location access |
| Searching race databases when you look for a race | Your search text only | Legitimate interests, Art. 6(1)(f), in running the search you asked for |
| Recording your consent to health-data processing, and its withdrawal (Section 6) | Account identifier, the date of consent, and the version of the consent text shown to you | Legal obligation, Art. 6(1)(c), to be able to demonstrate consent under Art. 7(1) |
| Evidencing that an erasure request was carried out (Section 11) | Account identifier, timestamp and deletion reason; no health or profile data | Legal obligation, Art. 6(1)(c), to demonstrate compliance with your request |
| Handling your data-protection rights requests and complaints (Sections 13 and 17) | Your identity, your account data, and the content of your request | Legal obligation, Art. 6(1)(c) |
| Disclosures required by law, and establishing, exercising or defending legal claims (Section 9.2) | Only the data the specific matter requires | Legal obligation, Art. 6(1)(c), and legitimate interests, Art. 6(1)(f), in defending legal claims |
| Maintaining the security of accounts (login monitoring, rate limiting) | IP address, device description | Legitimate interests, Art. 6(1)(f) |
| Diagnosing and resolving crashes and errors | Filtered error reports, technical context and a grouping identifier; health-content and IP limits and the current intake pause are described in Section 12.2 | Legitimate interests, Art. 6(1)(f), for limited technical diagnosis; no new health-data diagnostic purpose |
| Understanding feature usage in order to improve the Service | Usage events, basic device and application information, and your account identifier (no name or email address) | Consent, Art. 6(1)(a); opt-in and off by default, and you may switch it off at any time (Section 4.5) |
| Improving Bricko using anonymised, aggregated data | De-identified data that cannot identify you | Separate opt-in consent, Art. 6(1)(a); disabled by default |
Where we rely on legitimate interests, we have assessed that those interests are not overridden by your interests or fundamental rights and freedoms. You may request further information about that assessment using the contact details in Section 18.
We do not sell your personal data, and we do not use it for third-party advertising.
6.1 Because HRV, sleep, heart rate, weight, injury, and wellness data constitute health data under Article 9 of the UK GDPR, we obtain your explicit consent before collecting or processing any of it. That consent is:
6.2 Withdrawal of consent does not affect the lawfulness of processing carried out before withdrawal.
6.3 If you do not provide consent, the personalised features (readiness, plan adaptation, and the safety flags) will be unavailable, as they cannot operate without the relevant data. The Service will indicate which features are affected.
6.4 A separate, independent, and off-by-default option allows the anonymised, aggregated use of your data to improve the Service. This option is never a condition of using the Service.
7.1 Your readiness score and plan adaptations are generated automatically by a deterministic algorithm that weighs your HRV, sleep, training load, and check-ins and adjusts your plan accordingly. This constitutes automated processing of your health data.
7.2 These outputs are advisory only: they provide recommendations, and you retain full control over your decisions. No feature of the Service produces a legal effect concerning you or a similarly significant effect within the meaning of Article 22 of the UK GDPR. You may view the reasoning behind any recommendation within the application, disregard it, or contact us at hello@getbricko.com.
8.1 We use AI language models provided by Anthropic (the Claude model family) for the natural-language elements of the Service. The following describes precisely how these models are used:
9.1 We disclose personal data only to the processors listed below, each of which acts on our documented instructions under a written data processing agreement. We do not sell personal data.
| Recipient | Function | Data received | Location |
|---|---|---|---|
| Cloudflare | Hosting, database, and infrastructure; the email redirect that carries messages sent to our published address into our mailbox | All application data (encrypted in transit and at rest); for the redirect, the message in transit only, which is not stored by Cloudflare | Global network (UK/EU/US) |
| Anthropic | AI text generation (Section 8) | Morning brief: first name and summarised recovery and training metrics. Session personalisation: session structure and training parameters only. Weekly recap: coarse, de-identified statistics. Not used for model training | US |
| SweatStack | Garmin connection service (only where you connect Garmin) | Secure connection tokens; retrieval of daily health and activity summaries | EEA (Norway) |
| Expo | Push-notification delivery | Push token and notification content | US |
| Authentication (if used); Android push delivery (FCM); the Google Workspace mailbox that receives and stores email you send to us | Authentication: name, email, picture. Push: device token. Email: your address and the content of your message | US | |
| Apple | iOS push delivery (APNs); App Store distribution | Device push token | US |
| Resend | Transactional email delivery | Your email address and message content | US |
| PostHog | Optional product analytics; all new project events are currently dropped by a saved ingestion filter | Account identifier, permitted usage-event properties and device/app information. Requests and temporary processing can occur before events are dropped; historical data is not erased | Observed EU Cloud project |
| Sentry | Crash/error diagnostics; mobile intake key currently disabled | Filtered reports, grouping identifiers and technical context; no universal health/IP exclusion. Attempted sends and earlier reports remain possible (Section 12.2) | Observed EU account storage; no Germany-only or all-EU processing claim |
| OpenWeather | Optional weather preview | Coordinates rounded to two decimal places, sent directly from your device; request network information including IP address. On-device caching is described in Section 4.4 | US/global |
| Race databases (OpenTrack, RunSignup, British Triathlon) | Race search | Your search text only | UK/US |
9.2 We may also disclose personal data where required to do so by law, court order, or a competent regulatory authority, or where necessary to establish, exercise, or defend legal claims.
9.3 Payments. The Service is currently provided free of charge (see the Terms of Service). We do not use a payment processor at present. Should we introduce paid subscriptions, we will engage a payment provider, update this Policy, and notify you in advance.
10.1 Certain of our processors are located outside the United Kingdom and the European Economic Area (principally in the United States). Where personal data is transferred to such a jurisdiction, we ensure that an appropriate safeguard under Chapter V of the UK GDPR is in place.
10.2 The safeguards we rely on include the International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, the EU Standard Contractual Clauses, and/or transfers to recipients certified under the UK–US and EU–US Data Privacy Frameworks. You may request a copy of the relevant safeguard using the contact details in Section 18.
We retain personal data only for as long as necessary for the purposes for which it was collected, in accordance with the following schedule.
| Circumstance | Retention |
|---|---|
| Active account | Retained for the duration of your account |
| Account deletion | At your election, either immediately or following a 14-day grace period during which you may restore the account; thereafter, permanent deletion across our systems, including revocation of wearable connections |
| Erasure audit record | A minimal audit record (account identifier, timestamp, and deletion reason, containing no health or profile data) is retained to evidence completion of the erasure, and is kept for as long as we may need to demonstrate that the erasure was carried out |
| Wearable disconnection | Connection tokens are deleted immediately; previously synchronised data is retained in your account until you delete it or your account |
| Email verification links | Expire after 24 hours |
| Password reset links | Expire after 1 hour |
| Data export downloads | Download links are time-limited and then removed |
| Email enquiries | Correspondence is kept only as long as needed to deal with your enquiry and for a short period afterwards, then deleted |
| Approximate location | Rounded coordinates are stored in an account-tagged cache on your device. The app attempts to remove that cache when account ownership changes or the applicable data is erased. Storage failures can leave a cached copy; owner checks prevent another account from using it. Forecasts are cached in memory and reused for up to one hour. The one-hour reuse limit does not itself remove expired entries from memory. This weather path sends rounded coordinates directly to OpenWeather and does not send the unrounded fix to the Bricko backend |
| Race search text | Not retained by us. It is passed to the race database to run the search |
| Consent records | Retained for the life of the account and afterwards for as long as we may need to evidence that consent was given or withdrawn. They contain no health data |
| Rights requests, complaints and legal matters | Kept for as long as needed to deal with the matter and to evidence that it was dealt with, then deleted |
| Security logs (login attempts, rate limits) | Retained briefly for security purposes, then automatically deleted |
| Residual backup copies | Copies within our database provider's automated backups expire within approximately 30 days of deletion |
12.1 We implement appropriate technical and organisational measures to protect personal data against unauthorised or unlawful processing and against accidental loss, destruction, or damage, as required by Article 32 of the UK GDPR.
12.2 These measures include, and are grounded in, how the Service is actually built: passwords stored solely as salted PBKDF2 hashes (100,000 iterations); session, verification, and reset tokens stored solely as hashes; wearable connection tokens revoked and deleted on disconnection and on account deletion; error telemetry filtered for listed contact and credential fields, with the current health-content and IP limitations and intake-key pause described below; authentication tokens held in your device's secure storage; and login rate-limiting with lockout on repeated failures. All data is encrypted in transit (TLS) and at rest.
We use Sentry for limited technical diagnosis of app crashes and faults under our legitimate interest in running a reliable service. Reports can contain error details, app and operating-system versions, technical device context and an identifier used to group recurring faults. Reports are not anonymous. The app filters listed contact and credential fields, but its filters can retain health fields or health information in error text if supplied. We have not established that such information was actually sent to or retained by Sentry. Sentry may process or store IP addresses; provider settings do not suppress their storage. This notice does not authorize a new health-data diagnostic purpose.
For the current beta, we have disabled the Sentry intake key used by the mobile app. The app can still attempt to send reports. The key change is subject to provider propagation; once it takes effect, the key no longer accepts new reports. We have not measured rejection of a report. This pause does not erase earlier reports or establish that no temporary processing occurs. The observed Sentry account stores data in the EU; we do not claim Germany-only storage or that all processing stays within the EU.
Our adopted report-handling procedure calls for access to be limited to people assigned to investigate faults. If unnecessary sensitive information enters a report, we will limit its circulation, arrange removal where possible, assess the incident and correct the sending path. Adopting this procedure does not establish that every access restriction has been implemented or every provider copy can be removed immediately.
12.3 In the event of a personal data breach likely to result in a risk to your rights and freedoms, we will notify the Information Commissioner's Office (and, where required, you) within the timeframes prescribed by the UK GDPR.
13.1 Subject to the conditions and exemptions in applicable data protection law, you have the following rights in respect of your personal data:
13.2 To exercise any right that cannot be exercised within the application, contact hello@getbricko.com using the subject line "Data Protection". We will respond within one month of receipt, as required by the UK GDPR, and may extend that period by up to two further months for complex or numerous requests, in which case we will inform you.
The Service is intended for individuals aged 16 or over. We verify date of birth at registration and refuse accounts below the minimum age. We do not knowingly process the personal data of any person under 16. If you believe that a person under 16 has provided us with personal data, please contact hello@getbricko.com and we will delete it promptly.
The Bricko website uses only strictly necessary cookies (for authentication and session management). We do not use advertising cookies, social-media trackers, or third-party tracking pixels. In-application analytics are described in Sections 4 and 9. These cookies last no longer than your signed-in session and are cleared when you sign out or the session expires.
We may update this Policy from time to time. Where we make a material change, in particular to how we process health data or to the recipients of your data, we will notify you by email and/or in-application notice at least 14 days before the change takes effect. The date at the top of this Policy indicates the version currently in force.
17.1 If you have a concern about how we process your personal data, we ask that you contact us first at hello@getbricko.com so that we may seek to resolve it.
17.2 You also have the right to lodge a complaint with the UK Information Commissioner's Office (ICO), which is our lead supervisory authority. If you are located in the EU or EEA, you may instead lodge a complaint with the supervisory authority in your country of residence, for example, in Belgium, the Data Protection Authority (GBA/APD).
BCKLE Ltd (operating Bricko)
Company No. 17098453 (England and Wales)
Registered office: 78 Flag Meadow Walk, Worcester, WR1 1QU, United Kingdom
Email: hello@getbricko.com, with the subject line "Data Protection" for privacy matters
Website: getbricko.com