1Introductory Provisions and Scope
This Privacy Policy (the "Policy") sets forth the principles and conditions governing the collection, storage, processing, and transfer of Personal Data of Users of the SpringBoard mobile application (the "Application"). The Policy has been prepared in compliance with:
- Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data ("GDPR");
- Regulation (EU) 2022/2065 of the European Parliament and of the Council of 19 October 2022 on a Single Market For Digital Services ("Digital Services Act" / "DSA");
- Applicable provisions of Polish civil law; and
- Platform policies of Google Play Console (including the Health Connect policies) and Apple App Store.
This Policy applies to all natural persons who install, access, or otherwise use the Application, irrespective of their jurisdiction of residence, to the extent permitted by applicable mandatory law.
2Definitions
For the purposes of this Policy, the following terms shall bear the meanings ascribed to them below:
- "Controller" means the natural or legal person who, alone or jointly with others, determines the purposes and means of processing of Personal Data. For the purposes of this Policy, the Controller is Kamil Mazurkiewicz, reachable at: kmdevworks.contact@gmail.com.
- "Application" means the SpringBoard mobile software application, including all versions, updates, modules, and embedded features thereof, distributed via Google Play Store and Apple App Store.
- "User" means any natural person who creates an Account or otherwise uses the Application, acting in their personal capacity.
- "Account" means the individual access profile created by the User upon registration, enabling access to the personalised features of the Application.
- "Personal Data" means any information relating to an identified or identifiable natural person, as defined in Article 4(1) GDPR.
- "Step Data" means the User's daily step totals and related technical values (such as the cumulative reading of the device's step counter sensor, used as a reference point to calculate daily totals), together with the daily step goal and the walking distance estimated from the step count and the User's height, whether obtained from the step counter sensor of the User's device or, where the User has permitted it, from Health Connect.
- "Health Connect" means the Android system component operated by Google that allows apps, with the User's permission, to read and share health and fitness data stored on the device.
- "AI Services" means the artificial-intelligence-powered analytical and informational features of the Application, including but not limited to training load analysis, fatigue estimation, workout plan generation, and the AI trainer chat. The AI Services are powered by large language models provided by the following AI Providers: (i) Google LLC (Google Cloud / Google AI Studio, Gemini API) and (ii) Hangzhou DeepSeek Artificial Intelligence Co., Ltd. ("DeepSeek", DeepSeek V4 model, via the api.deepseek.com interface).
- "AI Providers" means the third-party providers of language models used to deliver the AI Services, as listed in Section 6.
- "User Content" means all data, texts, parameters, and configurations inputted into the Application by the User, including anthropometric parameters, training logs, plan structures, and chat conversations.
- "Processor" means a natural or legal person, public authority, agency, or other body which processes Personal Data on behalf of the Controller, including Supabase Inc., the AI Providers, PostHog, Sentry, and RevenueCat in their respective capacities.
- "Sub-processor" means a third party engaged by a Processor to perform specific processing activities on behalf of the Controller.
- "Services" means all functionalities made available through the Application, including the Free Plan and the Premium Plan subscription tier.
- "Third Country" means any country outside the European Economic Area (EEA) that has not been the subject of an adequacy decision by the European Commission pursuant to Article 45 GDPR.
3Identity and Contact Details of the Controller
The Controller of Personal Data processed in connection with the use of the Application is: Kamil Mazurkiewicz, conducting business activity under the trade name SpringBoard, contactable at: kmdevworks.contact@gmail.com or contact@springboardlift.com.
Users may contact the Controller in all matters concerning the processing of their Personal Data, exercise of data subject rights, and lodging of complaints, using the electronic mail address stated above. The Controller undertakes to respond to correspondence relating to data protection matters within thirty (30) calendar days of receipt.
4Categories of Personal Data Collected
4.1 Identification and Authentication Data
- Electronic mail address (e-mail), used as the primary Account identifier;
- Cryptographic hash of the User's password (stored exclusively in hashed form; the Controller does not retain plaintext passwords);
- Where the User signs in with Google: the e-mail address and basic profile information that Google makes available to the Application through the sign-in flow (for example, name, where provided), and the Google account identifier;
- A randomly generated Account identifier, which is also used to link the Account across the services described in Section 6;
- Account creation timestamp and last-authentication metadata.
4.2 Anthropometric and Training Data
- Body mass, height, and derived biometric parameters (e.g., body mass index) where voluntarily provided;
- Exercise logs: exercise names, sets, repetitions, loads (in kilograms or pounds), and rest intervals;
- User-defined workout plan architectures, training blocks, and periodisation schemes;
- Dynamic indicators of central nervous system (CNS) fatigue and per-muscle-group recovery status, as calculated by the Application's algorithms on the basis of User-inputted training data.
4.3 Step and Activity Data
- Daily step totals calculated from the step counter sensor of the User's device. This requires the "Physical activity" (Activity Recognition) permission, which the Application requests separately and which the User may refuse or revoke at any time in the device settings;
- Where the User additionally grants access, step totals read from Health Connect (read-only access to the "Steps" data type). The Application does not write any data to Health Connect;
- Technical reference values of the step counter sensor (for example, the last reading and the day on which it was taken), stored so that daily totals are calculated correctly and steps taken while the Application is closed are not lost;
- The daily step goal set by the User, and the walking distance estimated from the step count and the User's height (calculated on the device).
To keep daily totals accurate, the Application periodically reads the step counter in the background (approximately every fifteen minutes), including when the Application is closed. This does not involve location tracking, and the Application does not use Step Data to determine the User's location.
Health Connect. Data obtained through Health Connect is used solely to provide and improve the user-facing step tracking features of the Application. It is not used or transferred for advertising purposes, is not sold, and is not used to determine credit-worthiness or for insurance purposes. It is not transferred to third parties except where necessary to comply with applicable law, and it is not read by humans unless the User has given consent, it is necessary for security purposes, or it is required by law.
4.4 AI Services Interaction Data
- Textual content of conversational queries submitted to the AI Services (chat metadata);
- AI-generated responses stored for continuity of the User session;
- Aggregated usage metrics relating to the daily interaction volume limits applicable under the Free Plan and the Premium Plan.
4.5 Technical and Device Data
- Anonymised or pseudonymised application session logs stored on Supabase infrastructure;
- Crash reports, error diagnostics, and performance traces generated by the Application (for example, stack traces, device model, operating system version, Application version, and the Account identifier), collected through Sentry;
- Product analytics events (screens viewed and Application lifecycle events such as installation, opening, and updating), associated with the Account identifier, collected through PostHog;
- Subscription and purchase status (for example, the active plan, purchase and renewal dates, and store transaction identifiers), linked to the Account identifier and managed through RevenueCat;
- User interface cache data and query-limit identifiers stored in SharedPreferences / Local Storage on the User's device (persisted locally; not transmitted to the Controller's servers);
- Application version, operating system type and version, and device locale settings.
4.6 Data Not Collected
The Controller expressly does not collect: precise geolocation data (including for the purposes of step counting); payment card or banking details (subscription payments are processed exclusively by Google Play Billing or Apple In-App Purchase, and the Controller receives only a non-sensitive transaction confirmation and the resulting subscription status, including through RevenueCat); biometric identifiers within the meaning of Article 9 GDPR; or any data relating to minors under the age of sixteen (16).
4.7 Website and iOS Waitlist Data
If the User joins the iOS waitlist on the website springboardlift.com, the Controller collects the User's electronic mail address, the language setting of the User's web browser, the date and time of sign-up and the source page of the sign-up. The website does not use cookies, tracking technologies or analytics tools.
5Purposes and Legal Bases for Processing
The Controller processes Personal Data for the following purposes and on the following legal bases pursuant to Article 6 GDPR:
5.1 Performance of a Contract (Article 6(1)(b) GDPR)
- Creation, maintenance, and authentication of the User's Account;
- Provision of the core features of the Application, including workout tracking and AI Services, including the transmission of User Content to the AI Providers for the purpose of generating responses;
- Calculation, storage, and display on the User's device of step counts, the daily step goal, and estimated distance (subject to the consent described in Section 5.4 where Step Data is regarded as data concerning health);
- Administration of the Free Plan and Premium Plan subscription, including verification of subscription status (through RevenueCat) and enforcement of daily AI interaction limits.
5.2 Legitimate Interests of the Controller (Article 6(1)(f) GDPR)
- Detection, investigation, and prevention of fraudulent activity, abuse, and violations of the Terms of Service;
- Ensuring the technical security and operational integrity of the Application and its infrastructure, including the detection and diagnosis of crashes and errors (through Sentry);
- Statistical analysis and product analytics (through PostHog) for the purpose of understanding how the Application is used and improving its features. Analytics events are linked to a pseudonymous Account identifier and are therefore pseudonymised, not anonymous, data.
The User may object to processing based on legitimate interests as described in Section 8.
5.3 Compliance with Legal Obligations (Article 6(1)(c) GDPR)
- Retention of data required by applicable tax, accounting, and consumer protection legislation;
- Response to lawful requests of competent public authorities.
5.4 Consent (Article 6(1)(a), Article 9(2)(a) and Article 49(1)(a) GDPR)
Where the Controller sends optional electronic communications (e.g., product newsletters), solely on the basis of the User's freely given, specific, informed, and unambiguous consent, which may be withdrawn at any time without detriment.
Where User Content is transmitted to an AI Provider located in a Third Country in respect of which no adequacy decision exists (see Section 6.3), such transmission takes place on the basis of the User's explicit consent, given by an active, separate action in the Application before first use of any AI feature, after being informed of the risks described in Section 6.3. The User may withdraw this consent at any time in the Application settings or by contacting the Controller, without prejudice to the lawfulness of processing carried out before withdrawal.
To the extent that Step Data is regarded as data concerning health within the meaning of Article 9 GDPR, it is processed on the basis of the User's explicit consent, given by granting the relevant system permission (Activity Recognition and/or Health Connect) after the Application has explained why the permission is needed. The User may withdraw this consent at any time by revoking the permission in the device settings or in Health Connect. Withdrawal stops further collection and does not affect the lawfulness of processing carried out before withdrawal. Without this permission, step counting is not available, while the other features of the Application remain usable.
5.5 iOS Waitlist (Article 6(1)(a) GDPR)
The electronic mail address provided on the iOS waitlist is processed solely to notify the User when the Application becomes available on iOS, on the basis of the User's consent. The User may withdraw consent at any time by using the unsubscribe link included in the notification or by contacting the Controller. Withdrawal does not affect the lawfulness of processing carried out before withdrawal.
6Data Processors and International Transfers
6.1 Supabase Inc.
The Controller has engaged Supabase Inc. (548 Market St PMB 72296, San Francisco, CA 94104, USA) as a data Processor for the following purposes: hosting and storage of Account identification data and training logs; user authentication and session management; and retention of application-level log data. Data processing by Supabase Inc. is governed by a Data Processing Agreement (DPA) incorporating the Standard Contractual Clauses (SCCs) adopted by European Commission Implementing Decision (EU) 2021/914 of 4 June 2021, constituting an appropriate safeguard for transfers to a Third Country pursuant to Article 46(2)(c) GDPR.
6.2 Google LLC (Google Cloud / AI Studio — Gemini API)
As a fallback in case the DeepSeek service is unavailable or returns an error (Section 6.3), the Controller utilises Google Cloud infrastructure and the Google AI Studio Gemini API, operated by Google LLC (1600 Amphitheatre Parkway, Mountain View, CA 94043, USA), for the processing of User Content and associated metadata transmitted via serverless Edge Functions. The Controller warrants that:
- User Content transmitted to the Gemini API is not used for the training of publicly available large language models (LLMs);
- Data transmission occurs exclusively pursuant to the applicable Google Cloud Data Processing Addendum, which incorporates SCCs as the appropriate transfer mechanism under Article 46 GDPR.
6.3 DeepSeek (Hangzhou DeepSeek Artificial Intelligence Co., Ltd.)
The primary language model used for all AI Services is DeepSeek V4, provided via the official DeepSeek API (api.deepseek.com) by Hangzhou DeepSeek Artificial Intelligence Co., Ltd., a company established in the People's Republic of China. Each AI request is sent to DeepSeek first. Only if the DeepSeek service returns an error or is unavailable is the request automatically redirected to Google Gemini (Section 6.2). User Content is transmitted through the Controller's serverless Edge Functions and consists of: the text of the User's query, the User's training history, and the calculated fatigue level necessary to generate a response. The Controller does not transmit the User's e-mail address, name, or Account identifier to DeepSeek. As at the date of this Policy, Step Data is not included in the data transmitted to the AI Providers.
Transfer to a Third Country. According to DeepSeek's published privacy policy, data is processed and stored on servers located in the People's Republic of China, for which the European Commission has not issued an adequacy decision. The Controller has no standard contractual clauses or other Article 46 GDPR safeguard in place with DeepSeek. The laws of the People's Republic of China may allow public authorities to access data held by DeepSeek, and the level of protection may be lower than in the EEA, and enforcing your rights against DeepSeek may be difficult or impossible. For these reasons, User Content is transmitted to DeepSeek only on the basis of the User's explicit consent pursuant to Article 49(1)(a) GDPR, as described in Section 5.4. A User who does not give consent can still use the Application, but the AI Services will not be available.
Use of data by DeepSeek. DeepSeek acts under its own terms and privacy policy, on which the Controller has no influence. DeepSeek does not publish a fixed retention period for data sent through its API, and its terms and privacy policy may allow it to use submitted content to develop and improve its models. The Controller cannot guarantee that User Content will not be used for those purposes, nor can the Controller guarantee its deletion. In contrast to Google (Section 6.2), no such warranty is given in relation to DeepSeek. Users are therefore advised not to include in the AI chat any information they do not wish to be processed in this way.
6.4 Local Device Storage
Certain data is stored exclusively in SharedPreferences (Android) or equivalent Local Storage mechanisms (iOS) on the User's physical device — specifically, user interface preference settings, interface cache, session-independent query-limit counters, and Step Data (daily step totals, sensor reference values, and the daily step goal). Step Data is Personal Data. The Application does not transmit this data to the Controller or to any Processor. Depending on the User's device settings, the device's operating system may include Application data in device backups made to the User's own account with the operating system provider, which is outside the Controller's control.
6.5 PostHog (Product Analytics)
The Application uses PostHog (PostHog, Inc.) for product analytics. Events are sent to PostHog's European cloud infrastructure and consist of the Account identifier, names of screens viewed, Application lifecycle events, and basic device information. The Controller does not send the content of training logs, AI chat messages, Step Data, or the User's e-mail address to PostHog. Because PostHog, Inc. is established in the United States, access to data from outside the EEA cannot be excluded; any such transfer is governed by the data processing agreement of PostHog, which incorporates the Standard Contractual Clauses.
6.6 Sentry (Crash Reporting and Performance Monitoring)
The Application uses Sentry (Functional Software, Inc., trading as Sentry) to detect and diagnose crashes, errors, and performance problems. Reports are sent to Sentry's European (Germany) data region and contain technical information about the error, the device model, the operating system and Application versions, and the Account identifier. Because Sentry is established in the United States, access to data from outside the EEA cannot be excluded; any such transfer is governed by the data processing agreement of Sentry, which incorporates the Standard Contractual Clauses.
6.7 RevenueCat (Subscription Management)
To manage and validate subscriptions purchased through Google Play or the Apple App Store, the Application uses RevenueCat, Inc. (United States). RevenueCat receives the Account identifier, purchase information from the relevant store, and the resulting subscription status, and may process technical identifiers (such as the IP address) necessary to provide its service. Any transfer to the United States is governed by the data processing agreement of RevenueCat, which incorporates the Standard Contractual Clauses.
6.8 Platform and Sign-In Providers
Distribution of the Application via Google Play Store (Google LLC) and Apple App Store (Apple Inc., One Apple Park Way, Cupertino, CA 95014, USA) may result in those platform providers processing certain technical metadata in accordance with their own, independent privacy policies. Where the User signs in with Google, Google LLC authenticates the User as an independent controller under its own privacy policy and shares with the Application the data described in Section 4.1. The Controller bears no responsibility for the data processing practices of platform providers and sign-in providers acting as independent controllers.
6.9 Cloudflare, Inc.
The Controller uses Cloudflare, Inc. (101 Townsend St, San Francisco, CA 94107, USA) to host the website springboardlift.com and to route electronic mail sent to addresses in the springboardlift.com domain. Cloudflare processes technical data necessary to deliver the website and e-mail (such as IP addresses and request metadata). Waitlist data submitted through the website is stored with Supabase (Section 6.1).
7Data Retention Periods
Personal Data shall be retained for the following periods:
- Account Data: for the duration of the active Account and for a period of three (3) years following Account deletion, unless a longer retention period is mandated by applicable law (e.g., tax obligations);
- Training and Anthropometric Data: for the duration of the active Account; deleted within ninety (90) days of Account deletion upon User request;
- AI Services Interaction Data (chat metadata): retained on Supabase servers for a rolling period of twelve (12) months from the date of each interaction, then permanently deleted;
- Data held by AI Providers: retained by each AI Provider in accordance with its own terms. Google determines retention under the applicable Google Cloud terms. DeepSeek does not publish a fixed retention period, and the Controller has no influence over how long data is retained by DeepSeek;
- Step Data: stored on the User's device only, until the User uninstalls the Application or clears the Application's data. Revoking the Activity Recognition or Health Connect permission stops further collection but does not delete totals already stored on the device. The Controller has no access to Step Data and does not retain it;
- Analytics, crash, and subscription data (PostHog, Sentry, RevenueCat): retained only for as long as necessary for the purposes described in Section 5, in line with the retention settings applied by the Controller in each service and the provider's terms. Upon deletion of an Account, the Controller will take steps to have the Account-linked data in these services deleted or anonymised, except where retention is required by law (for example, records of purchases);
- Application Log Data: retained for a period of ninety (90) days for security and debugging purposes, then automatically purged;
- Other data on Local Device Storage: persisted until the User uninstalls the Application or manually clears Application data through device settings.
- iOS Waitlist Data: until the iOS launch notification is sent and no longer than three (3) months thereafter, or until earlier withdrawal of consent;
Upon expiry of the applicable retention period, Personal Data shall be permanently deleted or irreversibly anonymised in a manner that prevents re-identification.
8Rights of Data Subjects
Pursuant to Chapter III GDPR, every User has the following rights with respect to their Personal Data:
- Right of Access (Article 15 GDPR): the right to obtain confirmation as to whether Personal Data are being processed and, if so, to receive a copy thereof.
- Right to Rectification (Article 16 GDPR): the right to obtain rectification of inaccurate Personal Data and completion of incomplete data.
- Right to Erasure / "Right to be Forgotten" (Article 17 GDPR): the right to obtain erasure of Personal Data where one of the grounds specified in Article 17(1) GDPR applies.
- Right to Restriction of Processing (Article 18 GDPR): the right to obtain restriction of processing in the circumstances set out in Article 18(1) GDPR.
- Right to Data Portability (Article 20 GDPR): the right to receive Personal Data in a structured, commonly used, and machine-readable format and to transmit it to another controller, where processing is based on consent or contract.
- Right to Object (Article 21 GDPR): the right to object, on grounds relating to the User's particular situation, to processing based on legitimate interests.
- Right to Withdraw Consent (Article 7(3) GDPR): where processing is based on consent, the right to withdraw such consent at any time, without prejudice to the lawfulness of processing prior to withdrawal.
- Right to Lodge a Complaint: the right to lodge a complaint with the President of the Office for Personal Data Protection (Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warsaw, Poland), or with the supervisory authority in the User's Member State of habitual residence.
9Local Storage and Device-Side Data
The Application does not use browser-based cookies. However, it employs the following device-side storage mechanisms:
- SharedPreferences (Android) / NSUserDefaults (iOS): used for storing user interface preferences (e.g., dark mode setting, unit system), query-limit counters for rate-limiting purposes under the Free Plan, and Step Data together with the daily step goal. The step-related entries are Personal Data processed as described in Section 4.3; the remaining entries are strictly functional and do not constitute profiling or behavioural tracking.
- In-Memory Cache: transient session data that is cleared upon Application closure and is never persisted to disk.
No third-party advertising SDKs or cross-app tracking frameworks are embedded in the Application. The Application does embed the SDKs of PostHog (product analytics), Sentry (crash reporting and performance monitoring), and RevenueCat (subscription management), which process the data described in Sections 4.5 and 6.
10Protection of Minors
The Application is intended exclusively for natural persons who have attained the age of sixteen (16) years. The Application does not knowingly collect Personal Data from individuals under the age of sixteen (16). If the Controller becomes aware that Personal Data of a minor under the age of sixteen (16) has been collected without verifiable parental or guardian consent, the Controller shall promptly take steps to delete such data.
Parents or legal guardians who believe that their minor child has provided Personal Data to the Application without consent are requested to contact the Controller at the address specified in Section 3.
11Security Measures
The Controller implements appropriate technical and organisational measures, in accordance with Article 32 GDPR, to ensure a level of security appropriate to the risk, including:
- Encryption (TLS 1.2 or higher) for all data in transit between the Application, the Supabase backend servers, and the AI Providers;
- Storage of User passwords exclusively in the form of irreversible cryptographic hashes using industry-standard hashing algorithms (e.g., bcrypt/Argon2), as managed by Supabase Authentication;
- Role-based access controls and row-level security policies (RLS) on the Supabase database layer, ensuring that each User can access exclusively their own data;
- Data minimisation in communication with AI Providers: requests are routed through the Controller's server-side Edge Functions, API keys are never stored in the Application, and e-mail addresses and Account identifiers are not forwarded to AI Providers;
- Regular security assessments of the Application's infrastructure;
- Contractual obligations on Processors to implement equivalent security standards where the provider's standard terms allow it; the Controller does not have a negotiated agreement with DeepSeek.
In the event of a Personal Data Breach that is likely to result in a high risk to the rights and freedoms of natural persons, the Controller shall notify the affected Users without undue delay, in accordance with Article 34 GDPR.
12Changes to This Policy
The Controller reserves the right to amend this Policy at any time, in particular to reflect changes in applicable law, decisions of supervisory authorities, changes of AI Providers, or modifications to the Application's features. In the event of material amendments, the Controller shall notify Users by means of an in-application notice or electronic mail sent to the address associated with the User's Account, no less than fourteen (14) days prior to the entry into force of the amended Policy.
Continued use of the Application following the effective date of an amended Policy shall constitute the User's acceptance of the changes, to the extent permitted by applicable mandatory law. Where the amendment requires renewed consent (including consent under Section 5.4), the User shall be explicitly invited to provide such consent.
13Governing Law
This Policy is governed by the law of the Republic of Poland. In matters not regulated by this Policy, the provisions of the GDPR, the DSA, and applicable Polish civil law shall apply. Any disputes arising from or in connection with this Policy shall be subject to the jurisdiction of the competent Polish courts, without prejudice to the User's right to bring proceedings before the supervisory authority as set out in Section 8.