How HEARTz Handles Your Data

1. Local Audio Processing

All audio generation, synthesis (pure sine/triangle waves, binaural sound, isochronic tones, 432 Hz retuning), and file decoding happen entirely within your web browser using client-side Web Audio API and WebAssembly.

• Audio files remain on your device: When you select or retune a music track, it is decoded in your local device RAM. We do not store or transmit your audio files to our servers.
• No server-side audio analysis: The Converter analyzes your selected file locally to prepare its preview and export; HEARTz does not send that file to a server for analysis.

2. Information We Collect & Authentication

An account is required to enter the application. Firebase Authentication manages sign-in; cloud synchronization of your saved settings is not active yet.

• Email address and account ID: Firebase uses these to identify your account. HEARTz uses the account ID to keep local settings separate for different signed-in users on the same browser.
• Sign-in method: You can use Google or email and password. Firebase handles authentication and stores the sign-in session in browser storage on this device; HEARTz does not receive your plain-text password.

3. Local Storage (IndexedDB & LocalStorage)

Saved recipes, library entries and interface preferences use this browser's IndexedDB and localStorage. They do not automatically appear on another device. You can export your saved settings from the app; clearing browser data can remove local copies.

4. Cookies & Tracking Technologies

The application uses browser storage for its sign-in session and local settings. It does not include advertising trackers:

• Sign-in storage: Firebase Authentication persists the session on this device so you can return without signing in again. Signing out clears the sign-in session; saved local settings remain until you remove them.
• Site delivery: Cloudflare serves HEARTz pages and receives the network requests needed to load them.
• No Advertising Cookies: We do not load Facebook Pixels, Google AdSense, behavioral marketing beacons, or cross-site tracking scripts.

5. Third-Party Infrastructure Providers

These services support the current website and app:

• Firebase Authentication: Manages HEARTz accounts and sign-in. HEARTz does not currently sync your saved recipes or upload your audio to a Firebase database.
• Cloudflare: Provides global DNS management, SSL/TLS certificate termination, and edge caching for static assets.
• Google Fonts: Provides typography stylesheets for consistent display across operating systems.
• PostHog (EU Cloud): Provides interface usage analytics hosted in the European Union (Frankfurt, Germany) to measure page views, page leaves, and UI interactions using browser localStorage persistence without advertising trackers.
• Google Forms: Opens only if you choose “Share feedback”. Responses you submit there are handled by Google Forms.

6. Your Rights & Data Deletion

To ask about the personal data connected with your HEARTz account, use the contact address below. Available rights depend on applicable law.

• Access or correction: Contact us if you want to see or correct account information.
• Deletion: To request deletion of your account, email contact@aitificer.com with the subject “HEARTz account deletion”. Local browser data can also be removed from your browser.

7. Contact & Controller Information

If you have questions, feedback, or data privacy inquiries regarding HEARTz, please contact the development and support team: