Skip to content
Bubble Serenity
  • About the game
  • Developer journal
  • Guides and help
  • Community
  • Technical support
RUENHE

Legal documents are currently available in English only. The original English document and its status are shown below.

Privacy policy

This is a specific published version. View the current version.

Version 1.0

Effective: 2026-11-09
Published: 2026-11-09

Privacy at a glance

  • Website applicants submit a name, email and message so the developer can review closed-beta applications, choose participants and send invitations manually. Applying does not guarantee acceptance.
  • Optional website GA4 measures public visits and beta/download requests. Optional game Firebase Analytics measures the implemented startup, tutorial, battle and progression events; Crashlytics helps diagnose crashes. This is not a recording of every action.
  • Game Analytics and Diagnostics have independent permissions. Website analytics has a separate choice. Refusal does not block ordinary gameplay; use the respective settings to refuse or withdraw. Stored permissions and native initialization have the limits in Section 3.9.
  • Request access, correction or deletion at https://bubbleserenitygame.com/privacy-choices or privacy@bubbleserenitygame.com. Applicant retention is 90 calendar days from submission for all statuses; mailbox copies, backups, lawful holds and audit evidence have separate handling below.

1. Who is responsible for your information

Bubble Serenity is developed by Albert Azaryev, trading as Bubble Serenity, at Shapira 14, Netanya, Israel. Albert Azaryev is the controller of personal information processed to operate Bubble Serenity and its related website and support services. Albert Azaryev currently operates as an individual developer.

Privacy contact: privacy@bubbleserenitygame.com. Privacy emails are received and reviewed by Albert Azaryev, who is responsible for responding to them.

You can also submit a request at https://bubbleserenitygame.com/privacy-choices. Account deletion requests can be submitted at https://bubbleserenitygame.com/account/delete.

No government or personal identification number is published in this policy. If the operator changes to a registered business or a successor company, we will update the controller details and give any legally required notice.

2. What this policy covers

This policy is designed for international availability, including the EEA, UK and other launch markets, subject to the requirements applicable in each territory. It explains how we collect, use, disclose, retain and protect personal information through Bubble Serenity, https://bubbleserenitygame.com and our support and privacy-request processes.

This covers the website and features actually available in your closed Android beta build. Account linking, online competition, social functions, purchases, advertising and Bots are conditional features, not assertions that the whole planned release is deployed. Later activation requires matching notices and choices.

Apple, Google and other services may also process information for their own purposes under their own privacy notices. Their notices do not replace our responsibility to describe the processing that we arrange or control.

Reading this policy or accepting the Terms of Service is not consent to optional advertising, tracking, analytics or any processing that requires separate consent. We obtain that consent separately where required.

3. Information we process and where it comes from

3.1 Website visitors and requests

When you use our website, the hosting provider receives technical request information necessary to deliver and protect the site, such as your IP address, request time, requested resource, browser information and response details.

If you submit a support, privacy or deletion request, we receive the information you enter: contact email, request category, subject or explanation, an optional player ID or display name where requested, and any supporting information. Support submissions may include screenshots. Their original filenames, file types, sizes and file-integrity hashes are also processed. Images may contain embedded metadata, including location information; remove such metadata and unrelated content before submitting a screenshot.

Please avoid putting passwords, payment-card details, government identity numbers, unrelated sensitive information or another person's personal information into a request. Crop or obscure unrelated information in screenshots. We request additional verification only where necessary to protect your account or fulfill a lawful request; see Section 12.

Our application uses a rotating pseudonymous identifier derived from the client IP address to limit abusive form submissions. It does not store the raw IP address in the support or privacy business records for this rate-limiting purpose. The hosting provider may separately process IP addresses in its infrastructure logs. Pseudonymous identifiers remain personal information where they can be linked to a person; they are not automatically anonymous.

3.1.1 Closed-beta applications and invitations

Applicants supply a name, email and message for the owner's private review, selection and manual invitation email. Applying does not guarantee acceptance or trigger an automatic email. Do not include sensitive or unrelated third-party information.

Neon/PostgreSQL stores these fields, creation time, status, revision, legal versions and deduplication metadata. An unchecked confirmation asks applicants to meet the applicable age/guardian requirements; its confirmation time is recorded, without birth dates or identity documents. This is self-confirmation, not verified age or guardian identity. Only the owner reviews applications. A status change or retry does not restart the retention clock. See Sections 11–12 for expiry, holds and rights.

Codes are checked on the server, excluded from URLs/storage/analytics, and exchanged for a short-lived signed ticket containing expiry/legal versions. The GitHub APK is public; the code is only a soft distribution gate. GitHub receives technical download requests under https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement. Applicant fields, codes and IDs are excluded from our GA4 payloads.

