Privacy Policy

About this policy

Operator: VoidWorks Pte. Ltd. Privacy contact: [email protected]

This policy explains how Biaura handles information when you use its iOS app, website, purchases and related services. Information can be associated with an app, customer or device identifier even when you have not supplied your name or email address.

App preferences and reminders

Biaura stores saved sound presets, audio settings, onboarding preferences and reminder choices on your device to provide and personalize the app. Reminders are scheduled locally through iOS notifications. Selected onboarding goals, such as sleep or focus, are also included in the analytics described below; those analytics are separate from local preference storage.

Purchases and subscriptions

Apple and RevenueCat process subscription and purchase information so Biaura can provide premium access, restore purchases and manage entitlements. Information includes product identifiers, subscription/trial status, transaction identifiers, purchase or renewal times, and payment amount and currency. Apple handles payment details; Biaura's purchase code receives transaction and entitlement information, not your payment-card or bank-account details. Eligible purchase and trial events are also used to measure Biaura's advertising.

App activity and analytics

Biaura uses PostHog for events such as installation, opening and backgrounding the app, onboarding steps and selected goals, paywall views, purchase attempts and outcomes, and tracking-permission actions. Purchase-error codes can accompany failed-purchase events. PostHog events use the RevenueCat app-user identifier so app activity can be associated with subscription activity. We use this information to understand app use, improve features and understand the effectiveness of our acquisition campaigns.

Website analytics

The Biaura website uses PostHog to record page views and App Store link clicks, including the visited URL, language, article and link position, and campaign parameters present in the URL. The website configuration disables session recording and automatic interaction capture. PostHog may use browser storage and technical information to recognize visits. Browser settings can limit storage; the iOS tracking setting applies to the app, not this website.

Identifiers and technical context

Depending on the service and your permissions, information includes the RevenueCat app-user identifier, Meta's app-scoped anonymous identifier, Apple's vendor identifier, an advertising identifier when permitted, and IP information. Technical context sent to RevenueCat includes app/build version, operating system, device model, language/locale, timezone, screen dimensions and density, and rounded total and available disk space. The app also sends tracking-permission state and when it was observed. These fields support attribution, app-event measurement and investigation of integration problems. Third-party SDKs may also process technical and crash information under their own policies.

Advertising measurement

Biaura uses Meta's SDK and event services to measure which campaigns lead to app activity, trials and paid subscriptions, and to optimize Biaura campaigns. Events can include product and transaction identifiers, event times, purchase amount/currency, matching identifiers, device context and tracking-permission flags. Advertising measurement can involve Meta matching app events with information it holds from its services or other sources. A permitted advertising identifier provides an additional matching signal; an identifier described as “anonymous” does not mean the associated records cannot be linked to a device or customer.

Biaura's event service

When paid-event reporting is enabled, the app can send an Apple-signed transaction and a random installation identifier to Biaura's service hosted on DigitalOcean. The service verifies the transaction and keeps a record of whether the app or server is responsible for reporting that payment, to reduce duplicate events. It also receives paid-lifecycle events from RevenueCat, including renewals while the app is closed. Retained records include transaction/product identifiers, payment amount/currency/time, a hash of the installation identifier when applicable, necessary matching and consent context, and delivery status. The service does not store the signed transaction itself or complete incoming webhook bodies. Its operational logs use fixed result codes rather than full customer/event payloads.

Support

If you contact us by email, your message and contact information are available to us to handle your request. Please avoid including payment-card details or other unnecessary sensitive information.

Services receiving information

Apple provides App Store purchases and platform services. RevenueCat processes subscription information and the identifiers/context described above. PostHog processes app analytics. Meta receives app and conversion events for advertising measurement. DigitalOcean hosts Biaura's event service and database. Information is shared with these services for those functions; it is not accurate to describe all of this sharing as anonymized. Their handling of information also depends on their applicable terms, policies and the account settings selected by Biaura.

The current event server is in Singapore, and Biaura's PostHog configuration uses its US service endpoint. Other providers may process information in additional countries. Contact us for questions about the services involved in your information.

Your choices

You can change Biaura's tracking permission in iOS Settings → Privacy & Security → Tracking. The app reads the current permission and refreshes its reported consent when you return to it. The app requests advertising-identifier collection only when authorized and reports the permission state to its measurement services. Declining tracking does not remove premium access or stop purchase processing, and it does not turn off all app analytics or every app-event transmission. A server handling a renewal while the app is closed has the permission state most recently reported by the app.

You can control reminders in Biaura and iOS notification settings, manage subscriptions through Apple, and edit or remove saved presets within the app. Uninstalling Biaura does not itself cancel an Apple subscription or delete information already received by service providers. There is currently no general in-app analytics opt-out switch.

For privacy questions or requests to access, correct or delete information, contact [email protected]. We may need information to locate the relevant records and verify a request. What can be provided or removed depends on the records we can identify, the services holding them and applicable requirements. Apple and other providers may require requests through their own processes.

Storage, security and retention

Biaura's event service uses HTTPS, restricted server/database access and database backups. These measures do not eliminate every risk. Its database records and backups support event delivery, investigation and prevention of duplicate reporting. The current implementation has no automatic expiry of those records or backups; the operator must manage their retention. The service's event-delivery age limits are not deletion deadlines. Retention of RevenueCat, PostHog, Meta, Apple and support records also depends on those systems and their configured policies. Contact us for retention or deletion questions; this policy does not promise that every copy can be erased immediately.

Policy changes and contact

We may update this policy as Biaura's practices change. The published policy will show its effective date. Contact [email protected] about this policy or your information.