Privacy Policy
Version 1.1 · last updated 13 November 2026
1. Who We Are
Vardeck ("we", "us", "our") provides compliance management software for UK leisure facilities. When your organisation uses Vardeck, your organisation is the data controller and Vardeck acts as a data processor under UK GDPR and the Data Protection Act 2018.
Vardeck is provided by Vardeck Ltd.
For enquiries about this policy, contact: privacy@vardeck.app
When Vardeck Is The Controller
For some data Vardeck decides why and how it is used, so we are the controller of it:
- Our customers' contacts and billing: the name, email and phone number of the people who sign an organisation up or manage its subscription, and the billing records of the subscription. Used to provide and charge for the service (contract), and kept for 6 years after the end of the financial year for tax law.
- Sign-up, demo and feedback messages: name, email, organisation and what you wrote. Used to reply (legitimate interests), and deleted 2 years after the last contact.
- Security logs: sign-ins, failed sign-ins and other security events, with the account, IP address and browser. Used to keep the service and your account secure (legitimate interests), and deleted after 2 years.
- Website visitors: only the strictly necessary cookies described in our Cookie Policy.
2. What Data We Collect
"Encrypted at rest" below means the field is stored encrypted (AES-256) in the database and only decrypted by the application for people allowed to see it. Fields not marked are protected by access controls and encrypted connections, but are not individually encrypted.
Staff Users (via your organisation)
- Name, job title, role
- Email address (encrypted at rest, with a keyed hash used to find the account)
- Phone number, town, county and postcode (encrypted at rest)
- Emergency contact details (encrypted at rest)
- DBS check and right to work references (encrypted at rest); check dates
- Pay, National Insurance number and bank details (encrypted at rest)
- Medical notes where provided (encrypted at rest)
- Kiosk PIN (hashed, not stored in plaintext)
Parents / Guardians (via the Parent Portal)
- Name and email address
- Phone number and postcode (encrypted at rest); first lines of the address
- Emergency contact details (encrypted at rest)
- Marketing preferences, with a record of when and how they were given
- Payment information (processed by Stripe or GoCardless, card and bank details are not stored by Vardeck)
Pupils (Children)
- Name, date of birth
- Medical notes, allergies, SEND (additional needs) notes, general notes and emergency contacts (encrypted at rest)
- Teachers' lesson notes about a child (encrypted at rest)
- Safeguarding concerns: the description, the child's words, actions taken and outcomes (encrypted at rest)
- The parent's choices about photography, emergency medical treatment and health information, with when and by whom they were given
- Lesson attendance, skill progress, certificates
Spa and Treatment Clients
- Consultation (health) questionnaire answers given before a treatment, with the client's name and email (encrypted at rest)
Technical Data
- IP address and browser user agent (for session security and consent records)
- Session data (encrypted in database)
- Activity audit logs (what actions were taken, by whom, when). Encrypted fields such as health details are left out of the log.
- Marketing email engagement: marketing emails sent on your organisation's behalf contain a small tracking image (a "pixel") and tracked links, which record whether and when an email was opened and which links were clicked. This is used for campaign statistics and to avoid over-mailing. Transactional emails (bookings, receipts, password resets) are not tracked. Every marketing email includes an unsubscribe link; unsubscribing stops further marketing and the tracking that goes with it.
3. Lawful Basis for Processing
| Processing Activity | Lawful Basis (UK GDPR Art 6) | Special category condition (Art 9 / DPA 2018) |
|---|---|---|
| Staff account management | Contract (employment), Art 6(1)(b) | Employment health records: Art 9(2)(b) with DPA 2018 Sch 1 para 1 |
| Pupil lesson booking, attendance and progress | Contract with the parent (service provision), Art 6(1)(b) | — |
| Pupils' medical notes, allergies and SEND notes given by a parent | Contract, Art 6(1)(b), or legitimate interests in keeping children safe in lessons, Art 6(1)(f) | The parent's explicit consent, Art 9(2)(a), given as a separate statement when the details are entered. Where the details are needed to protect a child and consent cannot be given or obtained: DPA 2018 Sch 1 para 18. In a genuine emergency where nobody can consent: vital interests, Art 9(2)(c). |
| Treatment consultation (health) questionnaires | Contract, Art 6(1)(b) | The client's explicit consent, Art 9(2)(a) |
| DBS screening records | Legal obligation where the role is regulated, otherwise legitimate interests | Criminal offence data (Art 10), under DPA 2018 s.10(5): Sch 1 para 1 (employment obligations) or para 18 (safeguarding of children and individuals at risk) |
| Safeguarding concerns | Legitimate interests in protecting children, Art 6(1)(f) | Safeguarding of children and individuals at risk, DPA 2018 Sch 1 para 18 |
| Photos / media of children | Consent of the parent or guardian, for every child under 18, Art 6(1)(a) | — |
| Marketing communications | Consent of the adult (never sent to children), Art 6(1)(a) and PECR | — |
| Audit trail / activity logging | Legitimate interest (security), Art 6(1)(f) | — |
| Pool water testing data | Legal obligation (Health and Safety at Work etc. Act 1974; PWTAG / HSG282 guidance) | — |
4. How We Protect Your Data
- Encryption at rest: the sensitive fields listed in section 2 (health information, safeguarding records, contact details, staff pay and bank details, consultation answers and others) are encrypted using AES-256. Not every field is encrypted: names, dates of birth and booking details are protected by access controls instead.
- Encryption in transit: All connections use TLS/HTTPS
- Password security: Passwords are stored only as one-way salted hashes (Argon2id)
- Session security: Sessions are encrypted, HTTP-only, secure cookies with SameSite protection
- Access control: Role-based access, with each organisation's data in its own database
- Audit logging: Data changes are logged with user identification (encrypted fields are left out of the log)
- Rate limiting: Login attempts are rate-limited to prevent brute force attacks
5. Data Retention
We keep personal data only for as long as it is needed. Each organisation can lengthen a period where the law or its own policy needs it (for example accident and safeguarding records), and can shorten some of them. Every removal is recorded so the organisation can show what was removed and when. The main periods:
- Deleting a record: pressing Delete hides it at once. It can be brought back for 90 days. After 90 days a deleted member, parent or child is anonymised; other deleted records follow the period for their type below.
- Members: anonymised 6 years after the membership ended. Children and parents on swim lessons: 3 years after the last lesson.
- Staff: HR, absence and pay records 6 years after leaving; right to work checks 2 years after leaving; fit notes and sickness details 3 years after the tax year.
- Accident records: at least 3 years (RIDDOR); a child's until they are 21. The people on them are anonymised after 6 years.
- Safeguarding records: a concern about a child until the child is 25; about an adult until they are 65 or for 10 years, whichever is longer.
- Signed waivers and health questionnaires: 3 years after they end (a child's waiver until they are 21); unanswered questionnaire links after 90 days.
- Payments and sales: 6 years (tax law).
- Complaints: the complainant's details 6 years after the complaint was resolved. Parent and teacher messages: 3 years. Text messages: 12 months. Marketing email records: 24 months.
- Imported spreadsheets: deleted as soon as the import has run.
- Audit logs: 3 years. Security logs: 2 years. Sessions: end after 2 hours of inactivity.
- Subject access files: deleted 7 days after they are sent.
When an organisation leaves Vardeck, its account is closed and kept for 90 days so it can export its data; then its database, files, backups held by Vardeck and staff sign-ins are deleted (see our Data Processing Agreement, section 11).
6. Your Rights
Under UK GDPR, you have the right to:
- Access your personal data (Subject Access Request)
- Rectification of inaccurate data
- Erasure ("right to be forgotten")
- Data portability (receive your data in a machine-readable format)
- Restrict processing in certain circumstances
- Object to processing based on legitimate interest
- Withdraw consent at any time (for consent-based processing)
To exercise any of these rights, contact privacy@vardeck.app, or the organisation that holds your data. We will respond without undue delay and within one month of receiving your request. For complex or numerous requests this can be extended by up to two further months; we will tell you within the first month if so.
7. Children's Data
We take extra care with children's data. A child's name, date of birth, attendance and progress are used to run the lessons their parent or guardian has booked: that is part of the contract with the parent, not a consent choice. Some uses are optional and only happen with a parent or guardian's consent, which they can change at any time in the parent portal: photographs and filming (for every child under 18), sharing with third parties, and holding health information the parent gives. Marketing is only ever sent to adults. Medical, allergy and additional needs notes are encrypted and visible only to authorised staff.
We also publish an age-appropriate version of this notice written for young swimmers themselves: Your information — a guide for young swimmers.
8. Third-Party Services
We use the following sub-processors. Each receives only the data needed for its purpose. This is the same list as in our Data Processing Agreement.
| Company | What for | What data | Where |
|---|---|---|---|
| Amazon Web Services (S3 off-site backups) | Encrypted off-site copies of database backups | All platform data, in password-protected backup archives | United Kingdom (eu-west-2, London) |
| Browser push services (Google FCM, Mozilla, Apple) | Delivering browser push notifications | Anonymous device subscription, notification content | US / EU |
| Email delivery provider (Postmark; Resend or Amazon SES if configured instead) | Transactional and marketing email delivery (alerts, bookings, receipts, consultation links) | Email addresses, recipient names, message content | US (Amazon SES: eu-west-2, London) |
| Functional Software Inc. (Sentry error monitoring) | Error and performance monitoring of the application | Technical data in error reports (URLs, IP addresses, user IDs); may incidentally include other data | US or EU (per account region) |
| GoCardless Ltd | Direct Debit collection for membership and lesson fees | Names, email addresses, bank account details (held by GoCardless) | United Kingdom |
| Microsoft (Teams webhooks — optional, tenant-enabled) | Warning/critical alert delivery to a tenant-configured Teams channel | Alert summaries, which may include staff names and facility details | UK / EU |
| Slack Technologies (optional, tenant-enabled) | Warning/critical alert delivery to a tenant-configured Slack channel | Alert summaries, which may include staff names and facility details | US |
| Stripe, Inc. | Card payment processing and SaaS subscription billing | Names, email addresses, payment tokens (no card numbers stored by Vardeck) | UK / EU (US parent) |
| Twilio Inc. (SMS — if selected instead of Vonage) | SMS alerts and reminders | Mobile numbers, message content | US |
| UK hosting provider (Plesk-managed, London) | Application hosting, database storage and backups | All platform data (encrypted at rest) | United Kingdom |
| Vonage (SMS) | SMS alerts (critical compliance and safety notifications) | Staff/guardian mobile numbers, alert message content | UK / EU (US parent) |
An organisation can also connect its own accounts with other services (for example its own Trybe spa booking account, or Slack or Microsoft Teams for staff alerts). Those services then receive the data needed for that purpose under the organisation's own agreement with them, and the organisation's privacy notice names them.
We do not sell or share personal data with third parties for marketing purposes.
9. Data Breach Notification
If a breach affects data we hold for an organisation, we tell that organisation within 24 hours of becoming aware of it, so it can tell the Information Commissioner's Office (ICO) within 72 hours where the law requires. For data Vardeck itself controls (see section 1), we notify the ICO within 72 hours where the breach is likely to result in a risk to people's rights and freedoms. People affected are told without undue delay where the risk to them is high.
10. Complaints
If you have concerns about how your data is handled, you can:
- Contact us at privacy@vardeck.app
- Lodge a complaint with the Information Commissioner's Office (ICO)
11. Changes to This Policy
We may update this privacy policy from time to time. Material changes will be communicated via email or in-app notification.