Privacy Policy

1. Who we are and what this policy covers

This policy explains how we handle information for the SwoonLine V3 connected Android app, the website pages that support it, and support communications. SwoonLine V3 offers interactive stories, account-based progress, virtual Diamonds and Google Play purchases. It is intended for people aged 18 or older.

Our Google Play public developer name is Gula. The developer and data controller is Gula, operated by HE LIHUA, Hong Kong SAR, China. Our postal address is Flat 9, 11/F, The Hudson, 11 Davis Street, Hong Kong. Contact us at support@crushlinegame.com for privacy questions, account-deletion requests and player support.

2. Account and sign-in information

Guest sign-in uses an installation identifier to create or restore your SwoonLine account. The app may also establish a separate automatic recovery key using Google Play services Block Store when secure backup is available. This key can help restore the same account after reinstallation; it is distinct from your Support ID and device identifier. Android backup settings and platform availability affect whether restoration succeeds.

Google sign-in is optional. We receive and verify a Google authentication token and the authentication claims it carries, which may include an account identifier and email-related claims. Receiving this token for verification is different from using those details as your game profile. We retain a protected form of Google's account identifier to associate the identity with your SwoonLine account; we do not store the raw Google ID token, email address, name or profile photo as your SwoonLine profile or request your Google password.

We store your SwoonLine account identifier, your chosen nickname and preset avatar, authentication links, session information, your 18+ confirmation, and the versions and times of legal confirmations submitted to our account service; the app also keeps version-specific reading confirmations locally. Linking an eligible Google account from Profile → Account settings preserves your current SwoonLine account. Separate SwoonLine accounts are not automatically merged.

Earlier manual and automatic recovery codes are randomly generated, account-bound secrets. Our server retains a cryptographic digest rather than their plain-text value. Earlier automatic keys may use Google's supported encrypted backup services, and manual codes are shown for you to save outside the app. Those earlier codes expire after one year unless renewed; replacing or revoking a code invalidates that earlier code, and signing out revokes earlier automatic codes. The separate reinstall protection described in section 7 has different retention and does not have that scheduled one-year expiry. Account deletion prevents recovery of the deleted account.

3. Game, purchase and support information

To provide the connected game, we process progress, story and dialogue choices, relationship state, unlocks, achievements, rewards, virtual-Diamond balances and related game records. The app also keeps account-related data and content on your device to support play and resume progress.

Local storage includes account-scoped game progress, pending synchronization records, preferences, legal-reading confirmations, and cached story and interface images or audio. Ordinary story progress can be recorded locally before it is sent to our service. Media caches improve loading and may be reused across sessions; clearing a media cache is different from deleting your connected account or its payment records.

When you purchase Diamonds, Google Play handles the payment. We process the product identifier, purchase token, available order reference, purchase and verification status, Diamond grants, first-purchase bonuses, refund or reversal information, and the related Diamond ledger. A purchase is associated with the SwoonLine account used for that purchase. We do not receive your full payment-card number from Google Play.

During a Google Play purchase, the app sends a pseudonymous account identifier, and a profile identifier where applicable, to Google Play to associate and verify the purchase and help prevent misuse. These identifiers are not your payment-card details or a plain-text Google email address, but they may be linked to account and transaction records and are not treated as anonymous.

We process technical information needed to operate and diagnose the service: app/build version, device manufacturer and model, Android and WebView version, a separate installation reference, network requests, IP addresses, and error or operational logs. An app-scoped Android device identifier may be sent to our server and converted into a keyed pseudonymous device reference; the raw identifier is not retained in support records. Device references help investigate related installations and do not authorize access to an account or wallet. We do not use IMEI, advertising IDs, contacts or precise location for this support system.

Our network edge derives a coarse country or region code from the IP address to apply service-availability and security controls. The connected service is not currently offered in mainland China. This does not use GPS or require Android location permission. Network-derived country information can be inaccurate; contact support if you believe a supported connection has been classified incorrectly.

When you submit a support report, we associate the report and replies with your SwoonLine account, Support ID, submission time, available session/story context and technical diagnostic information. You may choose to attach a screenshot. Staff can view the conversation, relevant retained events and financial records to investigate the issue; other players cannot access your reports. Do not send passwords, recovery codes, authentication tokens or full payment-card details. Your Player ID (also called Support ID) is a public support reference that you can copy; it does not sign you in or prove ownership. A previous Player ID or Google Play order reference supplied by you is an unverified search clue, not authority to merge accounts, transfer balances or grant a purchase.