3.1.2 Optional website analytics

Google Analytics 4 (GA4) is selected for website analytics. The integration defaults off. Only separate activation AND explicit website consent load our Google tag or initiate GA requests, cookies or tracking events. Policy publication alone does not enable analytics.

When enabled with permission, GA4 measures public page visits, Android APK download requests and the beta workflow (opening the download or application window, successful invitation validation, requesting a download and submitting an application). These events do not prove a completed download, installation or acceptance as a tester. Our custom events use fixed event names and minimized public page paths. We omit URL query strings and fragments, keep private/admin/receipt and unsupported routes out of this tracking, and do not intentionally send names, emails, form contents, player account identifiers or sensitive URL parameters.

Google's tag can process browser/device details, pseudonymous cookie/client identifiers, approximate regional information and technical request information. These can be personal information even without a name or email. Advertising personalization and Google signals are disabled in the reviewed integration. Website GA4 is distinct from the Android Firebase choices described below: accepting one does not grant the other. See Sections 11 and 15 for retention, cookies and choices.

3.2 Account and authentication information

Guest accounts involve account/session/recovery identifiers. Supported linking supplies provider data; it does not automatically merge separate progression and may require conflict/recovery records.

3.3 Age assurance

The game uses a neutral age step before account admission and access to age-restricted functions. The Android Firebase beta has a specific initialization limitation: native SDK initialization can occur before Unity C# onboarding and age checks. Default-disabled collection is not the same as delayed initialization and does not guarantee the absence of SDK technical network activity. Section 3.9 explains collection permissions and previously stored SDK settings. This exception does not remove the minimum age or authorize optional collection from an ineligible player.

The local age-assurance design stores an age band and, for players under 18, the month/year of adulthood for protective feature access. The agreed Cloud Code account inventory receives age band only, not original birth month/year. These are different records. This value reveals the birth month and year. Any authoritative age upgrade/erasure beyond the local record must be verified in the enabled backend; it is not asserted as a deployed UGS deletion capability. For players who are already 18 or older when they enter their age, we store only the age band. We never store a day of birth. Raw age input is discarded and excluded from logs and analytics.

Where available, trusted Apple or Google age-range signals can be used to apply the more protective age status. We also retain the age-assurance method, source, verification time, schema/version information and a reference to any verified correction. The age record does not contain identity documents.

Platform age signals are used for age-appropriate access and legal compliance, not advertising, profiling for advertisements or analytics. Other systems receive only the restricted access state they need. We exclude from analytics the exact age, full birth date, original month/year or stored adulthood month.

3.4 Legal choices and their records

Applications retain legal versions, submission and eligibility confirmation times. Download acknowledgement is bound to the effective terms in a short-lived ticket, not a permanent identified acceptance ledger. Website GA4 remembers granted/denied locally; game permissions are local choices and SDK switches. Neither adapter creates a server consent-history ledger. Any account acceptance record is separate. Policy acknowledgement and beta terms are not optional analytics consent, and birth input is excluded.

3.5 Necessary backend, progression and competitive integrity

Unity Gaming Services (UGS) Authentication, Cloud Code and Cloud Save are the selected account, server-operation and protected-save services. Only activated game/backend functions use these services; this website release does not activate them. Necessary account/gameplay processing is separate from optional Firebase or website analytics permissions and is not disabled by refusing those services.

The agreed backend inventory includes UGS Player ID and authentication/session tokens; age band (not raw birth input); protected account/progression state, Heroes, city/house state, balances and inventory; validated transactions, server receipts and reward outcomes. Access is limited to the data needed for the requested function, with under-18 protections for eligible younger players.

Where Ranked/competitive services are enabled, records can include match ID/configuration, seed, actions/timing, result, league points (LP), settlement/disposition, integrity incidents and necessary replay/validation evidence. Account-security and regulatory decision/appeal notices may also be processed. Unity can receive technical request/log information, including IP addresses. No fixed UGS match-journal/replay period or provider-specific region/deletion guarantee is established by this policy.

Later Leaderboards, Matchmaker/Relay and live-match transient actions/emotes apply only after activation and corresponding notices; their mention is not evidence of deployment. Store purchase-receipt validation likewise applies only where enabled. Optional analytics is not a prerequisite for necessary backend operations, and pseudonymous gameplay records remain personal information.

3.6 Public profiles, adult social features and reports

Where those features are enabled, other players may see the approved public profile fields, such as your approved display name, avatar, league, LP and squad snapshot in rankings/PvP, subject to under-18 visibility restrictions. A permitted read-only snapshot may also support a Bot opponent, which must not be presented as a live human player (Section 8).

