Privacy Policy

Effective: 11 June 2026 · Pursuant to Art. 13 & 14 GDPR (DSGVO) and § 25 TTDSG

This Privacy Policy explains how Healtown collects, uses, stores, and shares your personal data, and sets out your rights under the EU General Data Protection Regulation (GDPR / DSGVO) and the German Telekommunikations-Telemedien-Datenschutzgesetz (TTDSG).

§ 1 — Data Controller (Verantwortlicher)

The data controller within the meaning of Art. 4(7) GDPR is:

Ali TaheriAzandaryani
Langewiesenweg 7
69469 Weinheim, Germany
Email: privacy@healtown.net
Website: healtown.net

A Data Protection Officer (Datenschutzbeauftragter) is not obligated under Art. 37 GDPR for the current scale of processing. Data protection enquiries may be directed to the controller at the contact details above.

§ 2 — Definitions

Terms used in this policy have the same meaning as defined in Art. 4 GDPR. In particular: "personal data" means any information relating to an identified or identifiable natural person; "processing" means any operation performed on personal data; "data subject" means the identifiable natural person to whom personal data relates.

§ 3 — Categories of Personal Data We Collect

3.1 Data You Provide Directly

Account data
Full name, email address, hashed password, role (Client / Provider), username, profile photo. Required for account creation.
Provider profile data
Business/professional name, biography, service descriptions, pricing, availability, session location (in-person address or online link), category.
Professional credentials
Certificates, diplomas, professional licences, or proof of insurance uploaded for Provider verification. Stored securely in access-controlled storage.
Identity verification data
Government-issued ID document and biometric selfie, processed by our KYC partner DiDit. Healtown does not receive or store raw biometric data — DiDit processes this under its own privacy policy and returns only a verification result.
Payment data
Booking amounts, refund records, and Stripe payment intent IDs. Full card numbers and payment credentials are processed exclusively by Stripe and are never stored on Healtown servers.
Messages
In-platform messages exchanged between Clients and Providers. Stored to enable the messaging feature and to resolve disputes.
Support communications
Emails, enquiries, and complaint records when you contact us.

3.2 Data Collected Automatically

Server logs
IP address, HTTP request method, URL, response code, browser type (User-Agent), timestamp. Collected automatically by the web server.
Authentication tokens
Session cookies and authentication tokens issued by Supabase Auth to maintain your logged-in session. These are strictly necessary.
Booking & transaction records
Automatically generated upon Booking confirmation: booking ID, listing ID, timeslot, status, payment intent reference, cancellation and refund events.

3.3 Special Category Data (Art. 9 GDPR)

Biometric data (selfie used for liveness detection) qualifies as special category data under Art. 9(1) GDPR. This data is processed exclusively by DiDit for identity verification purposes. Healtown processes this data only with your explicit consent (Art. 9(2)(a) GDPR), which you provide when initiating the identity verification flow. You may withdraw consent at any time; however, withdrawal will prevent you from publishing Listings as a Provider.

Healtown does not process health data of Clients beyond what Clients may voluntarily share with Providers via the messaging system. Clients are advised to review a Provider's own privacy notice before sharing health information.

§ 4 — Purposes of Processing and Legal Bases (Art. 13(1)(c)(d) GDPR)

Account management
To create and manage your user account, authenticate you, and provide access to the Platform. Legal basis: performance of contract — Art. 6(1)(b) GDPR.
Booking & payment processing
To confirm Bookings, process payments via Stripe, manage payouts to Providers, and handle refunds. Legal basis: performance of contract — Art. 6(1)(b) GDPR.
Notifications & email communications
To send booking confirmations, receipts, session reminders, and account alerts. Legal basis: performance of contract — Art. 6(1)(b) GDPR.
Identity verification (Providers)
To verify Provider identity via DiDit KYC to reduce fraud risk. Legal basis: legitimate interest (Art. 6(1)(f) GDPR) — protecting platform integrity and Client safety; additionally Art. 9(2)(a) GDPR for biometric data.
Credential verification (Providers)
To review and store professional certificates. Legal basis: legitimate interest — protecting Clients from unqualified practitioners — Art. 6(1)(f) GDPR.
In-app messaging
To facilitate communication between Clients and Providers. Legal basis: performance of contract — Art. 6(1)(b) GDPR.
Platform security & fraud prevention
To detect and prevent fraudulent, abusive, or illegal activity. Legal basis: legitimate interest — Art. 6(1)(f) GDPR.
Legal compliance
To retain accounting, tax, and transaction records as required by German law (§ 147 AO, § 257 HGB — 6/10 year retention). Legal basis: legal obligation — Art. 6(1)(c) GDPR.
Marketing communications
To send promotional emails, platform updates, or feature announcements. Legal basis: consent — Art. 6(1)(a) GDPR; or, for existing Clients, § 7 Abs. 3 UWG (legitimate interest in direct marketing of own similar services). You may opt out at any time.
Improving the Platform
Aggregated, anonymised usage analysis to improve platform features. Legal basis: legitimate interest — Art. 6(1)(f) GDPR.

