How AuroraKajo handles information for Aurora Play, AuroraTube, AuroraShare and AuroraMessenger.
Last updated November 17, 2026
Aurora Play is the AuroraKajo app catalog at aurorakajo.com. Browsing, public downloads and review submissions do not require an account. The current public store has no consumer sign-in. Its pages do not include third-party advertising or analytics trackers.
The optional store_view cookie remembers your Full or Lite choice for up to one year. Automatic selection recognizes older Nokia and Symbian browsers; a small script on full pages can also select Lite below 360 CSS pixels unless you have chosen a view. Lite pages run without JavaScript. Choosing Automatic view clears the preference. Network providers and separate sign-in or account-connection services may use essential security cookies.
The storefront logs request methods, requested addresses, response codes and processing times for operation and troubleshooting. Addresses can include search terms or other query parameters; do not put private information in URLs. Its application log does not explicitly record IP addresses or cookies, but network providers and other components process connection addresses and security information. Heartbeat and review records are described separately below.
AuroraKajo operates Aurora Play and the Aurora services described here. This policy covers the store, our application services and information our apps send to them. Third-party platforms, independent relay operators and external websites also have their own privacy practices.
For privacy questions, access, correction or deletion requests, contact AuroraKajo on Telegram. Do not send passwords, recovery PINs, session tokens or private conversations in a support message.
The download service records the release, transfer status and completion time to count delivered packages. Delivery does not establish installation or use. Anonymous transfers are not linked to a store account; older signed-in download records may remain associated with the account that created them.
Reviews store the display name and phone model you enter, stars, optional review text and submission time. Phone model means a device name, not your telephone number. Reviews wait for moderation. Approved reviews publicly show your chosen name, phone model, stars and text. Use a nickname and avoid sensitive information. Older account-based reviews may use an anonymous public label. Contact us to request correction or removal.
To limit review spam, the service stores a keyed hash derived from the connection IP instead of placing the raw address in the review record. The abuse window is seven days; older hashes are cleared when reviews are processed. This does not remove the review or control separate infrastructure logs.
Apps with heartbeat support automatically report activity without a store account, pairing code or account-page switch. Reports can include random device and installation identifiers, app/library versions, phone model, platform/system version, network type, screen dimensions, uptime and start, heartbeat or stop events. A shared random device identifier helps count distinct devices across Aurora apps on the same phone.
Reports are normally scheduled about every five minutes while the app state and connection permit. Backgrounding, inactivity, loss of connection or stopping an app can suspend reporting, depending on the version. A recent event estimates activity; it does not prove a device is online at this exact moment. Distinct devices are not necessarily distinct people.
The server records receipt time and the most recent connection IP. Approximate country estimates can be affected by VPNs, proxies and routing. Reports support operation, reliability and country/device statistics. They do not include GPS coordinates, IMEI, contacts, messages, passwords, recovery PINs, shared-file names or folder paths, and are not linked to a store account.
Current AuroraTube playback connects directly to YouTube; older versions or selected services may use Aurora relays or gateways. Search, media requests, connection addresses and chosen content are processed by the services involved. Local history, favorites and downloads can remain on the phone until removed.
Where you choose to connect YouTube, AuroraTube uses YouTube API Services with read-only authorization to show your selected channel, subscriptions, playlists and uploaded videos. The service stores the installation ID, channel ID, name, handle, avatar URL, uploads playlist ID and subscriber count, plus protected access/refresh tokens. It does not request your Google password or use this permission to upload or change your account. Lists are requested as needed rather than stored in the linked-account record. Separate saved-video records may also exist.
Disconnect in AuroraTube or revoke access through Google Account permissions. Successful in-app disconnection revokes the grant and removes the linked-account record; retry or contact us if revocation fails. External revocation stops authorized access but does not erase local downloads or separate saved-video records; request their deletion separately. Google processes its own service data under the Google Privacy Policy.
We use Google user data only for requested account features and necessary security or legal purposes. We do not sell it, use it for personalized advertising or give Google OAuth credentials to media relays. Human access is limited to your specific permission, necessary security investigation or applicable legal requirements. Contact us to delete retained account-connection data.
LAN mode exchanges your selected folder's files directly between phone and browser; the store catalog does not receive those contents. The authorized browser can access the file names, folder contents and transfers you expose. Read/write mode permits supported file changes.
In Internet mode, the selected relay processes pairing/session information, connection addresses and file-transfer traffic. Do not treat it as an end-to-end encrypted vault. Relay operators can differ and have their own access/logging practices. Stop sharing or end the session when finished. Copies already downloaded by someone else are outside your phone's control.
AuroraMessenger provides native Messenger conversations on Symbian. A Facebook account is required for messaging, but an Aurora Play account is not. The installed client connects directly to Meta's sign-in and messaging services and the services delivering its media. Those services process the credentials, session material, messages, attachments and connection information needed for the requested features under the Meta Privacy Policy and Meta Terms of Service.
Aurora heartbeat, support and update services are separate from the Messenger transport. They receive the device/service information described here, not a cloud copy of your Facebook password, session cookies, recovery PIN or conversations. Do not send these secrets to support. Where history recovery is enabled in your version, its Messenger recovery PIN is separate from an Aurora Play password.
The client can retain session information, cryptographic keys, conversations, cached attachments and local diagnostics on the phone. Protect the phone, memory card and exported files. End-to-end messaging encryption does not by itself protect every downloaded or exported copy. Logging out does not promise to erase exported files or every existing copy. Use the local-data controls available in your version; ask support if the required control is unavailable.
In versions offering Send log to developer, opening that screen prepares a local diagnostic export and a 12-digit report reference. It does not upload the export. Choosing Send log uploads it over HTTPS for troubleshooting. The report contains numeric operational events, timestamps, error/performance information and app/version information. The service associates it with random device and installation identifiers, a report ID/reference, receipt time and an integrity hash. These identifiers support diagnosis and are not anonymous data.
The supported upload schema accepts bounded numeric diagnostics, not chat transcripts, attachments, Facebook passwords, session cookies or recovery PINs. Check any separately exported file before sharing it elsewhere. Authorized owner/auditor staff can read server reports; reading report text creates an audit record. Reports are limited to 600 KiB and eight per installation per day. Scheduled cleanup removes reports from the active database after 30 days; separate audit records, infrastructure logs and backups do not share that expiry.
For access, correction or deletion requests, contact AuroraKajo on Telegram with the app name and report reference. The reference helps locate a report; it is not a password or sufficient proof of ownership by itself. Requests are reviewed and may require proportionate verification. Live deletion does not immediately erase backup copies.
Apps supporting managed updates use app/version, random device and installation identifiers and an installation authorization credential to check eligible updates. This credential is separate from a Facebook session. Stable is the ordinary release channel. Beta requires authorization from AuroraKajo for the specific app, device and installation; choosing Beta alone does not enroll a phone. A reinstall or changed authorization may require fresh admission.
Authorized release administrators manage Beta groups and membership. The service records app/group, device/installation and authorization binding, admission/revocation times and audit reasons to enforce access and investigate changes. Membership/audit records do not automatically expire with the 30-day diagnostic-report window. Contact support to request withdrawal or review/deletion of retained membership data. Revoking access does not uninstall a build, erase local data or remove an already submitted report. Connection addresses may also be processed by the infrastructure described below.
Accounts created on earlier Aurora Play versions may retain email addresses, protected password hashes, sessions, download history and account-request records. Staff use separate protected CMS accounts. These records do not make sign-in necessary on today's public store.
Where a separate service offers Google sign-in, its Google account identifier and verified email find or create the service account. Google passwords are not requested, and the identity access token is not retained as an account field. Authentication and OAuth flows may use essential session, request-protection and short-lived connection cookies. The current public store has no account dashboard; contact us if old account controls are unavailable.
Application/database services are hosted with OVHcloud in Singapore. Cloudflare carries public traffic and supplies network/security services. Providers may process service and connection data on our behalf, including in other countries. Google/YouTube, Meta/Facebook, selected relays and external support/social platforms process data needed for their features. Authorized operators access service records for administration, support, abuse prevention and security; disclosure may also be legally required. We do not sell personal information or share it with advertising brokers.
Access controls and protected credential storage reduce risk; connected YouTube tokens are protected before database storage. No system or older phone guarantees absolute security. HTTPS protects supported connections in transit. HTTP Lite and public package delivery remain available for older Nokia browsers, and LAN or selected relay connections may use HTTP. HTTP is unencrypted and can be observed or altered. Prefer HTTPS, use trusted networks and avoid sensitive information in HTTP forms. A checksum on the same HTTP page does not independently authenticate that page.
Scheduled cleanup removes heartbeat events older than 30 days. Only the owner can view a recent connection IP, with audited access. It is hidden after seven days of installation inactivity and cleared by scheduled cleanup. Device/installation records, last-seen information, country information and cumulative counts can remain after individual events expire.
Expired pairing codes and sessions are removed by scheduled cleanup. Review hashes and diagnostic reports follow their separate rules above. Reviews, download statistics, existing accounts, Beta memberships, audit records and separate saved-video records do not all have the same automatic expiry; they are retained for the described operation, moderation and security purposes and reviewed on deletion requests. Operational logs and backups have separate retention/rotation schedules. Live deletion does not immediately erase older backups.
Request access, correction or deletion through AuroraKajo on Telegram, identifying the app, approximate dates and relevant display name or installation information if available. We may request proportionate proof that data is yours; never send a password or PIN as proof. Requests are reviewed rather than instantly executed. Security, others' rights or legal obligations may require some retention. Contact the relevant third party about data it controls.
Do not submit children's private information in reviews or support messages. Contact us if you believe a child's personal information should be removed so we can review it.
This policy is updated as features/data practices change, with the revision date shown here. An update does not grant permission to repurpose previously collected information; additional notice or permission will be provided where required.
Terms of use | AuroraKajo on Telegram | Google Privacy Policy | Google Account permissions | Meta Privacy Policy
Full website | Install help | Privacy | Terms
Free downloads. No Aurora Play account needed. Key 0: home.