Current beta boundary
Data Aura is designed to process
- Account and profile: name, age confirmation, email or provider identifier, photo, biography, interests, education, work, social links, settings, verification state, friends, blocks, and subscriptions.
- Events and user content: event details, invitations, attendance, groups, messages, reactions, polls, reviews, reports, photos, videos, memories, and selected audiences.
- Location: a selected city and, only after a separate runtime choice, precise or approximate device or live location for nearby discovery, maps, carpools, and permissioned sharing.
- Transactions: Google Play purchase token and entitlement status for digital Premium; event-payment records, receipts, refunds, and fraud signals only after a compliant production provider is enabled.
- Device and operations: app version, device and operating-system information, IP address, security events, crash and performance diagnostics, notification token, and service logs needed to protect and operate Aura.
- Safety and support: reports, blocked identifiers, moderation decisions, appeals, support correspondence, and evidence required to investigate abuse.
Do not place passwords, government identifiers, medical records, card numbers, or other unnecessary sensitive data in messages or events.
Purposes and sharing
Aura uses data to authenticate users; provide discovery, messaging, events, maps, planning, payments, subscriptions, and memories; apply privacy audiences; prevent fraud and abuse; provide support; comply with law; and maintain service reliability. Aura does not sell personal data or use it for cross-context behavioral advertising.
Data may be shared with the people and audiences a user selects, event or group participants, and contracted infrastructure, identity, map, media, email, support, moderation, security, payment, and app-store providers only as necessary for their services. Google processes Play purchases under Google’s terms. A final subprocessor list and applicable transfer safeguards are required before public launch.
Control, retention, and deletion
Users can control profile, friends, event-history, attendee, and live-location audiences; stop live sharing; block people; and report profiles, events, or conversations. Runtime permissions can be denied or revoked in Android settings without losing unrelated features.
Production data will be retained only for the feature, disclosed business record, safety, fraud, dispute, or legal purpose that requires it. Deleting a message may not delete copies already lawfully shared with other participants. Users can initiate account and associated-data deletion in Profile or at the public account deletion page. Narrow records may remain when law or safety requires them. Deletion does not cancel an app-store subscription.
Security, age, and contact
Aura uses HTTPS-only transport, least-privilege access, protected release signing, server-side authorization, and encrypted provider storage as production requirements. No system can guarantee absolute security. Aura is for adults age 18 and older, does not offer child profiles, and follows its child safety standards.
For access, correction, deletion, appeal, or privacy questions, contact support@parathoughtlabs.com. Identity verification may be required. Applicable users may also complain to their privacy regulator.