Private by default
Source tracks, generated stems, and recordings are stored as private objects.
AudioEdge Trust Center
Your music should never travel through a black box.
We publish who operates AudioEdge, where your audio goes, why each service receives it, and how you can remove it. These are verified product controls—not vague promises.
Last reviewed July 31, 2026
We update this page when our data flow, vendors, or retention practices change.
Accountability
A real product. A named legal operator.
Chiller Tech Support LLC
AudioEdge is a product operated by Chiller Tech Support LLC, a United States company. The company is responsible for the service, customer support, privacy commitments, and vendor relationships described here.
Audio data flow
Exactly where an uploaded track goes
Processing requires limited disclosure to infrastructure providers. We minimize that access by object, purpose, and time instead of treating a secret URL as permanent security.
- 01
Your browser
Your audio uploads directly over encrypted HTTPS. Large file bytes do not pass through an AudioEdge server function.
- 02
Private storage
The source file is stored in a private Vercel Blob namespace scoped to your account.
- 03
Processing window
Replicate receives read-only access to that one source object through a signed URL that expires after 30 minutes.
- 04
Private results
Completed stems are copied into private AudioEdge storage. Temporary processor URLs are not saved as your library.
- 05
Controlled playback
Audio is delivered through AudioEdge routes that verify account ownership or a sharing token you intentionally enabled.
Verified controls
What protects your account and audio
We avoid claims like “100% secure.” Security is a maintained system of controls, monitoring, access boundaries, and honest incident communication.
No password access
Passwords are hashed and sessions are managed by Better Auth. AudioEdge staff cannot read your password.
Scoped database access
Every customer-data query is tied to the authenticated user identifier.
Verified processing callbacks
Processor webhooks are signature-checked and handled idempotently before results are accepted.
Customer-controlled retention
Files remain available until you delete your account. Account deletion purges stored audio and application records.
Payment separation
Payment credentials are handled by Square. AudioEdge stores transaction references, not full card numbers.
Retention and deletion
Uploaded tracks, stems, and saved recordings remain available until you delete your account. The account center’s Total Information Purge removes account data, tracks, stems, sessions, and associated stored media. Required financial records may be retained where law requires.
Sharing is deliberate
Audio is private by default. If you enable a jam-session share link, possession of that unguessable link permits playback for that shared session. You can disable sharing, and account deletion removes the underlying media.
Subprocessors
Services that help operate AudioEdge
We list operational vendors by purpose so customers can understand where limited data may be processed.
VercelApplication hosting and private object storage
NeonEncrypted PostgreSQL database hosting
ReplicateTime-limited audio stem processing
SquarePayment processing
ResendTransactional account email
UpstashAbuse prevention and rate limiting
How we verified this
Claims we tested, not just wrote
Transparency is meaningless if nobody checks it. Before publishing this page we audited the live system and corrected what did not match.
Anonymous access is refused
We requested every stored audio object without credentials. All returned HTTP 403.
Delivery is ownership-checked
Playback runs through routes that confirm the signed-in owner or an intentionally enabled share token.
Processor access is time-boxed
Replicate receives a signed, single-object, read-only URL that expires after 30 minutes.
Questions about your data?
Ask us directly. Accountability includes being reachable.