המסמכים המשפטיים זמינים כרגע באנגלית בלבד. בהמשך מוצגים המסמך המקורי באנגלית והסטטוס הנוכחי שלו.
Bubble Serenity · Review draft
Privacy Policy — DRAFT
Draft 0.7. No effective date. This document is available for review and is not a legal acceptance version.
Draft version: 0.7 Prepared: 2026-10-04 NOT FINAL / NOT FOR RELEASE — no effective date
This is a candidate release-policy text for owner, Claude and legal review. It is not an operative policy. Present-tense game statements describe the intended release behavior and require evidence before publication. The concrete retention schedule is a drafted project policy; website retention and new-image sanitization were deployed on 2026-10-04. New-image processing, retry handling, owner hold controls, 12-month correspondence expiry and three-year proof expiry have been verified on synthetic production data; the daily cleanup is enabled. Removal of the temporary original at its grant-safe expiry still needs its scheduled verification. Game/provider deletion remains separately unverified. No document here authorizes a deployment or paid commitment.
Unresolved publication and implementation requirements are tracked separately in the Legal Documents Completion Register.
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.
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.2 Account and authentication information
An eligible player can start with a guest account. We process the account identifier, authentication and session records, and information necessary to maintain or recover that account. A guest account can still involve personal information, even if no name or email is requested.
If you choose a supported account-linking method, we receive the identifiers and other information that the selected authentication provider makes available for that method.
Linking does not automatically merge two accounts with separate progression. We may process account-conflict or recovery records to resolve a conflict through the supported process.
3.3 Age assurance
The game asks for birth month and year through a neutral age step before creating an account or initializing third-party analytics with identifiers, crash reporting with identifiers, advertising or attribution services.
We store an age band. For players under 18 we also store the month and year in which they turn 18, so that adult features open at the appropriate time. This value reveals the birth month and year. At the first authoritative account read after adulthood, the server updates the age band and erases that value; an inactive account may retain it until that read or account deletion. 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
We keep minimal records of the published legal document version you accept or acknowledge and of any optional privacy choices: version/hash, language, choice, time, method, application/platform context and necessary account reference. Acknowledging a Privacy Policy is not blanket processing consent. Consent changes and withdrawal are recorded separately; precise age or birth input is not needed in these records.
3.5 Progression, gameplay and competitive integrity
We process account-linked game progress, unlocked content, Heroes and their progression, city and house state, virtual currencies and inventory, battle preparation, rewards, claims, subscription entitlements, competitive ratings, and game-result history needed for the features you use.
For online battles, we process matchmaking and connection information, match identifiers, the necessary combat configuration, player actions and timing information, validation records and integrity evidence. The multiplayer provider also processes network addresses needed for the connection; connection providers process network addresses for session delivery. These support matchmaking, reproducible results, reconnect/recovery, rewards and cheating investigations. A combat validation record does not necessarily include a full recording of a battle.
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 display name, selected avatar and public game progression or competitive information.
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
Apple App Store or Google Play handles the payment details that you provide to the store. We process the transaction, receipt or purchase-token information, product and store identifiers, entitlement/renewal state, validation results, refund/revocation information and claim records necessary to verify purchases and provide or recover benefits.
We do not need your full payment-card number or security code to grant an in-game purchase. Do not send them to us in support requests. Store payment records may remain with the store after deletion of a game account.
3.8 Technical information and optional services
Essential technical processing can include device/operating-system and game versions, language, network/connection data, error details and security information required to operate the online game. We do not use essential technical processing for optional tracking.
Advertising and attribution information is described in Section 7 and applies only where the adult advertising features are enabled with the necessary legal and platform permissions.
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.
Where enabled on a lawful basis, we also use limited diagnostics and gameplay measurements to understand errors, performance and progression, and optional adult advertising information for the purposes disclosed at the point of choice.
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.
| Purpose | Legal ground |
|---|---|
| Necessary account, save, gameplay and purchase fulfillment | Contract, 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 reliability | Legitimate interests, subject to necessity, proportionality and an assessment of your rights, with particular care for children |
| Support, reports and appeals | Contract 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 responses | Legal obligation, with the actual obligation identified |
| Age assurance and safety restrictions | Applicable legal obligation where one exists; otherwise a specifically assessed legitimate interest. The basis depends on the relevant territorial requirement |
| Limited server-generated gameplay and retention measurements | Legitimate interest in improving retention, game balance and stability, where the necessity and balancing assessment supports this processing, including the best interests of younger players; otherwise obtain required consent or disable the processing |
| Optional device analytics, advertising identifiers, attribution and tracking | Separate consent where required by data-protection or device-access law, together with necessary platform permissions |
| Read-only Bot donor combat configuration | Legitimate 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.
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.
For all players, including players under 18, we use limited pseudonymous gameplay and retention measurements to improve the game. These measurements use a pseudonymous player identifier and a Teen or Adult segment, without advertising identifiers, device fingerprinting, precise location or the month of adulthood. They are not used to personalize offers or prices, or for advertising or marketing to players under 18. We prefer events generated by the game server and restrict any external analytics recipient to an appropriately contracted processor for this purpose. Pseudonymous measurements remain personal information. We enable this processing only on a lawful basis for the relevant territory, with particular care for children; necessary device-access consent cannot be bypassed by routing information through a server. Security and game-integrity processing remains limited to what is necessary and lawfully justified.
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. Optional adult rewarded advertising and tracking choices
Rewarded advertisements are optional and available only to eligible adult accounts. Adult advertising records include daily eligibility/completion counters and transaction-deduplication references needed to verify rewards. Watching an advertisement is a separate choice from consenting to personalization or cross-app tracking.
When an eligible adult chooses an advertising feature, approved providers may process ad-delivery and completion events, fraud-prevention information, technical device/network data and advertising identifiers where permitted. Personalization, attribution and cross-app tracking depend on the actual provider configuration, applicable law and your choices.
Where consent is required, the relevant processing starts only after valid consent. On iOS, tracking that requires App Tracking Transparency permission also requires that permission. A separate privacy choice cannot override an ATT refusal. We apply any required privacy and device-access choices to contextual advertisements too.
You can decline or withdraw optional consent through the in-game privacy settings or our privacy contact. Withdrawal does not affect the lawfulness of earlier processing based on consent. Ordinary gameplay remains available. Refusing or granting a privacy consent does not itself earn a reward or incur a penalty; an advertised reward is for voluntarily completing an eligible advertisement, not for choosing consent.
8. Bot opponents and use of combat snapshots
When a live opponent is unavailable, the game may provide an autonomous Bot using a limited, read-only combat configuration derived from an eligible player's game state. This is not a recording of that person's actions and does not mean that the donor is online or controls the Bot.
The configuration contains only approved game-combat fields required for that opponent. It does not include the donor's email, age record, private payment information, social relationships or unrelated account data. Changes during the Bot match affect its virtual match copy; the donor's inventory, progress and competitive results are not changed.
Under-18 donor profiles are displayed using a neutral name and default avatar. Eligible adults may object to use of their public profile for AI opponents through Settings → Privacy options . After a profile objection, your display name and avatar are no longer used for Bot display; the approved combat configuration may still be used with a neutral display, subject to your applicable rights. This profile objection is distinct from a request about the underlying combat snapshot. Where applicable data-protection law gives you a right to object to the underlying processing, you may also contact us; we consider that request under the applicable law rather than claiming the profile toggle exhausts your rights.
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 requests are not automatically forwarded to another person or sent by email simply because a form is submitted.
| Service | Role |
|---|---|
| Vercel | Website hosting and private support-file storage |
| Neon | Website database storage |
| Google Gmail | Current email correspondence; Albert Azaryev reviews privacy emails |
| Unity Gaming Services | Game authentication, protected saves and networking, for products actually activated |
| Apple and Google | Store purchases and supported authentication or age signals, where enabled |
Advertising, attribution, analytics and crash-reporting providers have not yet been selected. These services are not currently offered through the website. Before activation, we identify the provider, data, purpose, role, retention and applicable choices in the policy and relevant collection notice.
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, we use an applicable adequacy decision or appropriate safeguards, such as approved contractual clauses and required supplementary measures, for the particular transfer. You can request information about the applicable safeguards through our privacy contact.
11. How long information is kept
Current website handling and planned release schedule
The current website stores accepted support and privacy requests in a Neon database in Frankfurt, Germany, and accepted screenshots in private Vercel Blob storage. Requests are reviewed by the owner. Changing a request status to Closed or Completed does not erase its content or an associated game account. The current upload implementation re-encodes accepted JPEG, PNG and WebP images to remove embedded metadata while retaining orientation in the pixels. This has been verified on a synthetic production upload; temporary raw uploads are tracked separately until their grant-safe cleanup date. Historical screenshots are not silently rewritten by the migration and require a separate verified cleanup.
The existing cleanup job is scheduled daily at 03:00 UTC, within Vercel's Hobby scheduling window. It removes expired abuse counters and abandoned uploads, subject to authorization, execution limits and successful completion. Upload reservations last 30 minutes, with a five-minute safety delay before cleanup eligibility; files are not necessarily erased as soon as that interval ends. Accepted tickets and attachments are excluded from that abandoned-upload cleanup.
The schedule below is the adopted release retention policy. Automated expiry of accepted website correspondence and attachments is deployed and enabled. The existing daily cleanup runs at 03:00 UTC within the hosting plan's one-hour scheduling window; retries and backlog can delay erasure. It must not be read as a claim that every existing copy is already being automatically erased on that schedule. Requests to erase website information are reviewed individually through the privacy contact.
The Neon database's configured recovery history window was verified as six hours on 2026-10-04. This describes this database's point-in-time recovery window, not every provider's internal recovery or legal retention. Vercel's published Hobby runtime-log availability is one hour; this does not establish a one-hour lifetime for all provider security, billing or operational information.
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.
| Category | Normal period |
|---|---|
| Ordinary support correspondence | 12 calendar months after first resolution or closure; an open investigation is reviewed separately |
| Ordinary support screenshots and attachments | 90 days after first resolution or closure; report/appeal evidence follows its separate period |
| Temporary original uploads for revised image processing | Eligible 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 correspondence | 12 calendar months after completion, rejection or cancellation; website records are then redacted |
| Minimal proof of handling a website privacy/deletion request | 3 years after the terminal outcome; minimal reference, type, status and timestamps, without correspondence, email or account reference |
| Exceptionally retained verification evidence | Normally no copy; if necessary, up to 30 days after verification or case closure, whichever is later |
| Ordinary crash/performance diagnostics and validation evidence | 90 days after collection |
| Optional account-linked product analytics, if enabled | Target maximum 90 days; exact provider behavior must be confirmed before activation |
| Vercel Hobby runtime-log availability | 1 hour; other provider records have separately applicable purposes and periods |
| Non-legal website administrative audit records | 24 calendar months, subject to a documented hold; legal publication history is retained separately |
| Required Israeli database access/security technical records, where applicable | At least 24 calendar months; normally deleted at 24 months unless a lawful hold requires longer |
| Report, enforcement and appeal evidence | Later of 7 calendar months after notification of the decision or 1 calendar month after final appeal resolution |
| Minimal serious-abuse prevention reference | Normally 24 months after termination, subject to necessity review and a specifically justified continuing-risk exception |
| Minimal legal acceptance/consent history | While account maintained plus normally 3 years after closure, subject to applicable longer requirements |
| California automatic-renewal consent proof, where required | Later of 3 years after consent or 1 year after the contract ends |
| Bot match-bound validation snapshot | Until recovery/validation no longer needs it, normally no more than 90 days; stop future donor use on deletion |
| Website database recovery history | Verified Neon window: 6 hours; no guarantee about unrelated provider records |
| Future game/provider recovery copies | Configuration and deletion behavior remain unverified; 30-day release target is not an implemented guarantee |
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 verified privacy contact. Include your player ID if available and explain the request. 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 intended game deletion entry is Settings → Account → Delete account. Its implementation has not yet been verified. The website provides the external request page https://bubbleserenitygame.com/account/delete. The current website records a deletion request and receipt for owner review; it does not itself automatically delete a UGS account.
The release deletion process is designed to complete requests within 30 days of receipt after proportionate verification, provide a completion confirmation and meet any shorter applicable legal deadline. The end-to-end game/provider deletion process is not yet verified; submitting a website request is not itself confirmation that deletion has occurred. In other players’ retained match history, a deleted account is shown as “Deleted player”, without the former public name or avatar. We delete or genuinely anonymize the associated game data, remove public/social discoverability and resolve linked provider records, except narrowly justified retained records disclosed in Section 11. Retained exceptions are limited to required transaction/accounting evidence, minimal privacy/consent/completion proof, applicable security audit records, necessary fraud/serious-abuse evidence and records under an actual legal hold. Routine support copies expire on their separate schedule; a valid earlier erasure request is assessed on its merits. Disabling or suspending an account is not deletion.
Routine backups have a planned recovery window of at most 30 days after source deletion. The actual provider-specific windows remain to be confirmed before game release. They are restricted to recovery/security purposes. If a backup is restored, completed deletions and privacy corrections must be reapplied so that recovery does not reactivate a deleted account or removed relationship. Limited financial or fraud records retained under a lawful exception must not recreate an ordinary game profile.
Deleting an account does not cancel an Apple or Google subscription. You must manage cancellation through the store. The deletion information explains how store subscriptions are managed. 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 used | Information and purpose | Duration and removal |
|---|---|---|
| Public support, privacy-request and account-deletion forms | A 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. |
| Restricted owner console | Local 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 reviewed website application does not include advertising or audience-analytics scripts. We do not treat continued browsing or acceptance of the Terms as consent to optional tracking. Before introducing any storage or access technology that requires consent, we explain its purposes and providers and obtain that consent before it operates, with an appropriate way to refuse or withdraw.
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 its local operation, including appropriate caches and the local under-age block flag. 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
When this policy is finalized, we will publish a separate document version and effective date and retain published versions 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.
END OF PRIVACY POLICY DRAFT 0.7