Privacy policy

Last updated: 10-11-2026

Poolse is software for running clubs, swimming schools and pools. This page explains what personal data Poolse processes, why, for how long and who it is shared with.

Who is responsible for the data

The data of a club's students, guardians and staff belongs to the club. The club is the controller; Poolse processes that data on the club's behalf, as a processor (Article 28 GDPR), and only to provide the service.

For requests about that data — access, correction, erasure — please contact your club first. Poolse helps the club answer.

The data of whoever creates an account to run a club (name, email and the subscription's billing details) is processed by Poolse as controller.

What data we process

  • Identity and contact: name, date of birth, gender, tax number, address, email, phone and, with consent, a photograph.
  • Club life: classes, attendance, levels, race times and comments about lessons.
  • Payments: monthly fees, the club's internal documents and recorded payments. Poolse does not store card details.
  • Health: medical and mobility notes, medical exams, medical certificates and the emergency contact. This is special-category data: it is encrypted, only the club office and the family itself see it, and every read is logged.
  • Identity documents: encrypted, and every read is logged.
  • Staff: contract, qualifications, pay and holidays.
  • Technical records: when an account signs in, and a history of the changes made.

Why

  • To provide the service the club signed up for: organising lessons, communicating with families, collecting fees and meeting its safety and health obligations.
  • To keep accounts and data secure.
  • To meet legal obligations, such as tax rules.

The legal basis is the contract with the club, the club's legal obligations and, where the club asks for it, consent (for photographs, for example). Poolse does not sell data or use it for advertising.

Children

Many students are minors. Their record is managed by the club and by their guardian. A student can only have their own account from the age of 12, invited by the club.

At 18, a parent's link stops giving access to the record, and the young adult decides on the consents given on their behalf.

Who sees what

  • The club office (owner and administrators) sees the full record.
  • Instructors see the students of their own sports, without the health documents.
  • Each family sees only its own children.
  • An adult student is shown to classmates in their class with their first name, surname initial and photograph. This cannot be switched off. Minors are never shown to other families.
  • The club and Poolse support can see the app as a person sees it, read-only, to help with a problem. The person is not told, but every visit is logged.
  • Poolse support only enters a club with the club owner's permission, for a limited time, and never sees health data or identity documents.

For how long

  • While a student attends the club, the data is kept.
  • One year after they leave, medical and mobility notes, consents, the emergency contact and medical justifications are erased.
  • Five years after they leave, the name and contact details are anonymised; only figures such as attendance and amounts remain.
  • Billing documents keep the payer's name and tax number for ten years, as tax law requires.
  • A registration request that never becomes an enrolment is archived after 12 months, and its details are anonymised five years later.
  • Backups are kept for 30 days. An erasure is complete when the oldest backup holding the data expires.
  • If a club stops using Poolse, the account becomes read-only with export available; after 60 days, the account and its data are deleted.

Who we share with (processors)

  • Clerk (US): accounts and sign-in — name and email.
  • Vercel (EU and US): hosting of the web app.
  • Railway (EU): server and database.
  • Cloudflare R2 (EU): files and encrypted backups.
  • GitHub (US): runs the nightly backup; the backup is encrypted before it leaves the server.
  • Resend (US): sending email, when switched on.
  • Stripe (EU and US): the club's subscription payment; it receives no student data.
  • Sentry (EU and US): error tracking, when switched on, with no personal data.
  • Anthropic (US): automatic reading of documents (energy bills, membership forms), only if the club switches it on; the document is sent to be read.
  • Open-Meteo (Europe): weather; it receives only the facility's town.

Transfers outside the European Union rely on the European Commission's standard contractual clauses or the EU-US Data Privacy Framework.

Your rights

You have the right to access your data, correct it, ask for it to be erased or its processing restricted, object, and receive it in a portable format. You can withdraw consent at any time, without affecting what was done before.

Send your request to your club or to the contact below; we answer within 30 days. You can also complain to the Portuguese data protection authority, the CNPD (www.cnpd.pt).

Security

  • Each club's data is kept separate in the database itself.
  • Connections are encrypted (HTTPS).
  • Health data and identity documents are encrypted.
  • Backups are encrypted, and the key is kept offline.
  • Each person reaches only what their role allows.

Cookies

Poolse uses only necessary cookies: the session, the active club, the language and the theme. It uses no third-party advertising or analytics cookies.

Changes

If this policy changes, the date at the top is updated, and an important change is announced in the app.

Contact

suporte@poolse.org