Recovery-help email drafts can include a verified current Player ID, optional player-provided previous ID or Google Play order reference, and basic app/device information: app version, build number, platform, manufacturer, model and OS version. These drafts exclude recovery secrets, authentication or purchase tokens, installation/device identifiers and full receipts. The app only previews, copies or asks your mail application to open a draft; you must send it yourself. Those actions do not confirm delivery, restore an account or complete deletion. Your mail provider processes the message you choose to send under its own terms.

4. Account statistics, Google and TikTok SDK product defaults

For accounts acknowledging the applicable revision, first-party account-linked custom statistics can be enabled by the disclosed product default. In the configured V3 Android 46 release, Profile > Account settings > Privacy & data provides read-only information; it does not provide a collection switch or a button to change the account-statistics setting. Account-linked events still require the existing current-account, installation, release and server eligibility checks. Existing server-side eligibility decisions and recorded account-statistics preferences remain relevant to the custom processing they govern; a new document acknowledgement is not a manual advertising choice. Contact support@crushlinegame.com for applicable privacy requests.

Account-linked custom events help us understand story use and improve reliability. They include sessions, app and content versions, content loading, character and story interactions, choices, media playback, shop and purchase-flow events, structured story feedback, and server-assigned feature or content variations. Events can include timing, completion, failure codes and pseudonymous references. These usage events do not include chat text, recovery secrets or payment credentials and are not anonymous.

In the configured V3 Android 46 release, Google Firebase automatic Analytics collection, advertising-related storage, advertising user data and advertising personalization settings, Crashlytics and Sessions are enabled by product default. The four Google consent-mode values analytics_storage, ad_storage, ad_user_data and ad_personalization are set to GRANTED by the product configuration. Automatic SDK collection may begin when the app process starts, before sign-in or an authorized account-linked custom-event session. This release can override earlier persisted SDK-off values. There is no in-app switch that turns off these automatic Google SDK functions.

Through these SDKs, Google may receive technical app and device information, installation or app-instance identifiers, advertising identifiers where available, network information and automatic app, session, screen and engagement observations. The SDKs also support crash and stability diagnostics and signals used for advertising measurement or personalization. Android advertising-ID availability, deletion or reset settings and other operating-system restrictions still apply; an advertising identifier is not guaranteed to be available. Automatic SDK records can be generated before a SwoonLine account is known.

Separately, custom sign_up and server_verified_purchase observations sent to Firebase require the existing account, installation and release eligibility checks, server-side account-statistics eligibility, QA exclusions, registered-version and submission-time rules, current short-lived custom-event authorization and, for a purchase observation, a genuine server-verified purchase confirmation. The app's custom reading and sending of app-instance, installation/referrer and pseudonymous event references remain subject to those checks. Account or authorization changes can stop those custom events without disabling the SDK's automatic collection. A measurement event is not authority to grant Diamonds or settle a payment. Purchase tokens, authentication credentials and raw payment receipts are not sent through these custom measurement events.

Crashlytics is separate production fault diagnostics, and Sessions supports SDK session and stability diagnostics. Automatic SDK diagnostics and the existing bounded native billing diagnostic fields, such as product identifiers, stages and result codes, follow the product default rather than a player-operated collection switch. Additional web-runtime failure reports still require current diagnostic permission and use only validated error-source and generic error-code values. The app does not forward a JavaScript error message, stack, URL, request body or player input through that reporting bridge.

The current configured release has no in-app control to turn off account-linked custom collection, automatic Firebase Analytics, Google advertising signals or personalization, Crashlytics, Sessions or TikTok SDK collection. Privacy & data is informational. A privacy request concerning statistics is different from deleting progress, wallet or transaction records, support conversations or required operational records. Contact support@crushlinegame.com to request the applicable rights or processing restrictions. Opening an information page or an email draft does not itself stop collection, submit a request or delete records held by us, Google or TikTok.

