Privacy policy
This policy explains how Stemsession (stemsession.com) processes data when you sign in, separate songs into stems, analyse chords, practise with backing tracks and use your library. It covers the website and its backend.
1. Controller and contact
The controller of personal data processed through Stemsession is Dominik Mietla, the application operator. You can send privacy questions and requests to access, correct or delete data to the email address below.
Contact for personal data requests: contact@stemsession.com
2. Data we process
- Account data: Firebase identifier, email address, verification status and, if provided by Google, profile name and picture. Firebase handles email/password authentication. Our backend does not receive your Google password or store user passwords.
- Materials and results: uploaded audio, filenames, user-supplied titles, source links, duration, stems, chords, key, any requested lyrics transcription, edits and exported files. Recordings can contain personal data, such as an identifiable voice.
- Service usage: file ownership, job status, operation dates, trial and credit usage, plan, access rights and processing errors. This information is also used in our internal administration panel.
- Transaction data: email, selected package, amount and currency, customer, order, subscription and Stripe event identifiers, status and billing history. Full card details and CVC do not reach our backend.
- Technical data and correspondence: IP address, browser information, hosting/API requests and errors, interface preferences and messages you send us.
3. Google sign-in and Firebase data
Google sign-in verifies your identity and associates your account with your private library, credits and settings. We receive the basic profile information listed above and a token needed to verify the sign-in. Firebase also handles registration, email verification and password resets.
Signing in with Google does not give Stemsession access to Gmail messages, contacts, Google Drive files, private videos or your YouTube watch history. Importing a YouTube link is a separate feature and does not expand Google sign-in permissions.
Google sign-in data is used for account functionality, access control and service security. We do not sell it, share it with data brokers, or use it for behavioural advertising or training AI models.
4. Purposes and legal bases
Providing account data is voluntary but necessary for features requiring sign-in. Audio analysis requires the relevant material. You can browse public pages without an account. We do not run a newsletter. Visit analytics requires separate consent.
- Accounts, library, processing, exports, trials, credits and requested features: performing a contract or taking steps at your request before entering a contract - Article 6(1)(b) GDPR.
- Security, abuse prevention, troubleshooting, internal operational statistics and establishing or defending claims: legitimate interests - Article 6(1)(f) GDPR. These interests are operating a secure, functioning service and maintaining accurate billing.
- Sales documentation, accounting and other mandatory record keeping, where applicable: legal obligations - Article 6(1)(c) GDPR.
- Optional Google Tag Manager/Google Analytics measurement: consent - Article 6(1)(a) GDPR. Refusing does not restrict app access.
- Responding to messages: contractual steps or the legitimate interest in handling correspondence - Article 6(1)(b) or (f) GDPR, depending on the request.
5. Audio, microphone and library
Stem separation, chord analysis and transcription run in software on our AWS backend. Using these features does not itself make your recordings available to other users. We do not use uploaded recordings to train AI models.
A quick session without saving to the library currently uses temporary server memory. Choosing library storage, saving a session later, or using library-mode import stores the source and results persistently. Not all processing modes are therefore memory-only.
Live input monitoring and the tuner require browser permission for your microphone or audio interface. The live signal used by these features is processed locally in your browser; enabling monitoring alone does not upload it. You can stop monitoring and revoke permission in browser settings.
Only submit material you are entitled to have processed and avoid unnecessary personal information about others. We do not identify users by their voice.
6. Recipients and service providers
Authorised administrators may access information necessary for account support, security and billing. Data can be disclosed to competent authorities when required by law. We do not publish a directory of users’ libraries.
Your browser also contacts Google Fonts to obtain fonts and api.country.is to determine an IP-based country and suggest a currency. These connections disclose your IP address and request metadata to the provider. We do not send account identifiers, email or cookies to api.country.is or request precise device location. The country result is cached in session storage for up to one day. Browser region settings are used if the lookup fails.
For YouTube imports, our backend contacts YouTube/Google to retrieve the specified material. It does not send your Google password or use sign-in permissions to read a private account.
- Google/Firebase: authentication and identity management; Cloud Firestore stores information used by the administration panel. Account data also links service operations to the relevant user.
- Amazon Web Services (AWS): backend, audio processing, library, operational and billing databases and technical logs.
- OVHcloud: website hosting, domain and frontend requests.
- Stripe: hosted Checkout, subscriptions, payment confirmations and events. Stripe receives the email and account/order identifiers, among other transaction data. It may act as an independent controller for its own payment and fraud-prevention obligations.
- Google Tag Manager and Google Analytics, after analytics consent: technical information, pseudonymous cookie identifiers, visited view names and visit data. Our events do not contain email, Firebase identifiers, song titles, audio or URL query strings and fragments. The provider also sees the connection IP. We do not enable Google Signals or ad personalisation.
- Email provider: handling messages sent to our contact address.
7. Locations and transfers outside the EEA
Our backend and application files are currently hosted in AWS Stockholm. This does not mean all data stays in the European Economic Area: Firebase Authentication processes data in the US, and our Firestore database is in the North American nam5 region. Google, Stripe and other providers can involve processing outside the EEA.
Transfer safeguards depend on applicable provider terms and GDPR requirements. They can include a European Commission adequacy decision, including the EU–US Data Privacy Framework where the recipient’s certification covers the transfer, or standard contractual clauses and required supplementary measures. Contact the controller for information about safeguards relevant to a particular transfer.
8. Retention and deletion
In the current version, removing a library entry hides it from the list and does not physically erase all underlying files. Email the controller to request deletion of materials or an account. Signing out or removing the Google connection likewise does not delete information already stored in Stemsession.
Deletion from the active service does not immediately erase every backup or data a provider must retain. When handling requests, we consider backups, legally required records and provider terms, and explain any applicable limitations.
- Account data and associations: while the account is maintained, and after a deletion request only to the extent justified by billing, legal obligations or establishing and defending claims.
- Saved library materials: while you keep them in the service and maintain an account, or until a deletion request is handled. Ending a subscription does not automatically erase the library.
- Temporary sessions: cleanup is triggered after ending a session or approximately 30 minutes of inactivity. Deletion may wait for ongoing processing, saving or export to finish. Saving to the library creates a separate persistent copy.
- Trial, credit and transaction history: while needed to administer the account and access rights, then to the extent necessary for required records, complaints and claims. Applicable statutory retention periods govern records subject to legal obligations.
- Correspondence and logs: while handling the request, error or security incident and related claims. Providers also retain some logs and copies according to their service terms.
9. Cookies and browser storage
With your consent, we load Google Tag Manager container GTM-MM3J8HHM to enable Google Analytics 4. Visit and app-usage measurement depends on an active Analytics configuration in the container. Before consent or after refusal, we do not load the container or send analytics events. We do not enable advertising pixels or personalised advertising.
With analytics consent, we may also measure checkout starts and confirmed payments, including automatic renewals without a website visit. The backend links your account to a pseudonymous Analytics identifier while consent remains valid, for up to 180 days. Google receives a transaction identifier, package, amount, currency and payment type, without email, Firebase UID or card details. Sandbox operations use separate test events. The delivery queue is retained for up to 71 hours. A random token stored in your browser allows withdrawal of this measurement even after sign-out. Withdrawal requires delivery to our server; failed requests are retried on your next visit. If you clear browser storage or need to withdraw without access to it, contact the controller.
We store analytics consent or refusal for 180 days and then request a new choice. You can change it through “Cookie settings” in the footer. Accepting the previous cookie notice is not Analytics consent. Withdrawal stops our events, removes accessible Analytics cookies and reloads the page to unload the container. This can interrupt the current monitoring session.
Analytics cookies are configured for up to 180 days without automatic renewal on each page view. Event retention in Google also depends on property settings and provider policies; contact the controller for the specific configuration. Withdrawal does not automatically delete data already sent. Google information: https://policies.google.com/privacy and https://policies.google.com/technologies/partner-sites.
- API session: a secure HttpOnly cookie authorises requests, including audio downloads; the session is limited to 24 hours from sign-in. Firebase also uses browser mechanisms to maintain authentication state.
- Preferences: language, theme, cookie notice choice and live sound settings. The audio settings cookie can remain for up to a year; localStorage remains until removed by you or your browser.
- Session storage: includes the current session identifier and temporary country/currency lookup result. Clearing browser storage can remove preferences or sign you out.
10. Payments and the current test environment
At this policy’s update date, Stripe is used only in Sandbox. Test orders and subscriptions are not real purchases or card charges. Use test data and do not enter real card details during testing.
Account email, identifiers and operation history can still be personal data in Sandbox and are processed to test billing functionality. We will update payment and mandatory retention information before starting live sales.
11. Your rights
Subject to GDPR conditions, you may access and obtain a copy of your data, rectify it, request erasure or restriction and exercise data portability. You may object to processing based on legitimate interests. Where particular processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing.
Send requests to our contact address. We may need proportionate identity verification to protect your account. We normally respond within one month; where GDPR permits an extension, we explain it and the reason. Erasure does not automatically include records we must keep under another applicable legal basis.
You may complain to the President of the Polish Personal Data Protection Office (uodo.gov.pl). Ordinary musical analysis and automatic credit checks are not intended to make decisions producing legal or similarly significant effects within Article 22 GDPR.
12. Security and policy updates
We use HTTPS, authentication checks, account-based resource ownership and restricted administration access. No system is risk-free; protect your account and do not disclose authentication tokens or session files.
We update this policy when features, providers or processing practices change. The date appears at the beginning. Where a material change requires additional notice or consent, we will provide it before applying the new processing practice.