Skip to main content
Skip to content
TAPStart your release
§ Legal

Privacy policy.

Last updated: 4 November 2026

1. Introduction

Chris Schofield, trading as Total Audio Promo (“TAP”, “we”, “us”, or “our”) operates totalaudiopromo.com and related services. We aim to meet the requirements of the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018.

Data Controller: Chris Schofield, trading as Total Audio Promo
Address: 56 Lynton Street, Brighton BN2 9XR, United Kingdom
ICO registration number: ZC293866
Contact: info@totalaudiopromo.com

2. Information We Collect

2.1 Account Information

When you create an account, we collect your name, email address, and authentication credentials (managed by our authentication provider, Supabase).

2.2 Workspace Data

Data you create within TAP, including releases, artist rosters, contact lists, pitch drafts, and outreach records. This data is stored in your workspace and accessible only to workspace members.

2.3 Usage Data

With consent, we collect page visits, feature use and performance data, and record masked sessions in PostHog’s EU region. Separately, to run and measure the service, we record a small set of account events without analytics cookies: payments, pitches sent and replies received. These carry only IDs and counts, never message content, contact details or card data. You can ask us to stop at any time.

3. How We Use Your Data and Our Lawful Basis

UK GDPR requires a lawful basis for each use of personal data. These are ours:

  • Running your account and workspace, drafting and sending pitches on your behalf, and handling replies: Contract: we need it to provide the Service you signed up for.
  • Taking payment and keeping billing records: Contract, and legal obligation for the records UK tax law requires us to keep.
  • Service emails: receipts, renewal reminders, security and account notices: Contract.
  • Analytics cookies and masked session recordings (PostHog): Consent, which you give or refuse in the cookie banner and can withdraw at any time.
  • Account events recorded without cookies (payments, pitches sent, replies received), error monitoring, and telling us when someone signs up: Legitimate interests: running, measuring and fixing the Service.
  • Security and abuse prevention, such as bot checks and rate limits by IP address: Legitimate interests: keeping the Service and its users safe.
  • Newsletter and marketing emails: Consent, given by ticking a box when you sign up. You can unsubscribe at any time.
  • Answering support and data protection requests: Legal obligation where the law requires a response, otherwise legitimate interests.

Where we rely on legitimate interests, you can object (see Section 8). For contacts in your workspace, you decide why they are processed and TAP acts on your behalf; see the Data Processing Addendum.

4. How We Protect Your Data

Your data is stored using Supabase (hosted on AWS in the EU region). Payment information is processed by Stripe and never stored on our servers. These are the safeguards that protect your data, including sensitive data such as Google account access and the content of files you import:

  • Encryption in transit: every connection to TAP uses HTTPS (TLS), and our site requires it through HTTP Strict Transport Security. Our servers also use TLS when they talk to Google, to our database and to our AI provider.
  • Encryption at rest: our database and file storage are encrypted at rest with AES-256. On top of that, Google access and refresh tokens, mailbox app passwords and other connected-service credentials are encrypted by TAP with AES-256-GCM before they are saved. The key is held in our hosting provider’s secret store, separately from the database.
  • Access control: row-level security keeps each workspace’s data visible only to that workspace’s members. Refresh tokens, app passwords and API keys stay on our servers, and your browser never receives a Google credential. TAP staff access your data only to resolve a support request you raise, to keep the service secure, or where the law requires it.
  • Minimum access: we ask for the narrowest Google permission each feature needs, and only when you turn that feature on (see Section 5.1).
  • Retention and deletion: disconnecting a Google account revokes our access with Google and deletes the stored tokens and the email records synced through that connection. You can ask us to delete your account and its data at any time by writing to info@totalaudiopromo.com; we complete deletion within one month. Section 6 sets out how long we keep each kind of data.
  • Breach response: if a personal data breach occurs, we report it to the UK Information Commissioner’s Office within 72 hours of becoming aware of it, where the law requires, and tell affected users without undue delay.

5. Third-Party Services