A product default is not recorded as an affirmative user analytics or advertising choice. The SDK's technical GRANTED settings do not establish that you personally gave advertising consent. Reading or acknowledging this policy, using Guest or Google sign-in, or making a purchase does not itself obtain a separate permission that applicable law requires. Neither the Google nor the TikTok product default is a record of manual advertising authorization. Publishing this policy does not itself establish a lawful basis or compliance in every jurisdiction.

The configured release also includes the TikTok Business SDK with product-default autoStart and automatic events enabled: Install, Launch and Retention, advertising-ID use where available (GAID), SDK monitoring and enhanced data postback. These are product configuration values, not a separate player choice. Our wrapper initializes the SDK only for a configured release with an eligible current account and installation, a registered submitted release and the required current server authorization; missing or invalid authorization does not initialize it. This TikTok qualification is separate from the older account-statistics preference. Once initialized, the SDK can generate its own automatic lifecycle, configuration and measurement records; those records are not each individually authorized by our custom-event lease.

TikTok may receive relevant technical app/device, installation, advertising-identifier, network and event information for configuration, advertising-performance measurement, monitoring and enhanced data postback. Operating-system advertising-ID availability, deletion, reset and other device restrictions still apply; GAID is not guaranteed to be available. Automatic in-app-purchase reporting (AutoIAP) is disabled to avoid duplicating a purchase. Our separate manual registration observation requires a genuine newly created account and current eligibility. A manual purchase observation is based on the existing single server-verified, captured purchase result and remains subject to its account, installation, release and custom-event authorization checks. It uses a pseudonymous event reference, not raw account identifiers, order references, purchase tokens or receipts. The current purchase observation has no trusted amount or currency and reports purchase occurrence without inventing revenue. A measurement event cannot itself grant Diamonds, verify or settle a payment.

The app stops its new manual SDK calls when the associated account, installation, authorization or foreground eligibility is no longer valid and uses best-effort SDK shutdown where available. Automatic SDK callbacks, in-flight requests and background configuration after initialization cannot be guaranteed to stop immediately. The current release offers no in-app TikTok opt-out switch, and we do not describe a close or destroy call as immediate cancellation of every provider request. Provider privacy notices and applicable request procedures also apply.

5. Why we use information

We use information to create and secure accounts, save and restore progress, deliver stories and media, provide rewards and purchased Diamonds, verify purchases, prevent duplicate grants and fraud, handle refunds and disputes, investigate errors, comply with applicable obligations, and answer support and deletion requests. Account-linked custom statistics support service improvement. The Google and TikTok SDK processing also supports the measurement, advertising, personalization, monitoring and stability purposes described in section 4.

Required and optional information: account identifiers, authentication information, age confirmation and records needed for a requested game or purchase feature are necessary for those features. Without them we may be unable to create or recover an account, synchronize progress or fulfill a purchase. Google sign-in, support messages and screenshot attachments are optional. In the current configured release, the Google and TikTok SDK functions use the product defaults described in section 4, and Privacy & data is read-only; it is not a collection-off control. A privacy request concerning statistics does not remove purchased entitlements.

Where an applicable law requires a stated legal basis, account access and requested game, purchase and related support functions may rely on performance of our agreement; records or disclosures required by law on the relevant legal obligation. Proportionate service improvement, reliability diagnostics, security, fraud prevention and legal claims may rely on legitimate interests where that basis is legally available and after considering affected rights. Where particular measurement, advertising or other processing requires consent or another separate permission, that requirement must be satisfied for that processing. The Google and TikTok product defaults do not constitute that permission or establish that every jurisdiction's requirements have been satisfied. We do not record a product default as affirmative consent, and reading this policy does not replace a separate permission that applicable law requires. Withdrawing consent does not affect processing lawfully carried out before withdrawal.

First-party account-linked statistics, Google SDK measurement/advertising/diagnostics, and TikTok SDK measurement and advertising functions are distinct processing channels described in section 4. The V3 story app does not ask for access to your contacts, precise location, camera, microphone or personal photo library to play its stories. Images and voice messages supplied by the game are game content.

6. Service providers and other disclosures

