Privacy Policy

This Privacy Policy explains how CONSCIOUS AUDIO ("we," "our," "us") collects, uses, and protects your personal data when you access or use https://consciousaudio.com.au, the Conscious Audio installer (our desktop app), the HeartSync plugin, and the HeartSync Mobile app. By using our site or software, you consent to the practices described in this policy.

Optional HeartSync Mobile analytics require a separate, explicit choice. Using the mobile app does not turn them on. The mobile-specific terms in section 2.5 apply to that telemetry, including where they differ from the general statements elsewhere in this policy.

2.1 Voluntarily Provided Information

• Name and email address (via contact form or checkout)
• Message content (via contact form)
• Spark submissions (if submitted to River of Spark)

2.2 Automatically Collected Information

• IP address, browser type, and access times (via server logs)
• Usage and event data from analytics/advertising tools (for example: page views, button clicks, and HeartSync download-related events)
• Device metadata during checkout (collected by Stripe)

2.3 Conscious Audio Installer

• Account (optional): your email address and account ID, if you create an account or sign in.
• Installation ID: a random identifier created the first time the installer runs and stored on your computer. It is not derived from your hardware, and it changes if you remove the installer's data or reinstall.
• Usage analytics (on by default; you can turn it off when you first set up the installer or at any time in Settings): plugin installs and updates, sign-ins and sign-outs, and other activity in the app.
• Essential diagnostics: if you have an account, a small set of events is sent even when usage analytics is off, so we can keep updates working: app start and close, a signal every minute while the app is open (which shows how long it stays open), app and plugin update results, install errors, plugin health problems, and a one-time summary of your system (operating system and version, processor type, app version).

You can use the installer without an account. In that case, if usage analytics is on, the installer creates an anonymous profile so we can count usage without knowing who you are. If you later create an account or sign in on the same computer, that earlier anonymous activity is linked to your account so it forms one history. If you use the installer without an account and usage analytics is off, no analytics are sent.

2.4 HeartSync Plugin

The HeartSync plugin sends usage data so we can improve stability and compatibility: plugin version and format, the name and version of the music software it runs in, operating system and version, processor type, sample rate and buffer size, session length, and counts of features used (for example, heart rate monitor scans and connections). It does not send your heart rate readings or your audio.

These records carry a device identifier that the plugin calculates from details of your computer (such as its name and network hardware address) and stores only as a hashed value. Plugin analytics has its own switch in the installer's Settings, separate from installer analytics: turning one off does not turn off the other.

2.5 HeartSync Mobile (iPhone and Apple Watch)

HeartSync Mobile reads your heart rate from Apple Health, the HeartSync Apple Watch app or a Bluetooth heart rate monitor, with your permission, and sends it straight to HeartSync on your own computer over Bluetooth or your local network. Your heart rate readings are not sent to us or stored on our servers.

Optional telemetry uploads from older mobile versions were stopped on October 18, 2026, and those versions cannot upload optional telemetry. The consent controls described below are in HeartSync Mobile 1.3.1, released on October 24, 2026; update to 1.3.1 or later to use them. This change applies to HeartSync Mobile only; it does not change the installer or plugin analytics settings.

In HeartSync Mobile 1.3.1 and later, optional usage analytics are off until you choose Allow. You can change your choice using the Settings gear → Optional analytics. Heart-rate streaming continues to work when analytics is off. The phone's choice also controls optional watch analytics. An offline watch receives changes when it reconnects; the phone rejects messages from an older consent setting.

If enabled, this telemetry contains coarse app, connection, streaming and failure events, app/watch versions, platform, event times, session duration and a random installation label. Event time comes from the phone or watch clock; server receipt time is recorded separately. The label is not a hardware identifier or an account. It links events from the same installation and should not be treated as anonymous data or a count of people. This telemetry does not collect heart-rate readings, sensor names, raw sample timing or counts, account/email data, or free-form error text. The local heart-rate connection to your computer remains separate.

We check Apple-signed app authenticity and distribution evidence to distinguish released and test apps where possible. Verification receipts and their device/account identifiers are not retained. Traffic without verified classification remains unclassified. The mobile telemetry database is hosted by Supabase in Tokyo, Japan. Operational reporting uses private aggregates without installation or device identifiers. Optional mobile telemetry is not used for advertising tracking or the website's advertising measurement.

Turning analytics off stops new local events, clears unsent queues and retries the server preference when online. It does not itself erase earlier received events or undo a request already committed by the server. Offline queues have a fixed capacity and expire after 90 days; delivery is not guaranteed if the app is suspended, removed or cannot save data.

New raw operational events are retained for 90 days from server receipt, then contribute only to aggregates without device or installation identifiers, retained within a 13-month receipt-date window. Retention cleanup runs hourly and uses UTC dates for aggregates, so removal follows the applicable date boundary and normal scheduling delay. Existing history collected before the October 18, 2026 consent cutover remains a legacy exception until a verified deletion request or a later announced policy change. That history can contain the sample counts and error text sent by earlier versions; it is not retrospectively treated as newly consented data.

Delete this installation's analytics stops collection and requests removal of attributable newer records. Requests retry when online; keep the app installed until acknowledged, or contact support if that is not possible. We complete requests within 30 days after receiving them. Encrypted backup copies have a 30-day retention target, subject to the local cleanup limitations below. We retain one-way installation and capability hashes as deletion markers for 120 days to prevent old offline queues or restored backups from recreating deleted records. A marker awaiting deletion reconciliation is retained until that work succeeds. Restore procedures reapply the current deletion ledger before collection resumes. Aggregates already made anonymous cannot be matched back to an installation.

