Your life is personal. NURA keeps you in control.

1. Information you provide

Depending on the features you use, NURA may store account and profile information, assistant preferences, memories you choose to save, documents and attachments, health organization records, vehicle records, travel records, expenses and budgets, planner items, home information, family information, pet records, shopping information and conversations with NURA.

2. Authentication and account data

Authentication is provided through Supabase Auth. The NURA backend verifies authenticated sessions before reading or changing user records. The application maintains a NURA profile linked to the authenticated Supabase user so product-specific preferences and life records can be stored separately from authentication credentials.

3. Files and documents

Files you choose to upload or capture are sent to NURA's backend and stored in a private Supabase Storage bucket. File metadata and structured document information are stored in the user's NURA database records. NURA can issue short-lived signed access URLs when an authenticated feature needs to display a private file.

4. Camera, microphone, calendar, contacts, location and notifications

NURA requests operating-system access only when you use or enable a related feature. You can deny or revoke operating-system permissions through your device settings. NURA also stores its own permission preferences so the assistant can respect whether a capability is denied, should ask first, or is allowed.

5. AI processing

NURA can operate with deterministic record retrieval even when no external AI provider is configured. If the server operator configures the optional AI provider, text, voice or document content required for an AI request may be sent from the NURA backend to that configured provider to generate the requested response, transcription or document analysis. NURA does not fabricate provider results when the provider is unavailable.

6. Connected services

Device calendar and contacts integrations are optional and require the corresponding device permission. Cloud providers such as Google, Apple or Outlook require separate provider credentials and authorization before they can be connected. NURA does not display a service as connected unless a connection record has actually been established.

7. Notifications and device registration

If you enable notifications, NURA may register the device and an Expo push token so reminders and attention items can be delivered. Notification permission can be disabled in NURA and in your device settings.

8. Billing, subscriptions and AI usage records

If you use a paid plan or purchase additional Nura Tokens, NURA stores billing identifiers, plan and subscription status, transaction references, token balances and AI usage accounting needed to provide the service and prevent duplicate credits. Website card details are entered into the payment provider's checkout and are not stored by NURA. NURA records model usage totals and estimated provider cost for account balances and administrative usage reporting.

9. Security and access controls

NURA uses authenticated API access, user-scoped database queries, private object storage, database row-level security, application-level authorization, rate limiting for API operations, audit records for important changes and secure transport when deployed over HTTPS. No system can guarantee absolute security, so keep your device and account credentials protected.

10. Retention, deletion and account removal

Records remain associated with your account until they are deleted or the account is deleted, subject to infrastructure backups and legal obligations that may apply. The in-app Account screen can initiate permanent account deletion. The public account-deletion page provides an additional deletion path. The deletion flow removes NURA database data, private NURA Storage objects and the associated Supabase Auth user through the server-side deletion process.

11. Advertising and sale of private records

NURA is not designed to sell private life records to advertisers or data brokers and does not use those records to build third-party cross-app advertising profiles.

12. Children

NURA is not intended to be used in a way that violates applicable age or parental-consent laws. Store age ratings and any regional eligibility requirements should be configured to match the final release and connected services.

13. Changes and privacy requests

This policy should be updated when NURA's material data flows change. Users can manage data directly in the app and can use the current support or privacy contact published with NURA's official website and store listing for additional privacy requests.