Privacy & cookies
How information moves through CuePack, and the choices available in this public test preview.
Operator and contact details pending. Live purchasing is unavailable.
Scope and responsible business
This notice covers the CuePack website and signed-in songwriting studio. The legal operator, business address, and support/privacy email are awaiting confirmation. This is a launch draft for the public test preview, not a finalized customer privacy notice.
Information used by the studio
Sign-in provides your account identifier, email, and name where available. A song request can contain a working title, genre, story or concept, energy, optional song shape, requested language, and lyrics you supply. Saved records include the completed writing, original brief, creation date, model and workflow information, and automated review results. Usage counts associate your allowance with your account and billing period.
Why it is used
CuePack uses this information to authenticate access, develop and save your writing, provide copy and download tools, apply allowances, process enabled artwork requests, administer account-linked sandbox billing, and investigate service or security problems. Do not submit sensitive personal information or material you are not entitled to share.
Service providers
The site runs on OpenAI Sites infrastructure with Cloudflare hosting and storage. Supabase manages CuePack account registration and email/password sign-in. The public test preview also has an OpenAI Sites access gate. Supabase processes account information; Cloudflare storage holds saved Briefs and billing balances. When AI features are enabled, the submitted brief, lyrics, relevant instructions, and any repair context are sent to the OpenAI API. Artwork requests send the relevant visual direction to the configured image service. These providers process information under their own terms and privacy practices; this preview makes no promise of zero retention.
Payment information
Checkout opens on Stripe. Stripe receives the information you enter there, including contact and payment details. CuePack does not receive your full card number through its own card form. Connected billing retains Stripe customer and checkout references, purchased song balances, subscription period grants, and generation reservation records. The server verifies Stripe payment and subscription status before granting allowance. Full card numbers remain with Stripe. Account-linked Stripe sandbox checkout is connected. After server-side verification, a completed test purchase adds test credits to the signed-in CuePack account. No real money is charged, and no live subscription is started.
Cookies, storage, and analytics
CuePack uses secure HttpOnly cookies for sign-in and session renewal. Access cookies last up to one hour. A rotating renewal cookie is retained for up to 30 days and renewed during active use; Supabase session policies and revocation still apply. Sign-out clears the CuePack session and renewal cookies. Owner sandbox testing uses a separate restricted cookie. Hosting may also use storage required to protect access. The CuePack application currently includes no optional advertising pixels or analytics scripts. There is therefore no optional tracking consent switch to operate in this preview. Providers and linked sites can use their own storage; their policies apply separately. Optional measurement tools must be disclosed and any required consent controls implemented before they are added.
Retention and deletion
Completed songs remain available after cancellation under the stated service design. The studio includes deletion of saved writing and associated stored artwork. Deleting a studio record does not delete copies you downloaded, material pasted into Suno, Udio, or another service, or provider logs and backups. A complete retention schedule and verified account-wide deletion process must be finalized before public launch; no fixed deletion deadline is promised by this draft.
Sharing and security
The current application has no feature for selling personal information or sharing it for targeted advertising. Processing by providers is needed for the functions described above. Account-linked access checks restrict saved work; no system can guarantee absolute security. Hosting and security providers may process technical request and error information. Information may also need to be disclosed where legally required or to address abuse.
Your choices and privacy requests
You can choose what to submit, copy or download your saved writing, and delete saved songs in the studio. Requests about access, correction, account deletion, or other privacy rights require an identity check and may be subject to applicable legal limits. A working privacy contact must be published before customers are invited; see the Contact page for the current setup status.
International processing and younger users
Service providers may process information in countries other than your own. Launch territories, applicable transfer arrangements, and age eligibility are not finalized. This public test preview is not directed to children; do not submit children’s personal information.
Updates
Changes to the service or its data handling will be reflected here with a revised date. Material changes must be communicated as required before the affected processing begins.
Provider policies
OpenAI privacy · OpenAI API data controls · Cloudflare privacy · Stripe privacy