AsiaraPre-beta

Controlled-beta draft

Asiara Privacy Policy draft

This plain-language draft describes the information Asiara expects to use for a United States controlled beta. It is not a final or currently effective public policy.

Draft date: July 17, 2026Status: founder and qualified legal/privacy review required
This policy is still under review.

Hosting, retention periods, verified deletion and export procedures, provider terms, governing requirements, and the exact public operator wording must be completed before external tester launch.

1. Who operates Asiara

Asiara is currently operated by an individual founder under the public Asiara brand. The exact public founder alias is still pending. The founder's legal identity is used privately where providers, contracts, tax, or law require it.

Privacy questions and data requests can be sent privately to privacy@asiara.app. That incoming route is live and tested. A detailed request-verification and response procedure is still being finalized.

2. Scope and eligibility

The initial controlled beta is intended for eligible people age 15 or older in the United States. Asiara is not claiming international beta availability. Additional age-assurance, parental-consent, provider, and legal requirements still need qualified review before invitations open.

3. Information Asiara uses

Account, authentication, and access

  • Email address, authentication identity, OTP delivery information, session state, and limited security events needed for email OTP sign-in.
  • Minimal profile information, account status, beta invite or grant state, and Terms acceptance when implemented for launch.
  • Temporary device or installation binding information used to protect account transitions and optional push ownership.

Product state

  • Account-backed follows, Saved News, Calendar stars, and relationship-aware Following read or unread state.
  • Optional display-name or profile settings that are actually supported by the beta.
  • Some Library, notes, ratings, progress, onboarding, interests, groups, and general News read state remain scoped to the signed-in account on that device rather than synchronized to the server.

Push notifications

  • Optional notification preference, installation ownership, Expo push token, platform/build information, and delivery or receipt records needed to send and troubleshoot permitted notifications.
  • The token and private installation identifiers are not shown publicly.

Diagnostics, security, and administration

  • Limited app version, platform, permission state, privacy-restricted Sentry crash or error diagnostics when Sentry is enabled, security events, and protected admin audit events.
  • Product analytics are not currently implemented.

Messages sent to Asiara

  • Information a person chooses to include in support, beta, correction, privacy, or security email.
  • People should not send passwords, OTPs, tokens, private keys, payment details, or unrelated personal information.

4. This website

This local website shell does not include analytics, advertising pixels, cookies, forms, external fonts, embedded widgets, or third-party scripts. Contact links open the visitor's email app. A static hosting provider has not been selected, so any standard hosting logs, data location, retention, or security details must be added before publication.

5. Why information is used

  • Authenticate a person and restore a valid session.
  • Confirm and manage controlled beta access.
  • Provide Following, saves, Calendar state, unread state, and requested app features.
  • Register and deliver optional phone notifications.
  • Protect accounts, enforce access and safety controls, prevent abuse, and investigate incidents.
  • Diagnose technical problems and operate the beta.
  • Respond to support, correction, privacy, and security requests.

The appropriate legal bases for these uses require qualified review before the policy becomes effective.

6. Service providers

Depending on the feature and approved platform, Asiara may use:

  • Supabase for authentication, database, access controls, and backend functions.
  • Resend for OTP and transactional email delivery and the separately configured Support sending identity.
  • Cloudflare for domain DNS and incoming functional email routing.
  • Sentry for privacy-restricted crash and error reporting when enabled.
  • Expo/EAS and the Expo Push Service for app builds and optional notification delivery.
  • Apple and Google for platform distribution and notification delivery where applicable.

The final policy must identify the selected website host, each active provider's role, relevant data location and transfer information, retention, safeguards, and required policy links. Ko-fi and supporter data are not part of the initial controlled beta.

7. Local device storage

Some private state is stored only on the device and scoped to the active signed-in account. It can survive an app restart or later sign-in by the same account on that device, but it does not follow the account to another device and is lost if app data is cleared or the app is reinstalled.

Signing out clears rendered private state so another account should not see it. Same-account local data may remain stored on the device for the same account. Local-only state is not part of a server export.

8. Push notifications

Phone push is optional. A person can deny or revoke operating-system permission and turn the account preference off in Asiara. Delivery can fail or be delayed by the operating system, network, Expo, Apple, Google, or device settings. Disabling push does not remove unread followed content from Home > Following.

9. Security and audit records

Asiara uses account isolation, server-side access checks, role protections, beta controls, protected audit records, and incident-containment measures. Some security and audit records may need to be retained after account closure where lawful and necessary. The final rule and retention period require qualified review.

Private security controls, keys, thresholds, infrastructure, and incident procedures are not disclosed publicly.

10. Retention

Final category-specific retention periods are not decided. Before launch, Asiara must document or approve retention criteria for active and closed accounts, beta grants, push installations and deliveries, support and correction messages, Sentry events, security and audit logs, backups, and local device state.

Asiara will not claim that information is deleted immediately or kept for an exact period until the complete account, provider, backup, audit, and local-device path is verified.

11. Choices and requests

Depending on the feature, a person can sign out, change follows, saves, stars, or read state, disable push, change operating-system notification permission, avoid optional submissions, and choose whether to participate in Discord.

Requests to access, correct, delete, or export personal information can be sent to privacy@asiara.app. Asiara does not yet claim a complete self-service deletion or export tool. A reliable identity-verification and manual response procedure must be tested before launch, including lawful security or audit exceptions and local-device instructions.

Opening an original Source or another external link leaves Asiara. The destination may receive normal browser or network information and applies its own privacy and terms. A link does not mean Asiara operates or controls the destination.

13. Policy updates

The final policy needs an effective date, version history, method for communicating material changes, and a decision about when renewed agreement is required. This draft may change substantially before it is published.

14. Contact

For a private privacy or data question, email privacy@asiara.app. For a suspected security issue, use Security Reporting or email security@asiara.app.