After acknowledged deletion, a future opt-in creates a new installation label. Removing app data, reinstalling or moving to another device can also reset the label and choice. Earlier versions have no secure self-service ownership capability. Contact support@consciousaudio.com.au for assistance with that history or access, correction and deletion requests; we require possession of the original installation and independent existing corroboration before acting on legacy requests. Uncertain cases are escalated to the owner. Extra support verification attachments are deleted within 30 days after case closure; minimal audit outcomes are kept for up to 120 days after closure. These periods are separate from telemetry replay-marker retention.

Supabase also processes service request metadata, which may include IP address, user agent, request time/path and response status, for service operation, security and troubleshooting. These logs are separate from optional telemetry events and are not erased by the in-app analytics deletion control. Provider internal and security-copy retention limits have not been confirmed; we do not promise that deleting analytics erases all provider logs. We do not use these logs for advertising.

Mobile telemetry backups currently reside encrypted on the owner's Mac. Copies older than 30 days are removed when a backup run succeeds. The job depends on that Mac, network, Docker and Keychain access being available; interruptions can delay removal. An independent offsite backup and external failure alerts are not yet configured. These arrangements apply to mobile telemetry only.

We use your information only to:

• Respond to inquiries and support requests
• Deliver purchased digital products
• Process transactions through Stripe
• Re-send download links if requested
• Display Spark submissions (if submitted)
• Improve site accessibility and performance
• Measure site usage and ad campaign performance with TikTok Pixel and Metricool
• Keep installer and plugin updates working, and understand how our software is used so we can improve it
• Detect fraud and troubleshoot issues

If you use the Spark feature:

• Responses you "burn" are deleted immediately and not stored.
• If you submit a Spark creation to the River of Spark, it may be displayed publicly and archived for future use.
• Submissions are anonymous and not linked to personal data.

We use:

• LocalStorage to remember your site preferences (contrast, font size, reduced motion)
• Session cookies for cart functionality (if applicable)
• Stripe cookies during checkout for payment and fraud detection (see Stripe's privacy policy)
• TikTok Pixel in production to record page views and selected conversion events (including HeartSync view/click/download events)
• Metricool tracker in production for traffic and campaign analytics

These tools receive technical/browser context (such as page URL, referrer, device/browser information, and event metadata). Based on our current implementation, HeartSync conversion events include labels such as content ID/name, platform, currency, and value; they are not populated with contact-form message content or full payment card details.

Your choices

• Browser settings can block or delete cookies and similar trackers.
• TikTok privacy and cookie information: Privacy Policy and Cookies Policy.
• Metricool privacy and cookie information: Privacy Policy and Cookies Policy.

At this time, we do not provide an on-site cookie banner or granular tracker toggles.

We use Stripe Payments Australia Pty Ltd to process transactions.

We collect and store:

• Customer email address
• Product purchased and purchase timestamp
• Download link (secure and time-limited)
• Stripe session ID for purchase verification

We do NOT collect or store:

• Card numbers or CVV
• Full billing addresses
• Phone numbers

Stripe handles all financial data and is PCI DSS Level 1 certified. View their Privacy Policy.

We use trusted third-party services:

• Stripe for secure payments
• Supabase to store non-sensitive purchase metadata, installer accounts, and installer and plugin analytics
• Cloudflare R2 to deliver downloads (signed URLs)
• TikTok for pixel-based analytics and advertising conversion measurement
• Metricool for analytics reporting and campaign measurement
• Vercel for hosting (with standard server logs)
• Public APIs (e.g. Art Institute of Chicago, Getty) for River of Resonance

We do not control third-party privacy policies linked through our platform.

• Purchase records: retained indefinitely (for license access)
• Spark submissions (if submitted): retained for display/archive
• Contact form emails: stored in our email inbox only
• Failed transactions: removed after 90 days
• Download logs: stored for 12 months (security/audit purposes)
• Installer and plugin analytics: kept until you ask us to delete them; deleting your installer account removes its link to your analytics
• HeartSync Mobile telemetry: the choice, retention, legacy-history exception, deletion and backup terms in section 2.5 apply separately.

Under the Australian Privacy Act 1988, you have the right to:

• Access your personal data
• Correct or delete your information
• Request re-sending of your download link
• Withdraw consent (where applicable), including turning off installer analytics or HeartSync plugin analytics in the installer's Settings at any time
• For HeartSync Mobile, use the separate choice and deletion controls described in section 2.5 (HeartSync Mobile 1.3.1 or later), or contact support for earlier history.

To exercise your rights, email: support@consciousaudio.com.au

We comply with international privacy laws:

GDPR (EU Users):

• Lawful basis: contract performance + legitimate interest
• Right to access, correct, delete, or transfer your data
• Data transfers use Standard Contractual Clauses (via Stripe)

The general lawful-basis description above does not replace the explicit opt-in required for optional HeartSync Mobile analytics in section 2.5.

CCPA (California Users):

• Right to know what personal data is collected
• Right to request deletion
• We do NOT sell personal data
• No discrimination for exercising rights

Our site is intended for general audiences. We do not knowingly collect personal data from children under 13.

We may update this Privacy Policy periodically. The latest version will be posted here. Continued use of the site indicates acceptance of the changes.

For any privacy-related inquiries: