Last updated: October 15, 2026
1. Who is responsible and how to contact us
This Privacy Policy explains how LumaPutt, published under the name Kullion Games, handles information when you use the Android game, its online features, purchase functions and our support service.
The data controller is Martin Kull, trading as Kullion Games. Postal address: Postweg 26H, 21629 Neu Wulmstorf, Germany. Email: kulliongames@gmail.com. Website: kulliongames.de (https://kulliongames.de/).
For privacy questions or requests, email kulliongames@gmail.com and name LumaPutt in the subject. You can also write to the controller at the postal address above.
This notice explains data handling. Merely reading it, installing the game or continuing to play does not constitute consent to a separate optional processing activity.
2. Privacy overview
Local play does not require an online player identity. If you use online duels, the game creates a pseudonymous guest identity and sends the match information needed to our game server.
The game contains no third-party advertising and does not use advertising identifiers for advertising or cross-app tracking.
We have not integrated a separate developer analytics or crash-reporting service into this version. Google Play and Android may process their own service, billing and diagnostic information as explained below.
The game does not request access to your contacts, camera, microphone, messages, call history, precise location or photo library.
Optional paid content is processed through Google Play Billing. The game does not receive your full payment-card number or Google Account password.
3. Information stored on your device
The game stores the following on your device: best strokes and stars, unlocked holes, light-shard balance, owned and selected ball cosmetics, holes played and aces, recent daily-challenge records, language, audio, graphics and reduced-motion preferences. It also keeps a local record of purchased-content entitlements so it can enable content you own.
Saved gameplay and preferences are used to resume play, display your progress, apply your chosen settings and remember unlocked content. Device-language settings may be read to select an initial interface language. These local records are not uploaded to a developer gameplay-analytics database.
The online credential stored on your device is a secret access token. It is used to recognise the same online profile on later visits. It is not your Google Account password and should not be shared with other players or sent to us in an ordinary email.
4. Network and online-service information
When you use online duels, your device connects over HTTPS to the LumaPutt service hosted using Supabase. The online identity is a guest profile protected by a random access token; the server stores a hash of that token rather than using an email/password login.
Guest profile: a generated guest identifier, token hash, chosen display name, associated room code, last-activity and expiry timestamps, and request-rate counters.
Rooms and matches: room code, participating guest identifiers, room status and revisions, selected courses, shot direction and power, physics/game-state snapshots, stroke scores, turn timing, results, last-shot/request identifiers and rematch choices.
Connection and abuse prevention: the server infrastructure receives your IP address to deliver requests. Application rate limiting stores a hash derived from the connection IP with rate-limit timestamps and counters. Hashing does not make a value automatically anonymous. Hosting infrastructure can also process connection and operational logs.
Your display name, shots, scores, match state and results are visible to the other participant in your duel. Room codes are used to join rooms; share them only with people you intend to play with. This version has no persistent global player leaderboard or public player-name directory.
Leaving a room or ending a duel updates the room state; it does not immediately erase the guest profile. Server retention and deletion are explained in Sections 10 and 11.
5. Purchases and Google Play
The game uses Google Play Billing for optional one-time content purchases. This version offers full-game and expansion unlocks. Google processes the checkout and payment details within its own service.
The game receives product identifiers and descriptions, localized price/offer information, purchase and acknowledgement status, and a purchase token. It uses this information to show purchase options, acknowledge completed purchases, check ownership and restore access. Ownership may be checked when the game starts or resumes and when you request restoration; this is not limited to the moment you buy an item.
Purchase tokens are used during billing operations; the game persistently caches entitlement flags or owned product identifiers rather than your payment-card details. It does not send purchase receipts or purchase tokens to the multiplayer server.
Google maintains its own order and payment records. If you contact us about a purchase, we may receive an order reference, the details you provide and any relevant merchant information made available by Google to handle that request. Do not send payment-card numbers, passwords or authentication tokens.
Google’s processing is described in the Google Privacy Policy (https://policies.google.com/privacy?hl=en) and the Google Payments Privacy Notice (https://payments.google.com/payments/apis-secure/get_legal_document?ldl=gl&ldo=0&ldt=privacynotice). Google may process device/app, service and transaction information for billing operation, reliability, security and its own legal obligations. This policy does not control Google’s independent processing.
6. Information you send to support
If you email us, we receive your email address, the name shown in your message, its contents, any attachments and relevant correspondence metadata. You may voluntarily provide a device model, Android version, app version, screenshot or order reference to explain a problem.
We use this information to answer you, investigate the reported issue, deal with purchase questions and handle privacy requests. Email is delivered through our Gmail mailbox and the email services used by you and us. We do not automatically collect a diagnostic attachment from your device when you contact us; only send information needed for your request.
Please remove unrelated personal information from screenshots. We do not need a copy of your identity document for an ordinary support request. For a privacy request, we may ask for proportionate additional information where necessary to locate records or protect another person’s information.
7. Purposes and legal bases
Where the GDPR or comparable law applies, we rely on the following bases for developer-controlled processing. A legal basis applies only to the relevant purpose and data; it does not authorize unrelated tracking.
Purpose | Information and legal basis |
Operate the game and save your chosen progress/settings | Gameplay records, settings and local entitlements: performance of the requested game service under Article 6(1)(b) GDPR, where personal data and an applicable service contract are involved. |
Provide requested online play | Guest/player identifiers, credentials, names and match records: Article 6(1)(b) GDPR to run the online feature you choose. Security/rate-limit processing also serves the legitimate interests described below. |
Process purchases and restore paid content | Product and purchase-status information: Article 6(1)(b) GDPR. Any statutory transaction obligations apply under Article 6(1)(c) GDPR. |
Answer support and privacy requests | Contact details and correspondence: Article 6(1)(b) GDPR for service-related support; Article 6(1)(c) GDPR for applicable privacy-law duties; otherwise Article 6(1)(f) GDPR for the legitimate interest in responding to voluntary enquiries. |
Protect the service and establish or defend legal claims | Necessary security, request and dispute information: Article 6(1)(f) GDPR, based on the legitimate interests of preventing abuse, maintaining reliability and handling disputes, subject to your rights; Article 6(1)(c) where a specific legal duty applies. |
If we introduce an optional activity requiring consent, we will request that consent before the activity begins. Consent can be withdrawn for the future without affecting earlier lawful processing. We do not rely on this privacy notice as consent. Necessary storage/access for a service you expressly request is distinguished from optional storage/access requiring consent under applicable device-privacy law.
8. Who receives information
Supabase Pte. Ltd., 65 Chulia Street #38-02/03, OCBC Centre, Singapore 049513, and its infrastructure subprocessors: host the default game server and database and process the online information described in Section 4 on behalf of the game operator. Service-side operational processing is also subject to the provider’s applicable terms. Provider information: Supabase privacy information (https://supabase.com/privacy) and Data Processing Addendum (https://supabase.com/legal/customer-resources/data-processing-addendum).
Other players: receive the online profile and gameplay information described in Section 4, as necessary for matches.
Google and payment-service providers: receive information through the Google Play distribution and purchase flows they operate. Google determines its own purposes for its independently controlled store, account and payment services.
Google email services: deliver and store correspondence sent to our Gmail contact address. We control how we use and answer that correspondence. Google is responsible for the independent processing described in its own privacy notice; the EEA Google Privacy Policy identifies Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.
Authorities and professional advisers: receive relevant developer-held information only where a disclosure is legally required or necessary to protect rights, investigate fraud or handle a legal claim, subject to applicable law.
A business successor: if the game or business is transferred, relevant records may be transferred with appropriate safeguards and notice where required. Any successor must respect applicable data-protection obligations.
We do not sell your personal information or disclose it for cross-context behavioural advertising. We do not send local gameplay histories to an advertising network. Only information relevant to the stated purpose is intended to be disclosed.
9. International processing
Our contact mailbox uses Gmail. Google operates internationally and can process service and email information outside Germany and the European Economic Area, including in the United States. We remain responsible for the support correspondence we receive and use. Google’s own account, security and service processing is governed by its Privacy Policy (https://policies.google.com/privacy?gl=DE&hl=en). For processing covered by Google’s EEA Privacy Policy, Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, is the responsible Google entity.
Google publishes its applicable international data-transfer frameworks (https://policies.google.com/privacy/frameworks?hl=en), including adequacy decisions, the EU–U.S. and Swiss–U.S. Data Privacy Frameworks and the UK Extension to the EU–U.S. Data Privacy Framework for certified Google entities, and Standard Contractual Clauses where required. These are the provider’s published mechanisms; the transfer basis depends on the relevant Google recipient and processing activity.
The default online service uses Supabase Pte. Ltd. The primary game database is hosted in Frankfurt, Germany (eu-central-1). Network routing, Edge Function execution, operational support and provider subprocessors can involve processing in other regions, including the United States and Singapore. Frankfurt database hosting does not mean that all associated processing remains within the European Economic Area.
Supabase processes hosted game data on behalf of the game operator under its applicable Data Processing Addendum (https://supabase.com/legal/customer-resources/data-processing-addendum), which forms part of its service agreement. For covered transfers, that addendum incorporates the European Commission’s Standard Contractual Clauses, including the controller-to-processor module where applicable and the relevant UK and Swiss adaptations. Supabase identifies its service subprocessors in its published subprocessor information (https://supabase.com/legal/customer-resources/subprocessor-list).
You can contact kulliongames@gmail.com to request information about the safeguards relevant to developer-controlled processing and a copy where applicable, subject to permitted confidentiality redactions. Separate Google Play and payment processing is governed by the provider notices linked in Section 5.
10. Retention and backups
Local game records: remain on your device until overwritten in ordinary play, removed by clearing app storage or removed when you uninstall the game. Local purchase flags can be restored by Google Play; deleting a save does not delete a purchase from your Google Account.
The app configuration disables Android cloud backup and excludes its app records from device-transfer backup. Google Play’s own purchase history remains separate from these local app records.
Rooms: waiting, finished or cancelled rooms are set to expire approximately 10 minutes after the relevant creation/state update. Active rooms have a two-hour expiry after the latest game-state update. Expired rooms are removed during later service requests; expiry is not a guarantee of immediate deletion at a fixed wall-clock time.
Guest profiles: the expiry timestamp is normally set to seven days after activity. Removal of expired guest records runs when new guests are enrolled, and an existing guest may be renewed on return before cleanup. A guest record can therefore remain longer than seven days; do not treat inactivity as an immediate erasure request.
Application IP-hash rate limits: records older than 24 hours are eligible for cleanup on later new-guest enrollments. This is also request-triggered cleanup.
Infrastructure logs: the hosting service separately processes connection and request metadata, such as IP addresses, request times, endpoints, response information and operational errors. The default project currently uses Supabase’s Free plan, with one-day API/database log retention in the plan’s log-retention feature. This is separate from application records and does not describe a universal deletion deadline for every provider-held security or recovery record.
Recovery copies: the current Free plan does not include the paid automatic daily-backup feature. Any provider recovery, security or legal-retention copies are separate from the live game tables and are handled under the provider’s applicable service and deletion processes. They are used for recovery and protection rather than ordinary gameplay. Supabase’s DPA provides for covered data to be retained for the service-agreement duration unless earlier deletion is requested through the service; following expiry of the agreement, it provides a 30-day return-request period followed by deletion of covered copies. Deleting an individual live row does not mean an already-created recovery copy is erased immediately. See plan details (https://supabase.com/pricing) and backup information (https://supabase.com/docs/guides/platform/backups).
Support and dispute records: are retained while needed to handle the enquiry, any necessary follow-up, an applicable legal obligation or a reasonably relevant legal claim. Retention is determined by the request’s subject, whether a dispute remains open and any applicable statutory period. When those purposes end, we delete or anonymise developer-held identifiable records. Google retains its independent payment records under its own rules.
Email-provider deletion: deleting a message from Gmail normally places it in Trash for up to 30 days unless permanently deleted sooner. Provider-wide deletion can take longer than mailbox removal. Google describes a usual complete deletion process of around two months and encrypted backup retention of up to six months, with stated security, legal and other exceptions. These provider periods are separate from our support-purpose retention criteria. See Gmail deletion controls (https://support.google.com/mail/answer/7401?hl=en) and Google’s retention explanation (https://policies.google.com/technologies/retention?hl=en).
11. Deleting data and submitting a request
To remove local game records, open Android Settings → Apps → LumaPutt → Storage and choose the option to clear storage/app data, or uninstall the game. Labels differ by device. This can permanently remove progress and preferences. Clearing only the cache may not remove saved data. Backups, if enabled as described above, must be managed separately.
Online information is separate. Clearing local storage or uninstalling removes the local online credential but does not immediately delete the server-side guest profile and room records. It can also make the profile harder to identify or access later.
To request deletion of information we hold, email kulliongames@gmail.com with the subject “LumaPutt — Data deletion request”. State whether your request concerns support correspondence, online information or another record and give enough information to locate it.
For online records, useful details include your display name/nickname, the room or match reference if you still have it, the approximate date and time with time zone, and whether you used the default server. A display name alone may not uniquely identify a profile. Do not email your secret access token, Google password or full payment details. We may need to arrange a proportionate secure verification step to locate the correct profile and protect other users.
This version does not contain an automatic in-app server-profile deletion button. The email route is a request to the operator, rather than an automatic deletion command. Where a request is valid, associated personal data under our control is deleted or irreversibly anonymised unless a specific lawful retention exception applies. Necessary limited retention, its purpose and the applicable period or criteria will be explained to you. Mere deactivation is not account deletion.
A privacy request does not require you to buy content or open a new game account. Deletion of Google Account, Google Play payment or platform-backup data must be requested through the relevant provider’s controls. Erasing developer-held data does not itself refund a purchase or remove Google’s legally required order records.
12. Security
Local saves use the Android app’s private storage area. This reduces ordinary access by other apps; it is not a promise that saves are separately encrypted by the game or protected against every compromised or unlocked device. Protect your device and account credentials.
The release game requires HTTPS for its default online connection. The server checks the random access credential for profile/match operations, stores a hash of the credential and applies request/rate-limit controls. These measures help restrict access and abuse, but an access token must still be kept secret. They do not make online records anonymous or eliminate all security risks.
Google Play handles its purchase connections and checkout security. Developer-held support information is handled only for the purposes described in this notice. No method of storage or transmission can guarantee absolute security. If you suspect an incident affecting your information, contact the privacy address. Where a personal-data breach requires notification, we will follow the applicable legal requirements.
13. Your privacy rights
Depending on your location and the law that applies, you may have the right to:
ask for access to your personal data and information about its processing;
request correction of inaccurate or incomplete personal data;
request erasure or restriction, subject to applicable legal conditions and exceptions;
receive data you provided in a portable format where the legal conditions for portability are met;
object to processing based on legitimate interests on grounds relating to your particular situation; if we ever use information for direct marketing, object to that use at any time;
withdraw consent for future processing that actually relies on consent; and
complain to a competent data-protection authority, including an authority in your place of habitual residence, work or the alleged infringement in the EEA, or the relevant authority in another applicable jurisdiction.
Contact kulliongames@gmail.com to exercise a right. We will respond within the applicable time limit. For GDPR requests this is generally one month; a permitted extension of up to two further months for complexity or number of requests must be explained within the first month. Requests are normally free, subject to the legal rules on manifestly unfounded or excessive requests.
We may need reasonable verification, but will not ask for more identifying information than necessary. We cannot identify an individual from every purely local or no-longer-attributable record and will explain practical limits. Where applicable local law provides additional rights, including appeal or authorised-agent procedures, contact us to use them. We do not penalise you for exercising a privacy right.
14. Children and younger players
The game does not contain third-party advertising or ask players to submit a date of birth. We do not need a child’s real name, school, home address or similar details for gameplay. Parents and guardians should supervise purchases and help children avoid including identifying information in support messages or online display names.
Where a child’s use of a feature or a processing activity requires authorisation from a parent or guardian under applicable law, that requirement must be satisfied before the relevant activity. This privacy notice does not provide parental authorisation. A parent or guardian who believes that a child has supplied personal information inappropriately can contact us to request assistance or deletion, subject to proportionate verification and applicable law.
Any age eligibility shown in the store or game is separate from the information in this notice. The privacy rights described in this notice also apply to younger players, subject to the representation and verification rules that apply in their jurisdiction.
15. Choices, required information and automated processing
You do not have to contact support or buy optional content to use the available free local gameplay. Without local storage, the game cannot reliably remember progress, settings or entitlement caches. Without the necessary Google Play information, a purchase or ownership restoration cannot be completed.
Online play is optional. It cannot function without a pseudonymous profile, a network connection and the match/security information described above. Declining online play does not prevent the available offline gameplay.
The game automatically applies its rules to scores and unlocks. These gameplay operations are not intended to produce legal or similarly significant effects about you. We do not use the game to create advertising profiles or make credit, employment or comparable significant decisions.
16. Changes and further contact
We update this notice when relevant game features, services or data-handling practices change. The “Last updated” date identifies the revision. If a change requires additional notice or consent, that notice or consent request will be provided as required before the relevant new processing.
For any question about privacy in LumaPutt, or to request deletion, contact Kullion Games at kulliongames@gmail.com or use the controller’s postal address in Section 1.