Public privacy notice

How GolfNode currently handles personal information.

This notice describes personal-information processing evidenced by the current GolfNode application and identifies current operational privacy boundaries. GolfNode continues to review provider, retention, transfer, security, and deletion controls as the service develops.

Information categories

Information processed through current product workflows.

The exact information depends on the workflow used. GolfNode should collect only information required for the stated operational purpose.

Club Claims

Name, work email address, optional work telephone number, role or relationship to a club, authority statement, public evidence reference, verification state, review state, and operational reference identifiers.

Authentication and access

Email address, authentication events, session information, exact-club affiliation, access role, and server-derived entitlement state.

Optional product analytics

Nonessential product analytics are disabled for this public release. The site does not send page or action analytics events. Previously recorded analytics, if any, remain subject to applicable retention and access controls.

GolfNode OS activation

Authenticated work email, preferred commercial-contact email, optional work telephone number, purchase-order requirement, bounded commercial notes, declarations, review status, and operational reference identifiers.

Billing and payment evidence

Invoice and club references, payment date, stated amount, payment reference, payer or organisation name, optional bounded note, review state, and reconciliation evidence.

Institutional and media intake

Representative name and role, source references, submitted institutional information, private files, rights declarations, authority declarations, and review records.

Enterprise partner requests

Organisation and contact name, role, work email, country, optional region or city, public website, bounded request summary, request-specific contact permission, access-code hash, and review status. The private access code is shown once and is not stored in readable form.

Support and privacy requests

Contact details, request content, relevant evidence, correspondence, identity-verification information where required, and operational handling records.

Google Calendar connection

New Google Calendar connections, event writes, and synchronization are disabled in this public release. Previously stored connection information is not used for public club information.

Processing purposes

Why this information is used.

  • Record, verify, review, approve, reject, revoke, or otherwise administer governed club Claims.
  • Authenticate users and enforce exact-club affiliation, role, subscription, and entitlement boundaries.
  • Review GolfNode OS activation requests and administer the controlled commercial process.
  • Prepare and review invoices, payment information, reconciliation evidence, and subscription state.
  • Receive governed institutional information, correction proposals, evidence, media, and rights declarations.
  • Review private supplier, sponsor, tourism, hospitality, and other enterprise requests and reply only where the requester has given permission for that specific request.
  • Operate security, abuse prevention, troubleshooting, audit, support, and request-handling controls.
  • Nonessential product analytics are disabled in this public release.
  • Google Calendar connections, event writes, and synchronization are disabled in this public release.

Google Calendar data disclosure

Google Calendar access is explicit and limited.

Google Calendar access is requested only after you choose Connect Google Calendar. The current intended scope is https://www.googleapis.com/auth/calendar.events.owned, which is used to create, change, and delete events on calendars you own for events GolfNode is responsible for.

GolfNode stores an encrypted server-side refresh token and non-secret connection and event-mapping state so it can perform later one-way syncs. Access tokens are short-lived and are not stored in the browser, FAIRWAYS canonical truth, public provider rows, logs, or analytics.

GolfNode does not sell or share Google Calendar content for advertising, does not turn private Calendar data into public club truth, and does not read unrelated calendars or contacts. Disconnecting removes the stored encrypted token, attempts provider revocation, and retains only non-secret connection history needed for safety and audit. You can also revoke GolfNode in your Google Account security settings.

These practices are intended to follow the Google API Services User Data Policy and Limited Use requirements. The integration is not represented as production-connected until credentials, deployment, provider testing, and any required Google review are separately completed.

Data minimisation

Do not provide unnecessary sensitive material.

Unless a separately governed process expressly requires it, do not submit passwords, authentication secrets, identity documents, bank credentials, card information, private bank statements, unrelated medical information, or unrelated personal records.

Security and access

Access should remain purpose-bound.

Authentication, exact-club affiliation, role, subscription, and entitlement are enforced as separate server-derived states. Personal information should be available only to authorised functions and reviewers for the relevant operational purpose.

Material unresolved controls

Current production privacy controls and open operational items.

GolfNode distinguishes current controls from matters that remain subject to operational review. This notice does not represent an unresolved item as complete.

  • GolfNode uses external infrastructure and service providers for hosting, database, authentication, email, and related operational processing.
  • Some provider processing may occur outside South Africa. Provider locations, subprocessors, contractual safeguards, and international-transfer controls remain subject to ongoing provider and governance review.
  • Final category-specific retention periods and the complete deletion schedule have not yet been adopted. Records remain subject to purpose-bound retention and applicable legal, security, audit, and dispute requirements.
  • The server-side retention period for previously recorded analytics events and jurisdiction-specific consent/legal review have not yet been adopted. No new nonessential analytics events are collected in this public release.
  • The public GolfNode service is operated by GOLFNODE, a Private Company (registration number K2026644143), effective 13 August 2026. The Information Officer is Alvin van Rooyen. Privacy enquiries may be addressed to privacy@golfnode.co.za.
  • Production logging, monitoring, backup, support-access, deletion, and provider controls remain subject to continuing operational review and hardening.

Retention

Retention must have a defined purpose.

Personal information should not be retained indefinitely by default. Records should be retained only while required for their governed purpose, applicable obligations, security, audit, dispute handling, or controlled evidence. Final category-specific retention periods and deletion rules are not yet adopted.

Providers and processing locations

Production arrangements remain under qualification.

GolfNode uses external providers for hosting, database, authentication, transactional email, and related operational services. Processing may occur in South Africa and other jurisdictions depending on the provider and service. Provider, subprocessor, contractual, and transfer arrangements remain subject to continuing governance review.

Privacy requests

Ask about information linked to you.

GolfNode may need to verify your identity and the scope of the request before disclosing, correcting, restricting, or deleting personal information.

  • Ask what personal information is held about you.
  • Request correction of inaccurate or incomplete personal information.
  • Request deletion or restriction where applicable and supportable.
  • Object to processing or ask for the processing purpose to be explained.
  • Raise a concern about access, security, disclosure, retention, or provider handling.

Privacy contact: privacy@golfnode.co.za.

This notice creates no affiliation, entitlement, subscription, publication authority, regulatory approval, or launch authority. Production privacy readiness remains subject to retained evidence, authorised review, and separate launch qualification.