DAY ONE / RUNNING
← Back to home

DAY ONE RUNNING

Privacy Policy

Transparency draft under GDPR Articles 5, 6, 9 and 13–22. This notice distinguishes current website activity from future paid coaching. Unverified retention, vendor agreements and transfer arrangements remain paid-launch blockers.

Draft for legal review — not lawyer-approved. Incomplete business and policy information must be resolved before paid coaching starts.

Document version
2026-11-04-draft.1
Last updated
2026-11-04
Effective date
Not effective for paid contracts yet

Contents

  1. 1. Controller and contact
  2. 2. Enquiry data and purposes
  3. 3. Health and special-category information
  4. 4. Processing overview — purpose, basis and retention
  5. 5. Confirmed services and recipient relationships
  6. 6. International transfers
  7. 7. Rights and requests
  8. 8. Supervisory authority
  9. 9. Actual security and retention review
  10. 10. Children and updates
Terms and ConditionsSubscription and Payment ConditionsCookie and Website Storage Policy

Bartha Bálint egyéni vállalkozó

2013 Pomáz, Cseresznyés utca 4., Magyarország

Business identity supplied by the owner; registry verification and required contact details are outstanding.

1. Controller and contact

The controller is Bartha Bálint egyéni vállalkozó, 2013 Pomáz, Cseresznyés utca 4., Magyarország. Public business email and registry information are awaiting confirmation unless verified details are shown. Send privacy requests to the confirmed contact, or by post to the stated address. The coach’s Gmail sender is not automatically designated the public business contact.

2. Enquiry data and purposes

The call form collects name, email, optional phone, main goal and goal race, current weekly running and preferred call time; page language, package choice and optional race-prep interest accompany the request. No health comments are requested. Checklist signup, once enabled after coach review, stores name, email, language, source and timestamped consent solely to supply the checklist, not to subscribe anyone to marketing. Ordinary enquiry data is used to assess suitability, respond and take steps at the applicant’s request before a possible contract: GDPR Article 6(1)(b). A privacy acknowledgement records that the notice was read, not a blanket consent or paid agreement.

Only provide information necessary for your enquiry. Providing required contact and training fields is necessary to review this form; no marketing list or automated decision-making is implemented. Applications are reviewed by the owner coach.

3. Health and special-category information

Injury history, medical limitations, health disclosures and some inferred coaching metrics may qualify as special-category data. Contract performance alone is not an Article 9 exception. Optional health disclosures in the application require separate, explicit, informed consent: Articles 6(1)(a) and 9(2)(a). They are used only for suitability assessment and an application response.

The separate box is not preselected; you may apply without health data. The optional text field is not available before consent. Keep goal and event fields free of medical details and do not send medical records or another person’s data. A separate notice and any required explicit consent must precede health-data processing for ongoing coaching.

Withdrawal is possible via the controller’s contact; it does not affect earlier lawful processing. Stop consent-based use and delete information where required, subject to a separately applicable legal duty or legal-claims basis. Withdrawal may prevent an optional health-specific assessment but does not cancel the ordinary enquiry. Unrequested sensitive data should not be further used without a lawful basis.

4. Processing overview — purpose, basis and retention

Application assessment: ordinary form data; Article 6(1)(b); coach and website infrastructure; retain only while assessing and following up the enquiry, then erase or minimise unless another lawful purpose applies. A final retention period or review criterion must be adopted before paid launch.

Optional health assessment: voluntarily disclosed limitations; Articles 6(1)(a) and 9(2)(a); coach and secured application storage only; retain only while necessary for the stated assessment and consent, then erase subject to applicable legal obligations. Raw health comments and free-text goals are excluded from coach notification emails.

Coaching delivery, if contracted: schedules, activities, pace, distance, feedback, race results and availability; Article 6(1)(b) for ordinary data; assess Article 9 separately for health data. Recipients include the coach and TrainingPeaks when the athlete establishes that relationship. Retention must follow purpose, the agreement and the applicable legal-claims assessment.

Billing, if introduced: billing name/address, invoices, payment status and references; Article 6(1)(c) for applicable statutory accounting/tax duties and Article 6(1)(b) for payment administration. No operational invoice or payment provider is configured here. The applicable statutory retention period must be verified for this sole proprietor; do not assume a universal period. Full card numbers are not collected or stored by this website.

Security and owner login: necessary session, account and technical/security data; Article 6(1)(f) for the legitimate interest in secure operation, subject to balancing and minimisation. Authentication is for the private coach workspace, not an athlete account requirement. Provider log retention and exact operational periods need verification.

