Privacy Policy

01 Who we are

Cookup Factory (cookupfactory.com) is operated by Marcus Mayhem Media LLC, 2550 Noble Ave, Hamilton, OH 45015 (“we”, “us”). For your account data we are the controller. For data about your fans collected through your pages, you (the artist) are the controller and we are your processor (see Fan data). Contact: [email protected].

02 What we collect from you

• Account: email address, password (stored hashed by Supabase, never seen by us), name and profile picture if you sign in with Google, Apple or Spotify, and when you accepted these policies.
• Your content: songs, lyrics, photos, footage, artwork, project settings and the videos you render.
• Artist pages: what you publish on your link-in-bio, release and pre-save pages.
• Billing: plan, credit balance and usage, and a Stripe customer id. Card details go straight to Stripe; we never see or store them.
• Connections: if you connect Facebook/Instagram for ads, an access token, stored encrypted, deleted when you disconnect.
• Technical: IP address (used for security and rate limiting), browser and device type, and error reports. In the phone app, if you allow notifications, a device notification token (deleted when you sign out or delete your account).

03 How we use it

We do not sell personal data, we do not use your music, vocals, lyrics or footage to train AI models, and we don’t share your content with anyone except the processors below, as needed to run the features you use.

04 AI processing

When you use an AI feature, the input it needs goes to the provider for that feature: your song to Replicate (or OpenAI) for lyric timing, your instructions and the relevant project settings to Anthropic for “Ask”, a prompt to the image provider for cover art. These providers process the data to return a result and, under their API terms, do not use it to train their models. Audio is shared by a short-lived private link rather than made public.

05 Fan data (artists are the controller)

Your pages may collect, only when a fan chooses to:

• Spotify pre-save: the fan’s Spotify user id and a permission token (stored encrypted) that lets us save your release to their library on release day. No email or name. The fan can withdraw it from the link in their confirmation, or in their Spotify settings.
• Cookup pre-save (via Feature.fm): the fan pre-saves on a page run by Feature.fm, which connects to their music service with their permission. If the fan agrees to share their contact with the artist, we import their email, country and service user id (never their birthdate) so the artist can see them in Insights. An email that unsubscribed from the artist with us is never re-imported.
• “Notify me”: the fan’s email address, with the exact consent wording they agreed to and when. Where you switch on the release-day email, we send the fan a link to confirm their address first (double opt-in) and then one email when the release is out, on your behalf, through our email provider (Resend). We record whether each email was sent and clicked (a click passes through our link), and whether it was opened ONLY if the fan separately agreed to that when signing up. Every message carries an unsubscribe link and our postal address.
• Page statistics: counts of views and clicks by day, country and device type. No profiles of individual visitors.

As your processor we: process fan data only to provide these features on your instructions; keep it confidential and secured; use only the sub-processors listed below; help you answer fans’ requests to see or delete their data; tell you without undue delay about a breach affecting it; and delete it when you delete the page, the campaign or your account. Fans who contact us directly will be pointed to you, or helped on your behalf.

You are responsible for telling your fans who you are and how you use their data, and for having a lawful basis to contact them.

06 Cookies, analytics and the Meta Pixel

On cookupfactory.com itself we use only essential cookies: the sign-in session (Supabase), a short-lived cookie that carries your Terms acceptance through Google/Apple/Spotify sign-in, and security cookies from Cloudflare. We don’t use advertising cookies in the app.

Product analytics (PostHog). To see where people get stuck, we may count which steps of the app are used (for example “song uploaded”, “video rendered”, “video shared”, “checkout started”). Each event carries a pseudonymous id (a keyed hash of your account id, or, before you sign in, a random id kept in your browser’s storage, which we link to your account id once you sign in) and simple values like the preset you picked; never your email, name, songs, lyrics, file names or IP address. We also note how you first arrived: the campaign tags in the link (utm_source, utm_campaign and similar), the kind of site that sent you (for example “instagram” or “google”, never the full address), and whether you came through an invite link (never whose). In the EU, the UK and Switzerland (and wherever we can’t tell your country) nothing is sent until you choose “Allow”; elsewhere you can turn it off. If your browser sends Do Not Track or Global Privacy Control, nothing is sent and we don’t ask. We remember your choice in one cookie (ccf_analytics); the phone app asks separately and remembers its own answer. Analytics never runs on artists’ fan pages. Cookie choices

