The Pronunciation Refinery

The Pronunciation Refinery · Legal

Privacy policy

Effective 8 November 2026

This notice explains how James Leyshon T/A The Pronunciation Refinery, the controller of your course-account information, uses personal data.

1. Contact and scope

Email [email protected] . Postal/business address: 84 Victoria Road, Bradmore, Wolverhampton, WV3 7EU, United Kingdom.

It covers the website, Account, subscriptions, learning progress, Tools and support. It is not a statement that every supplier acts only as our processor.

2. Information and lawful bases

We use course and account information to provide the features you request; security and technical logs help us prevent abuse and diagnose faults. We balance these interests against your rights and limit what we collect. Tools process the examples you enter to return a pronunciation result; avoid adding private or sensitive information. If you use community features, Supabase stores your author identifier/name, post title/body, replies and timestamps. Other members can see what you publish there. We do not use course text to decide your eligibility for credit, employment or insurance.

Account and payment details are needed for paid access; without them we cannot provide membership. Do not put sensitive personal information into pronunciation examples. We do not use this course to make automated decisions with legal or similarly significant effects .

Marketing: we will send promotional emails only after a separate, optional consent. Buying the course or agreeing to these terms is not marketing consent. You can unsubscribe at any time without losing paid access. Necessary account/security/order messages are separate. No newsletter sending workflow was found in the inspected implementation.

Performance measurement: the observed Cloudflare Web Analytics beacon uses aggregate page/performance information rather than tracking cookies or user profiles. Our interest is maintaining a reliable, usable course; we do not use it to make individual marketing decisions.

3. Providers and recipients

Supabase

Authentication, account database, membership and backend functions. Observed project region: Frankfurt (eu-central-1). Supplier support, subprocessors and function execution may involve other locations.

Stripe

Merchant of record through Stripe Managed Payments: payment collection, transaction records, refunds, tax compliance where covered, fraud controls, disputes and transaction support. Stripe processes relevant identity, contact, billing and payment information for its own merchant, legal and compliance responsibilities as an independent controller. It is not merely our payment processor. We receive the identifiers and payment/subscription status needed to provide course access.

Read Stripe’s privacy policy for its processing and your rights with Stripe.

Resend

Transactional email delivery and delivery logs. Observed sending region: Ireland (eu-west-1). This alone does not establish where all support or log data is processed.

Cloudflare

Website hosting, network delivery, security, request logs and email routing. Its global network can process request information internationally.

Embedded YouTube players also receive information when loaded. Professional advisers or public authorities may receive information where necessary for legal obligations or claims. We do not sell personal data.

Our suppliers are Supabase, Stripe, Resend and Cloudflare, with Google/YouTube involved if you choose their video players. Stripe acts as an independent controller for its merchant-of-record purposes; other providers process relevant data under their applicable service/data-protection terms, and may act as controllers for their own legal/security purposes. Current provider privacy and subprocessor information is linked below. We do not present every provider as only our processor.

Provider information: Supabase privacy · Stripe privacy · Resend privacy · Cloudflare privacy. Supplier support/subprocessor access must be checked against the actual contracted terms, not inferred from a region label.

4. International transfers

Some suppliers or their support/subprocessors may process data outside the UK, including in the EEA or US. Where required, we must rely on applicable adequacy regulations or appropriate safeguards, such as the UK IDTA or UK Addendum to EU standard contractual clauses, with the necessary transfer assessment. Ask us for information about the safeguards applying to your data.

Supabase’s observed project region is Frankfurt and Resend’s sending region is Ireland. Cloudflare operates globally; payment, email, media, support and supplier subprocessors may involve the UK, EEA, US or other countries. A hosting region does not prove all processing stays there. Our policy is to require an applicable UK adequacy regulation or appropriate safeguards, such as the UK IDTA or UK Addendum, with the required assessment for a restricted transfer. Contact [email protected] for information about the safeguards applying to your data. This notice is not evidence that a particular contract or transfer assessment has been executed.

5. How long we keep it

Account/learning information is kept while needed to provide your account, then deleted or anonymised when no longer needed. Accounting, payment and legal-claim records are retained for the applicable statutory or claims period. Security/support/email logs are kept only for a justified operational period. Browser storage can remain until you clear it or the application removes it.

Our retention schedule is: account and learning records while the Account is open, then up to 24 months after the last paid membership ends, to allow return to the course; before closing a dormant Account we aim to give 30 days’ notice. Support correspondence: up to 2 years after resolution. Routine security/request logs: up to 90 days, longer only for a specific incident or legal hold. Transactional email bodies/delivery logs: a 30-day operational target, subject to the provider’s available retention controls. Keep only a minimal welcome-send marker while the Account exists to avoid duplicate welcomes. Contract/consent and dispute evidence: up to 6 years after the relevant contract ends where needed for legal claims. Sole-trader tax records: at least 5 years after the 31 January filing deadline for the relevant tax year, longer if required by an enquiry or other law. Backup copies are restricted, not used for ordinary processing and removed through the provider’s rotation; our deletion target is within 90 days where supported. Minimal marketing suppression records are retained to respect an opt-out. We review these periods and delete or anonymise information no longer needed. These are the operating rules for this policy, not a claim that automatic deletion jobs or supplier log limits have already been configured.

6. Your rights

Depending on the circumstances, you can request access, correction, erasure, restriction or portability. You may object to processing based on legitimate interests, and to direct marketing at any time. You may withdraw consent where we rely on it. Some records must be retained by law.

Email us to exercise a right. We normally respond within one month; permitted extensions and any necessary identity checks will be explained. Requests are normally free. You can complain directly to the Information Commissioner’s Office, whether or not you contact us first.

7. Storage and changes

Read our cookie and local-storage notice. Material changes to this notice will be explained where required. Last reviewed: 8 November 2026.