Cuepoint — Privacy Policy

Last updated: September 9, 2026.

1. Data Controller

FLASHLABS, os. Młodości 8/20, 31-908 Kraków, Poland, NIP: PL6782679841.
Contact: hello@cuepoint.fm

2. Data We Collect

Data	Purpose	Legal Basis (GDPR)
Email address	Account creation, login, notifications, password reset	Contract (Art. 6(1)(b))
Username	Display name in comments and projects	Contract (Art. 6(1)(b))
Password (hashed)	Authentication	Contract (Art. 6(1)(b))
Project data	Project creation, ownership, membership, collaboration, and pending invites	Contract (Art. 6(1)(b))
Audio files, stems, revisions, voice notes, and waveform data	Core service functionality	Contract (Art. 6(1)(b))
Track Analysis metrics, AI Revision Guidance inputs, outputs, and run metadata	Generating technical audio measurements and optional AI-assisted revision guidance from track metrics, project context, comments, optional user instructions, and previous revision context. Raw audio files are analyzed on Cuepoint servers and are not sent to the AI model.	Contract (Art. 6(1)(b))
Comments, mentions, comment resolution state, and review decisions	Core service functionality, collaboration notifications, and approval workflow	Contract (Art. 6(1)(b))
Guest display names and public share comments/replies	Allowing invited recipients of public preview links to leave timestamped feedback without a Cuepoint account, showing that feedback to other recipients of the same active link and to project members, and notifying project members who enabled comment notifications	Legitimate interest in providing the public review workflow requested by the project owner (Art. 6(1)(f))
Client preview link metadata	Creating, securing, expiring, revoking, and auditing public preview links, including whether a password is required and when the link was last accessed	Contract (Art. 6(1)(b))
Notification preferences	Letting you control optional email notifications	Contract (Art. 6(1)(b))
Authentication, password reset, and email verification tokens	Login sessions, account security, password reset, and email verification	Contract (Art. 6(1)(b))
Billing metadata (via Stripe)	Subscription billing, plan provisioning, checkout, and billing portal access	Contract (Art. 6(1)(b))
Optional page feedback, the related in-app page path, account email, username, and internal user identifier	Collecting, attributing, and triaging product feedback submitted from the authenticated application	Legitimate interest in improving the Service (Art. 6(1)(f))
IP address, user agent, and request logs	Server logs, security, rate limiting, abuse prevention, and troubleshooting	Legitimate interest (Art. 6(1)(f))
Sanitized browser error diagnostics, browser and device information, runtime capability status, and technical network metadata	Detecting and diagnosing production application failures. Reports may include a stable error type, a normalized safe form of recognized browser error messages, sanitized application and React stack locations, normalized page and API route patterns, API method/status/content-type/timing categories, release, environment, browser user agent and derived browser/operating-system/device details, coarse viewport and connectivity state, browser-storage capability status, a random identifier limited to one page load, trace identifiers, and technical metadata inherent in secure network delivery. They exclude account identity, cookies, authentication headers, query strings, request or response bodies, form or content values, user-supplied filenames, and raw project, track, or public-share identifiers.	Legitimate interest in maintaining the reliability and security of the Service (Art. 6(1)(f))
Privacy-minimized website analytics and conversion data	Measuring aggregate visits, traffic sources, approved campaign labels, successful product actions, first paid Pro subscription purchases, and initial collected payment revenue. Cuepoint sends normalized route templates instead of project, track, share, reset, or verification identifiers; fixed event properties; and approved campaign-level UTM values. Plausible receives technical IP address and browser user agent as part of event delivery. For a purchase, Cuepoint temporarily retains those two values and approved campaign labels from checkout for up to 48 hours so the verified Stripe payment can be reported without identifying the account in Plausible.	Legitimate interest in understanding and improving the Service and measuring aggregate campaign performance (Art. 6(1)(f))

We collect only the data needed to provide, secure, operate, and understand the aggregate use of the Service. Payment card details are collected and stored exclusively by Stripe — we never see or store your full card number. We use Plausible for cookieless, aggregate website analytics. We do not use Google Analytics, advertising pixels, remarketing tags, or cross-site tracking.

