Album Conceptualizer

Privacy policy

How Album Conceptualizer handles your data

This page explains what account, project, billing, and analytics data the app can store, why it is used, and how support requests are handled.

1. Data we collect

Depending on how the deployment is configured, we may collect account information such as your name, email address, provider account identifiers, and session data.

We also store workspace data needed to operate the product, including album metadata, song structure, lyrics drafts, comments, tasks, versions, shares, notifications, and analytics events.

2. How we use data

We use your data to authenticate you, save projects, provide export workflows, show workspace analytics, enforce rate limits, prevent abuse, and support billing and subscription management where enabled.

We may also use operational logs and aggregate product analytics to diagnose issues, improve reliability, and understand feature adoption.

3. Billing and payments

Billing is handled through Stripe. We do not store raw payment-card numbers in this app. We may store Stripe customer, subscription, and checkout identifiers so plans stay in sync with your workspace.

4. Sharing and service providers

We may share data with infrastructure and service providers that help us run the product, such as hosting, database, cache, email, authentication, logging, and payment providers.

We may also disclose information when required by law, to protect the service, or during a merger, acquisition, financing, or similar business transfer.

5. Cookies and session storage

The app uses cookies or equivalent session mechanisms for authentication, security, and core product behavior. If you disable them, sign-in and protected routes may stop working correctly.

6. Retention and deletion

We retain account and project data for as long as needed to operate the service, comply with legal obligations, resolve disputes, and enforce agreements. Backups may persist for a limited period after deletion.

If you want account or project data removed, use /support to contact the team for the current deployment.

7. Security

We use reasonable technical and organizational measures to protect data, but no system is perfectly secure. You should still use strong authentication, avoid sharing credentials, and keep your own backups of critical material.

8. Your choices

You can usually review or update workspace content directly in the app. Billing settings can be managed from the workspace billing area when enabled. For privacy requests that are not self-serve, contact support.