These services process personal data for us. Where a provider is outside the UK, we name the safeguard UK GDPR requires for the transfer, or say where we have not yet confirmed it.

  • Supabase: Authentication, database and file storage. Where: Hosted on AWS in the EU; Supabase Inc. is in the US. Safeguard: EU hosting is covered by UK adequacy regulations. Transfer safeguard not yet confirmed by us; we are checking it against the provider’s data processing terms.
  • Vercel: Application hosting; our server functions run in London. Where: Vercel Inc., US. Safeguard: Transfer safeguard not yet confirmed by us; we are checking it against the provider’s data processing terms.
  • Stripe: Payment processing. Card details go to Stripe, never to us. Where: Stripe Payments Europe (Ireland) and Stripe Inc. (US). Safeguard: Transfer safeguard not yet confirmed by us; we are checking it against the provider’s data processing terms.
  • Resend: Service emails, pitches sent through the via-TAP channel, and the reply relay. Where: US. Safeguard: UK Extension to the EU-US Data Privacy Framework (UK-US Data Bridge). Resend announced its certification on 13 March 2025.
  • PostHog: Analytics, with your consent. Where: EU region (data stored in the EU); PostHog Inc. is in the US. Safeguard: EU hosting is covered by UK adequacy regulations, and PostHog’s data processing agreement states participation in the UK Extension to the EU-US Data Privacy Framework (UK-US Data Bridge).
  • Sentry: Error monitoring, so we can find and fix faults. Where: EU (Germany) data region; Functional Software Inc. is in the US. Safeguard: EU hosting is covered by UK adequacy regulations. Transfer safeguard not yet confirmed by us; we are checking it against the provider’s data processing terms.
  • OpenRouter: Routes our AI requests to a hosting provider for DeepSeek V4.1 Flash, with Z.ai GLM Flash as a fallback. Every request is restricted to providers that do not collect user data and to endpoints with a zero data retention policy, so prompts are neither stored nor used for training. OpenRouter picks the cheapest provider that meets those rules, so which provider serves a request, and in which country, is not fixed in our code.. Where: OpenRouter Inc., US; downstream providers vary. Safeguard: Transfer safeguard not yet confirmed by us; we are checking it against the provider’s data processing terms.
  • TypeSafe: Helps sort replies to your pitches. It receives only a de-identified version of a reply’s opening lines, with names, email addresses, links, phone numbers, social handles, postcodes and sign-offs removed. It never receives your mailbox credentials or any data from Google APIs.. Where: Not yet confirmed. Safeguard: Transfer safeguard not yet confirmed by us; we are checking it against the provider’s data processing terms.
  • Google: Google sign-in, your Gmail mailbox (via IMAP and SMTP) and sending with Google, each only when you connect them (see Section 5.1). Where: Google LLC, US. Safeguard: Transfer safeguard not yet confirmed by us; we are checking it against the provider’s data processing terms.
  • Cloudflare: Turnstile bot checks on public forms. Where: Cloudflare Inc., US. Safeguard: Transfer safeguard not yet confirmed by us; we are checking it against the provider’s data processing terms.
  • Upstash: Rate limiting, which briefly stores IP addresses and request counts. Where: Not yet confirmed. Safeguard: Transfer safeguard not yet confirmed by us; we are checking it against the provider’s data processing terms.
  • Inngest: Runs background tasks, receiving the data each task needs. Where: Inngest Inc., US. Safeguard: Transfer safeguard not yet confirmed by us; we are checking it against the provider’s data processing terms.
  • Perplexity, Exa and Firecrawl: Contact and outlet research. They receive a contact’s name and outlet, or an outlet’s public web address, never your account data. Where: US. Safeguard: Transfer safeguard not yet confirmed by us; we are checking it against the provider’s data processing terms.
  • Discord: Tells us when someone signs up, with their name and email address. Where: Discord Inc., US. Safeguard: Transfer safeguard not yet confirmed by us; we are checking it against the provider’s data processing terms.
  • Spotify, Last.fm and YouTube: Public music data lookups. They receive artist and track names only. Where: Various, including the US. Safeguard: Transfer safeguard not yet confirmed by us; we are checking it against the provider’s data processing terms.
  • Dub: Referral links, only while the referral programme is running. Where: US. Safeguard: Transfer safeguard not yet confirmed by us; we are checking it against the provider’s data processing terms.

5.1 Google API Services Disclosure

TAP’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Your mailbox: app password, not a Gmail API scope

