Privacy and data safety
CRYA Privacy Policy
How CRYA handles account identity, diagnostics, support reports, store submissions, billing evidence, Telegram-linked flows, and website contact data.
Policy summary
CRYA Privacy Policy
CRYA should collect only the data needed to run the Livingstone Toolkit, support accounts, protect the Boot Store, verify purchases, diagnose package failures, and operate safe community/admin workflows.
Email, Google/Firebase identifiers, Telegram-linked identity where connected, role flags, premium state, and account recovery context.
Package failures, support reports, client errors, device/app context, and access-violation evidence used for support and safety.
Creator names, pack metadata, compatibility notes, previews, package status, review decisions, and purchase entitlement evidence.
Private users, billing, moderation, AI budgets, and role changes stay behind protected CRYA Mission Control.
| Services | CRYA website, Livingstone Toolkit, Boot Store, Creator Hub, LivingBootBOT, support routes, Firebase-backed APIs, mail/support inboxes, and protected Mission Control. |
|---|---|
| Why data is used | Authentication, entitlement checks, package diagnostics, store moderation, support replies, fraud/abuse protection, maintenance notices, and product reliability. |
| Billing data | Google Play purchase and entitlement evidence is used to verify Premium, clean exports, and app-side digital items. CRYA should not ask users to post purchase tokens publicly. |
| AI data | AI help should use reviewed support context and should not publish private account, billing, or moderation details. Admin controls govern budgets and review queues. |
| User control | Users can request account deletion, support correction, or privacy help through the app account surface when available or by contacting support@crya.pt. |
Workflow
What happens in practice
This makes the policy operational for users, creators, support, and Play review.
Only request data needed for account, support, store, billing, or safety work.
Move account and billing questions out of public community threads.
Use role checks and audit trails for admin workflows.
Provide an account deletion route and verify ownership before action.
Review this page before Play Store submissions and major feature launches.
Review note
Keep policy evidence current
Before Play Store submissions, billing launches, ads changes, or major app updates, recheck current platform policies and update this page if behavior changed.
Public policy and account requests should route through support@crya.pt so private details stay out of community threads.
Private account, billing, moderation, and deletion handling belongs in CRYA Mission Control with role checks and audit records.
Use /privacy, /terms, /delete-account, and /disclaimer in app About screens, bot link replies, footer links, and Play Console fields.