# Battle Plushie Privacy Policy
Last updated: October 9, 2026
## Request deletion of your data
You can request deletion of information retained in connection with Battle Plushie, published by Kullion Games. You do not need to create a Kullion Games account, sign in, or reinstall the game to submit a request.
### How to submit a request
- Email **kulliongames@gmail.com**.
- Use the subject **“Battle Plushie — Data deletion request”**.
- If available, include your multiplayer room code and the approximate match date and time, including the time zone. These details help us locate relevant online records. To request deletion of support correspondence, identify the conversation and the email address used to contact us.
Please provide only information needed to locate the records and handle your request. Do not send passwords, session tokens, or full payment-card details. We may ask for proportionate additional information to identify the relevant records and protect other players’ privacy.
A request can cover retained, identifiable developer-controlled room and match records, gameplay-input records, match-verification records, associated session-token or rate-limit hashes where they can be identified, and support emails and attachments you sent us. We delete or anonymize information when the request applies and no lawful retention exception prevents erasure. Some temporary records may already have been removed or may no longer be attributable to a particular person or session. We explain the outcome and any information that cannot be located or must remain.
Room expiry and physical deletion are separate. The game’s current cleanup deletes expired match records during later online admission activity. Without a later cleanup, expired records can remain stored; there is no guaranteed maximum storage period arising from the expiry timer alone. Hosting logs and any backup copies have separate retention arrangements described in section 9.
Local progress and settings can be removed through **Android Settings → Apps → Battle Plushie → Storage → Clear data / Clear storage**. Menu names vary. Clearing only the cache may leave game information intact. We cannot erase a local save remotely. Platform backups must also be managed through the relevant device or account controls.
Google Play Games records are managed separately. You can delete Battle Plushie’s Google-hosted game data through the [Google Play Games profile controls](https://play.google.com/games/profile) or the deletion options in Google Play Games. Google’s instructions are available [here](https://support.google.com/googleplay/answer/9130646?hl=en). This does not erase our arena records, local game statistics, Google purchase records, or Google Play History. See sections 5 and 9 for details.
We respond to privacy requests within the time limits required by applicable law.
## 1. About this policy
This Privacy Policy explains how Battle Plushie, an Android game published by Kullion Games, handles information during gameplay, use of online services, purchases, Google Play Games features, and support requests.
The data controller is:
**Martin Kull, trading as Kullion Games**
Postweg 26H
21629 Neu Wulmstorf
Germany
Privacy and support contact: **kulliongames@gmail.com**.
In this policy, “we”, “us”, and “our” refer to that developer. Google and other platform providers also process information under their own applicable terms and privacy notices.
## 2. Local gameplay information
Battle Plushie stores campaign progress and stars, selected fighters, language and audio settings, wins, losses, online results, combat and fighter statistics, play duration, and purchased-content unlocks in the app’s private storage on your device. These records allow the game to remember your preferences, preserve progress, and display your results.
When Google Play Games is used, the app also stores the current game-specific Google player identifier and achievement synchronization records locally. These help the game associate submissions with the current player and track progress already reported to Google.
The complete local save is not uploaded as a developer-operated cloud save. Online match data and Google Play Games score and achievement submissions are processed separately, as described below. Android backup or device transfer can copy local app information depending on your device and account settings.
## 3. Online matches and hosting
When you use online play, Battle Plushie connects to an arena service hosted with Supabase. The game does not require a separate Kullion Games registration or a Supabase Auth account. It creates a temporary random session token for the online client. The token remains in client memory and is transmitted over HTTPS; the arena stores a hash of it to recognize participation in a match.
The arena processes room identifiers and friend-room codes, matchmaking mode, fighter and arena selections, timestamps, input frames and sequence numbers, synchronization checksums, and match results. This information is used to find or join an opponent, synchronize the match, check result consistency, and operate the online service. Your opponent receives the room information, gameplay selections, input frames, and results needed for the match.
The arena does not request your real name, email address, or contact list. Battle Plushie’s Google Play Games player identifier and profile are not included in the arena’s match payload.
Internet connections expose an IP address to the service infrastructure. The arena application derives a keyed hash from connection-address information for short-term admission rate limits. That hash is a pseudonymous security record, not anonymous data. The application does not store the raw connection address in its match tables.
Supabase infrastructure can separately process technical connection and diagnostic information, including IP addresses, request times, requested endpoints, user-agent information, response status, and service errors. This supports delivery, troubleshooting, and protection of the online service.
The primary arena database is configured in **Frankfurt, Germany, in the Supabase region eu-central-1**. Request handling through Edge Functions and other provider infrastructure can take place in other regions. The database location therefore does not mean all associated processing occurs exclusively in Germany. International processing is described in section 8; logs and retention are described in section 9.
Online play requires transmission of match data. Local game modes remain available without using the online arena. We use match data to provide the feature you request and proportionate rate limiting to protect service availability. These checks are not used for advertising or decisions with legal or similarly significant effects.
## 4. Google Play purchases
Battle Plushie offers optional full-game and expansion purchases through Google Play Billing. Google provides payment checkout. The game does not request or receive your full payment-card number, bank credentials, or Google account password.
The app handles product identifiers, purchase states, purchase tokens, and acknowledgement status to activate content and recognize eligible purchases. It caches content ownership locally. Purchase tokens are processed for Google Play acknowledgement rather than stored as a local purchase-history database. The game does not send those tokens to the arena or to a developer-operated receipt-validation server.
Google processes account, payment, and transaction information under its own privacy terms. Purchase and order information made available to the developer through Google Play may be used for purchase support, refunds, and required records. Removing local game data does not delete Google’s purchase records or cancel a purchase.
Google’s Privacy Policy is available at [https://policies.google.com/privacy?hl=en](https://policies.google.com/privacy?hl=en).
## 5. Google Play Games
Battle Plushie integrates Google Play Games for player authentication, the **Online Wins** leaderboard, and twelve achievements. Ordinary local gameplay and the online arena do not require a Google Play Games profile.
The Google Play Games SDK initializes when the configured game starts. The app checks existing authentication when it resumes. If you are already authenticated, it can synchronize results and achievement progress automatically. Opening the leaderboard or achievements can start Google’s sign-in flow if you are not authenticated. Automatic sign-in preferences are managed through Google’s controls.
The app uses your game-specific player identifier to associate submissions with your Google Play Games profile. It reports the cumulative number of confirmed online wins and achievement progress or unlocks based on campaign wins, completed fights, stars, combos, hits, kicks, blocks, special attacks, online wins, and the number of different fighters used. These submissions are aggregate progress values; this integration does not upload the complete local save or the arena’s individual input frames.
The app’s own synchronization code uses the player identifier; it does not request access to your email, contacts, Google Drive files, or friends list. Google’s service also processes gamer identity information, such as your gamertag and avatar, and its SDK collects analytics and diagnostic information for stability and product improvements. Google describes this processing in its [Play Games Services data disclosure](https://developer.android.com/games/pgs/data-collection).
The game opens Google’s public leaderboard interface. Profile and game-data visibility depend on your Google Play Games settings, which can allow visibility to everyone, friends, or only you. Other players may see your gamer identity and results according to those settings.
We use information obtained through Google APIs for the game features disclosed here and handle it in accordance with the [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy), including applicable Limited Use requirements. We do not sell Google API data or use it for personalized advertising.
Google stores scores, achievements, and profile information under its own retention and privacy controls. You can manage or delete game data through [your Play Games profile](https://play.google.com/games/profile). Deleting Google-hosted records does not erase local statistics. If the game remains authenticated, synchronization can submit locally retained results again. To prevent those old local totals from being submitted again, manage the game’s sign-in connection through Google’s controls and remove the relevant local app data.
## 6. Permissions, advertising, and device services
Battle Plushie uses internet access and Google Play Billing. It does not request access to your camera, microphone, contacts, messages, precise location, or personal photo library. It does not ask for a real name, postal address, or date of birth during ordinary play.
The game does not include advertising networks or separate developer analytics or remote crash-reporting SDKs. Google Play Games SDK analytics and diagnostics are described in section 5.
Android backup is permitted by the app configuration. Depending on your device and account settings, Android backup or device transfer can copy and restore local app information. These platform features are separate from a Kullion Games cloud-save service.
Google Play and Android can process service information when installing, updating, providing backups, or operating platform services. Their privacy policies and controls apply to that processing.
## 7. Support information, purposes, and legal bases
If you contact **kulliongames@gmail.com**, we receive your email address, the sender name included in your email, your message, and attachments or technical details you choose to provide. We use them to answer questions, investigate problems, assist with purchases where applicable, and handle privacy requests. Support correspondence is handled through Google’s email service.
Providing support details is voluntary, but missing information can prevent us from resolving a request. Please include only relevant information and avoid sending passwords, session tokens, or full payment details.
Where the GDPR applies:
- Information necessary to provide requested game features or purchased content is processed under **Article 6(1)(b)**.
- General correspondence and proportionate service-security measures rely on **Article 6(1)(f)**. Our legitimate interests are answering users, resolving problems, and protecting service availability and integrity.
- Legally required records and processing necessary to comply with binding legal obligations rely on **Article 6(1)(c)**.
- If a separate activity requires consent, consent must be obtained for that specific activity and can be withdrawn. Installing the game is not consent to additional collection.
Providing data needed for an online match or service authentication is necessary to operate that particular feature. Choosing not to provide it can prevent use of that feature while leaving local gameplay available.
## 8. Recipients and international processing
The services involved are **Supabase** for arena hosting and **Google** for Play Billing, Play Games, email, and Android or Google platform services. An online opponent receives the limited match information needed to participate. Information may also be disclosed when a binding legal obligation requires it or when necessary and legally permitted to establish, exercise, or defend legal claims.
Supabase’s ordinary non-marketplace contracting entity is **Supabase Pte. Ltd., 65 Chulia Street #38-02/03, OCBC Centre, Singapore 049513**. Supabase uses infrastructure and service subprocessors, which can process relevant technical or hosted information on its behalf. Its current [subprocessor list](https://supabase.com/legal/customer-resources/subprocessor-list) identifies the subprocessors and their processing functions.
The arena database is in Germany. Edge request processing and provider infrastructure, support, logs, or backup operations can involve locations outside the European Economic Area, including the United States and Singapore. The Supabase [Data Processing Addendum](https://supabase.com/legal/customer-resources/data-processing-addendum), incorporated into its service terms, provides contractual safeguards and includes European Commission Standard Contractual Clauses for transfers to which they apply.
For users in the European Economic Area, Google’s privacy information identifies **Google Ireland Limited**, with processing also involving **Google LLC** and Google’s infrastructure in other countries. Google describes the transfer safeguards applicable to its services, including adequacy decisions, the EU–US Data Privacy Framework where applicable, and Standard Contractual Clauses, in its [data transfer framework information](https://policies.google.com/privacy/frameworks?hl=en).
Copies and information about applicable safeguards can be obtained through the linked provider information or by contacting **kulliongames@gmail.com** for processing for which we are responsible. Google’s independently controlled account and transaction processing is also subject to its own privacy notice and user controls.
## 9. Retention and deletion
### Local records and platform copies
Local game records remain in app storage until you clear the app’s data, they are replaced during normal use, or the app’s local storage is removed. To remove them, use Android’s app-storage controls for Battle Plushie. Clearing only the cache may leave progress intact.
Clearing app data can erase progress and preferences. Uninstalling normally removes local app storage, but platform backups or later restoration can retain or recreate copies. Manage those through your device or account settings. Google-held purchase records and eligible purchase ownership are separate from local records.
### Arena rooms, inputs, and verification records
Arena rooms have an expiry condition of **15 minutes after creation**. Completion, exit, or other match-ending conditions set an expiry of approximately **two minutes after the match ends**. Expired rooms are no longer available for normal match use.
The current cleanup deletes expired rooms and linked input and verification records when a later room-admission request runs cleanup. Rate-limit hashes more than two minute-buckets old are also removed during admission processing. This is event-triggered cleanup. If no later admission triggers it, expired records can remain until another cleanup or an applicable individual deletion takes place. The expiry timer does not establish a fixed maximum storage period.
Closing or uninstalling the game does not itself delete hosting records. To request deletion of identifiable match information, contact us with the game name, room code if available, and approximate match date and time. A temporary session may no longer be identifiable, and we may need proportionate information to locate relevant records.
### Infrastructure logs and backups
Supabase processes technical service logs separately from the arena tables. Its published **Free-plan retention for API and database logs is one day**. This describes the plan’s log-retention feature; it is not a guarantee that every provider security record, infrastructure copy, or backup is physically erased within 24 hours.
The Free plan does not include the same guaranteed daily-backup feature offered on paid plans. Provider backup copies can nevertheless exist. Deletion from the live database does not necessarily remove an already-created backup immediately. Such copies are handled through the provider’s backup, recovery, security, and retention processes.
A separate fixed maximum for all provider infrastructure and backup records is not specified here because it has not been established for this project. We consider applicable deletion requests for identifiable information under our control and seek provider assistance where necessary. If retained copies are restored into an active dataset, applicable deletion obligations also need to be reflected in that restored dataset.
### Support and required records
Support correspondence is retained while it is necessary to resolve the request and associated follow-up questions. The retention criterion ends when the matter is resolved and the information is no longer needed for further handling, subject to specific legal obligations or the need to establish, exercise, or defend a legal claim.
Where developer-held documents fall within German statutory tax-record categories, **section 147 of the German Fiscal Code (Abgabenordnung)** requires, depending on the document category, retention of accounting vouchers for **eight years**, relevant business correspondence and other covered documents for **six years**, and covered accounting books and records for **ten years**. The applicable period generally starts at the end of the calendar year specified by that provision; statutory extensions can apply. These periods apply to documents in the relevant legal category, rather than automatically to every support email or every match record.
Information needed for a specific legal claim can be retained while it is necessary for that claim and the applicable limitation or proceeding period. Germany’s ordinary civil limitation period is generally three years, calculated under sections 195 and 199 of the German Civil Code; other periods, suspensions, or extensions can apply to particular claims.
When the purpose and any necessary lawful retention end, developer-held information is deleted or anonymized. For a deletion request, we explain any specific lawful reason for retaining limited records and the applicable period or criteria.
### Google Play Games and Google purchases
Google-hosted game records are retained and deleted under Google’s controls described in section 5. Purchase records are separate and are not erased by clearing app data or deleting a Play Games profile. Requests concerning information independently controlled by Google should use Google’s privacy and account controls.
There is no separate Kullion Games or Supabase player account to close. Third-party service profiles are managed with their providers.
## 10. Security
Local records use Android’s app-private storage protections. Google service connections use the provider’s secure interfaces. Arena requests use HTTPS, and server-side session and admission-rate-limit records use hashed or keyed identifiers.
Arena records are held in a separate database schema with row-level access controls. Access through the game service is checked against match-session participation. Administrative server credentials are kept on the server and are not embedded in the Android app. Hosting and Google administration use the providers’ account-access controls.
Support correspondence is handled through the developer’s support email account for the purposes described above and is not exposed to other players through the game. Information is disclosed only within the recipient and purpose arrangements set out in this policy.
No storage or transmission method can guarantee absolute security.
## 11. Your rights and younger players
Where applicable, you can request access, correction, erasure, restriction, and portability of your personal data; object to processing based on legitimate interests; and withdraw consent for future processing that relies on it. These rights have legal conditions and exceptions. You can complain to a competent data-protection authority, including the [Lower Saxony data-protection authority](https://www.lfd.niedersachsen.de/).
Contact **kulliongames@gmail.com** to exercise your rights. We respond within applicable legal time limits. We cannot read or remove a local save remotely. Privacy requests do not require creating a new player account. We request identity information only when proportionate and necessary to handle the request.
The app does not request dates of birth and does not create a separate child-account system or its own parental-consent flow. Age eligibility and supervision requirements for Google accounts, Google Play Games, purchases, and other platform services are governed by the relevant platform rules and applicable law. Local game modes are available without signing in to Google Play Games.
Parents or guardians can manage platform and purchase controls and contact us if a child has supplied personal information to us or needs assistance with a privacy request. Where we identify developer-controlled information received or processed contrary to applicable children’s privacy requirements, we take appropriate steps to stop that processing and delete the information unless a lawful retention obligation applies.
## 12. Changes and contact
We update this policy when the game’s data handling or relevant requirements change. The date above identifies the latest revision. Material changes will be communicated as required by applicable law.
For privacy questions about Battle Plushie, contact:
**Martin Kull — Kullion Games**
Postweg 26H
21629 Neu Wulmstorf
Germany
**kulliongames@gmail.com**