Your data: request a copy

Under UK GDPR Article 15, you have the right to receive a copy of all personal data Badminton Clubhouse holds about you. We make this self-serve at /me/data.

What you get

A .zip archive containing:

README.txt: plain-English orientation
summary.html: opens in any browser; one-page overview of categories and record counts
manifest.json: schema version, generation timestamp, complete inventory of tables and record counts, pseudonymisation method

data/.json: one file per category (memberships, games, payments, notifications, audit log, etc.). Empty categories are still included so you can verify the inventory is complete.How to request it Sign in and visit /me/data. Click Request my data. Confirm in the dialog. Watch the page for the status (pending → running → ready), usually under 5 minutes for typical accounts. You'll also receive an email when it's ready. Click Download to fetch the archive via a 24-hour signed link. Rate limit: one request per 28 days UK ICO guidance permits us to refuse "manifestly excessive" requests, in particular repetitive ones. We enforce a 28-day cooling-off period between requests per subject. If you need an additional export sooner, for example a court order, an active grievance, or you genuinely lost the previous download, email privacy@badmintonclubhouse.com with a brief reason and we'll override. What's pseudonymised, and why Some records describe activities involving you and other people: a doubles game has four players; a session booking has a different person who confirmed your place. We can't expose other people's identifying details to you without doing a separate balance test for each, so in the archive: Other users' user_id values are replaced with opaque tokens (psn:<12-character-hash>). The same person across multiple rows in your export gets the same token, so you can spot patterns. The token is unique to this export, it doesn't match a token in your previous or future archives. Other parties' first_name, last_name, email, phone, and postcode columns are replaced with . If you need to know who a specific psn:... token refers to, email privacy@badmintonclubhouse.com. We'll do a one-off legitimate-interest balance test per the UK ICO's guidance under Art. 12, then either reveal or refuse with reasons. How long we keep the archive The download link expires 24 hours after we send it. The archive itself is retained for 28 days then deleted automatically. A small audit row (date, requester, scope) is kept for 7 years as proof we responded, that audit row does not include the personal data itself. Rectification and erasure (Art. 16 & 17) This page is for access requests only. For: Rectification: fixing wrong data, use the in-app edit controls on /me/profile, /me/settings, and each tenant's settings page. For data you can't edit yourself, email privacy@badmintonclubhouse.com. Erasure: fully deleting your account, use the Delete my data card on /me/data. We give you a 30-day cooling-off window before the deletion becomes permanent. See Deleting your account for the full breakdown of what gets deleted, what we keep (financial records, audit log, safeguarding) and why, and the cancel paths. On behalf of a junior If you are the active guardian of a junior player, you can request the junior's data via the Juniors area at /me/juniors//data. The same archive is generated, scoped to the junior. Tenant-fulfilled requests If you receive an email saying "an administrator at has requested a copy of your data", that means the club's secretary (DPO function) fulfilled a SAR on your behalf, usually because you asked them in writing, or because you are a vulnerable adult and the club is handling it as accessible-format support. You can see what was requested in the email and you'll get the same download link the administrator did. If you didn't ask for this, reply to the email, we treat unexpected admin requests as a potential safeguarding incident. Quick portability snapshot The /me/data page also has a small Download a JSON-only archive link at the bottom. It hits /api/me-data-export directly and streams a synchronous ZIP, a smaller JSON-only archive that's useful for a quick portability snapshot. The full asynchronous flow above is the formal Article 15 fulfilment; the inline link is fine for everyday "just give me my data" use. Was this article helpful? PreviousUnderstanding Your DashboardNextDeleting your data (UK GDPR Art. 17) Related Articles Fulfilling a Subject Access Request (GDPR Art. 15) How a club committee user (typically the secretary acting as DPO) fulfils a UK GDPR Article 15 SAR on behalf of a member who can't operate the self-serve flow.GDPR Right to Erasure (Art. 17): committee playbook How to fulfil a right-to-erasure request on behalf of a member as the club's DPO function.