Service providers include Google for optional sign-in, Google Play distribution and payments; Cloudflare for network-edge, DNS and security services; Tencent Cloud, COS and CDN for media and related infrastructure; and the API, database, hosting and email services used to operate SwoonLine and respond to support requests. These providers process information needed for their functions. Google also handles information under its own applicable terms and privacy notices. Google Play services Block Store may store and restore a recovery key through its supported encrypted backup facilities. Google Firebase Analytics, Crashlytics, Sessions and related installation services provide the automatic SDK and separately qualified custom-measurement functions described in section 4. Google advertising-related collection and personalization settings follow the product configuration described there. TikTok provides the automatic SDK and separately qualified manual advertising-performance observations described there, under its release, account, installation and server-authorization conditions. Neither SDK product default is recorded as a separate player advertising choice.

Data shared for those functions includes authentication tokens and identifiers used with Google sign-in; purchase, verification and pseudonymous account information used with Google Play; IP addresses, requested resource paths and technical request information handled by our network, hosting and media providers; and the contact details, message and attachments you send through our support email services. Providers receive the information needed for their function rather than unrestricted access to all game or payment records. Their own privacy notices may also apply when they act independently.

Provider notices include Google (https://policies.google.com/privacy), Cloudflare (https://www.cloudflare.com/privacypolicy/), and Tencent Cloud (https://www.tencentcloud.com/document/product/301/17345). You may contact us for further information about the providers relevant to your request.

We may disclose information when required by law or reasonably necessary to protect users, investigate fraud or security incidents, or establish, exercise or defend legal claims. The disclosed Google and TikTok SDK configuration is not permission to give advertisers or data brokers unrestricted access to game, support or payment records.

7. Retention and account deletion

We retain your account and connected game data while your account remains open, until you request deletion or it is otherwise deleted under the service rules.

Our server-side account-linked custom usage-analytics records are retained for the configured, limited analysis period (currently up to 90 days), or removed earlier following an applicable privacy or account-deletion request. This does not remove progress, purchase records or the separate support records described below. Google and TikTok SDK records are separate and may use provider-specific retention settings and request procedures; they are not all removed by a SwoonLine account-deletion request, and the current configured release has no in-app switch to delete those provider records.

Account deletion removes from our connected account service your profile, authentication links, active sessions, progress, choices, unlocks, achievements, first-party account-linked custom analytics, and the account's spendable Diamond balance and ordinary game records. The app also removes the corresponding account data it manages locally, subject to completing its local cleanup. Uninstalling the app or clearing app storage alone does not delete the server account.

Some payment information remains after account deletion for purchase verification, refunds, fraud prevention, disputes, accounting and other applicable obligations. This includes purchase and order references, verification and reversal status, grant and first-bonus records, and the minimum financial record of Diamond credits, reversals and related adjustments. We remove the direct link to your deleted SwoonLine account. This does not make all payment records anonymous or erase records held independently by Google.

Support conversations and screenshots are normally retained for up to 180 days after last activity; device-diagnostic records for up to 180 days after last update, and support access/action audit records for up to 180 days. Earlier manual and automatic recovery codes normally expire after one year unless renewed and can be revoked earlier. The separate reinstall proof and minimum security markers described below have different retention. Necessary financial, operational or dispute records may have different periods.

Retention criteria differ by record: account and game records support the open account; usage analytics support the disclosed service-improvement purposes and are subject to applicable privacy requests or account deletion; operational and security logs support diagnosis and investigation; support correspondence supports resolution and follow-up of your request; and retained payment records support verification, reversals, prevention of duplicate claims, disputes and applicable accounting or legal requirements. We assess whether the stated purpose still requires the record rather than treating every category as permanently necessary.

A record retained for a legal obligation or dispute is limited to that purpose for the applicable period. Backup copies, where maintained, may be removed through their normal replacement cycle rather than immediately with a live record; their continued retention remains subject to the same necessity and access restrictions. Restoring a backup must not be used to restore a deleted account for ordinary use. Contact us if you need information about the retention criteria or deletion status for your records.

Request deletion through Profile → Account settings → Account management → Remove personal data, https://crushlinegame.com/delete-account/, or support@crushlinegame.com. The app prepares a draft with your Support ID. You must send the email yourself; opening or copying it does not submit a request or delete your account. After receiving a request and verifying ownership, processing may take up to 30 days, subject to applicable legal requirements. We will confirm when processing is completed and explain applicable retention. A Support ID alone is not proof of ownership; do not send passwords, session tokens, recovery credentials or payment credentials.

Same-device reinstall recovery uses a separate high-entropy credential stored through Android backup services and a protected app-scoped device reference. It restores the original account and server-confirmed state, not a new account or a merged wallet. This protection has no scheduled one-year expiry while the account remains open, but platform backup availability and retention still apply. A local write is not a cloud-backup completion receipt, and an identifier by itself cannot authorize recovery.

We retain the minimum protected device lookup, legacy recovery guard and retired credential identifiers or cryptographic fingerprints needed to prevent ambiguous account replacement and replay of deleted-account credentials. After account deletion, these records are detached from the account where applicable and cannot restore its contents. They are restricted to account security and recovery decisions, not advertising, and retained only while necessary for that purpose. Existing manual/support recovery credentials and support records keep their separately stated retention periods.

8. Security and international processing

We use reasonable administrative and technical safeguards, including TLS/HTTPS for data in transit and access controls for account and payment systems. No service can guarantee absolute security.

The developer operates from Hong Kong SAR, China, and our V3 account and game API infrastructure is hosted in Singapore. Google, network-edge, cloud, media and support providers may process information in additional countries where they operate. Storage, support access and delivery of content do not necessarily occur in the same country.

Where an applicable international-transfer rule requires a particular transfer mechanism or safeguard, the relevant processing must use a legally available arrangement and protect the rights of affected individuals. Contact support@crushlinegame.com to ask about destinations and the safeguards applicable to your information or how to obtain relevant details. Using this app is not, by itself, consent to unrestricted international transfers.

9. Your choices and rights

Depending on where you live and the processing involved, you may have rights to access, correct, delete, restrict, object to or receive a portable copy of certain personal information, withdraw consent, and complain to a competent privacy regulator. Some rights have legal exceptions. A privacy request concerning usage statistics and a request to delete your account have different effects; support can explain the available options. In the current configured release, Privacy & data provides read-only information and no in-app control to turn off account-linked custom statistics, Google SDK collection or advertising settings, Crashlytics, Sessions or TikTok SDK functions. Operating-system advertising-ID controls can limit that identifier; they do not promise to stop all SDK measurement, advertising, crash or session processing.

Send requests to support@crushlinegame.com. Describe the information or right concerned and provide only what is reasonably needed to identify the account. We may ask for proportionate verification of control to avoid disclosing or deleting another person's data. Do not send passwords, sign-in tokens or full payment-card details. We will explain if more information is needed or if a request cannot be fulfilled.

We respond without undue delay and within the period required by applicable law. For requests subject to the GDPR, this is ordinarily within one month of receiving the request; where a permitted extension is necessary, we will notify you within that month and explain why. Other jurisdictions may use different response periods or appeal procedures. We will explain the applicable next steps when responding. You may contact the Hong Kong Privacy Commissioner for Personal Data or, where applicable, the competent authority where you live or work; contacting us first is not a condition of making a regulatory complaint.

10. Age, changes and contact

SwoonLine is intended only for people aged 18 or older. If you believe a person under 18 has provided personal information to us, contact support@crushlinegame.com.

We will identify the effective date and revision of this policy and keep previous versions available. Material changes will be communicated through the app or another appropriate service notice. Server-side account-statistics preferences and eligibility decisions continue to apply to the custom events they govern. The current Google and TikTok SDK product defaults are separate from those decisions and are not a record of manual advertising authorization. The current configured release provides privacy information without an in-app collection-off control. Publishing this revision does not change the behavior of an older installed app or itself obtain consent or another legal basis required for processing. Contact support@crushlinegame.com with questions or applicable privacy requests.

Earlier editions

The earlier V1 offline edition keeps its game data on the device. The V2 connected edition has its own account and limited-free service model. The September 2, 2026 policy and service information for those editions remain available below. This V3 update does not erase the earlier terms or promise an automatic transfer of accounts, progress or gems between separate environments.

The September 14, 2026 V3 revision remains available at https://crushlinegame.com/privacy/2026-09-14-r2/. Older app versions may continue using that revision during the rollout; their collection settings are not silently changed by publishing this document.

The September 17, 2026 V3 revision remains separately available at https://crushlinegame.com/privacy/2026-09-17-r3/. Older45 apps keep their declared R3 document pair and recorded choices; publishing revision4 does not silently change them.