Last updated: November 2026
This Privacy Policy explains how PitchHighway (“we,” “us,” or “our”) collects, uses, stores, and protects your personal data when you use our web application and iOS application (collectively, the “Service”).
We are committed to protecting your privacy in accordance with the General Data Protection Regulation (EU) 2016/679 (“GDPR”) and applicable Romanian data protection law. Please also review our Terms of Service.
The data controller responsible for your personal data is:
When you create an account, we collect:
When you use pitch training features, we process:
Classification: Voice and audio data is personal data under the GDPR, but it is not biometric special-category data under Article 9. We use voice data for pitch training, scoring, and progress tracking — not for uniquely identifying you as a person. Therefore, processing is based on Article 6 (not Article 9) of the GDPR.
If you subscribe in the iOS app, we receive from Apple:
If you subscribe on the website, we receive from Stripe:
We do not receive or store your payment card details. All payment processing is handled by Apple or Stripe.
If you sign up to be notified about PitchHighway’s app launch, we collect:
This email address is stored in our database to send you a notification when the PitchHighway app is available, along with launch-related updates, early-access offers, and occasional promotional communications about PitchHighway. We do not share this email with third parties for their own marketing purposes. Email delivery is handled via Resend. You may unsubscribe or request deletion of your email at any time by emailing [email protected] with the subject line “Unsubscribe.”
If you upload your own songs for processing into Highway exercises, we collect and process:
Uploaded songs are stored in Cloudflare R2 (EU-preferred regions) and are associated with your user account. You retain full ownership of the songs you upload.
If you explicitly choose to share a performance on social media from the web app, we collect and store:
The recording is uploaded only after you confirm the sharing prompt — nothing is uploaded automatically. It is stored in Cloudflare R2 (EU-preferred regions) and is reachable by anyone who has the share link. Shared performances are automatically deleted 30 days after sharing.
If you connect an AI assistant through our Model Context Protocol (MCP) server, we store:
We receive the tool name and the arguments needed for that request, never your conversation with it. Tool-call records do not contain arguments. An MCP upload request includes a YouTube link, an optional song name and difficulty. We retain those inputs with the song-processing job. See Section 7.1 for the tools and Section 9 for retention.
If you request access to our affiliate program through the form at pitchhighway.com/affiliate, we collect:
We use this only to review your application and reply to you. Each application is stored in our database and a copy is emailed to our support inbox; email delivery is handled via Resend. We do not share it with third parties for their own purposes. You may request deletion of your application at any time by emailing [email protected].
The Community tab in the app and on the web shows recent practice activity from other PitchHighway users.
What other users can see about you. If you turn on “Show me in Community”, the feed can show:
The feed never shows your email address, your recordings, or which songs you practice next to your name. A separate entry type shows only a song title, for example: Someone is learning “Song title”. This entry never contains a name.
Older versions of the iOS app show a leaderboard instead of the feed. It shows your first name, a Premium badge, the number of songs you sang and your best and total scores from the last 30 days. The same setting controls the leaderboard.
Opt-in. You do not appear in the feed unless you choose to. To turn it on or off, go to Profile > Settings > “Show me in Community” in the app, or to the same setting in your account on the web. If you turn it off, you stop appearing to other users the next time their feed loads. You can still see the feed. Guest accounts never appear in the feed.
What we use. We do not keep a separate copy of the feed. The server builds it on request from your account data (name, subscription tier) and your practice activity of the last 7 days (30 days for the leaderboard). Your own weekly summary (“Your last 7 days”) is visible only to you.
Legal basis. Your consent (GDPR Art. 6(1)(a)). You can withdraw it at any time with the setting above.
Report another user. If a name or entry in the feed is offensive or impersonates someone, send an email to [email protected]. Include the name and the approximate time you saw it. We review each report and can remove a user from the feed or change an offensive name.
We collect personal data through three channels:
We process your personal data for the following purposes, each with a corresponding legal basis under GDPR Article 6(1):
| Purpose | Data Used | Legal Basis |
|---|---|---|
| Account creation & authentication | Account data, OAuth data, auth tokens | Art. 6(1)(b) — Performance of contract |
| Providing pitch training features | Voice & audio data, usage data | Art. 6(1)(b) — Performance of contract |
| Tracking progress, scores & streaks | Usage & progress data | Art. 6(1)(b) — Performance of contract |
| Vocal range tracking | Voice data (pitch samples, MIDI range) | Art. 6(1)(b) — Performance of contract |
| Subscription management | Subscription data, Apple transaction IDs | Art. 6(1)(b) — Performance of contract |
| Security (fraud prevention, token management) | IP address, device info, auth tokens, web server logs (with your account ID when you are signed in) | Art. 6(1)(f) — Legitimate interest |
| Understanding where our users come from (country-level product and advertising analysis) | Approximate country derived from your IP address; web server logs (pages visited, referring page) | Art. 6(1)(f) — Legitimate interest |
| Preventing free-tier abuse (e.g. resetting upload limits by deleting and re-creating an account) | One-way hashed identifier derived from your email, Apple ID, and/or Google account identifier | Art. 6(1)(f) — Legitimate interest |
| Service email communications | Email address | Art. 6(1)(b) — Performance of contract |
| App launch notification & promotional communications | Email address (from launch signup) | Art. 6(1)(a) — Consent |
| Reviewing affiliate program applications | Email address, name, and sharing plans (from the affiliate form) | Art. 6(1)(b) — Steps taken at your request prior to entering into a contract |
| Error monitoring & debugging | Technical/device data, web server logs | Art. 6(1)(f) — Legitimate interest |
| Future anonymised ML training | Anonymised/aggregated voice data | Art. 6(1)(f) — Legitimate interest (with anonymisation) |
| Processing user-uploaded songs into Highway exercises | Uploaded song audio, processed outputs | Art. 6(1)(b) — Performance of contract |
| Hosting performances you explicitly choose to share | Shared performance recordings, song title | Art. 6(1)(a) — Consent |
| Creating My Covers and analysing your voice; diagnosing pitch detection from telemetry (derived numbers only) | Pitch diagnostics telemetry (per-frame pitch values); and, while the “Practice recordings” setting is enabled, the raw microphone recording of a practice run | Art. 6(1)(f) — Legitimate interest (telemetry); Art. 6(1)(a) — Consent, via the “Practice recordings” setting, withdrawable at any time in Account settings (practice-run recordings and the covers created from them). Processed under Article 6, not Article 9 — see the Classification note in Section 3.2 |
| Advertising-conversion measurement (Reddit Pixel, Meta Pixel, Meta Conversions API) | Cookie/pixel identifiers, IP address, browser/User-Agent, pages viewed, sign-up, song-upload and purchase events; for the Meta Conversions API only, a hashed (SHA-256) email address | Art. 6(1)(a) — Consent (EEA/UK, via our cookie banner). Outside the EEA/UK the pixels and the server-side events are on by default and you may opt out (see Section 11). |
| Advertising audiences on Meta (customer lists and lookalike audiences) | Hashed (SHA-256) email address | Art. 6(1)(f) — Legitimate interest. You can object at any time (see Section 7.2). |
| Advertising-conversion measurement in the iOS app (Meta SDK) | App install, app opens, App Store subscriptions and free trials (with price and currency), sign-up and song-upload events, an app-installation identifier, IP address, device and app information | Art. 6(1)(f) — Legitimate interest. You can object at any time (see Section 7.3). |
| Serving your training data to an AI assistant you have connected (MCP) | Voice profile, usage & progress data, uploaded song metadata, MCP connection tokens | Art. 6(1)(a) — Consent, given when you approve the connection on our sign-in screen or, for a connection made before November 2026, when you generated and pasted a personal access token yourself, and withdrawable at any time by disconnecting the assistant or asking us to revoke the token (see Section 7.1) |
Given the sensitive nature of voice data, we want to be fully transparent about how it is handled:
We share personal data only with the following third-party service providers, strictly for the purposes described:
| Provider | Purpose | Data Shared | Location |
|---|---|---|---|
| Apple | Authentication (Sign-In with Apple) & subscription/payment processing (IAP) | Apple ID, transaction IDs, subscription status | USA (EU-US Data Privacy Framework) |
| Authentication (Sign in with Google) | Google account identifier, email, name | USA (EU-US Data Privacy Framework) | |
| Stripe | Subscription and one-time payment processing for purchases made on the website | Email address, our internal user identifier, and purchase details (amount, currency, plan). If advertising measurement applies to you (see Section 11), the checkout session also holds your IP address, browser/User-Agent and Meta browser identifiers, so that we can report the purchase to Meta. Card details are entered directly with Stripe and never reach our servers. | USA (EU-US Data Privacy Framework) |
| Cloudflare R2 | Storage of AI-generated song tracks, user-uploaded songs used in exercises, performances you explicitly choose to share, and practice-run voice recordings and generated covers collected under the practice recordings setting | Song audio files; user-uploaded audio files and their processed outputs (linked to user account); shared performance recordings; raw microphone recordings of practice runs (linked to user account, never public) | EU-preferred regions |
| Resend | Transactional email delivery | Email address, email content | USA |
| Telegram | Error alerts & in-app support chat | Error data, user email, chat messages | Global |
| OpenAI | AI-powered chat support | Chat messages, user questions | USA |
| Simple Analytics | Privacy-first website analytics (page views, referrers) | No personal data — no IP addresses, no cookies, no tracking | Netherlands (EU) |
| Advertising-conversion measurement for our ad campaigns on Reddit, via the Reddit Pixel (see Section 11) | Pixel events (pages visited on our site, and whether you create an account) together with the technical data Reddit’s pixel collects automatically: cookie identifiers, IP address, and browser/User-Agent information. We do not send Reddit your email address, name, or other directly identifying account details. | USA | |
| Meta Platforms (Facebook / Instagram) | Advertising-conversion measurement for our ad campaigns on Facebook and Instagram, via the Meta Pixel and the Meta Conversions API (see Section 11); advertising audiences built from hashed customer email addresses (see Section 7.2); advertising-conversion measurement in our iOS app, via the Meta SDK (see Section 7.3) | Pixel events (pages visited on our site, clicks on our App Store links, and whether you create an account, upload a song or make a purchase) together with the technical data Meta’s pixel collects automatically: cookie identifiers, IP address, and browser/User-Agent information. Our server sends the registration, song-upload and purchase events to Meta directly (Meta Conversions API) with a hashed (SHA-256) copy of your email address, your IP address, your browser/User-Agent and the Meta browser identifiers (_fbp, _fbc). In the iOS app, the Meta SDK sends Meta the app install, app opens, App Store subscriptions and free trials, and the sign-up and song-upload events, with an app-installation identifier, your IP address and device information. We do not send Meta your name, your email address in readable form, your recordings or your songs. |
Ireland (EU) / USA |
We do not sell your personal data for money. We use the Reddit Pixel and the Meta Pixel on our website to measure how effective our advertising on Reddit, Facebook and Instagram is (see Section 11). For visitors in the European Economic Area and the United Kingdom, these pixels load only if you consent through our cookie banner; for visitors elsewhere they load by default and you can opt out as described in Section 11. The server-side events that we send to Meta follow the same consent rule. Our iOS app uses the Meta SDK for the same measurement (see Section 7.3). Under some U.S. state privacy laws (such as the California CPRA), the information shared with Reddit and Meta for advertising may be considered a “sale” or “sharing” of personal information. Apart from this advertising measurement and the Meta advertising audiences in Section 7.2, we do not share data with advertisers or ad networks.
PitchHighway offers a Model Context Protocol (MCP) server so that you can let an AI assistant of your choice — for example Claude (Anthropic) or ChatGPT (OpenAI) — read your PitchHighway data and, if you approve write access, add songs to your account. This only happens if you connect the assistant yourself: you add PitchHighway inside the assistant, sign in to your PitchHighway account on our authorisation screen, and approve the connection. The authorisation screen names the access the assistant asked for: read-only, or read and add songs. Personal access tokens generated in the web app before November 2026 keep working with read-only access; the web app no longer issues new ones. Nothing is shared until you connect an assistant.
A connected assistant can read these details from your account:
The server returns practice data, never the audio. Older clients can also read earlier progress summaries and cached voice reports.
The read-only connection at /mcp/readonly exposes only the 7 practice-data tools. Its OAuth tokens permit read-only access, including when a client uses another MCP endpoint. This connection cannot upload songs or generate media.
Every MCP tool is read-only except upload_song, which an assistant can call only if you approved write access. It adds a song from a YouTube link and uses one of your uploads, exactly as an upload in the app does. If your uploads are spent, the tool returns a link to our Stripe checkout page for one extra upload; the assistant never charges you, and no payment happens unless you complete it in your browser. No MCP tool can generate media, rename or delete songs, change account settings, or make payments.
Once an assistant has read your data, that data is processed by the assistant’s provider under their own privacy policy, which you should review. The provider acts as an independent controller of that data; we do not control what they retain.
You can end a connection at any time by removing PitchHighway from the assistant’s connector settings. Access tokens expire after 24 hours and refresh tokens after 90 days; expired token records are kept for a period after expiry to detect reuse of a replaced token (see Section 9), and all MCP tokens are deleted with your account. A personal access token can be revoked on request via the contact details in Section 15.
We may upload hashed (SHA-256) email addresses of our customers to Meta to build advertising audiences. A customer list lets us show our ads to people who already use PitchHighway, or leave them out of a campaign. A lookalike audience lets Meta show our ads to people who are similar to our customers. Meta uses the hashes only to find matching Meta accounts and deletes the hashes that do not match. We do not send your name, recordings, songs or practice data.
We leave out anyone who has unsubscribed from our marketing emails or deleted their account. To opt out, use the unsubscribe link in any of our marketing emails or delete your account. You can also email [email protected] to object.
Our iOS app includes the Meta SDK (Facebook SDK for iOS) to measure our advertising campaigns on Facebook and Instagram. The SDK sends these events to Meta: the app install, each app open, subscriptions and free trials that you buy through the App Store (with price and currency), account creation, and song upload. The song-upload event carries the internal ID of the song and tells whether the song came from a file or a YouTube link.
With each event, the SDK sends an app-installation identifier that it stores on your device, your IP address, and device and app information (such as device model, iOS version, app version, language and time zone). The app does not ask for tracking permission through Apple’s App Tracking Transparency, so the SDK does not get the advertising identifier (IDFA) of your device. Apple’s SKAdNetwork tells Meta which ads led to installs without identifying you. We do not send your name, email address, recordings or songs through the SDK.
The legal basis is our legitimate interest in measuring our advertising (Art. 6(1)(f)). You can object at any time by email to [email protected]. To disconnect this activity from your Meta account, use Meta’s “Your activity off Meta technologies” setting. To stop ads based on it, use your Facebook or Instagram ad settings. The SDK identifier is deleted when you delete the app. Meta processes this data under its own Privacy Policy.
Your personal data is primarily stored on servers within the European Union. Where data is transferred to service providers outside the EU (specifically Apple, Google, and Stripe, in the USA), such transfers are protected by:
Resend, OpenAI, Reddit, and Meta process data in the USA.
When you delete your account, we may keep a limited statistical summary to understand product usage before deletion and improve the Service. It contains broad brackets for account age, signup platform, premium access, practice activity, uploads and journey progress, plus whether song generation failed or a paywall was recorded. It does not contain your name, email, account or content identifiers (including hashed account identifiers), recordings, song names, messages, raw error text, or exact activity or deletion timestamps. No reason or questionnaire is required to delete your account. These observations do not establish why you left.
Access is restricted to internal analysis. Individual summaries are retained for the current and previous two calendar months. Our daily maintenance replaces older summaries with separate monthly totals for each measure, removing the individual combinations; those totals have no automatic expiry.
We retain your personal data only for as long as necessary to fulfil the purposes described in this policy:
| Data Category | Retention Period |
|---|---|
| Guest account data | Automatically deleted after 30 days of inactivity |
| Registered account data | Until you delete your account |
| Voice data (pitch samples, vocal range) | Until you delete your account (server-side). Audio recordings stay on your device except as described in Section 3.2. |
| Practice-run recordings (the “Practice recordings” setting) | Until you delete the cover, use “Delete my audio”, or delete your account (whichever comes first) |
| Note recordings | Until you delete them (“Delete all recordings” or “Delete my audio”) or delete your account (whichever comes first) |
| Community feed | No separate storage. Entries come from the last 7 days of activity (30 days for the leaderboard in older app versions) and stop appearing when you turn off “Show me in Community” or delete your account |
| Usage & progress data | Until you delete your account |
| Subscription data | Until you delete your account (Apple and Stripe retain their own records independently) |
| Launch notification email | Until the user requests deletion or unsubscribes, or 12 months after the app launch (whichever comes first) |
| Affiliate applications | Until we have replied and, for accepted affiliates, for the duration of the partnership — or earlier on request |
| Session records (hashed refresh tokens, device type, IP address) | Refresh tokens expire 180 days after issue. We remove the IP address from a session record 90 days after issue. All session records are deleted when you delete your account. |
| Web server logs (IP address, path, referring page, User-Agent, account ID) | 90 days, then deleted automatically |
| Approximate country | Until you delete your account |
| Password reset tokens | Until used or expired |
| Apple and Stripe webhook logs | Retained for operational integrity and debugging |
| Subscription payment ledger | Provider transaction and subscription references, charged amounts, currencies and payment dates are retained after account deletion for payment deduplication and reconciliation. No automatic expiry is currently applied. Deleting your account removes its campaign tags and the subscription-to-account link; these payment records contain no email or name. |
| Uploaded song data (original audio & processed outputs) | Until you delete the song or delete your account (whichever comes first) |
| Shared performance recordings | 30 days from sharing (or earlier on request, or when you delete your account) |
| Pitch diagnostics telemetry | Until pruned by periodic retention sweeps, or when you delete your account |
| Free-tier abuse-prevention identifier (hashed) | Retained after account deletion under our legitimate interest in preventing abuse, for no longer than necessary for that purpose |
| AI-assistant (MCP) OAuth tokens | Access tokens expire after 24 hours and refresh tokens after 90 days from issuance (each refresh replaces the previous one). Expired token records (hashed values only) are kept after the refresh token expires so that reuse of a replaced token can be detected, and are removed by routine cleanup once 30 days have passed since that expiry — or immediately when you delete your account |
| AI-assistant (MCP) personal access token | Until you ask us to revoke it (see Section 15) or delete your account |
| MCP tool-call records | Until you delete your account. These records have no automatic expiry. |
When you delete your account, account-linked personal data is deleted via cascading database deletion (subject to the retention exceptions below), including any songs you have uploaded and their processed outputs stored in Cloudflare R2. Any practice-run recordings, generated covers and note recordings are deleted along with the rest of your server-side data. You can also delete this audio without deleting your account: deleting a cover removes its recording, and “Delete my audio” in Account settings removes every cover, recording, note recording and shared performance at once. Audio recordings stored on your device are not affected by account deletion and remain under your control. Webhook logs and the subscription payment ledger are retained as described in the table above. We also retain a one-way hashed identifier (derived from your email, Apple ID, and/or Google account identifier, containing no plaintext email or name) to enforce free-tier upload limits across re-registration; it is used solely to prevent abuse and is kept for no longer than necessary for that purpose.
Under the GDPR, you have the following rights regarding your personal data:
How to exercise your rights: You may exercise your rights by emailing [email protected] with the subject line “GDPR Request.” You may also delete your account and all associated data, or only your audio (“Delete my audio” in Account settings), directly within the Service. We will respond to all requests within 30 days.
PitchHighway uses a JWT-based authentication system, not traditional browser cookies for session management.
ph_campaign cookie for up to 30 days; ph_campaign_consent stores your choice for the same period. In consent-required regions, we store the tags only after acceptance of the cookie banner. When you register, the tags are attached to your account so we can measure subsequent uploads and subscription purchases, including purchases on iOS using the same account. On iOS, tags received in an app link are retained locally for up to 30 days and attached to the signed-in account. These records do not contain an advertising device identifier or Facebook click identifier and do not identify every App Store install. Account-linked attribution is retained with your account and deleted when you delete it. Payment records used for this measurement have separate retention, described in Section 9.ph_practice_offer cookie keeps your test variant for up to 30 days. Your existing cookie choice controls this cookie where consent is required. A lesson click links the test variant to a new account. We then measure completed singing and return visits. We delete account-linked test data when you delete your account.?ref=), we set a first-party cookie holding only that partner’s public promo code, for 30 days. We use it to credit the partner if you subscribe and to apply their discount to your first payment automatically. It contains no identifier and is not used to track you across other websites._fbp and _fbc identifiers. These server-side events follow the same consent rule as the pixel. We do not send Meta your name or your email address in readable form. If you are in the European Economic Area or the United Kingdom, the Meta Pixel loads, and our server sends these events, only after you accept the cookie banner; you can withdraw your consent at any time by clearing this site’s cookies and site data in your browser, which makes the banner appear again so you can decline. If you are elsewhere, the pixel loads and the server-side events are sent by default. You can disconnect this activity from your Meta account with Meta’s “Your activity off Meta technologies” setting, and you can opt out through your Facebook or Instagram ad settings, by blocking third-party cookies or using tracking-protection/ad-blocking tools in your browser, or through the industry opt-out programmes linked above. Cookie blockers and ad blockers do not stop the server-side events. To stop them, turn on Global Privacy Control in your browser: our server treats the Sec-GPC signal as a refusal in every country. You can also email [email protected] and we stop them for your account. Meta processes this data under its own Privacy Policy.The Service is not directed at children under the age of 16 (the GDPR age threshold for consent to data processing). We do not knowingly collect personal data from children under 16. If we become aware that we have collected personal data from a child under 16, we will take steps to delete that data promptly. If you believe a child under 16 has provided us with personal data, please contact us at [email protected].
We implement appropriate technical and organisational measures to protect your personal data, including:
We may update this Privacy Policy from time to time. The “Last updated” date at the top of this page will be revised accordingly. For material changes that affect how we process your personal data, we will notify registered users by email. Previous versions of this policy are available upon request.
If you choose Facebook Login on the web, Meta shares your app-scoped account identifier, name and email address with us to create or sign in to your PitchHighway account. We request only public profile and email access. We use the authorization code and access token to verify the login and do not retain the Facebook access token.
To delete the PitchHighway data associated with Facebook Login, sign in at pitchhighway.com/login, open Account, choose “Delete account” and confirm. This removes the linked Facebook identifier with your account. If you cannot sign in, contact [email protected] to request deletion; we may need to verify account ownership. The retention exceptions described above still apply.
For privacy-related inquiries or to exercise your GDPR rights, please contact us:
We will respond to all GDPR requests within 30 days of receipt.