Adult Friends features process friend relationships, requests, blocks, discovery/presence data where supported, preset messages, social gifts and the records needed to enforce daily limits. Reports and appeals may contain the reporter's account reference, the reported account reference, reason, relevant game/message evidence, decisions and appeal records. Report evidence is not publicly displayed.

A profile country, where offered, is optional; minors' country is hidden from other players. We also process daily Teen Gratitude claim records to provide eligible younger players their non-social daily benefit and prevent duplicate claims.

The MVP does not include player free-text chat or Alliance leader text. Before their introduction, we will update the policy to identify text data, recipients, moderation tools/providers and retention, and give required notices. We will apply the approved adult-only communication and minor-safe display rules.

3.7 Purchases and subscriptions, where enabled

Apple/Google stores handle payment details. For enabled purchases we process transaction/receipt or purchase-token data, product/store IDs, entitlement/renewal state, validation, refund/revocation and claim records to verify and recover benefits. We do not need full card numbers/security codes; do not submit them to support. Stores may retain payment records after game-account deletion.

3.8 Technical information and optional services

Necessary operation may process device/OS/game versions, language, network/connection, error and security information. This is not permission for optional tracking. Future adult advertising/attribution has the separate conditions in Section 7.

3.9 Optional Android Firebase Analytics and Crashlytics

Google Firebase Analytics is the selected game analytics service; Firebase Crashlytics is the diagnostics service. The adapter operates only in eligible Android tester/development builds with the telemetry module enabled. SDK presence does not establish that a distributed APK has collection enabled.

The implemented custom catalogue covers startup stages/failures; first-frame/first-shot and first-session onboarding; tutorial steps/hints; campaign attempts, stars, unlocks and rewards; battle starts, outcomes, exits and resource-battle results; Heroes, special bubbles, crafting and progression; and app pause/resume. Fields include game-content identifiers, stage/mode/result codes, counts, durations, level/XP changes and build/schema versions. Bubble Combat counts are aggregated locally for battle summaries; the internal combat-action summary is not sent as an individual event. This does not record every tap, message, bubble or player action. Future events need implementation and appropriate disclosure.

The adapter does not attach name, email, player account ID, age/birth input, support text, replay or payment receipts, or set a custom analytics user ID. SDK app-instance/installation identifiers and technical device/app information can nevertheless be personal information. Reviewed Android defaults disable advertising-ID collection and advertising-related consent; merged APK behavior requires device verification.

Crashlytics can process crashes, exception traces, device/OS/app versions and installation-related identifiers. The adapter adds build version, startup-stage context and startup failure codes, not arbitrary form text. SDK crash reports and native diagnostic data may contain technical context beyond those custom fields and are not necessarily anonymous.

Analytics and Diagnostics have independent permissions, both initially off on a new eligible installation without a saved choice. Either, both or neither may be accepted; refusal does not block ordinary gameplay. Change or withdraw them using the game's Analytics/Diagnostics settings controls. Beta terms, an APK request, an invitation code and policy acknowledgement do not grant either permission.

Previously valid age eligibility and permissions can remain effective across launches. SDK switches persist separately from the game's local choice and may apply during native startup before Unity C# onboarding and age rechecks. The adapter reapplies eligibility and choices when it runs. This is not strict deferred SDK initialization: collection-disabled defaults do not guarantee that all initialization or technical network activity waits for a fresh age/consent screen.

Crash reports may be cached locally while collection is off and sent after Diagnostics is enabled. Withdrawal stops future application-controlled tracking on a best-effort basis; it cannot guarantee immediate cached-report deletion, cancellation of queued/in-progress uploads or erasure of reports already received by Google. Request applicable access/deletion under Section 12. Website choices never override an in-game refusal.

4. Why we use information

We use the information necessary to provide and secure accounts; store and restore game progress; run battles and matchmaking; validate outcomes and prevent cheating; deliver verified purchases and rewards; apply age restrictions; respond to support and privacy requests; investigate reports and appeals; and comply with legal obligations.

We review tester applications and manually contact selected applicants. With the separate applicable permissions and enabled features, we use website GA4 for traffic and beta-workflow measurement and Firebase Analytics/Crashlytics for limited gameplay measurement and diagnostics. Future adult advertising has the separate conditions in Section 7.

For information that you choose to provide, we explain whether it is optional. Essential account or security information is required to provide the corresponding service. Without a reply email, for example, we may be unable to respond to a submitted support request. Refusing optional advertising or tracking does not prevent ordinary gameplay. Some privacy requests may require proportionate verification before we can safely disclose account information or delete an account.

