← back
privacy policy
effective date: october 12, 2026
incandenza ("the service") is operated by deux collectif. this policy describes what data we collect, how we use it, and your rights regarding that data.
1. data we collect
when you use incandenza, we may collect:
- account information: email address, display name, and profile image via google sign-in.
- listening data: top artists, genres, listening patterns, and related metadata from services you choose to connect (youtube, apple music, last.fm, tidal). this data is used solely to generate your sonic profile.
- oauth tokens: authentication tokens from connected music services, stored on our server to access your listening data on your behalf.
- payment information: processed entirely by stripe. we do not store credit card numbers. we store your stripe customer id and subscription status.
- usage data: session records and the number of minutes streamed each month, used to apply the free tier allowance.
- browser storage: a random anonymous identifier stored in your browser's local storage so the service can recognize you before you sign in.
2. how we use your data
- to generate personalized sonic profiles from your listening history.
- to produce personalized generative audio streams.
- to manage your account, subscription, and free tier allowance.
- we do not sell your data. we do not use your data for advertising.
3. third-party services
your data is shared with the following services solely to provide the functionality of incandenza:
- anthropic (claude): artist names, playlist names, and genre data are sent to claude to generate sonic profiles. no personal identifiers are included. under anthropic's commercial api terms, this data is not used to train their models.
- spotify (catalog lookup): artist names from your connected services are looked up in spotify's public catalog, using incandenza's own credentials, to retrieve genre information. we do not access your spotify account, and no personal identifiers are included.
- google (lyria): sonic profile prompts (text descriptions of audio characteristics) are sent to google's lyria api to generate audio. no personal identifiers are included.
- stripe: email and payment details for subscription billing.
- railway (hosting): our servers and database run on railway's infrastructure, which stores the data described in this policy on our behalf.
- music services: youtube, apple music, last.fm, and tidal are accessed using the authorization you grant to read your listening data. spotify listening history is read only through last.fm, if you have linked the two.
4. youtube api services
incandenza uses youtube api services to read listening data from your youtube account, if you choose to connect it. by connecting youtube, you agree to be bound by the youtube terms of service. google's handling of your data is described in the google privacy policy.
- what we access: with the youtube.readonly permission, incandenza reads your liked videos, channel subscriptions, and playlists through the youtube data api v3. we never post, modify, or delete anything on your youtube account.
- what we store: artist and channel names derived from that data, your playlist names, summary counts (such as the number of liked videos and subscriptions), and the access tokens needed to read it, stored on our server and linked to your incandenza account.
- how we use it: solely to identify your listening preferences and generate your sonic profile — a set of text descriptions of audio characteristics used to steer audio generation. it is not used for any other purpose.
- who we share it with: artist names and playlist names are sent to anthropic's claude api, and artist names are looked up in spotify's public catalog, as described in section 3, only to build your sonic profile. no youtube account identifiers are shared. youtube data is not shared with anyone else, internally or externally.
- advertising and cookies: incandenza does not display ads and does not allow third parties to serve content or ads, or to place or read cookies or similar technologies, on your device.
- retention: youtube api data is automatically deleted 30 days after it was last retrieved. reconnecting youtube retrieves it again.
- revoking access: you can revoke incandenza's access to your youtube data at any time through the google security settings page. once access is revoked, we cannot read new youtube data, and you can ask us to delete stored youtube data immediately by contacting privacy@incandenza.io; we will delete it within 7 days.
5. google user data — limited use disclosure
incandenza's use and transfer of information received from google apis adheres to the google api services user data policy, including the limited use requirements.
- limited use: google user data (your google sign-in profile and youtube data) is used only to provide and improve the user-facing features of incandenza described in this policy.
- no transfers: google user data is not transferred, sold, or shared with third parties except as necessary to provide those features (as described in sections 3 and 4), to comply with applicable law, or as part of a merger or acquisition with notice to you.
- no advertising: google user data is not used for serving ads, retargeting, or interest-based advertising.
- no ai model training: google user data is not used to develop, improve, or train generalized artificial intelligence or machine learning models.
- no aggregated or anonymized datasets: we do not create aggregated or anonymized datasets from google user data, and do not use or share it in that form.
- no human reading: google user data is not read by humans unless you give explicit consent, it is necessary for security purposes such as investigating abuse, or it is required by law.
6. data security
- encryption in transit: all data exchanged between your browser, our servers, google, and other connected services is encrypted using https (tls).
- restricted storage: data is stored in a private database on our hosting provider's servers. it is not publicly accessible, and access is limited to the incandenza operator through authenticated accounts.
- tokens stay on the server: oauth access and refresh tokens are used only by our server to read your data. they are never sent to your browser or shared with third parties.
- secure sessions: your login session uses a signed cookie that is marked secure and http-only, so it is only sent over encrypted connections and cannot be read by scripts on the page.
- payments: card details are handled entirely by stripe, which is certified to pci dss level 1. we never see or store card numbers.
- data minimization: we request read-only access and store only what is needed to build your sonic profile. youtube api data is deleted automatically after 30 days.
- incidents: if a security incident affects your data, we will notify you and the relevant authorities as required by law.
7. data retention
- oauth tokens and listening data are stored as long as your account is active, except youtube api data, which is deleted 30 days after it was last retrieved (see section 4).
- usage records (minutes streamed) are kept for as long as your account is active.
- sonic profiles are stored as long as your account is active.
- generated audio is not stored. it is streamed in real-time and is non-recoverable once transmitted.
8. data deletion
you may request deletion of your account and all associated data at any time by contacting us at privacy@incandenza.io. upon request, we will delete your account, oauth tokens, sonic profiles, and session records within 30 days. we keep daily database backups for 7 days, so deleted data is fully removed from backups within 7 days after deletion.
9. cookies
incandenza uses a single session cookie (incandenza_session) to maintain your login state. this is a functional cookie required for the service to operate. we also store a random anonymous identifier in your browser's local storage so the service can recognize you before you sign in. we do not use tracking cookies, analytics cookies, or third-party advertising cookies.
10. children
incandenza is not intended for users under the age of 13. we do not knowingly collect data from children under 13. if you believe a child has provided us with personal data, contact us and we will delete it.
11. your rights
depending on your jurisdiction, you may have the right to:
- access the personal data we hold about you.
- request correction of inaccurate data.
- request deletion of your data.
- withdraw consent for data processing.
- lodge a complaint with a supervisory authority.
to exercise any of these rights, contact privacy@incandenza.io.
12. changes
we may update this policy from time to time. changes will be posted on this page with an updated effective date.
13. contact
for questions about this privacy policy, contact privacy@incandenza.io.