We do not request any Gmail OAuth scope to read your mailbox. TAP reaches your mailbox using an app password that you generate in your own Google account and paste into TAP, over the standard IMAP and SMTP protocols. That credential is stored encrypted against your workspace and is used for exactly two things:

  • Reading, to match replies: We read message metadata (sender, recipient, subject line, timestamp, thread ID) to detect replies to your pitches and track release outcomes. For a reply to one of your pitches, we also read its opening lines and send them to our AI provider (under the restrictions in Section 5) to tell a real reply from an automated one. A de-identified version of those lines may also go to TypeSafe to help sort the reply (see Section 5). We do not store the full body of your emails.
  • Writing, only what you approve: We save drafts into your mailbox and send messages from your own address. By default, a named person in your workspace approves each pitch. They can also approve ready pitches together. See Section 5.2 for these approval modes.

You can revoke this at any time by deleting the app password from your Google account, or by disconnecting from Settings > Integrations. Either takes effect immediately.

Sending your pitches with Google sign-in

If you connect Gmail with Google (in Settings > Connections, or on a release when you first send), TAP requests the gmail.send scope separately from the app-password mailbox access above: access to send mail as you, and nothing else. We cannot read, search, or otherwise view your mailbox through this grant. Sending is subject to the approval mode you choose in TAP: individual review or approval of ready pitches together, as described in Section 5.2. You do not need the app password connection if you use Google sign-in to send. You can revoke gmail.send at any time from your Google Account permissions page or by disconnecting in Settings > Integrations.

What we do request through Google sign-in

When you connect Google, TAP asks for these scopes and no others:

  • openid, userinfo.email and userinfo.profile: to sign you in with Google and know which Google account you connected.
  • gmail.send: only if you connect Gmail with Google, to send pitch emails using your connected account, subject to the approval modes described in Section 5.2.

Data storage and retention

Email metadata and imported press release text are stored in your workspace database, protected by the safeguards in Section 4. Only members of your workspace can access this data. App passwords and OAuth tokens are encrypted by TAP with AES-256-GCM before they are saved. We do not share, sell, or transfer Google user data to third parties, except as necessary to provide the feature you asked for. No TAP team member reads this data except to investigate a specific support issue the connected workspace's own member raises.

Google user data and AI

No data TAP obtains through Google APIs is sent to an AI model. TAP requests no Google Drive scope: if you paste a link to a publicly shared Google Doc or PDF as your press release, TAP reads it as any visitor could, without your Google account, and that text goes through OpenRouter to the models listed in Section 5, restricted to providers that do not collect user data and to zero data retention endpoints. We do not use Google user data, whether raw, aggregated or derived, to create, train or improve generalised or foundational artificial intelligence or machine learning models, and we do not allow our providers to.

Revoking access

You can disconnect your Google account at any time from Settings > Integrations. This immediately revokes our access. You can also revoke TAP’s access directly from your Google Account permissions page, and the mailbox app password from the link above.

5.3 Replies to Your Pitches

So you can see who replied without giving TAP access to your mailbox, pitches can carry a reply address on reply.totalaud.io, a domain we operate. When a contact replies, the message reaches TAP through Resend. We store the sender, subject, time and the first 280 characters of the reply against your release, so your replies and results stay up to date, and we forward the full message to your own email address with the sender set as the reply-to, so you answer them directly. This does not use any Google API and gives us no access to your mailbox. Messages sent from your own address to the reply address are not forwarded back to you.

5.2 Send-on-Behalf-Of

TAP can send pitch emails using your connected Gmail account (through SMTP with an app password, or Google sign-in with the gmail.send scope), or through TAP's sending service where that channel is available and selected for your workspace. TAP sends a pitch only after a named person in your workspace has approved it, as described below.

Approval is required before sending. A named person in your workspace approves every pitch before TAP dispatches it, either one at a time or all ready pitches at once. An agent cannot approve a pitch on its own. Approval is the safeguard, not the channel. See the Data Processing Addendum for the contractual detail.

When you send through Gmail, the From address is your connected mailbox. Replies may use TAP's reply relay so they can be logged and forwarded to you (Section 5.3). With the via-TAP channel, the From identity includes your artist name and “via Total Audio Promo” on TAP's sending domain, with a relay Reply-To address. The sending identity is shown for approval. A failed Gmail connection is not silently replaced with the via-TAP channel.

