Privacy Policy

Version
1.0
Effective
15 August 2026
Last updated
15 August 2026

This document is a prepared draft that reflects how OGS actually works. It has not yet been reviewed by a qualified lawyer and must be reviewed before OGS trades commercially.

This policy describes what OGS actually does with your data, audited against the running service. OGS holds detailed sporting performance data about you, so it is written plainly rather than defensively.

1Who is responsible

Dawie Stander's World of GolfBarmer Strasse 4445549 SprockhövelGermany

Email: info@ogs.golf · Telephone: +49 171 6805809

OGS has not appointed a Data Protection Officer; there is no statutory requirement to do so at the current scale. Contact the address above for any data protection matter.

2What OGS collects and why

Account data. Your email address and account identifier, so you can sign in and so your data belongs to you and not to a device. Legal basis: performance of the contract, Art. 6(1)(b) GDPR.

Golf rounds and hole scores. Course, tee, date, and your score on each hole. This is the core of the service: every metric OGS shows is calculated from it. Legal basis: Art. 6(1)(b) GDPR.

Derived performance analysis. Streaks, distributions, phase splits, rolling-window metrics, insights and investigations. OGS calculates these from your rounds and stores the results so they stay stable and explainable. Legal basis: Art. 6(1)(b) GDPR.

Scorecard photographs. If you upload a photograph of a scorecard, OGS stores the image and reads the numbers from it. You always review and confirm the numbers before they are saved as a round. Legal basis: Art. 6(1)(b) GDPR.

Player DNA answers. Your self-reported answers about how you approach the game. These are self-description, not observation, and OGS never presents them as measured fact. Legal basis: Art. 6(1)(b) GDPR.

Coach, team and university relationships. Who you have connected with and what you have permitted them to see. A coach sees your performance data only where a permission relationship exists, and you can withdraw it. Legal basis: Art. 6(1)(b) GDPR.

Subscription and billing records. Plan, currency, status, period dates and Stripe identifiers. OGS never receives or stores your card number. Legal basis: Art. 6(1)(b) GDPR and, for invoicing records, Art. 6(1)(c) GDPR.

Product usage events. First-party records of which OGS screens and actions you use, stored against your account, so the product can be improved. OGS does not use third-party advertising or cross-site tracking. Legal basis: legitimate interest in operating and improving the service, Art. 6(1)(f) GDPR.

3Storage in your browser

OGS sets no advertising, profiling or third-party tracking storage. There is therefore no consent banner: there is nothing that requires your prior consent. This is everything OGS writes to your browser.

  • Sign-in session (localStorage, strictly necessary) — Keeps you signed in between visits. Without it you would have to sign in on every page.
  • Return-to page (ogs.auth.redirect) (localStorage, strictly necessary) — Remembers the page you were heading to while you sign in, then clears itself.
  • Pricing currency (ogs.pricing.currency) (localStorage, preference) — Remembers whether you chose to see prices in USD or EUR.

You can review and clear preference storage at any time from Cookie settings in the footer.

4Who processes data on behalf of OGS

OGS does not sell your data and does not share it with advertisers. These are the only providers involved in running the service.

  • Lovable Cloud (Supabase infrastructure)Application hosting, database, authentication and file storage for scorecard photos.
    Data involved: Account and sign-in data; Golf rounds, hole scores and derived performance metrics; Player DNA assessments; Coach, team and university relationships; Scorecard photographs; Subscription and billing state records.
  • Google (Sign in with Google)Optional sign-in method. Used only if you choose to sign in with Google.
    Data involved: Email address; Account identifier; Name and avatar where provided.
  • StripeCheckout, subscription billing, invoices, the customer portal and payment webhooks. Stripe handles card data; OGS never receives or stores card numbers.
    Data involved: Email address; Payment and billing details you give Stripe; Stripe customer and subscription identifiers; Subscription status, currency and plan.
  • Lovable AI Gateway (Google Gemini models)Reads uploaded scorecard photographs into numbers, and writes the plain-language wording around figures OGS has already calculated.
    Data involved: Scorecard photographs you upload; Round figures and metric values already calculated by OGS.

Some of these providers may process data outside the European Economic Area. Where that happens, transfers rely on the European Commission’s Standard Contractual Clauses or an adequacy decision.

5Artificial intelligence

AI is used for exactly two things: reading a scorecard photograph into numbers you then confirm, and putting plain-language wording around figures OGS has already calculated itself. AI never invents a number, never changes a result, and never decides anything about you. Every figure you see comes from a deterministic calculation on your own rounds.

6How long data is kept

Your rounds, analysis and account remain until you delete them or close your account. Cancelling a paid subscription never deletes anything you recorded. Billing records are kept for as long as German commercial and tax law requires.

[[RETENTION POLICY REQUIRED]]

7Your rights

You have the right to access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and objection (Art. 21) under the GDPR. Where processing is based on consent, you may withdraw it at any time without affecting processing already carried out.

To exercise any right, email info@ogs.golf or use the contact page. You also have the right to complain to a supervisory authority.

[[COMPETENT SUPERVISORY AUTHORITY TO BE CONFIRMED]]

8Security

Access to your data is enforced in the database itself, not only in the interface: rows belong to accounts, and a coach or organisation can only read what a permission relationship allows. Data is encrypted in transit.

9Changes to this policy

This policy is versioned. The version and effective date are shown at the top of the page, and material changes will be communicated within the product.