3. Cookies and Local Storage

We use only essential cookies and browser storage required for the Service to function:

Name	Type	Purpose	Duration
token	Secure httpOnly cookie	Short-lived access session	15 minutes
refreshToken	Secure httpOnly cookie	Session renewal — keeps you logged in	7 days
token, username, emailVerified, userPlan	Local browser storage	Keeping the app state and authenticated API requests in your browser	Until logout, account deletion, or browser storage clearing
cuepoint.publicCommentAuthor	Local browser storage	Remembering the display name a guest used when commenting on a public preview link	Until browser storage clearing or replacement by the guest

Plausible analytics does not set cookies or use local storage. We do not use analytics, advertising, or third-party cookies and do not store campaign attribution in browser storage.

4. How We Use Your Data

To provide and operate the Service (uploading tracks, stems, revisions, and voice notes; posting comments; recording review decisions; creating client preview links; collecting guest feedback on public preview links; collaborating in projects).
To show public share comments and replies to recipients of the same active public preview link and to members of the related project.
To generate Track Analysis metrics and optional AI Revision Guidance. Technical analysis runs on our servers. AI Revision Guidance sends structured context such as metrics, project context, comments, optional instructions, and previous revision context to Google Vertex AI; raw audio files are not sent to the AI model.
To send transactional emails: email verification, password reset links, project invitations, new track notifications, new comment notifications, guest public share comment notifications, and mention notifications. You can disable optional notification emails in your profile settings.
To maintain security and prevent abuse (server logs, including visits to public preview links).
To process subscription payments and manage billing (via Stripe).
To collect and triage optional product feedback submitted from authenticated pages (via a private Canny board).
To detect and diagnose production application failures using sanitized browser error reports and limited browser/runtime context (via Sentry).
To measure aggregate website use, successful product actions, campaign performance, paid Pro conversions, and initial collected payment revenue using cookieless analytics (via Plausible).

We do not use your Content or personal data to train artificial intelligence or machine learning models.

We do not sell, rent, or share your personal data with third parties for marketing purposes.

5. Third-Party Processors

Service	Purpose	Data Shared	Location
Google Cloud Platform	Application hosting, database, file storage, frontend hosting/CDN, logging, and Vertex AI for optional AI Revision Guidance	All data listed in §2. For Vertex AI, structured AI guidance context and generated output; raw audio files are not sent to the AI model.	EU (europe-west1, Belgium) for primary application and data storage; Vertex AI processing may use Google Cloud locations configured for the AI service
Resend	Transactional email delivery	Email address, email content	US
Stripe	Payment processing, subscription management, checkout, and billing portal	Email address, subscription status, Stripe customer/subscription identifiers, payment metadata	US/EU
Canny	Private product-feedback collection and triage	Submitted feedback, related in-app page path, email address, username, and internal user identifier	US
Sentry	Production browser error monitoring and source-map-assisted diagnosis	Sanitized error type and recognized native-browser message form; application and React stack locations; normalized page and API route patterns; API method, status, content type, and duration; release and environment; browser user agent and derived browser, operating-system, and device details; coarse viewport, connectivity, and browser capability status; a random per-page diagnostic identifier; trace identifiers; and technical network metadata inherent in HTTPS delivery. Cuepoint does not send request or response bodies, account identity, cookies, authentication headers, query strings, form or content values, user-supplied filenames, or raw project, track, or public-share identifiers.	EU data region
Plausible	Cookieless aggregate website, campaign, conversion, and initial-payment revenue analytics	Normalized page locations and internal referrers, external referrer origins, approved campaign-level UTM values, fixed successful-action event properties, initial paid amount and invoice currency, browser user agent, and technical IP address used by Plausible to calculate privacy-preserving aggregate statistics. Cuepoint does not send account identity, customer/subscription/invoice/checkout identifiers, content, filenames, comments, raw dynamic route identifiers, arbitrary query strings, click IDs, cookies, or persistent user identifiers.	EU