Payments in analytics. When you buy a plan or credits, our server (not your browser) records that a payment, refund or dispute happened, with the plan and the amount, only if you had allowed analytics when you started checkout. Card details never reach us or PostHog: Stripe handles them.

Price tests. From time to time we may show some signed-in people a different price for a plan, to learn which works better. Only people who allowed analytics are included, and the price you see is always the price you pay at checkout.

On artists’ fan pages, an artist may add their own Meta Pixel. It loads only after the visitor agrees in the consent banner, and only on that artist’s pages. The artist controls that data with Meta; see their privacy notice and Meta’s.

07 Who processes data for us (sub-processors)

We use each provider under its standard terms, including its data processing terms where it offers them. Where data leaves the EU/UK, transfers rely on the provider’s EU–US Data Privacy Framework certification or Standard Contractual Clauses. Regions are each provider’s stated hosting location for our account. We will update this list before adding a new sub-processor.

08 How long we keep it

• Account and content: until you delete them or your account.
• Rendered videos: for your plan’s retention period (shown on the pricing page), then removed automatically.
• Fan data: until you delete the page or campaign, the fan withdraws, or your account closes.
• Billing records: invoices and payment records, kept by Stripe as long as tax law requires (typically 7 years), even after your account is deleted.
• Error reports and logs: up to 90 days.
• Backups: encrypted database backups roll off within 30 days (our nightly backups are kept 30 days; our database host’s own, 7).
• Deleted accounts: an anonymous record that an account was deleted and when (a one-way hash of the account id, no name or email), kept for legal and fraud purposes.

09 Your rights and deleting your data

You can ask to see, correct, export or delete your personal data, or object to how we use it, by emailing [email protected] from your account’s address. We’ll answer within 30 days.

Download your data any time from Settings → Account → Download my data: a file with your account, videos list, songs and lyrics, pages, releases and credit history.

Delete your account yourself from Settings → Account → Delete my account on cookupfactory.com, or in the phone app from Settings → Delete account (you confirm, and sign in again if you haven’t recently). You can also email us from your account’s address and we’ll delete it for you. What happens:

• Immediately: you’re signed out on every device and can’t sign back in; your artist page and release pages go offline; any paid subscription is cancelled so you aren’t charged again (the current period isn’t refunded).
• Within 30 days (usually within the hour): we erase your videos; uploads, footage and songs; artist page and release pages; the fan data you collected through them (fan emails and pre-save subscriptions — you are its controller, and fans who only followed you are removed with it); Insights; connected accounts (we revoke our access to Meta and delete stored tokens); your credits (forfeited); and your sign-in account.
• Backups: copies in our encrypted database backups roll off within a further 30 days and are never used to restore a deleted account.
• What we keep: invoices and payment records at Stripe for as long as tax law requires, and an anonymous record that an account was deleted and when (no name, email or content) for legal and fraud purposes.

If you are in the EU or UK you can also complain to your data protection authority. California residents: we do not sell or share personal information as those terms are defined in the CCPA.

10 Security

Data is encrypted in transit (HTTPS) and at rest. Access tokens for Spotify and Meta are encrypted with a key kept outside the database. Your files are private by default and shared only by short-lived signed links. No system is perfectly secure; if a breach affects you, we’ll tell you and the authorities as the law requires.

11 Children

The Service isn’t for children under 16, and we don’t knowingly collect their data. If you think a child has an account, tell us and we’ll delete it.

12 Changes

We’ll update this policy as the Service changes, and tell you by email or in the app before material changes apply.