Legal / BeatWise

Privacy Policy

Last updated 8 October 2026

The short version

BeatWise does not sell personal data.

No advertising trackers; only cookieless, aggregate visit statistics.

The landing-page waitlist is a visual demo and stores nothing.

Audio and video remain on YouTube; BeatWise stores references and cue points.

1. Who is responsible for your data

BeatWise is the controller for the personal data described in this policy. BeatWise is currently operated as an independent beta product. Privacy questions and requests can be sent to privacy@beatwise.live. BeatWise has not appointed a Data Protection Officer because the current scale and type of processing do not require one.

This policy covers the BeatWise website, account area and browser-based sampler. Google/YouTube and Stripe also act as controllers for some processing they determine themselves; their notices are linked below.

2. The data BeatWise actually processes

Account and authenticationEmail address, a Supabase user identifier, authentication and session records, and—only if you add them—username or avatar URL. BeatWise never receives your password in readable form.
Sampler activityFavourite track identifiers, pad number and cue timestamp, the tracks you loaded and when (History), playlist names and the tracks in them, remaining daily tokens, token reset time and token-use events linked to your account.
Plan and billingPlan, subscription status, renewal/end date, and Stripe customer and subscription identifiers. Stripe receives the payment information you enter; BeatWise does not store full card numbers or security codes.
Track cataloguePublic YouTube identifiers and metadata such as title, channel, thumbnail, duration and view count, together with estimated key, tempo and genre. These catalogue records become personal activity data only when linked to your favourites, pads or token history.
Technical dataNecessary session cookies and the ordinary request information received by infrastructure providers, such as IP address, browser/device information, timestamps and security logs.

BeatWise does not ask for special-category data such as health, biometric, political or religious information. Please do not place that information in profile fields or support messages.

The email typed into the landing-page waitlist stays in component memory only. The current proof-of-concept form sends no request and creates no database record. If a real waitlist is introduced, this policy and the form notice will be updated before collection begins.

3. Why we use it and our legal bases

  • Provide the account and sampler — authentication, track discovery, favourites, saved pad cues, token limits and plan access are necessary to perform the BeatWise service you request (Article 6(1)(b) GDPR).
  • Process Pro subscriptions — creating checkout and keeping the plan in sync are necessary to perform the subscription contract; limited transaction records may also be retained to comply with accounting, tax and consumer-law obligations (Articles 6(1)(b) and 6(1)(c)).
  • Secure and operate BeatWise — fraud prevention, debugging, rate-limit enforcement and protection of accounts rely on BeatWise's legitimate interests in running a safe and reliable service (Article 6(1)(f)). You may object where this basis applies.
  • Optional device storage or third-party media — where EU electronic privacy rules require consent for a non-essential technology, the appropriate basis is consent (Article 6(1)(a)). Consent can be withdrawn without affecting earlier lawful processing.

An email address and authentication information are required to create an account. Payment details are required only if you choose Pro. Profile details such as username and avatar are optional; without required account data, BeatWise cannot provide the signed-in sampler.

4. Where the data comes from

Account and sampler data comes directly from you and your use of BeatWise. Subscription status comes from Stripe after a checkout or billing event. Track metadata comes from publicly accessible YouTube data and, where applicable, catalogue sources used to identify a track. BeatWise does not use these sources to build an advertising profile about you.

5. Processors, recipients and international transfers

  • Supabase provides authentication and the database containing accounts, favourites, pads, tokens and subscription links. Supabase acts as BeatWise's processor for this data. Its Data Processing Addendum includes EU Standard Contractual Clauses where required.
  • Stripe provides checkout, subscriptions and the billing portal. Stripe may act as a processor and as an independent controller for payment, compliance and fraud-prevention activities. See Stripe's Privacy Policy and Data Processing Agreement.
  • Vercel hosts the BeatWise website and processes ordinary request data (such as IP address and browser information) to serve it. BeatWise also uses Vercel Web Analytics to count visits and page views. It sets no cookies and reports only aggregate statistics such as pages, referrers, countries and device types; visitors are not identified or followed across other sites. See Vercel's Privacy Policy and Web Analytics privacy notes.
  • Google/YouTube provides video metadata and embedded playback. When the player connects, Google may receive device, network and playback information under the Google Privacy Policy.

These providers and their subprocessors may process data outside the European Economic Area. Where no adequacy decision applies, BeatWise relies on contractual safeguards such as the European Commission's Standard Contractual Clauses and the provider's supplementary measures. You may request information about the safeguards relevant to your data using the privacy email above.

BeatWise does not sell personal data and does not disclose it to advertising networks or data brokers.

6. Cookies, local storage and the YouTube player

Supabase authentication uses cookies needed to keep you signed in and protect access to your account. These are service cookies, not advertising cookies. BeatWise uses Vercel Web Analytics for aggregate visit statistics, which works without cookies or device storage, and does not use behavioural advertising cookies.

The sampler loads YouTube's IFrame Player API. Loading or using that player creates a direct connection to Google, which may read or place device identifiers and associate playback with a Google account if you are signed in there. Your YouTube privacy and history controls are managed by Google. Avoid opening the sampler or loading a track if you do not want the YouTube connection to occur.

EU electronic-privacy rules may require prior consent before non-essential third-party storage is enabled. This privacy notice explains the processing, but a notice alone does not replace any consent mechanism that may be required for the deployed player configuration.

7. How long data is kept

  • Account, favourites, pad assignments, playlists, token balances and token events are kept while the account remains active. History keeps your most recent 200 tracks; older entries are deleted as new ones arrive.
  • Following account closure or a verified erasure request, account-linked records are deleted unless a limited record must be retained for law, fraud prevention, dispute resolution or security. Provider backups expire through the provider's controlled deletion cycle.
  • Billing identifiers and subscription records are kept for the subscription relationship and for any later statutory accounting, tax, chargeback or limitation period that applies. Stripe retains payment data under its own notice.
  • Session cookies last until their configured expiry or sign-out. Security logs are kept only for the period reasonably needed to investigate incidents and protect the service.
  • The proof-of-concept waitlist has no retention period because it does not transmit or store the email.

8. Your rights in the EU/EEA

Depending on the circumstances, you may request access, correction, erasure, restriction, portability or object to processing based on legitimate interests. You may also withdraw consent at any time where consent is the basis. BeatWise will respond without undue delay and normally within one month; identity verification may be required to protect the account.

Send a request from the email associated with your account to privacy@beatwise.live. There is no charge unless a request is manifestly unfounded or excessive as allowed by law.

You may complain to the supervisory authority where you live or work. In Spain, this is the Spanish Data Protection Agency (AEPD). You also have the right to seek a judicial remedy.

9. Automated decisions and security

BeatWise automatically applies daily token limits and changes feature access according to subscription status. These are ordinary contract and product rules; BeatWise does not make solely automated decisions that produce legal or similarly significant effects, and it does not profile users for advertising.

BeatWise uses account-level database access controls, server-only credentials for privileged operations and signed Stripe webhook verification. No internet service can guarantee absolute security, but access is limited according to role and purpose.

10. Children

BeatWise is not directed to children under 16 and does not knowingly collect their personal data. If you believe a child has created an account without the authorisation required in their country, contact BeatWise so the account can be reviewed and removed.

11. Changes to this policy

This notice will be updated when BeatWise changes what it collects—for example, before the waitlist begins storing addresses—or changes a provider or purpose. Material changes will be highlighted in the product or by email where appropriate. The date at the top identifies the current version.

For the legal framework behind this notice, see the EU General Data Protection Regulation and the AEPD's guide to exercising data-protection rights.

Return to the BeatWise landing page.