Consumer complaints: complaint and reply; Article 6(1)(c); retain for three years under the Hungarian Consumer Protection Act. Legal claims may justify necessary retention under Article 6(1)(f); assess special-category exceptions separately. Consent evidence records document version, server timestamp and language without an IP address or extra device fingerprint.

Application retention period or criteria
Requires owner confirmation before paid launch.
Coaching / consent evidence retention criteria
Requires owner confirmation before paid launch.
Applicable invoice retention obligation verified
Requires owner confirmation before paid launch.

5. Confirmed services and recipient relationships

Lovable-related website hosting and infrastructure support delivery of this site; Lovable Cloud database and authentication store applications, review history and the private coach profile. The underlying database/auth service is Supabase. The exact contracting entities, processing locations, subprocessors, agreements and transfer safeguards require contractual verification before paid launch.

Google Gmail is the configured email service, accessed through Lovable’s connector gateway. Coach notifications contain basic application/contact and structured training information; optional health comments and free-text goals are not included. Applicant decision emails contain the decision and, for information requests, the coach’s message. Avoid health details in correspondence unless appropriately disclosed and authorised.

TrainingPeaks is an independent external training platform, not a direct website integration. The athlete connects a TrainingPeaks account during onboarding; account/device data processing is governed by its own notice, with the coach responsible for their separate coaching uses. Confirm controller/processor roles for each actual relationship rather than assuming TrainingPeaks is solely this business’s processor.

Google Fonts supplies Anton and Manrope remotely. Font requests expose normal connection information, including IP address and browser request details, to Google. Project image assets are delivered through the Lovable asset infrastructure. No analytics, marketing, invoicing or card payment provider is currently integrated. External links do not themselves establish an integration.

6. International transfers

Do not infer EEA-only residency from this site. Google, TrainingPeaks and infrastructure relationships may involve processing outside the EEA. Locations, recipient roles and Chapter V GDPR mechanisms have not been verified. Before the relevant processing starts, verify applicable adequacy decisions or safeguards, assess necessary supplementary measures and state how a copy can be obtained. This draft does not assert that SCCs, an adequacy framework or a certification already covers these relationships.

7. Rights and requests

You may request access, correction, erasure or restriction; portability applies where processing is automated and based on consent or contract. You may object to legitimate-interest processing and withdraw consent at any time. Rights may have lawful exceptions, including retained accounting evidence; the controller must explain any refusal.

Requests normally receive a response within one month. Complexity or number of requests may justify up to two additional months, with reasons notified in the first month. Necessary identity checks must be proportionate; no routine unnecessary identity-document collection. No automated suitability or profiling decisions are implemented.

8. Supervisory authority

You may complain to the Hungarian National Authority for Data Protection and Freedom of Information (NAIH), 1055 Budapest, Falk Miksa utca 9–11; postal address 1363 Budapest, Pf. 9. Phone +36 (1) 391 1400; customer service ugyfelszolgalat@naih.hu. The official contact page below explains formal filing channels; ordinary email may not validly initiate authority proceedings. Judicial remedies remain available.

9. Actual security and retention review

Application records are not publicly readable; public submissions have insert-only access. The authenticated owner role is independently checked for private reads, updates and review history, with database row-level restrictions. Decisions and history are saved together with stale-status protection. Consent evidence is stored with the application and excluded from anonymous reads.

These controls do not establish a certification, audit, guaranteed breach prevention, encryption standard or data residency. Define access reviews, deletion procedures, incident handling, provider log retention and retention review before launch. The owner must action privacy requests and any required breach notifications within applicable statutory deadlines.

10. Children and updates

The coaching age policy is unconfirmed. Do not infer parental authorisation from a form submission or allow minors to independently form a paid contract. Confirm lawful representative involvement, age-appropriate information and safeguards before accepting minors. Material privacy changes require clear notice; obtain new consent before materially changing a consent-based purpose.

Hungarian is the authoritative drafting language. This English translation does not limit mandatory consumer rights in Hungary or your country of residence.

Official sources

  • 45/2014. (II. 26.) Korm. rendelet ↗
  • 1997. évi CLV. törvény ↗
  • GDPR ↗
  • NAIH ↗
  • Békéltető testületek ↗
  • Pest Vármegyei Békéltető Testület ↗
  • Fogyasztóvédelem ↗
Day One
/ Running

Bartha Bálint egyéni vállalkozó

Just have a quick question?

e.g. ‘Can you coach me for a race in 10 weeks?’ – message me, I usually reply the same day.

EmailWhatsApp

© 2026 DAY ONE RUNNING. All rights reserved.

Privacy PolicyTerms and ConditionsSubscription ConditionsCookie PolicyContactCoach sign-in