Privacy Policy — Greenzone
Effective date: July 3, 2026 Version: 1.0 (covers app versions v1–v3; forward-looking notes for planned features are marked)
1. Controller
The controller responsible for data processing on joingreenzone.de and joingreenzone.com is:
Philip Hattemer Falkenstr. 8A 81541 München, Germany Email: hello@joingreenzone.com
Greenzone is operated by a private individual in Germany. No Data Protection Officer has been appointed, as the statutory thresholds (Art. 37 GDPR, § 38 BDSG) are not met. Re-assess if user numbers or processing scope grow significantly.
2. What Greenzone Is — and Is Not
Greenzone is a personal fitness tracking application for military personnel, reservists, law enforcement officers, and civilian athletes. It is a private tool for personal use only:
- Greenzone is not connected to the Bundeswehr, any police force, or any government or military system.
- No data is ever shared with your employer, your unit, any military authority, or any government body. There is no interface, export, or reporting channel to any such organisation.
- Your results are not official test records.
3. Registration and Accounts
Greenzone is currently invite-only: the operator creates accounts manually. When open registration is introduced, this policy will be updated. You register with an email address and password (processed by our authentication provider Supabase, see Section 7). You choose a public alias/username instead of your real name — this is a deliberate privacy-by-design measure (Art. 25 GDPR). Your real name is not collected and never displayed.
Transactional emails (e.g. password recovery) are sent from noreply@joingreenzone.com via Ionos (see Section 7).
4. Categories of Data We Process
4.1 Account data
Email address, password (stored only as a cryptographic hash by Supabase Auth), alias/username, unit system preference (metric/imperial). Purpose: providing your account and logging you in. Legal basis: Art. 6(1)(b) GDPR (performance of contract).
4.2 Profile data (partly optional)
Date of birth (used solely for age-group benchmark calculations), gender (used for gender-specific benchmarks and test standards), height, body weight (logged over time), role (Military / Reserve / Police & Law Enforcement / Athlete Amateur / Athlete Professional / Other), nationality (flag picker, up to 2), military or police rank.
Rank, role, and nationality are optional. You may leave them empty. See Section 6 for considerations if you serve in a sensitive role. Purpose: correct benchmark comparison (age/gender-specific population norms and military test standards) and personalisation. Legal basis: Art. 6(1)(b) GDPR; for optional fields, Art. 6(1)(a) GDPR (consent, withdrawable by deleting the field).
4.3 Health and biometric data — special category data (Art. 9 GDPR)
If you choose to use the Bio & Health features, Greenzone processes data you enter manually:
VO2max, resting heart rate (average and minimum), maximum heart rate, weekly minutes in heart rate zones 1–3 and 4–5, heart rate variability (HRV), respiratory rate (average and low), lean body mass (kg and %), body fat % (with measurement method: bioimpedance, calipers, or DEXA), biological age / "Whoop Age", pace of aging, blood pressure (systolic/diastolic), weekly strength minutes, anaerobic threshold.
Body weight over time (4.2) is also treated as health data in this context.
Source: You type these values in manually, typically from your own wearable (e.g. Whoop). Greenzone has no connection to any device API and imports nothing automatically. You alone decide which values to enter, and every field is optional. Purpose: your personal scorecard, trend charts, and benchmark comparison. Legal basis: your explicit consent, Art. 9(2)(a) GDPR, given when you first activate a health metric. You can withdraw consent at any time by deleting the entries or your account (Section 10).
4.4 Fitness test results and training entries
Results of standardised tests and training sessions you log: DSA (Deutsches Sportabzeichen), BFT (Basis-Fitness-Test), KSK PFV (selection preparation, e.g. 5×1000 m interval run), 7D Test (Sieben-Disziplinen-Test), general fitness indicators (plank, dead hang, push-ups, pull-ups, sit-ups, standing long jump, vertical jump, sit-and-reach, grip strength, BMI), running results (3 km to 100 km ultra, Wings for Life), and endurance marches (time, distance, load weight).
Because performance data of this kind can allow inferences about physical fitness and health, we conservatively treat it under the same explicit consent (Art. 9(2)(a) GDPR) as Section 4.3, obtained at account activation. Purpose: logging, visualisation, personal-best tracking, benchmark comparison.
4.5 Technical data
Our hosting providers process connection data technically necessary to deliver the service (IP address, browser type, timestamps) in server logs. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in secure, functional operation). Greenzone runs no analytics platform, no tracking pixels, no advertising — see the separate Cookie Policy.
4.6 Contact form
If you use the contact form, we process your name, email address, and message to handle your request. The message is delivered to our inbox by email via Ionos (see Section 7). Purpose: handling your request. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in responding to enquiries); where your request concerns your account, Art. 6(1)(b) GDPR. Retention: deleted once your request has been resolved, unless statutory retention obligations apply.
5. What We Do NOT Do
- No data sales, no advertising, no marketing emails.
- No tracking or analytics cookies (only the technically required Supabase Auth session, see Cookie Policy).
- No automated decision-making or profiling within the meaning of Art. 22 GDPR. Benchmark comparisons are simple calculations displayed only to you.
- No automatic import from wearables or third-party services.
- No disclosure to military authorities, employers, or government bodies.
6. Note for Military and Law Enforcement Users
Your scorecard is private by default — visible only to you when logged in (v1–v3 have no sharing features at all). Still, please consider before entering data:
- Rank, role, nationality, and unit-typical test results (BFT, PFV, 7D) could, in combination, allow inferences about your assignment. All of these fields are optional.
- You are responsible for complying with your own service and security regulations (e.g. OPSEC guidance of your organisation) when deciding what to enter.
- When social and group features launch (Section 12), sharing will always be opt-in per data dimension and will require separate consent.
7. Recipients and Sub-Processors
We use three processors under Art. 28 GDPR data processing agreements; details and transfer mechanisms are set out below:
| Provider | Function | Location of processing |
|---|---|---|
| Supabase | Database and authentication | EU — Frankfurt (eu-central-1) |
| Vercel | Hosting and content delivery | EU and US (DPF-certified; SCCs in DPA) |
| Ionos | Transactional email (noreply@joingreenzone.com) | Germany |
Supabase DPA signed 2026-07-02. Vercel's DPA is incorporated into its terms. Ionos AVV is part of their standard T&Cs.
No other recipients exist. Data is disclosed to authorities only where we are legally obliged to do so (Art. 6(1)(c) GDPR).
8. Transfers to Third Countries
Your content data (profile, health, fitness entries) is stored by Supabase in the EU. Vercel serves the application through global infrastructure that includes US endpoints; Vercel is certified under the EU-US Data Privacy Framework (DPF) and additionally offers Standard Contractual Clauses (Art. 46(2)(c) GDPR) in its DPA. Note: the DPF adequacy decision was upheld by the EU General Court in September 2025; an appeal is pending before the CJEU. Should the DPF be invalidated, transfers will rest on the SCCs.
9. Retention Periods
| Data | Retention |
|---|---|
| Account and profile data | Until account deletion |
| Health, biometric, and fitness entries | Until you delete the entry or your account |
| Inactive accounts | Deleted 24 months after last login, with 60 days' prior email notice |
| Contact requests | Deleted once the request is resolved, unless statutory retention obligations apply |
| Database backups | Typically 7–30 days after deletion, then purged from backups |
| Transactional email logs (Ionos) | Typically ≤ 30 days |
| Server logs (Vercel/Supabase) | Per provider default, typically ≤ 30 days |
10. Your Rights
You have the right to:
- Access (Art. 15) — a copy of all data we hold about you
- Rectification (Art. 16) — you can edit all entries yourself in the app
- Erasure (Art. 17) — delete individual entries in-app at any time, or request full account deletion
- Restriction of processing (Art. 18)
- Data portability (Art. 20) — until a self-service export exists, exports are provided on request in machine-readable format (JSON/CSV)
- Objection (Art. 21) — against processing based on legitimate interest
- Withdraw consent (Art. 7(3)) — at any time with effect for the future, e.g. by deleting health entries or your account; withdrawal does not affect the lawfulness of prior processing
To exercise your rights, email hello@joingreenzone.com. We respond within one month (Art. 12(3) GDPR).
11. Right to Lodge a Complaint
You may complain to a data protection supervisory authority, in particular in your member state of residence. The authority competent for the operator is:
Bayerisches Landesamt für Datenschutzaufsicht (BayLDA) https://www.lda.bayern.de
A list of all German authorities: https://www.bfdi.bund.de/DE/Service/Anschriften/Laender/Laender-node.html
12. Planned Features — Advance Notice
The following features are not yet active. None of them will change what happens to your existing data without your action; each will be introduced with updated notices and, where required, fresh consent:
- Social layer: friends will be able to see personal bests only in dimensions you individually select. Off by default; separate consent per connection and dimension.
- Group dashboards: shared scorecards for training groups or units. Joining a group is opt-in and requires explicit consent to visibility within that group. Members of sensitive units should weigh Section 6 before joining.
- Community benchmarks: aggregated, anonymised medians, computed only once a comparison group has 50+ members so individuals cannot be singled out.
- Pro tier with Stripe payments: Stripe will be added as a payment processor with its own sub-processor entry and updated policy before launch. Greenzone will not store card data.
13. Data Security
Transport encryption (TLS) on all connections; passwords stored only as hashes; database access protected by row-level security so each user can only access their own records; invite-only registration limits exposure in the current phase.
14. Changes to This Policy
We will update this policy when features or processors change and notify registered users by email or in-app notice of material changes. The current version is always available at https://joingreenzone.com/privacy.
This document is provided in English for convenience on joingreenzone.com. The German version (Datenschutzerklärung) on joingreenzone.de is the authoritative version in case of discrepancies.