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.
Public privacy notice
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
The exact information depends on the workflow used. GolfNode should collect only information required for the stated operational purpose.
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.
Email address, authentication events, session information, exact-club affiliation, access role, and server-derived entitlement state.
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.
Authenticated work email, preferred commercial-contact email, optional work telephone number, purchase-order requirement, bounded commercial notes, declarations, review status, and operational reference identifiers.
Invoice and club references, payment date, stated amount, payment reference, payer or organisation name, optional bounded note, review state, and reconciliation evidence.
Representative name and role, source references, submitted institutional information, private files, rights declarations, authority declarations, and review records.
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.
Contact details, request content, relevant evidence, correspondence, identity-verification information where required, and operational handling records.
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
Google Calendar data disclosure
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
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
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
GolfNode distinguishes current controls from matters that remain subject to operational review. This notice does not represent an unresolved item as complete.
Retention
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
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
GolfNode may need to verify your identity and the scope of the request before disclosing, correcting, restricting, or deleting personal information.
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.