Practical customer-facing answers about using TrustedAudio, public verification, leak investigation, plans, branding, security, and delivery workflows.
TrustedAudio services are now free. See Plans and Pricing.
Yes. The Free plan is available without payment and without a trial expiry. It includes one workspace user, 1 GB of source storage, recipient-level watermarking on every delivery, up to 25 recipients per delivery, up to 250 recipient-deliveries per rolling 30-day window, up to 5 tracks registered for public verification, basic analytics, and unlimited leak investigations subject to abuse-control rate limits.
Create an account using email/password or social login through Google, Microsoft, or Apple. Confirm your email and your workspace is ready for uploads and deliveries.
No. Recipients receive a delivery link by email. That link opens a controlled delivery page where they can stream, download if allowed, and leave feedback.
A workspace is the container for one customer's tracks, albums, contacts, deliveries, templates, branding, and team members. Every plan applies to a single workspace.
| Plan | Monthly | Annual | Audience |
|---|---|---|---|
| Free | $0 | $0 | Testing and occasional protected sharing |
| Creator | $9 | $86 | Solo artists, producers, composers |
| Pro | $19 | $182 | Active artists and small promo operators |
| Team | $49 | $470 | Labels, agencies, small teams |
| Business | $129 | $1,238 | High-volume teams and API workflows |
| Enterprise | Custom | Custom | Contractual SLA and custom integration |
No. TrustedAudio plans are inclusive. There are no paid add-ons, no a la carte features, and no overage fees. Plan limits are enforced as hard caps.
Upgrades take effect immediately. Downgrades take effect at the end of the current billing period. On cancellation, data goes through a 30-day read-only period and then archive and purge rules, while public verification registrations and receipts remain available.
Recipient-delivery caps and storage caps are hard limits. New actions are blocked until older usage falls out of the rolling window, you delete source files to free space, or you upgrade.
Yes. Recipient-level watermarking is included in every plan, including Free. There is no separate watermarking fee or add-on.
TrustedAudio embeds a unique identifier into each recipient's copy of a file. That identifier maps internally to a specific recipient and delivery so a leaked copy can later be traced back by the workspace owner.
Yes. Watermark mode is set per track inside each delivery. The default is recipient-level watermarking, but any eligible user preparing a delivery may switch an individual track to No watermark.
TrustedAudio offers two fidelity profiles. Standard is the default and balances inaudibility and robustness. Studio minimizes audio impact for critical-listening material but is slightly more sensitive to aggressive post-processing.
Yes, under typical conditions such as MP3 or AAC encoding, forwarding, and normal upload/download cycles. It may fail under deliberately destructive processing, multiple chained re-encodes, or extreme editing.
The upload is rejected. If it is one of your own prior deliveries, TrustedAudio can tell you that it is already a watermarked copy. If it belongs to another customer, the upload is still blocked, but the identity of that other customer is never disclosed.
It is the public-facing verification surface that lets anyone confirm whether an audio file carries a TrustedAudio watermark and, depending on visibility settings, see owner-approved metadata about the publicly registered track.
Every successful public verification creates a persistent receipt URL identified by the SHA-256 hash of the analyzed file. It can be shared as proof that the file matches a TrustedAudio-publicly registered track.
Receipts persist as long as the matched track remains registered. They are live receipts: each visit shows the current visibility level, current registration state, and current owner display name.
No. Public registration is one-way. You may upgrade the visibility level from Minimal to Owner-identified to Track-identified, but you cannot downgrade it or self-serve remove the registration.
No. Recipient identity is never disclosed by any public verification surface. Recipient attribution is owner-only and available only through authenticated leak investigation inside the owner's workspace.
Leak investigation is the authenticated owner-side workflow that lets you upload a leaked or forwarded audio file and identify which recipient originally received it by decoding the embedded watermark.
The workspace owner can. Team members can run investigations only if the owner grants them the required permission.
Results fall into confidence buckets:
That can happen when a watermark is detected but no longer maps to an active record, when the file was heavily processed, or when the file never belonged to your workspace.
You choose tracks, choose recipients, set permissions such as playback or download, optionally brand the delivery page, and send the delivery. Every recipient gets their own controlled delivery page.
Yes. Watermark mode is configured per track inside a delivery.
Yes. The owner can stop a delivery and revoke access. Already downloaded files remain with the recipient, but the delivery page and future access can be disabled.
Usually no. The delivery link itself is the credential. Additional access restrictions can be applied depending on the delivery configuration.
Yes. TrustedAudio supports recipient lists, imports, and delivery reuse across campaigns.
The address is suppressed from future mailings according to the chosen unsubscribe scope: this workspace only or all TrustedAudio workspaces. Suppressed addresses are rejected in recipient import, recipient add/edit, and delivery assembly, with an additional overprotect check at send time.
The owner controls billing, plan state, and workspace-level settings. Team members work inside the same workspace with permissions granted by the owner.
Yes, if the owner grants the relevant permissions. TrustedAudio uses owner-controlled capability gating rather than one fixed staff role.
Only source uploads count against storage: original audio files, artwork, and attachments. Per-recipient watermarked outputs are generated on demand and cached temporarily; they do not count against storage.
The source is removed from your storage. Public verification registrations, where applicable, remain in the registry and do not free a lifetime registration slot.
TrustedAudio records engagement events such as page opens, listens, downloads, ratings, and other recipient interactions, subject to the delivery surface and permissions you used.
Yes. Delivery analytics are designed to show engagement by delivery and recipient in the workspace.
Yes. TrustedAudio supports API workflows for file transfer, watermarking, conversion, link generation, and analysis. Business includes the full API with webhooks.
Yes. TrustedAudio is designed to sit inside existing music-delivery or storefront workflows when the plan includes the required integration capabilities.
No. Recipient identities remain private to the owner workspace and never appear on public verification surfaces.
Yes. Higher plans expose audit-oriented tracking and operational history for important workspace actions.
TrustedAudio branding controls increase by plan tier. Lower tiers get basic accent and presentation changes, while higher tiers add full palette control, header text, favicon, email presentation control, and eventually custom CSS and white-label-style options.
Custom delivery domain support is available on higher plans. It is distinct from general branding controls.
A single account is associated with one workspace. If you need separate workspaces, create separate accounts. Enterprise agreements may cover broader arrangements.
Yes. Google, Microsoft, and Apple login are available.
No. Payments are non-refundable. Customers keep access until the end of the paid billing period.
No, unless explicitly stated. Taxes may apply depending on your jurisdiction.
Use the public documentation, the FAQ, and the workspace support and onboarding channels provided by your plan. Business and Enterprise are designed for heavier operational support.
No. Once a track is publicly registered, every future recipient copy of that track is publicly verifiable. If you need a non-public version, treat it as a separate track in the track manager.
Yes. The verification receipt is the public URL you share when you need a stable public verification page for a file that matched a registered track.
No. TrustedAudio provides technical tracing and verification tools. Legal support or courtroom strategy is outside service scope.
Only via legal erasure of the underlying registration, such as a valid GDPR erasure request, court order, or proven fraudulent registration. There is no normal self-serve deregistration flow.
Yes. This public FAQ is derived from the current TrustedAudio FAQ source document and is intended to reflect the product's customer-facing wording.