§ 5 — Recipients and Data Processors (Art. 13(1)(e) GDPR)

We do not sell personal data. We share data only as necessary and under binding data processing agreements (Art. 28 GDPR) with the following third parties:

5.1 Infrastructure and Cloud Services

Supabase Inc.
Database (PostgreSQL), file storage, and authentication infrastructure. Data stored in Supabase's EU region. DPA: supabase.com/privacy. Category: data processor.
Hostinger International Ltd.
VPS hosting provider for the Platform server. EU datacenter used. Category: data processor.

5.2 Payment Processing

Stripe Payments Europe, Ltd.
Payment processing, Connect payouts to Providers, refund handling. Stripe processes cardholder data as an independent data controller for its own compliance purposes, and as a data processor for Platform payment operations. DPA and privacy: stripe.com/de/privacy. Data may be transferred to the USA under Standard Contractual Clauses (Art. 46 GDPR).

5.3 Identity Verification

DiDit (DiDit SAS)
Identity verification and biometric liveness check for Provider onboarding. DiDit processes the government-issued ID and selfie as a data processor under its own GDPR-compliant privacy policy. Healtown receives only the verification result (Approved / Declined). DPA: didit.me/privacy.

5.4 Email Delivery

Hostinger Email / SMTP
Transactional email delivery (booking confirmations, notifications). Email content includes name, email address, booking details.

5.5 Intra-Platform Sharing

Client → Provider
When a Client books a session, the Client's name and (where provided) contact details are shared with the relevant Provider to fulfil the Booking.
Provider → Client (public)
Provider name, profile photo, biography, and professional credentials (to the extent displayed on the Listing) are visible to all Platform users.

5.6 Legal Disclosure

Healtown may disclose personal data to competent authorities, courts, or regulators where required by law, court order, or to protect the rights and safety of Healtown, Users, or the public.

§ 6 — International Transfers (Art. 13(1)(f) GDPR)

The primary processing of personal data takes place within the European Economic Area (EEA). Where data is transferred to third countries (notably the United States, for Stripe), Healtown ensures that such transfers are subject to appropriate safeguards pursuant to Art. 46 GDPR, including:

  • Standard Contractual Clauses (SCCs) adopted by the European Commission (Decision 2021/914/EU).
  • Adequacy decisions where applicable.
  • Binding Corporate Rules or other approved transfer mechanisms.

A copy of the applicable transfer safeguards may be requested at privacy@healtown.net.

§ 7 — Data Retention Periods (Art. 13(2)(a) GDPR)

Account data
Retained for the lifetime of the account. Upon closure, account data is deleted or anonymised within 90 days, subject to legal retention obligations below.
Transaction records
10 years from the transaction date pursuant to § 147 AO (German Tax Code) and § 257 HGB (German Commercial Code).
Booking records
7 years from the date of booking for tax and accounting purposes.
Identity verification
Verification result (Approved/Declined) retained for the duration of the Provider account. Raw biometric data is processed and deleted by DiDit per their policy.
Professional credentials
Retained while the Provider account is active. Deleted within 90 days of account closure.
Server logs
14 days rolling retention. Anonymised thereafter for security analysis.
Messages
Retained for 3 years after the associated Booking to enable dispute resolution. Deleted thereafter unless subject to an active legal hold.
Marketing consents
Until consent is withdrawn or the account is closed.

§ 8 — Your Data Subject Rights (Art. 15–22 GDPR)

