Know what stays.
Choose what’s measured.

Your creative files stay here.

My Studio uses this browser’s local storage and IndexedDB for favorites, demo selections, project metadata, session drafts, audio files, and notes. Data is not synced across devices or sent to Helluva. Clearing site data can remove it. Keep original files and backups.

Microphone access is your choice.

The demo booth asks for microphone permission only after you press Record. The saved take contains microphone audio, not a completed mix. It remains local unless you explicitly download and share it yourself.

Optional analytics.

Helluva’s separate Google Analytics 4 property is connected to this website. It waits for your analytics consent before loading Google’s tag. Rejecting analytics does not prevent the storefront or local studio from working.

With consent, the implementation can measure public-page visits, selected public calls to action, official-channel clicks, and labeled demo listening events. It excludes the private studio and does not send project titles, names, email addresses, filenames, creative briefs, notes, or recordings. Marketing campaign values are restricted to a small approved list rather than collecting arbitrary query strings.

Demo activity is not reported as paid orders or confirmed bookings. Advertising storage and personalization are disabled in this implementation. Analytics preferences can be changed using the control below; an enabled global privacy control prevents analytics loading.

External services.

Social buttons open Instagram or YouTube only when you follow a link. This build does not embed an automatically loading social feed. Web fonts are requested from Google Fonts; the hosting provider and font service may process ordinary connection information under their own policies.

Google Analytics processes consented measurement data under the Helluva property’s configured account settings. The production operator should review data retention, contact information, applicable privacy disclosures, and agreements before launch.

No payment details are collected here.

Payments, e-signatures, customer cloud accounts, confirmed bookings, and publishing are not connected in this build. The website does not request card or bank information. A future integration must update these disclosures before collecting new categories of data.

Contact.

Use the official channels for general contact. Do not send sensitive financial, identity, or private project information through public comments.

Submitted studio requests and private uploads

The Contact form is different from the local My Studio workspace. When you submit it, your name, email, request type, timezone, preferred times and message are stored in this Helluva Netlify project. Mixing-request audio uploads are stored privately in Netlify Blobs. Authorized studio operators can access them through their authenticated hosting account or the protected owner inbox.

Request access uses a secret key, stored as a hash on the server. Your browser holds the key only in session storage for the tab. Anyone you share it with can access that request. Filenames and file content are never sent to analytics. Uploads are checked for size, extension and audio-file signature; this is not a virus-scan guarantee. No data is sold or used to train a music model by this implementation.

There is no automatic retention or deletion schedule configured yet. Use the official contact channels with your request reference for access or deletion requests; never post your access key publicly. Hosting processes normal connection information. No confirmation email or newsletter subscription is created automatically.

Email updates and your choices

Signing up is optional and separate from submitting a studio request. We store the email address you submit, your chosen interest, the page path, the signup time and the exact consent version in this Helluva project’s private Netlify Blobs store. We do not subscribe visitors simply because they browse, fill in an unfinished form, upload stems or make a service request without selecting the separate email option.

Email sending is being connected. Signups are saved as pending; no newsletter delivery is claimed. When the sender is configured, a confirmation email asks you to verify your address before marketing begins. This implementation uses Resend for delivery once the studio’s own sender is verified. No RingFunnel mailing list or merchant account is used.

Every marketing email includes an unsubscribe link. Unsubscribes, delivery complaints and hard-bounce notifications suppress later marketing. Service or order messages are separate. Confirmation and unsubscribe links use signed tokens; opening the link shows a choice rather than silently changing your subscription. Email providers may submit the standard one-click unsubscribe request directly.

Marketing is limited to at most one email per 24 hours and three in seven days. Automatic marketing stops after 90 days without a recorded subscription confirmation or qualifying activity. A visitor invitation dismissal is remembered on this device for seven days. Names, addresses, email contents, signup field values and private tokens are not sent to Google Analytics by this layer.

Authorized studio operators can view/export contacts through the protected owner area. Suppression records are retained to honor opt-outs; there is no automatic deletion policy for the stored contact records yet. For access or deletion requests, use the official studio contact channels. No purchase, booking, discount or guaranteed inventory is created by an email signup.