5. Legal grounds where EU or UK data protection law applies

We identify a specific legal ground for each purpose. We do not use acceptance of the Terms as consent to all data processing.

PurposeLegal ground
Necessary account, save, gameplay and purchase fulfillmentContract, only to the extent objectively necessary for the requested service and supported by a valid contractual relationship
Security, cheating/fraud prevention, abuse controls and service reliabilityLegitimate interests, subject to necessity, proportionality and an assessment of your rights, with particular care for children
Support, reports and appealsContract where necessary for the requested service; otherwise a specifically assessed legitimate interest or legal obligation, depending on the activity
Accounting and legally required records or responsesLegal obligation, with the actual obligation identified
Age assurance and safety restrictionsApplicable legal obligation where one exists; otherwise a specifically assessed legitimate interest. The basis depends on the relevant territorial requirement
Tester recruitment and manual invitation correspondenceSteps requested by an applicant before participation where applicable; otherwise the assessed legitimate interest in administering closed-beta recruitment and responding to the request. Optional analytics consent is separate
Optional website GA4 and game Firebase Analytics/DiagnosticsSeparate affirmative permission for each applicable service; consent where required by data-protection or device-access law. Teen eligibility and any legally required guardian authorization must be established; the ordinary gameplay contract is not blanket analytics consent
Future optional advertising identifiers, attribution and trackingSeparate consent where required, together with necessary platform permissions; not activated by beta participation
Read-only Bot donor combat configurationLegitimate interest in providing a playable competitive service, subject to minimization and an objection assessment; public-profile display is assessed separately

6. Children and younger players

The game is not available to children under 13 or below any higher applicable minimum age. A failed age step creates only a local block flag: no game account and no server request containing the entered age data. Website hosting still processes the technical requests described in Section 3.1. The local age block does not undo native SDK initialization or technical traffic before age was established; see Section 3.9.

Players under 18, and players whose age status is unknown, receive the more protective experience. They do not access Friends or player free-text communication. Advertising and attribution SDKs are not initialized for them, and no advertising identifier or rewarded-ad claim is created for them. They are not shown adult advertising/tracking consent screens as a way to bypass this rule.

Optional Firebase gameplay measurement and diagnostics follow the separate age eligibility and permission controls in Section 3.9; they are not an always-on measurement of every younger player. The reviewed custom payloads do not include exact age, birth input or an age-segment field. We do not use these beta measurements to personalize advertising or prices. A minimum age of 13 does not by itself establish capacity to consent to optional processing in every territory: where additional authorization or a higher minimum age is required, participation or the optional service must remain restricted until those requirements can be met. Native Firebase startup and persisted-switch limitations remain as disclosed in Section 3.9.

We do not knowingly collect personal information from children under 13 through game accounts. Where COPPA applies, we meet its requirements before collecting covered children’s information. If we learn that an account belongs to a player below the applicable minimum age, we will close it and delete its personal information, except limited records that must lawfully be retained. A parent or guardian can contact us with a concern or an appropriate request. We verify authority proportionately and do not disclose a child's account to an unverified requester.

7. Future adult advertising and tracking choices

This telemetry module does not introduce advertising or attribution. The following rules apply only if a later build actually offers adult advertising, after provider/configuration review and updated notices. Advertising is unavailable to under-18 and age-unknown players. Ordinary gameplay does not depend on optional tracking.

Eligible adults may separately choose a rewarded advertisement. Necessary completion/eligibility counters and transaction-deduplication references would verify its reward. Watching an ad is distinct from consent to advertising personalization, attribution or cross-app tracking. Provider technical/network data, ad identifiers and actual contextual/personalized processing must be disclosed before activation, with applicable device-access choices. iOS tracking requiring App Tracking Transparency also requires that permission; another privacy choice cannot override refusal.

Consent may be refused or withdrawn through the applicable settings/contact without a gameplay penalty. An advertised reward is for completing an eligible ad, not for consenting. Withdrawal does not invalidate earlier lawful consent-based processing.

8. Bot opponents and combat snapshots, where offered

These rules apply only to builds that offer Bot opponents; they do not verify deployment of wider competitive features in the closed beta. An autonomous Bot may use an eligible player's limited read-only combat configuration, not a recording of that player's actions or evidence that the donor is online. Its virtual match must not change the donor's inventory, progress or results. The approved configuration excludes email, age records, payments, social relationships and unrelated account information.

Under-18 donor display uses a neutral name/avatar. Eligible adults can object to public-profile use for Bot display through the relevant Privacy options; future display then uses a neutral identity. This does not necessarily stop use of minimized combat configuration. Any applicable objection to the underlying processing may also be submitted through Section 12; a display toggle does not exhaust that right.

9. Who receives information

We disclose only the information needed for the recipient's role and authorized purpose. Relevant categories include hosting and database providers; private file-storage providers; game backend, authentication and networking providers; stores and linked authentication providers; approved analytics, diagnostic or adult advertising providers where enabled; other players for approved public/social/gameplay fields; professional advisers where necessary; and competent authorities when required or otherwise lawfully justified.

The owner and authorized operators can access necessary support, privacy and safety records through restricted operational tools. Website support/privacy requests and tester applications are not automatically forwarded to another person or sent by email simply because a form is submitted. The owner manually sends selected applicants a testing invitation.

ServiceRole
VercelWebsite hosting and private support-file storage
NeonWebsite database storage, including private tester applications
Google Analytics 4Optional website traffic, APK-request and beta-workflow measurement, only if enabled and accepted
Google Firebase AnalyticsOptional gameplay measurement in enabled eligible Android beta builds
Google Firebase CrashlyticsOptional Android crash/exception reporting and diagnostics
GitHubPublic APK release-asset hosting and download delivery
Google Cloud BigQueryFuture analytics daily-export storage only after separate approval; not activated by this release
Google GmailCurrent email correspondence; Albert Azaryev reviews privacy emails
Unity Gaming ServicesAuthentication, Cloud Code and Cloud Save where enabled; later Leaderboards/Matchmaker/Relay are conditional, not asserted active
Apple and GoogleStore purchases and supported authentication or age signals, where enabled

The selected Google services are not necessarily enabled in production or every beta build. Advertising/attribution need a separate provider review. Google Analytics has separate terms from other Firebase products. Account agreements, provider roles, regions and transfers require verification; no signed processor agreement or transfer mechanism is certified here.

Unity's player-facing information is available at https://unity.com/legal/game-player-and-app-user-privacy-policy. We disclose only the Unity products actually used; use of Unity as the engine does not mean every Unity service described in that notice is enabled.

Google's privacy notice is available at https://policies.google.com/privacy. We identify Gmail as our email service without implying that a consumer Gmail account has a Google Workspace data-processing contract.

We require processors handling data for us to act under appropriate instructions, data-protection terms and security measures. We separately disclose recipients acting for their own purposes; recipients processing information for independent purposes are identified accordingly.

If a successor entity takes over the service, any transfer of personal information remains subject to applicable law, purpose limitations and required notices. We do not treat this provision as permission for unrestricted transfers or new uses.

10. International processing and transfers

Our controller is in Israel. Service providers can process information in other countries. A selected storage region does not by itself guarantee that all support access, logs, backups and subprocessors remain in that region.

Where EU or UK transfer rules apply, an applicable adequacy decision or appropriate safeguards, such as approved contractual clauses and any required supplementary measures, must cover the particular transfer before the affected processing is opened. The applicable provider arrangements and territorial launch requirements require owner verification; a provider name or selected database region is not proof that a particular mechanism is in place. You can request the verified arrangements through our privacy contact.

11. How long information is kept

Current website handling and conditional release schedule

Website support/privacy records are in Neon and accepted screenshots in private Vercel Blob storage. Status changes do not erase them or a game account. New JPEG/PNG/WebP processing strips embedded metadata while retaining orientation; temporary raw uploads and historical images require separate cleanup.

The daily 03:00 UTC cleanup runs within Vercel's scheduling window, subject to limits, retries and backlog. Upload grants last 30 minutes plus a five-minute cleanup safety delay. Abandoned-upload cleanup excludes accepted tickets/files; their separate expiry rules follow below. Applicants have their own 90-day rule; Google and UGS records do not inherit it.

Frankfurt storage and a six-hour Neon recovery window were recorded on 2026-10-04; these historical observations do not establish all current locations, backup lifetimes, logs or support access. Game-only processing/retention remains conditional on implementation and approval.

Release retention schedule

We keep personal information only for a necessary, specified purpose. The normal periods below apply to copies under our control, including database records, private support files, corresponding Gmail messages and downloaded operational copies. We delete earlier where the purpose ends or a valid erasure right requires it.

