Thermowise — Privacy Policy
Draft, not legal advice. Check with a lawyer before publication.
Placeholders in
[...]must be filled in before publication. Items marked [to confirm] are proposals of the draft, not decisions. The retention periods in section 7 are proposals.
Last updated: [date] Version: 0.1 (draft)
This policy explains what personal data Thermowise (the “App”) processes, why, and what rights you have under the EU General Data Protection Regulation (GDPR, Regulation (EU) 2016/679) and, for users in the USA, applicable state privacy laws. Read it together with the Terms of Use.
1. Who is responsible (controller)
The controller is [full name], a self-employed person (OSVČ) registered in the Czech Republic, company ID (IČO) [IČO], address [address].
Contact for privacy questions and requests: [contact email].
A data protection officer has not been appointed, because we are not required to. [to confirm]
2. What data we process
| Category | What | When |
|---|---|---|
| Settings and choices | Default sport, thermal type (1–5), units, language, theme, entries for each recommendation (sport, duration, workout type, terrain) | Always. In guest mode stored on your device; with an account also in our cloud database |
| Account | Account ID, email address, display name and profile picture from your sign-in provider (Google; Apple and email may be added), role (user / tester / admin), sign-in method | If you sign in |
| Location | Approximate or precise device location | Only when you allow it, only to get the weather forecast for your position. We do not track you in the background. You can enter a place by hand instead |
| Journal and feedback | Recommendations you received, whether you wore what was recommended and what you changed, overall feeling, per-zone feedback (for example “hands cold”), workout time and place, the weather at that time | If you sign in and use the journal |
| Strava data | Strava athlete ID, access and refresh tokens (stored only on the server side), and for each activity: sport type, name, start date and time, elapsed time, start coordinates, average heart rate (if present) | Only if you connect Strava. Initial import covers the last 7 days, then new activities by webhook |
| Subscription | Subscription status, plan, trial and expiry dates, store transaction identifiers. We do not receive your card number or payment details — the store handles them | If you buy Pro |
| Notifications | Push token of your device (Firebase Cloud Messaging), notification settings | If you allow notifications |
| Analytics | App events (for example which screens or features are used: recommendation requested, paywall shown), device and app information (model, OS version, app version), anonymous or pseudonymous app-instance ID | Only with your consent (see section 8) |
| Crash reports | Crash and error logs, device model, OS version, app version, app state at the time of the crash | See section 8 |
| Technical data | IP address and request logs processed by our backend (Firebase, Google Cloud) for security and operation | When the app talks to our servers |
We do not send location, health data (such as heart rate), names or email addresses to analytics or crash reporting. Average heart rate imported from Strava and feedback about how you felt (for example “hands cold”) are data concerning health (special category data under Art. 9 GDPR). We process them only on the basis of your explicit consent under Art. 9(2)(a), as described below. [to confirm with lawyer]
3. Purposes and legal bases
| Purpose | Data | Legal basis (GDPR) |
|---|---|---|
| Provide the clothing recommendation (weather for your position, your settings) | Settings, location | Art. 6(1)(b) — performance of the contract (the Terms); location is processed on the basis of your permission in the device |
| Create and manage your account, sign-in, roles | Account data | Art. 6(1)(b) — contract |
| Keep a workout journal, collect feedback and improve your personal recommendations | Journal, feedback, settings | Art. 6(1)(b) — contract; for health-related content Art. 9(2)(a) — explicit consent (you give it when you enter feedback or connect Strava) |
| Import workouts from Strava | Strava data | Art. 6(1)(a) — consent (you connect Strava and can disconnect any time); Art. 9(2)(a) for health-related data |
| Send reminders (“How was it?”) and workout notifications | Push token, schedule | Art. 6(1)(b) — contract / Art. 6(1)(a) consent to push notifications (system permission) |
| Manage subscriptions, check Pro entitlement | Subscription data | Art. 6(1)(b) — contract; Art. 6(1)(c) — legal obligations (accounting, tax) |
| Improve and calibrate the recommendation system | Journal and feedback, in aggregated or anonymised form. Strava-derived data of public users is excluded (used only for the user’s own journal) until the Strava API terms question is closed [to confirm] | Art. 6(1)(a) — consent; for health-related content Art. 9(2)(a) — explicit consent specifically for calibration, collected on a separate consent screen in the App (you can refuse or withdraw it without losing any feature) [to confirm with lawyer: if only fully anonymised data is used, it is no longer personal data] |
| Product analytics | Analytics events | Art. 6(1)(a) — consent (and for the device storage/access also the ePrivacy rules) |
| Crash reporting and stability | Crash data | Art. 6(1)(f) — legitimate interest in keeping the app working; crash data contains no personal data by design [to confirm: or ask for consent too] |
| Security, abuse prevention, defending legal claims | Technical data, account data | Art. 6(1)(f) — legitimate interest |
| Accounting and tax | Subscription payouts | Art. 6(1)(c) — legal obligation |
| Private areas for testers and the admin (training log, calibration) | Training log data of invited testers, account data | Art. 6(1)(b) — agreement with the invited tester; Art. 6(1)(a) — consent; for health-related data (how the workout felt, average heart rate from Strava) Art. 9(2)(a) — explicit consent, which the tester gives when accepting the invitation |
Providing data is voluntary, but without some data (for example location or an account) parts of the App cannot work.
4. Who receives your data (recipients)
We use the following processors and independent providers. They process data only as needed for the stated purpose.
| Recipient | Role | What for | Data |
|---|---|---|---|
| Google (Firebase / Google Cloud) — Firestore, Authentication, Cloud Functions, Cloud Messaging, Analytics, Crashlytics | Processor | Database, server functions, sign-in, push, analytics, crash reports | Account, settings, journal, push token, analytics events, crash data. Our database and functions run in europe-west3 (Frankfurt, Germany) |
| Google (Sign-In) | Independent controller for its own sign-in | Signing in with Google | Identity data you choose to share |
| Apple (Sign in with Apple, App Store, push service) | Independent controller | Sign-in, billing, delivering push | Identity data you choose to share, purchase status, push token |
| Google Play / Apple App Store | Independent controllers (sellers of record) | Subscriptions, payments, refunds | Purchase and subscription status (we do not receive payment details) |
| Strava, Inc. | Independent controller | Importing your workouts when you connect | Activities you authorise; Strava receives our authorisation requests and webhook traffic |
| Open-Meteo | Independent provider of weather data | Weather forecast and historical weather | Coordinates of the requested place (rounded where practical) and requested time; no account data. Technical data such as IP address may be visible to Open-Meteo depending on how requests are made [to confirm: whether requests go through our backend] |
| Subscription management provider (for example RevenueCat, if used) [to confirm] | Processor | Checking subscription status | Subscription identifiers |
| Authorities, courts, advisers (accountant, lawyer) | Recipients where required | Legal obligations and defence of claims | Only what is necessary |
We do not intend to sell your personal data or use it for advertising. [to confirm: the project documents do not yet say how Firebase Analytics is configured. Before publication check that advertising personalisation and linking to Google advertising services are disabled in Firebase; only then keep this statement]
5. Transfers outside the EU / EEA
Our main data is stored in the EU (Frankfurt). Some providers (Google, Apple, Strava, RevenueCat if used) are companies in the USA or have group companies and support staff outside the EU/EEA, so data may be transferred there. We rely on:
- the EU–US Data Privacy Framework where the provider is certified (Google, Apple and others);
- otherwise the EU Standard Contractual Clauses (Art. 46 GDPR) with additional safeguards.
Open-Meteo and Strava have their own policies. You can obtain a copy of the safeguards by writing to [contact email]. [to confirm certification status of each provider before publication]
6. Automated decisions
Recommendations are generated automatically from weather data and your settings. This is not a decision that produces legal effects or similarly significantly affects you. We do not profile you for advertising.
7. How long we keep data
These periods are proposals [to confirm]:
| Data | Retention |
|---|---|
| Guest settings | On your device only, until you delete the App or its data |
| Account, settings, journal, feedback | As long as you have an account. Deleted when you delete your account (within 30 days; backups are overwritten within a further [35] days) |
| Strava tokens | Until you disconnect Strava or delete your account; then deleted at once |
| Imported Strava activities | As long as the journal exists; deleted on account deletion. An activity deleted in Strava is marked in the App (the filled-in log is kept). [to confirm: whether imported activities stay or are deleted when Strava is disconnected] |
| Push token | Until you turn off notifications, sign out or delete your account |
| Subscription records | Kept for the period required by Czech accounting and tax law (generally up to 10 years) in the minimum necessary form |
| Analytics | Per Firebase settings, [14 months] at most [to confirm] |
| Crash reports | [90 days] per Crashlytics default [to confirm] |
| Security logs | Up to [6 months] [to confirm] |
| Anonymised or aggregated data | May be kept indefinitely; it no longer identifies you |
| Inactive accounts | [to confirm: for example deleted after 24 months of inactivity after notice] |
8. Consent to analytics and crash reporting
8.1. Analytics (Firebase Analytics) is switched off until you agree in the consent screen. You can change your decision at any time in Settings. Withdrawing consent does not affect processing before that.
8.2. Analytics events and crash reports do not contain your coordinates, health data (such as heart rate), name or email address. Events use only coarse values (for example, a duration range, the sport).
8.3. Crash reports (Crashlytics) are used to find and fix errors. They are designed to carry no personal data. They may include technical data such as device model, OS and app version, and an installation identifier. Where the law requires consent for them, we ask for it. [to confirm with lawyer: default on or with consent]
8.4. Debug builds do not send data to production analytics.
9. Your rights
Under the GDPR you have the right to:
- access your data and get a copy (Art. 15);
- rectification of inaccurate data (Art. 16);
- erasure (“right to be forgotten”) (Art. 17) — you can delete your account in the App (Settings), and we will delete your data as described in section 7;
- restriction of processing (Art. 18);
- data portability (Art. 20) — receive the data you provided in a structured, commonly used, machine-readable format;
- object (Art. 21) to processing based on legitimate interest, at any time on grounds relating to your situation;
- withdraw consent at any time (Art. 7(3)), for example for analytics, Strava or notifications;
- not be subject to solely automated decisions with significant effects (Art. 22) — see section 6.
To use a right, write to [contact email]. We answer within one month (can be extended by two months for complex cases, with notice). We may ask you to verify your identity. Exercising your rights is free unless requests are manifestly unfounded or excessive.
Complaint. You have the right to lodge a complaint with a supervisory authority. In the Czech Republic that is the Office for Personal Data Protection (Úřad pro ochranu osobních údajů, ÚOOÚ), Pplk. Sochora 27, 170 00 Praha 7, www.uoou.cz ([to confirm the address]). You can also complain to the authority in the EU country where you live or work.
Users in the USA. Depending on your state (for example California, Colorado, Virginia and others), you may have rights to know, access, correct, delete and port your data, and to opt out of the sale or sharing of personal data and of targeted advertising. We do not intend to sell or share personal data for such advertising [to confirm: see the note in section 4 about Firebase advertising settings]. You can use the same contact for requests; you will not be treated worse for using your rights. [to confirm with lawyer: applicability thresholds and the California notice at collection]
10. Strava and other connected accounts
When you connect Strava, you grant us access in Strava’s consent screen (scope activity:read_all). You can disconnect at any time in the App or in your Strava settings (Settings → My Apps). On disconnect we delete the tokens and the webhook mapping and stop receiving activities. Activities already imported [to confirm: stay in your journal until you delete them or your account / are deleted on disconnect]. Strava’s own processing is under Strava’s privacy policy. We use Strava data only to run your journal and to improve your recommendations, and we follow the Strava API Agreement. [to confirm with lawyer: Strava API terms on storage and on analysis / model training; per-user calibration]
11. Children
The App is not directed to children under 16 [to confirm; Czech digital-consent age is 15, so 16 is a safer uniform limit], and we do not knowingly collect data from them. If you are under 16, do not use the App or provide data. If we learn that we hold data of a child under 16 without valid parental consent, we will delete it. A parent can contact us at [contact email]. In the USA the App is not directed to children under 13 (COPPA).
12. Security
We use access control, role checks in security rules and server code, encrypted transfer (TLS), and encryption at rest provided by Google Cloud. Strava tokens are stored only on the server side and never in the App. No system is completely secure. In case of a personal data breach we will notify the authority and, where required, you, as GDPR requires.
13. Cookies and similar technologies (web)
The web version is currently an admin panel for the owner only. When a public web version is launched, this section will describe cookies and similar technologies and the consent mechanism. [to update]
14. Changes to this policy
We may update this policy. We will publish the new version in the App and, for material changes, notify you in the App or by email in advance [at least 30 days]. Where the law requires consent, we will ask for it again. The date at the top shows the latest version.
15. Contact
[full name], IČO [IČO] [address] Email: [contact email]