Bivid Aura

Privacy Policy

Effective date: September 16, 2026 · Policy version: 2026-09-16

Pre-publication draft: the owner must confirm the operator identity, privacy inbox, and final hosting details before this page is published or shipped.

1. Scope and operator

This Privacy Policy describes how the Bivid Aura iPhone application and this policy page handle information. Bivid Aura is operated by the developer identified in the app's App Store listing (referred to here as “we,” “us,” or “the developer”).

The policy reflects the current application build. Features described in product concepts but not implemented in the build are not treated as active data collection.

2. Information handled by the app

Bivid Aura may handle the following information when you choose to enter or create it:

  • Profile preference: an optional nickname.
  • Planning details: location names, dates, viewing windows, reminder choices, and notes.
  • Journal details: a sighting location, date, rating, notes, and a saved conditions summary.
  • App preferences: onboarding completion, default location text, measurement units, alert settings, and selected thresholds.
  • Map interactions: viewing predefined aurora spots and moving around the Apple map shown in the app.

The current build also contains sample forecast, location, plan, and journal content. Sample content is bundled with or generated by the app and is not information collected from you.

3. Why this information is used

Information you provide is used to display your preferences, create viewing plans, maintain the journal during app use, personalize labels, and show the aurora-planning experience you request. It is not used for advertising, cross-app tracking, or sale.

4. Storage, accounts, and retention

The current build does not require an account and has no developer-operated cloud sync. The nickname and the fact that onboarding was completed are stored in iOS app storage on your device. Plans, sightings, alert choices, default-location text, and unit preferences are currently held only by the running app and may be reset when the app is relaunched.

iOS device backups may include app data according to your Apple and device backup settings. We do not control Apple's backup retention. Deleting the app normally removes its local container from the device, subject to any backups managed by you or Apple.

5. Location, notifications, and photos

The current build does not request precise device location, notification authorization, camera access, or photo library access. Location selection is manual, alert controls do not register for system push notifications, and the journal's “Add Photo” control does not currently select, capture, upload, or store a photo.

If a later version activates one of these features, the app must request the relevant iOS permission at the time the feature is used, and this policy must be updated to explain the resulting processing before release.

6. Network access and third-party services

The current forecast service uses local mock data and does not contact a forecast server. No third-party analytics, advertising, crash-reporting, social login, payment, or AI SDK is included in the current app target.

The map screen uses Apple's MapKit framework. Apple may provide map content and process technical requests under Apple's own privacy terms. Bivid Aura supplies predefined spot coordinates to the map and does not currently obtain your device's location for that screen.

7. This policy page

This HTML file contains no cookies, trackers, analytics scripts, external fonts, or required third-party resources. When it is viewed from a hosted website, the hosting or network provider may still receive standard request data, such as an IP address, date and time, user-agent information, and requested URL, according to that provider's logs and privacy terms. Hosting details and retention depend on the final publishing provider.

8. Sharing and sale

The current app does not send your profile, plans, journal entries, or preferences to the developer and does not sell them. Map content and platform services may involve Apple as described above. We do not disclose app content to advertisers or data brokers because those integrations are not present in the current build.

9. Your controls and deletion

You can edit the nickname and preferences shown in the app. “Delete Journal Data” removes the in-memory sightings shown in the current session. “Clear All Data” removes in-memory plans and sightings, resets alert choices and the nickname, and removes the saved nickname. The current implementation does not clear the saved onboarding-completion flag. Deleting the app removes the local app container from the device, subject to device backups.

Because the current build does not upload this app content to a developer-operated account or server, there is no corresponding server account to delete or data export to request from us.

10. Children's privacy

Bivid Aura is a general-audience aurora planning tool and does not include an age gate or a child account system. The current build does not knowingly request account registration or upload journal content to the developer. A parent or guardian with a privacy concern may contact us using the address below.

11. Security

Bivid Aura relies on iOS app sandboxing and device security for locally stored information. No method of storage is completely risk-free, so you should use an iPhone passcode and keep iOS updated. Avoid entering sensitive information in free-text notes that you do not need for aurora planning.

12. Changes to this policy

We may update this policy when the app's features or data practices change. The effective date and policy version at the top identify this edition. A changed date on a hosted page does not by itself mean that an installed app has recorded a new consent.

13. Contact

For privacy questions about Bivid Aura, contact the developer at [email protected].

Please do not include passwords, precise location history, photographs, or other sensitive material in your message.

Selecting “Agree & Continue” acknowledges this policy and asks the app to continue. The native Bivid Aura app—not this web page—validates the policy version and stores any completion state.