CategoryNormal period
Ordinary support correspondence12 calendar months after first resolution or closure; an open investigation is reviewed separately
Ordinary support screenshots and attachments90 days after first resolution or closure; report/appeal evidence follows its separate period
Temporary original uploads for revised image processingEligible for removal after the upload grant expires plus 5 minutes, then removed by the next successful daily cleanup, subject to a documented hold
Privacy/deletion-request correspondence12 calendar months after completion, rejection or cancellation; website records are then redacted
Minimal proof of handling a website privacy/deletion request3 years after the terminal outcome; minimal reference, type, status and timestamps, without correspondence, email or account reference
Exceptionally retained verification evidenceNormally no copy; if necessary, up to 30 days after verification or case closure, whichever is later
Beta tester applications and live deduplication mappings90 calendar days from submission, calculated in UTC, for pending, approved and rejected applications alike. After approved activation, the daily cleanup removes due live applications and their mappings atomically. Successful execution, retries and backlog affect actual deletion time; a documented lawful hold delays deletion until explicitly released. Earlier valid erasure requests are reviewed individually
Future Google Cloud BigQuery daily exportPlanning target: 36 months, not an approved production period. Daily export of website/Android streams requires separate approval and access/expiry/deletion controls. This release does not activate BigQuery or streaming export
Firebase Crashlytics reports and associated identifiersGoogle describes 90 days before removal from live/backup systems begins, not a guarantee of immediate erasure at day 90. On-device cached-report expiry and individual deletion behavior are not verified
GA4 website and Android streams in shared property 562429951Our initial release targets 14 months for supported user/event data and reset on new activity disabled at PROPERTY level for both streams. Verify Google Analytics Admin before enabling analytics; publication alone does not apply or confirm these settings. This does not bound aggregated reports, cookies or Firebase Crashlytics
UGS match journals, replays and integrity evidenceNo fixed period is yet approved. Define necessary periods, appeal/security exceptions and deletion before the related backend processing is activated; the applicant period does not apply
Vercel Hobby runtime-log availabilityEarlier review: 1 hour; reconfirm the current plan setting. Other provider records have separately applicable purposes and periods
Non-legal website administrative audit records24 calendar months, subject to a documented hold; legal publication history is retained separately
Required Israeli database access/security technical records, where applicableAt least 24 calendar months; normally deleted at 24 months unless a lawful hold requires longer
Report, enforcement and appeal evidenceLater of 7 calendar months after notification of the decision or 1 calendar month after final appeal resolution
Minimal serious-abuse prevention referenceNormally 24 months after termination, subject to necessity review and a specifically justified continuing-risk exception
Minimal legal acceptance/consent historyWhile account maintained plus normally 3 years after closure, subject to applicable longer requirements
California automatic-renewal consent proof, where requiredLater of 3 years after consent or 1 year after the contract ends
Bot match-bound validation snapshot, where offeredKeep only while necessary for recovery/validation, with a separately approved period before activation; stop future donor use on account deletion
Website database recovery historySix-hour Neon window was verified on 2026-10-04; this is a dated observation, not a guarantee of the current provider setting. No guarantee about unrelated provider records
Future game/provider recovery copiesConfiguration and deletion behavior remain unverified; 30-day release target is not an implemented guarantee

Applicant cleanup deletes live database fields and retry keys. Gmail, exports, provider backups and necessary audit records need separate justified retention/deletion; the database job does not erase them. Any future BigQuery copy likewise needs its own deletion/expiry handling; changing GA4 retention, withdrawing consent or deleting a game account does not itself guarantee erasure of exported copies. Retention holds require a recorded purpose and review within 90 days; an overdue review does not silently release the hold. Neither approval/rejection nor a duplicate retry extends submission time. Deduplication ends when its live mappings are deleted; a later explicit submission can create a new application. This is not indefinite deduplication or a guarantee of immediate physical backup erasure.

Account progress and essential entitlements remain while the account is maintained, subject to your deletion rights and periodic necessity review. We do not introduce automatic inactive-account destruction through this policy. Social relationships and other account-linked records are removed on deletion or retained only as minimal, separately justified evidence. Open cases require periodic necessity review. Reopening a case does not reset its original retention clock; deletion is paused while the case is open and reassessed when it is resolved again. Report expiry uses the recorded decision-notification time and final appeal resolution, rather than assuming that a status change notified the player.

Accounting records required under Israeli bookkeeping rules are retained for the applicable period, generally the later of seven years after the relevant tax-year end or six years after filing that year's income return. This applies to necessary accounting evidence, not your entire game profile, screenshots or unrelated email. Longer applicable obligations and legal holds can override an ordinary expiry.

A legal hold is limited to the necessary records and duration of an actual dispute, investigation or legal requirement, with a review deadline of no more than 90 days. Missing that review does not automatically release the hold; it remains until explicitly removed following review. Truly anonymous statistics may be retained longer; a hashed player ID or neutral avatar does not itself make information anonymous.

