Explain account data, diagnostics, support reports, Telegram-linked flows, and Firebase-backed services.
Give users a clear path to remove account-linked data or request help.
Document file access, billing separation, ads, notifications, root-tool safety, and review evidence.
Policy links
Use these routes in app, bot, footer, and Play Console fields
Each page is written as a public user-facing policy surface, while private account and billing handling stays behind support and Mission Control.
Data safety, account identity, diagnostics, support reports, billing evidence, and Firebase boundaries.
OpenTermsTerms of UseAcceptable use, creator submissions, Premium, clean exports, Boot Store review, and community rules.
OpenAccountAccount DeletionHow users request deletion, verify ownership, and understand store/billing retention limits.
OpenSafetyDevice and Root DisclaimerRoot, Samsung/QMG, Magisk/KSU, firmware, AI, and Boot Store compatibility limits.
OpenUser rights
Know where each request belongs
Users should not need to guess whether a question belongs in public community chat, private support, account settings, or a policy page.
Check the public policy route that matches privacy, terms, deletion, or device/root safety.
Gather the account, billing, package, or device evidence needed for the request.
Move private account, billing, deletion, and moderation questions to protected support.
Confirm identity or ownership before CRYA changes private account-linked data.
Keep support decisions and retention reasons reviewable for future policy checks.
| Privacy and data safety | Account identity, diagnostics, support reports, bot-linked flows, billing evidence, and deletion requests. |
|---|---|
| Billing separation | Premium, clean export credits, and future paid Store packs must stay clearly labeled as separate purchases. |
| Ads and rewards | Rewarded ad prompts, banner settings, and ad-free grants need visible user consent and admin evidence. |
| File and app access | Package inspection, workspace files, activity launches, notifications, cleanup, and firmware context need clear purpose and user action. |
| Creator rights | Ownership, attribution, takedown, review decisions, badges, and Store submissions need public rules and protected evidence. |
Review workflow
Keep policy pages launch-ready
Every major app, website, billing, Store, AI, or utility change should leave enough public wording and private evidence for a clean review.
Check policy pages, support routes, status notices, product labels, screenshots, and app copy together.
Move private data out of public channels and keep user-facing answers short, respectful, and traceable.
Update docs, legal routes, AI knowledge, Store rules, and support templates when behavior changes.
Run readiness checks, inspect public pages, verify mail/support contact paths, and save the evidence.
Policy, deletion, billing, and private account questions should route through support@crya.pt.
Before Play submissions or billing/ads changes, recheck current platform policy and record the review date.
Website pages explain user-facing policy. Protected account, billing, and moderation systems remain the source of truth for private records.