6. How Long We Keep Your Data

  • Your account and workspace data: Kept while your account is open, including if it is inactive. We currently have no automatic deletion for inactive accounts; we are working to add a retention policy. If you ask us to delete your account, we do so within one month.
  • Contacts, releases and artists you delete: Hidden straight away, then permanently deleted by a daily job 30 days later.
  • Google tokens and email records synced through a Google connection: Deleted when you disconnect that Google account.
  • Replies recorded through our reply relay (sender, subject, time, first 280 characters): Kept with your release while your account is open. We currently have no separate deletion period for them.
  • Records of the emails we send you: Kept while your account is open and deleted with it.
  • Payment and billing records: Kept for at least as long as UK tax law requires. We currently have no automatic deletion after that; we are working to add a retention policy.
  • Consent records (cookie choices, marketing consent, and the 14-day cancellation consent given at checkout): Kept as evidence of what you agreed to. We currently keep them indefinitely; we are working to add a retention policy.
  • Analytics (PostHog) and error reports (Sentry): Kept under each provider’s standard retention for our plan. We have not set a shorter period of our own.
  • Rate-limit counters: Expire automatically when the rate-limit window ends, typically within minutes.

7. People in the TAP Curator Network

This section is for radio presenters and producers, journalists and playlist curators whose details TAP holds. The network is opening by personal invitation. Nobody is added to it without answering an invite.

What we hold and where it came from

Your name, professional email address, the outlet, station or show you work for, the kinds of music you cover, and a record of past pitches and any replies or plays. Most of it comes from Chris Schofield’s own professional contacts, built over his career as a freelance radio promoter. The rest comes from public submission pages.

Why, and our lawful basis

To put new music in front of the people most likely to want it. Our lawful basis is legitimate interests: matching artists with the right contacts, with safeguards that keep the volume low and the fit high.

Who sees it

Only artists whose release fits what you cover, and only once you have opted in to the network, or where you run a public submission route.

What we store when you answer an invite

Each invite is a personal plain-text email with two links: one to your private preferences page and one that says “No thanks”. If you opt in, we store the genres, formats and delivery method you choose, how many pitches a week you will take, any quiet periods and notes you add, and the name, outlet and show you confirm. We also store a consent record: the exact wording you agreed to and its version, where you agreed (the invite email or your preferences page), and the date and time. A separate log keeps one line for each opt-in, change and opt-out, with the time and the option you ticked if you gave a reason for declining.

How long we keep it

If you neither opt in nor engage within 12 months, we remove you from the pool. The automatic 12-month removal is not built yet. If you say “No thanks” or leave the network, we delete your preferences and keep your email address on a permanent suppression list, with the log line that records your choice. Nothing else is kept. The suppression list applies across every TAP workspace, so no TAP artist pitches you again.

Your rights, and how to leave

You have the same rights as everyone else under this policy (Section 8), including the right to object, to see what we hold and to have it erased. Your preferences page has no public address. The link is in your invite email, and it is yours alone. Use it to opt in, change your preferences or leave. “Leave the network” on that page and “No thanks” in the invite are both permanent and take effect at once. Links expire after 90 days. If yours has, or you cannot find your invite, email info@totalaudiopromo.com and we will act on it.

8. Your Rights

Under UK GDPR, you have the right to:

  • Access your personal data
  • Rectify inaccurate data
  • Request erasure of your data
  • Restrict or object to processing
  • Data portability
  • Withdraw consent at any time

To exercise these rights, contact info@totalaudiopromo.com. We respond within one month.

You also have the right to complain to the Information Commissioner’s Office (ICO), the UK data protection regulator, at ico.org.uk/make-a-complaint or by calling 0303 123 1113. The ICO asks you to raise your concern with us first and give us the chance to put it right.

9. International Users

We serve users globally. Depending on where you live, you may also have rights under local law, including:

  • California (CCPA/CPRA): California residents have the right to know what personal information is collected, request deletion, and opt out of the sale of personal information. We do not sell personal information.
  • Canada (PIPEDA): Canadian users have the right to access and correct their personal information. We obtain meaningful consent for the collection, use, and disclosure of personal data.
  • Australia (APPs): Australian users are protected under the Australian Privacy Principles. We take reasonable steps to protect personal information from misuse, interference, and loss.

We do not sell your personal information to any third party, regardless of your location.

10. Changes to This Policy

We may update this policy from time to time. We will notify you of significant changes via email or an in-app notification.