Our website's rate-limit counters expire with the corresponding window and deduplication charge records after 24 hours, followed by monitored cleanup. Accepted tickets and screenshots have their own periods above. Moving Gmail messages to Archive is not deletion; Trash may retain a message for up to 30 days, so scheduled erasure must account for that behavior. Service providers may also retain limited information under their own applicable legal obligations and notices.

12. Your rights and how to make a request

Depending on the law applicable to you, you may have rights to access information; obtain a copy; correct it; request deletion; restrict processing; object to processing, including qualifying profiling; receive certain information in a portable format; withdraw consent; and complain to a competent data-protection authority. The conditions and exceptions differ by right and jurisdiction. Consent withdrawal does not authorize us to ignore necessary contractual or legal processing supported by a different valid basis.

Use https://bubbleserenitygame.com/privacy-choices or our privacy contact. These routes also cover tester applicants: tell us that the request concerns a beta application and use the application email where possible; no player account is needed. Include a player ID only if the request concerns an existing game account and it is available. Explain whether you seek access, correction, deletion or another right. We verify control proportionately before disclosing or deleting someone else's data. Owner deletion removes the live application and retry-key mappings; minimal audit records and recovery/provider copies require their separate handling and periods. We do not make every privacy right conditional on creating an account or making a purchase.

A public Player ID and an email alone do not prove account control. A verified signed-in request or a secure recovery/verification flow is needed for sensitive account actions, including guest accounts. We may request proportionate information to establish identity or authority where necessary, particularly before releasing account data or completing deletion. We prefer existing account verification over collecting identity documents. Do not send an identity document unless a secure, necessary verification method has been explained to you.

We respond without undue delay within the applicable legal deadline. Where EU GDPR applies, the response/action period is one calendar month from receipt; a necessary extension of up to two further months is explained within the first month. Identity verification does not automatically restart that clock. Other applicable territorial requirements continue to apply.

If you are in the EEA or UK, you may complain to your competent supervisory authority, including in the relevant place of residence, work or alleged infringement where applicable. Other jurisdictions may provide complaint rights through their own authorities. Our internal support process does not remove those rights.

13. Account deletion and recovery copies

The website https://bubbleserenitygame.com/account/delete records a request and receipt for owner review; it does not automatically delete a UGS account. The intended game entry, Settings → Account → Delete account, and end-to-end game/provider deletion remain unverified. A submitted request is not confirmation of completed deletion, and disabling/suspending an account is not deletion. Applicable response deadlines and proportionate verification in Section 12 still apply; the earlier 30-day design target is not a demonstrated automatic deletion service.

The intended game procedure must remove public/social discoverability and former profile display, delete or genuinely anonymize associated data, and address provider records. Any retained exception must have a specific lawful purpose: necessary accounting evidence, minimal privacy/consent/completion proof, applicable security logs, necessary serious-abuse/fraud evidence or an actual legal hold. Routine correspondence has its separate schedule and an earlier valid erasure request is assessed individually. Neutral display in retained match history and provider deletion require verification before being described as operational guarantees.

Game/provider backup windows and deletion capability remain unverified; the earlier 30-day recovery target is not a maximum erasure guarantee for game or Google data. Recovery copies must be restricted to their necessary purpose. Any restored backup must have completed deletions/corrections reapplied so it cannot reactivate a deleted profile or relationship. Retained financial/fraud evidence must not recreate an ordinary game account. Website recovery history is distinguished in Section 11.

Account deletion does not cancel an Apple or Google subscription; use the store's cancellation controls. Mandatory legal rights are unaffected.

14. Automated processing and human review

The service automatically applies age restrictions, eligibility and reward rules, matchmaking and validation, and detects possible anomalies. These operations can use account-linked data. A flag alone is not proof of cheating.

We do not permanently terminate accounts, impose account restrictions longer than seven days, or impose sanctions affecting purchased content or currency solely through automation. These decisions require human review. We provide an appropriate reason and appeal path for enforcement decisions; security-sensitive technical details can be withheld only as legally permitted without removing mandatory transparency.

Future free-text moderation requires its own approved safety package and privacy update before activation. We do not currently use third-party AI moderation or train AI on support submissions.

15. Website cookies, local storage and device permissions

Cookies and browser storage can hold information on your device. Browser storage used by our website application has the following purposes:

