Last updated 17 September 2026
Privacy Policy
The Service holds two kinds of personal data: the names and emails of the people on your team, and the business figures those people log. This page says exactly what we do with both, who else touches it, how long it stays, and how to get it out.
1.Who we are
Coaches Corner KPIs at https://kpi.coachescorner.io is operated by [LEGAL ENTITY NAME], trading as Coaches Corner, of [REGISTERED BUSINESS ADDRESS]. For the data you enter into a workspace, the business that owns the workspace is the controller and we are its processor. For the data we collect to run this website, bill you and support you, we are the controller.
Privacy questions and requests: [CONTACT EMAIL].
2.What we collect, and why
Account and team data. Name, email address and role of each person who is invited to a workspace, plus the times they sign in. We need it to send sign-in links, scope what each person can see, and show who logged what. Lawful basis: performing our contract with the workspace owner.
Workspace data. The business figures your team logs — leads, calls, bookings, sales, refunds, client counts, churn, ad spend, ledger entries, targets, notes — and anything you import from a spreadsheet or pull in through an integration. This is mostly business data, but it can identify people: team members appear by name against their numbers, and imported records may name clients. We process it only to run the Service for you, on the owner’s instructions.
Your clients’ roster and check-ins. If you use the Clients feature, we store the clients you add: their name, the email address they check in from, their program, dates, cadence, payment structure and amount, and any notes you write. When a check-in arrives from your form we record that it arrived — who from, which date it was for, and when it landed. We do not store what your clients wrote in it. Their weight, measurements, how they slept, how they felt and anything else they tell you stays in your own form, and the script you paste into it does not send those answers to us. Lawful basis: performing our contract with the workspace owner, who is the controller of their clients’ data and instructs us to process it.
Messages between your team. If you use Messages, we store what your team writes to each other in the workspace — the message, who wrote it and when. Only the people in a conversation can read it, and that includes owners and admins: a direct message between two colleagues is not visible to anybody else in the workspace, by design and not by setting. The author can delete their own message; nobody else can delete it for them. Lawful basis: performing our contract with the workspace owner.
Billing data. Billing name, email, company and the last four digits of the payment method, plus invoices. Card numbers are held by Stripe and never reach our systems. Lawful basis: contract and our legal obligation to keep financial records.
Support and contact. Whatever you send us when you email or book a call. Lawful basis: our legitimate interest in answering you.
Technical logs. Our host records the IP address, browser user agent, URL and timing of each request for up to 30 days, for security and debugging. We do not build profiles from these logs. Lawful basis: our legitimate interest in keeping the Service secure and working.
We do not collect data from children, do not use special-category data, and do not run advertising or behavioural analytics on this site.
3.If your details are in someone else's workspace
If you are a setter, closer, coach or manager whose name and email have been added to a workspace, the business that runs that workspace decided to hold your details there and is responsible for telling you. We process them on that business’s instructions. Questions about why you are in a workspace, or requests to be removed from it, should go to the workspace owner first; if you cannot resolve it with them, contact us and we will help.
4.Optional integrations and the AI connector
Every integration is off until the workspace owner turns it on, and every one is read-only — the Service pulls data in and never writes back. Disconnecting stops further reads immediately.
- Stripe (your own account): Charges, refunds, subscriptions and payouts, to reconcile revenue and cash
- GoHighLevel: Pipeline, opportunity and appointment records, to populate the sales funnel
- AI connector (MCP): Aggregate KPI figures — totals, rates and trends — served to an AI assistant the owner has authorised. Never individual client records, contact details or raw ledger lines.
The AI connector deserves a plain statement: when enabled, an AI assistant the owner has authorised (through a standard OAuth flow they can revoke) can request aggregate KPI figures — totals, rates and trends. It cannot retrieve individual client records — your roster, your clients’ check-ins and your team’s messages are not exposed to it at all — nor contact details, team members’ email addresses or raw ledger lines. The AI provider’s own privacy terms govern what it does with the figures it receives; we do not send anything to any AI provider ourselves.
6.Where data is stored
Workspace data lives in a Supabase-managed Postgres database in the region shown above, with encrypted backups in the same region. Our application runs on Vercel’s global network, so a request may be served from a location near you while the data it reads stays in the database region. Where personal data is transferred out of the UK or EEA we rely on the provider’s standard contractual clauses and, for US providers, their certification under the Data Privacy Framework where they hold it.
7.How we protect it
- Every workspace is isolated by row-level security enforced inside the database, not just in code.
- All traffic is encrypted in transit (TLS); the database and its backups are encrypted at rest.
- Sign-in is by single-use emailed link. There are no passwords for us to store or for anyone to leak.
- Integration credentials are encrypted and can be revoked by the owner at any time.
- Staff access to production data is limited to named people, used only to resolve issues, and logged.
If something goes wrong. If we become aware of a breach that affects personal data in your workspace, we will tell the workspace owner without undue delay and in any case within 72 hours of confirming it, with what we know about what was affected, what we have done, and what we recommend you do. We will co-operate with any notification you need to make to a regulator or to the people affected.
8.How long we keep it
- Workspace data — for as long as the subscription is active, then a 30-day read-only period, then deleted from the live database. Backups roll off within a further 30 days.
- Team member records — until the owner removes the person from the workspace, or the workspace is deleted. Removed members’ historical entries stay attributed to them, as a business record, until the workspace is deleted.
- Billing records — 7 years, as financial-record law requires.
- Support email — 2 years after the last message.
- Request logs — up to 30 days.
- Demo cookies — 30 days from last visit; nothing is stored server-side for the demo.
10.Your rights
Depending on where you are, you have the right to:
- Access the personal data we hold about you, and get a copy of it;
- Correct anything inaccurate;
- Delete it, where we no longer have a reason to keep it;
- Export it in a machine-readable form (workspace owners can do this themselves as CSV from Settings at any time);
- Restrict or object to processing based on legitimate interest;
- Complain to your data-protection regulator — in the UK the ICO, in the EU your national authority — though we would rather you told us first.
Email [CONTACT EMAIL]. We answer within 30 days and do not charge. Where your data sits in a customer’s workspace we will pass the request to that customer and help them respond. We may need to confirm who you are before acting.
Deleting a whole workspace. The owner can ask us to delete a workspace at any time by email. We confirm the request with the owner, delete it from the live database within 7 days, and confirm when backups have rolled off.
11.Changes to this policy
We will post changes here and update the date at the top. For anything that changes what we collect or who we share it with, we will email workspace owners at least 30 days in advance.