Privacy information for the Mastera website and app.

This summary explains the main categories of information used to run Mastera. It should be reviewed and approved as part of your formal legal process before production sign-off.

Updated 2026-03-14 by Mastera editorial team

Try Mastera Free Back to homepage

Information the service uses

Mastera supports Google sign-in, so account information may include identifiers such as your name, email address, Google account ID, and profile image returned by the authentication provider. This information is used to create and maintain your account.

If you upload audio for mastering, the service also processes uploaded files, rendered outputs, and the settings associated with each mastering workflow. These materials are necessary for delivering the core product experience.

Payments, storage, and infrastructure

Subscription and checkout activity may be handled by third-party payment infrastructure such as Stripe. Audio assets may be stored and delivered through cloud object storage. Core application data may also rely on database, caching, and hosting providers needed to operate the service.

Those providers should only receive the information necessary to perform their role in the service. Sensitive payment credentials should remain with the payment processor rather than being stored directly in the app.

Retention and user control

Account records, processed tracks, and subscription state may be retained for as long as reasonably necessary to operate the product, comply with legal obligations, and resolve disputes. The exact retention schedule should be reviewed as part of your final production policy.

Users should be able to request help with account access, subscription changes, and questions about how their data is used. If you expand analytics, marketing, or third-party data sharing, this page should be updated before those changes go live.