Where it is usedInformation and purposeDuration and removal
Public support, privacy-request and account-deletion formsA random request key in session storage helps retry the same submission and recover its receipt. The browser-storage entry does not contain your entered email, message or screenshots.Retained for the browser tab's session, unless cleared earlier. Choosing Start a separate request removes the previous key for that form. Browser session restoration can retain session data.
Tester application formA random submission UUID in session storage helps retry without duplicate applications. It does not contain a name, email or message.Browser tab session unless cleared; session restoration can retain it. Clearing it does not delete a submitted application
Website analytics choicesLocal storage records granted or denied for website GA4 separately from beta terms.No automatic expiry in the application; until changed or cleared in browser settings
Optional website GA4, after activation and consentGoogle Analytics cookies such as _ga and measurement-specific _ga_* hold pseudonymous analytics identifiers. The reviewed integration uses host-only cookies.No cookie lifetime is explicitly configured by the application. Actual tag/browser settings must be checked before activation; the GA4 user/event setting is not a cookie lifetime
Restricted owner consoleLocal storage remembers the interface language chosen by the owner. It does not store support messages or attachments in this preference.The preference has no automatic expiry in the application; it remains until changed or cleared through browser settings. This console is separate from the public website.

The request key is created when you submit a form or check for an existing receipt. It can be linked to a request on our server and is not anonymous merely because it is random. It is not used by the website application for advertising, analytics or tracking you across other sites.

You can use browser settings to block or clear site storage. Doing so can prevent receipt recovery or continuity between retries, and starting again may create a separate request. It does not delete a request already stored on our server, delete a game account or cancel a store subscription. For help or an applicable privacy request, contact privacy@bubbleserenitygame.com.

The direct GA4 integration (without Google Tag Manager) defaults off. If enabled, use website Analytics settings to accept, reject or later withdraw/change your choice. Rejection does not load our GA tag. Withdrawal disables subsequent tracking through the integration and attempts to clear its host-only GA cookies. It cannot recall a request already sent or erase Google-held data automatically. Browser storage failures may prevent remembering a choice across visits. Continued browsing, entering an invitation code and accepting beta terms are not consent to optional tracking. See Section 3.1.2 for the activation/consent boundary and Section 12 for rights requests.

Vercel Authentication protects the restricted owner console and protected previews. It can set an access cookie after an authorised sign-in. This is a separate access-control process; ordinary public pages do not require visitors to sign in to Vercel. Provider-managed authentication and security technologies follow their applicable settings and service rules, and are distinct from the application's browser-storage entries above.

The game stores information necessary for local operation, including appropriate caches and the local under-age block flag. Analytics/Diagnostics choices are stored locally in PlayerPrefs and the SDK can separately persist collection switches. These choices can survive launches; clearing local app data does not itself delete previously received provider reports. We disclose actual permissions and identifier use at the point required by the platform and applicable law.

The current website does not request access to contacts, camera, microphone, precise location or your photo library; you select any support attachment yourself. If a feature later needs such access, we explain the purpose and request the required permission before access.

16. Security

We use appropriate organizational and technical measures for the information we handle, including restricted administrative access, private support-file storage, validated uploads and protected server-controlled account records where those systems are deployed.

No online system can be guaranteed completely secure. We assess suspected incidents and notify affected people or competent authorities where required by applicable law.

17. Information for people in Israel

Albert Azaryev is responsible for the information described in this policy. You can contact privacy@bubbleserenitygame.com or write to Shapira 14, Netanya, Israel. You may exercise applicable Israeli rights of access and correction and contact the Israeli Privacy Protection Authority through https://www.gov.il/he/departments/the_privacy_protection_authority.

Providing support screenshots, optional profile country and optional linked login details is voluntary. Declining them limits the relevant support investigation, public field or recovery method, rather than removing unrelated gameplay. Essential account, age-band and online connection information is necessary for the requested online service; without it we cannot provide that account/session safely. A support reply requires a contact route; a sensitive privacy action requires proportionate identity verification. Purpose and recipients are described in Sections 3, 4 and 9 and in collection notices for the relevant form.

Transfers from Israel are assessed under the applicable Israeli transfer rules, including an available lawful route and the required written safeguards from recipients. An EU/UK transfer mechanism does not by itself certify compliance with Israeli requirements. Security incident reporting and technical-record retention follow the Israeli rules applicable to the database and incident, as well as other applicable regimes.

18. Policy updates

An approved operative version is published separately with its version and effective/publication dates at https://bubbleserenitygame.com/privacy; its permanent version link is shown there and in the Legal Center. A review candidate is not effective merely because it is visible. Published history is retained in the legal archive. We normally give at least 30 days’ advance notice of material changes. A legally required or urgent security change may need earlier effect; we explain it and give notice as required. We obtain new consent where a new activity requires it. An editorial update does not itself authorize a new processing purpose.

Legal Center

Bubble Serenity

  • Legal Center
  • Terms
  • Privacy
  • Purchases and refunds (Draft)
  • Community (Draft)
  • Parents and teens (Draft)
  • Privacy choices
  • Delete account
  • Contact (Draft)

Official website · More information coming soon.