Resend processes data under Standard Contractual Clauses (SCCs) for EU-US data transfers.

Stripe processes data under their Privacy Policy and EU data transfer mechanisms, including the Data Privacy Framework and SCCs where applicable.

Canny stores its service data in the United States and processes it under its Privacy Policy and applicable transfer safeguards.

Sentry processes sanitized browser error reports and the limited diagnostic context described above in its EU data region under its Privacy Policy and applicable contractual safeguards. Cuepoint does not enable Sentry analytics, tracing, Session Replay, logs, user feedback, or advertising features.

Plausible processes cookieless aggregate analytics under its Privacy Policy and Data Policy. Cuepoint does not enable session replay, advertising profiles, persistent visitor identifiers, or per-user analytics.

6. Data Retention

Account data — retained until you delete your account.
Audio files, stems, revisions, voice notes, waveforms, comments, review decisions, and client preview link metadata — retained until the project or account is deleted. Preview links may also become inaccessible when revoked or expired.
Track Analysis metrics, AI Revision Guidance inputs, outputs, and run metadata — retained with the related track or project until the project, track, or account is deleted.
Guest display names and public share comments/replies — retained as part of the project feedback history until the project, track, or account is deleted. Revoking, expiring, or removing a public preview link stops public access to that link, but does not automatically delete historical guest feedback from the project.
Password reset tokens — expire after 1 hour, are marked used after a successful reset, and are removed when your account is deleted.
Email verification tokens — expire after 24 hours and are removed when your email is verified or your account is deleted.
Refresh tokens — expire after 7 days. Expired tokens are deleted after a short cleanup grace period, and revoked tokens are deleted after up to 7 days.
Billing metadata — retained while needed to manage your subscription and meet legal, tax, accounting, and fraud-prevention obligations.
Optional page feedback and Canny end-user attribution — retained while needed to triage and act on product feedback, or until a valid erasure request is completed.
Server logs (IP, user agent) — retained for 30 days (Google Cloud Logging default).
Sanitized browser error events — retained in Sentry production for 30 days. Sentry states that backup copies are deleted 90 days after creation.
Plausible checkout context — browser user agent, IP address, and approved campaign labels are retained by Cuepoint for no more than 48 hours after checkout, then deleted. The related billing purchase record and delivery status remain for reconciliation without those visitor values.
Aggregate Plausible analytics — retained according to Cuepoint's Plausible account settings and Plausible's data policy. Plausible does not retain raw IP addresses or browser user agents in its reports.
Database backups — retained for 7 days (Google Cloud SQL automatic backups), then permanently deleted.
Anonymized comments — when you delete your account, comments in other users' projects are attributed to "deleted user" and retained as part of the collaborative discussion.
Review decisions and preview links tied to a deleted account — removed when that account is deleted.

7. Your Rights (GDPR)

Where GDPR applies, you have the right to:

Access — request a copy of your personal data.
Rectification — update your email, username, or password in your profile settings.
Erasure — delete your account from your profile settings (see Terms of Service §9 for details).
Data portability — request your data in a machine-readable format.
Object — object to processing based on legitimate interest.
Complaint — file a complaint with the Polish supervisory authority: Urząd Ochrony Danych Osobowych (UODO), ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl.

To exercise any of these rights, contact us at hello@cuepoint.fm. Guests who leave feedback through a public preview link do not have a Cuepoint profile, so they should use this email address for access, correction, or deletion requests.

8. Security

Passwords are securely hashed.
All traffic is encrypted via HTTPS.
Authentication uses short-lived tokens with server-side revocation.
Database and storage are isolated in a private network.

9. Children

The Service is not intended for users under 16 years of age. We do not knowingly collect data from children under 16. If you believe a child under 16 has created an account, contact us at hello@cuepoint.fm and we will delete it.

10. Changes

We may update this Privacy Policy from time to time. Unless a later date is stated, an updated version takes effect when published. The effective date of the current version is shown at the top of this page. We will provide any notice required by applicable law.

11. Contact

For privacy-related questions, contact us at hello@cuepoint.fm.