To exercise any of the rights below, contact us at privacy@healtown.net. We will respond within 30 days (extendable by a further 60 days for complex requests under Art. 12(3) GDPR). Requests are processed free of charge unless manifestly unfounded or excessive (Art. 12(5) GDPR).
Right of access (Art. 15)
Receive confirmation of whether we process your personal data and, if so, a copy of it.
Right to rectification (Art. 16)
Have inaccurate personal data corrected or incomplete data completed.
Right to erasure (Art. 17)
Request deletion of your personal data ('right to be forgotten'), subject to legal retention obligations and ongoing contractual necessity.
Right to restriction (Art. 18)
Restrict processing of your data where you contest its accuracy, object to processing, or we no longer need it but you require it for legal claims.
Right to portability (Art. 20)
Receive your personal data in a structured, machine-readable format (where processing is based on consent or contract and is automated).
Right to object (Art. 21)
Object at any time to processing based on legitimate interest (Art. 6(1)(f)), including profiling. We will cease processing unless we demonstrate compelling legitimate grounds that override your interests.
Right to withdraw consent (Art. 7)
Withdraw consent at any time where processing is based on consent. Withdrawal does not affect the lawfulness of prior processing.
Automated decision-making (Art. 22)
You have the right not to be subject to decisions based solely on automated processing, including profiling, that produce legal or similarly significant effects. Healtown does not currently make such decisions.
Right to complain (Art. 77)
Lodge a complaint with the competent supervisory authority. The authority for Baden-Württemberg is: Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg (LfDI BW), Lautenschlagerstraße 20, 70173 Stuttgart, poststelle@lfdi.bwl.de.

§ 9 — Cookies and Similar Technologies (§ 25 TTDSG)

The Platform uses cookies and similar storage technologies. Pursuant to § 25 TTDSG (implementing the EU ePrivacy Directive), we only set cookies requiring consent after obtaining your explicit agreement.

9.1 Strictly Necessary Cookies

These cookies are essential for the Platform to function. They do not require your consent under § 25 Abs. 2 Nr. 2 TTDSG. They include:

sb-auth-token
Supabase session authentication cookie. Maintains your logged-in state. Expires when you log out or after session timeout. Set by: Supabase.
CSRF tokens
Security token preventing cross-site request forgery. Session-scoped. Set by: Platform server.
Cookie consent
Records your cookie preference (localStorage). Expires: 1 year.

9.2 Optional / Functional Cookies

Currently, Healtown does not use advertising, tracking, analytics, or third-party marketing cookies. If this changes in the future, you will be informed and asked for your explicit consent before any such cookies are set.

For full details, see our Cookie Policy. You can withdraw cookie consent at any time via the cookie settings link in the footer.

§ 10 — Technical and Organisational Security Measures (Art. 32 GDPR)

Healtown implements appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including:

  • TLS encryption for all data in transit (HTTPS enforced).
  • Hashed password storage (bcrypt/Argon2 via Supabase Auth — plaintext passwords never stored).
  • Row-Level Security (RLS) on all database tables ensuring Users can only access their own data.
  • Access-controlled storage for Provider credential documents.
  • Webhook signature verification for all third-party integrations (Stripe, DiDit).
  • Regular server security updates and access log monitoring.
  • Principle of least privilege for internal data access.

No method of data transmission or storage is 100% secure. If you become aware of a security vulnerability, please report it responsibly to privacy@healtown.net.

In the event of a personal data breach that poses a risk to data subjects' rights and freedoms, Healtown will notify the competent supervisory authority within 72 hours (Art. 33 GDPR) and affected data subjects without undue delay where required (Art. 34 GDPR).

§ 11 — Children's Data

The Platform is not directed at persons under 16 years of age. We do not knowingly collect personal data from anyone under 16. If we become aware that a person under 16 has created an account, we will delete their data promptly. If you believe a child has registered, please contact us at privacy@healtown.net.

§ 12 — Changes to This Privacy Policy

Healtown may update this Privacy Policy from time to time. Where changes are material, registered Users will be notified by email at least 30 days before the new version takes effect. Minor clarifications may be made without notice. The current version is always available at healtown.net/privacy. Continued use of the Platform after the effective date of an updated policy constitutes acceptance.

§ 13 — Contact and Supervisory Authority

Data Protection Contact

Ali TaheriAzandaryani
Langewiesenweg 7, 69469 Weinheim, Germany
Email: privacy@healtown.net

Competent Supervisory Authority (Art. 77 GDPR)

Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg (LfDI BW)
Lautenschlagerstraße 20, 70173 Stuttgart
Web: www.baden-wuerttemberg.datenschutz.de
Email: poststelle@lfdi.bwl.de

Version 1.0 — Effective 11 June 2026 — Controller: Ali TaheriAzandaryani, Langewiesenweg 7, 69469 Weinheim, Germany