1. Apps covered
This notice covers the CRYA Bot Owner App, CRYA Home, CRYA Worker, CyberK Modules, Livingstone Toolkit, CRYA Play, and future CRYA-branded mobile releases that link to it. The product’s store listing and in-app notice identify its package and current features.
2. Account and sign-in
Where an app uses CRYA sign-in, the app sends the selected login proof to CRYA and receives the session needed for that account. Google Play Games, Google web sign-in, Telegram sign-in, and CRYA email/password have different platform mechanics but must resolve to authorised CRYA account state where the app uses CRYA identity.
CRYA Play catalogue discovery and watching do not require a CRYA account. If you choose to sign in, supported library, viewing progress, comments, reactions, reports, blocked-comment-author state, preferences, notification choices, AniList import, and auto-skip can be associated with that CRYA identity. Offline media downloads exist only in a separately identified private/sideload build and are excluded from the Google Play release.
The app should not store a plain-text password or expose a CRYA session token to another app. Optional device PIN or biometric unlock protects local access when enabled; it does not replace server permission checks.
3. Device permissions
An app may request notifications, files/media access, camera, location, nearby devices, network access, or biometric/device credential only when the selected feature needs it. Android shows the permission request and settings. Refusing a permission may disable that feature but should not silently grant an alternative permission.
CRYA Worker location or map features, CRYA Home device and network connections, and Toolkit file/package operations have different needs. Review the in-app explanation before granting access.
4. Product-specific information
- CRYA Bot Owner App: Telegram groups the signed-in user may manage, bot presence, owner/admin permission, group settings, moderation/federation/game controls, member or player summaries, and save receipts.
- CRYA Home: user-configured home connection details, entities, scenes, sensors, cameras, energy, alerts, and local intelligence needed for the selected dashboard and automations.
- CRYA Worker: worker identity, attendance, assignments when available, field forms, farm/map/weather context, notes, photos or location the user records, offline queue, and supervisor workflow.
- CyberK Modules: device and firmware compatibility, module catalogue, package/download state, validation, installation workflow, and diagnostics.
- Livingstone Toolkit: selected files, animation/project settings, previews, Package Doctor results, device-tool outputs, export history, and advanced-operation diagnostics.
- CRYA Play: selected Anime, Drama, or Chinese mode; catalogue/search interactions; title and episode references; playback position and completion; library/history; comments, reactions, reports, and blocked-comment-author state; notification and auto-skip preferences; TV or Google Cast connection results; and Sponsored Premiere delivery or interaction records. A separately identified private/sideload build may additionally keep a local adult-section unlock state and offline download state. Video addresses, provider credentials, authentication tokens, and cookies are excluded from redacted diagnostics.
5. Notifications and device registration
If notifications are enabled, CRYA may register a platform push token with the relevant app/account and send the categories the product supports. A token identifies an app installation for delivery; it is not a payment credential. You can disable notifications in the app or Android settings, subject to critical system notices permitted by law.
6. Diagnostics and analytics
Apps may process crash, performance, version, device compatibility, and action-result diagnostics needed to keep the product working and secure. CRYA Play may also record privacy-bounded viewing activity such as title/episode reference, progress, time spent, completion, mode, and Sponsored Premiere delivery or interaction so continuity and aggregate product reporting can work. Optional diagnostics are off by default for a new CRYA Play installation and begin only after the user enables the preference. CRYA must not treat a package configuration alone as proof that push or analytics is active.
6A. Advertising, Cast, and independent media providers
A CRYA app build that activates Google Mobile Ads can cause Google and its partners to receive device or advertising identifiers, IP/network information, app interactions, consent state, and diagnostics under Google’s notices and the choices required for the user’s region. CRYA must complete the matching Google Play Data safety declaration and consent configuration before enabling production advertising. A package dependency or test ad identifier alone does not mean production advertising is active.
When the user chooses Google Cast or another TV connection, the device discovers or connects to a receiver on the local network and sends the media request and playback controls needed for that action. Google, the receiver manufacturer, the network operator, and the selected media provider process the parts they control.
Opening or playing provider-hosted media sends an ordinary network request to the selected provider. That provider can receive the user’s IP address, request headers, device or player characteristics, requested media location, and other data described in its own privacy notice. CRYA diagnostics exclude provider credentials, cookies, authentication tokens, and full video addresses.
7. Purchases
Google Play handles payment details. CRYA receives only the purchase and entitlement evidence needed to activate, restore, support, prevent fraud, and meet legal duties. The app must show the current offer and provide a real route to manage or cancel the subscription.
8. Storage, offline data, and security
Some apps keep encrypted or app-private local data so a selected workflow can work offline or open quickly. Synchronised account data uses CRYA’s authorised service; user-configured external systems remain separate. Signing out should remove or protect account-bound local access as appropriate, but exported files remain where the user saved them.
CRYA Play may cache catalogue records, artwork, mode, scroll position, playback progress, and library context so navigation opens quickly. The Google Play release does not provide provider-media downloads. In a separately identified private/sideload build, an authenticated offline action can save an authorised direct episode file through Android Download Manager; the viewer can cancel or remove it, and uninstalling or deleting the CRYA account does not guarantee that a file already exported or downloaded outside synchronised storage is erased.
High-impact actions should require appropriate confirmation and remain subject to server permissions. Root, package, boot, and device-management tools require extra care and backups.
9. Your controls
Use Android settings to review permissions, notifications, storage, nearby-device access, and biometric access. Use the app to sign out, change available preferences, remove CRYA Play downloads, restore a purchase, or disconnect a service. Use My CRYA or the deletion route for account rights. Uninstalling removes the app from that device but does not necessarily cancel a subscription or delete synchronised data.
10. Full notice and support
The full Privacy Policy explains legal bases, recipients, international processing, retention criteria, rights, minors, and contact. For an app privacy problem, include the product, package/version, device model, permission or screen, and safe evidence.