Privacy Policy
Version 1.2 — effective 2026-11-06
This policy explains what personal information the curlingpoint.ca platform (the "Platform") collects, why, and how you can exercise your rights. It is operated by Sébastien Audet, doing business as AudeTI Solutions ("we").
1. Person in charge of the protection of personal information
Sébastien Audet, owner — [email protected]. For any question, access or correction request, or complaint.
The information that the members of a club entrust to that club is the club's responsibility (section 10).
2. Information collected and purposes
| Information | Who | Why |
|---|---|---|
| Display name, email, password (encrypted) | Account holders | Create and secure the account, communicate with you |
| Usage surface of the CurlingPoint app (installed app or browser) and date | Account holders | Measure adoption of the app; visible to the administrator only |
| Last opening of the CurlingPoint app tools (strategy board, draw-shot calculator) | Account holders | Count the use of the tools; numbers only, visible to the administrator |
| Date of the last time a club console was opened (one date per person and per club) | Account holders who have a role in a club | Know who uses the club console; visible to the club site managers and to the platform administrator |
| Rating and comment about the platform (optional) | Account holders | Improve the platform; never published; each rating is also sent to us by email, with your name and your email |
| Profile photo (optional) | Account holders | Show your photo in your account and to your teammates; it is not public, and the platform administrator sees it in order to approve it |
| Public player profile: display name, photo, tournaments played (team, position, result), win-loss record, regional and provincial championships | Players linked to a tournament who turn it on (off by default) | Show your profile to anyone who has its address; it is not indexed by search engines and never shows purses; a link between your account and a tournament is public only after your confirmation ("Yes, it's me") |
| Devices registered for notifications (address of your browser's notification service and sending keys, device name and language) and your notification preferences | Account holders who turn notifications on | Send the reminders and notices you chose |
| Team finances, calendar and Notebook (team members, expenses, contributions, events, availabilities, game and stone notes, memos) | Members of a team | Keep the team's accounts, calendar and notes; visible to the team's members and, for the finances only, to whoever receives the secret sharing link created by a team administrator. A team can encrypt its Notebook (section 6): we then keep only encrypted text, which we can neither read nor recover; the date, opponent, score, club, sheet, stone colour and number, author and date added stay readable |
| Team event images (images that members import into an event's sheet) | Members of a team | Keep the practical documents of an event (rules of a rented chalet, door code, receipt); visible to the team's members who can see the event; deleted automatically 60 days after the end of the event; encrypted on the device when the team has encrypted its Notebook (section 6): we then cannot read them |
| Team event lodging (name, address, arrival and departure dates, access code, booking link and notes that members enter in an event's sheet) | Members of a team | Keep the practical information about the stay for an event; visible to the team's members who can see the event; deleted automatically 60 days after the end of the event; encrypted on the device when the team has encrypted its Notebook (section 6): we then cannot read it |
| Emails sent to teams by an organizer: team address, text of the message, date the schedule link was opened and number of openings | Teams of a tournament | Let the organizer see which teams opened their schedule; no IP address and no device is recorded, and a signed-in account is never counted |
| Club member record: first name, last name, email, phones, address, date of birth, gender (according to the fields the club chooses), membership (type, season, status, payment) and answers to the membership form | Members of a club, entered by the club or by the person on the club's membership form | Manage the club's memberships, leagues and lockers and write to its members; the club is responsible for them (section 10) |
| Messages sent by a club to its members (subject, text, recipients, delivery status) | Members of a club | Keep track of what the club sent and to whom |
| Name, email and message from the contact form of a club site | Visitors of a club site | Pass the request on to the club |
| Club finances (Finances module): transactions (date, amount, counterparty, description, line, payment method, reference), budget and supporting documents (PDF, JPEG or PNG) | Entered by the club's treasurer or site manager | Keep the club's books; the name of a person who paid a membership or a locker is not copied into the register, it is read when displayed |
| Club customers and bookings (Customers module): name or company name, contact person, email, phone, billing address, bookings | Entered by the club | Manage the club's rentals and sales |
| Token purchases, plan | Account holders | Billing, token tracking |
| Names of players, coaches, club | Entered by the organizer | Display the tournament's teams and results |
| Name, email, message | Contact form | Reply to your request |
| Scoring log (who changed what, when) | Organizers, scorers | Integrity of results |
| Club change log (who did what, when, on whom, with the before and after) | Account holders who have a role in a club | Know who changed what in the club console, and who granted or removed whose access; visible to the club site managers and to the platform administrator |
| Language preference | Visitors | Display the site in your language |
We do not sell any personal information.
3. Technologies used
- Browser local storage: keeps your login session and language preference. No cross-site tracking.
- Advertising (Free tournaments only): the public pages of Free tournaments display Google AdSense ads. By default, these ads are not personalized. Google may use cookies to limit ad repetition and prevent fraud. No advertising on Premium tournaments, the home page or the consoles.
- Audience measurement of club and demonstration sites: each page view records the date, the page path (without parameters), its title, a random browser identifier (kept in local storage, no cookie), the domain you came from, the device, browser and operating system, and your approximate city and network name (derived from your IP address). Your IP address is not kept. If you arrive through a tracking link that was sent to you, the name given to that link is associated with your browser. This data is used to understand traffic, is kept for 12 months and then deleted, and is never sold. You can opt out with your browser's "Do Not Track" setting.
- Audience measurement of Premium tournaments: the public page of a Premium tournament sends our database a random browser identifier (kept in local storage, no cookie), the tab viewed and the time. The organizer sees the highest number of simultaneous visitors, the number of different visitors and the total number of visits. Presences older than 10 minutes are deleted at the next visit; the daily visitor identifiers stay with the tournament. The tournament organizer and the platform administrator are not counted.
- Cloudflare audience measurement (Web Analytics): Cloudflare, which hosts the Platform, adds its audience measurement beacon to its pages. This measurement is made and kept by Cloudflare; it is separate from ours.
- Functional cookie `cs_langue`: on a club site that offers a choice of language, the FR | EN button sets a `cs_langue` cookie (the value fr or en, one year, specific to that site) to keep your language. It is used for nothing else.
- Google Fonts: the tournament pages and the scoring app load their fonts from Google Fonts; Google then receives your IP address and the address of the site (without the page path).
- No other identification, geolocation or profiling technology is enabled by default.
4. Who has access to your information
- Organizers: the data of their tournaments.
- Public: the tournaments' public pages (teams, players, results), club sites (according to each club's choices) and the public profiles of the players who turned them on.
- Clubs: people who have a role in a club see that club's information according to their role (section 10).
- Platform administrator: for support and account management. The administrator does not see the member records of clubs (section 10).
- Service providers: hosting, database, email delivery and advertising (Free tournaments). Some are located outside Quebec. They are:
- Supabase: database, account authentication and storage of profile photos.
- Cloudflare: hosting of the Platform's pages and functions (every visit goes through Cloudflare), R2 storage of club site images and, in a private space, of the supporting documents of a club's finances and the images of a team's events, and Web Analytics audience measurement (section 3).
- Resend: email delivery (account confirmation, invoices, messages from organizers and clubs, email notifications, alerts to the administrator).
- Stripe: for a card payment, the payment details are entered on Stripe's page and sent to Stripe; we keep only the amount, the date and the payment identifier.
- Stripe Connect: if a club turns on card payment of memberships, the payment is made on Stripe's page and goes directly to the club's own Stripe account; we withhold no fee and keep only the amount, the date and the payment identifier.
- Google: AdSense ads of Free tournaments (section 3) and Google Fonts (section 3).
- Browser notification services (Google, Mozilla, Apple, Microsoft, depending on your device): Web Push notifications go through your browser's service; their content is encrypted.
- OpenStreetMap Foundation: the Trips view of CurlingPoint Team shows a map whose tiles come from OpenStreetMap's servers; your browser sends them your IP address, the address of the site (https://curlingpoint.ca/) and the coordinates of the tiles requested (the part of the map displayed). No information from your account is sent to them.
5. Retention
- Account: as long as it exists. On closure, the account and its tournaments are deleted.
- Tournaments: as long as the organizer's account exists. A deleted tournament stays 30 days in the organizer's trash, then is permanently deleted; a draft tournament that is not activated expires after 60 days and goes to the trash. The emails sent to teams and the visitor identifiers of a tournament (sections 2 and 3) are kept with the tournament.
- Audience measurement of club sites: 12 months, then deleted.
- Notifications: those of the notification centre 60 days; finished sends of the send queue 7 days; a registered device stays until you remove it or your browser's notification service permanently refuses it.
- Rating and comment about the platform: as long as the account exists.
- Last opening of the app tools: as long as the account exists.
- Public player profile: until you turn it off; it then stops being displayed and the public copy of the photo is removed.
- Date the club console was last opened: as long as the person has a role in that club.
- Member records, memberships, messages, finances and supporting documents of a club: as long as the club exists on the Platform; the site manager can delete a record. None of this data is erased automatically.
- Contact form messages: 24 months.
- Club change log: each line (date, person, action, on whom) 24 months; the "before and after" detail 10, 30, 60 or 90 days as chosen by the club site manager (90 days by default). The detail of an access granted or removed (the person and their roles) is kept with the line.
- Billing information: for the period required by tax laws.
6. Security
Encrypted connections (HTTPS), encrypted passwords, data access restricted by security rules at the database level, separate access codes for scorers.
A team's Notebook (game and stone notes, memos) can be end-to-end encrypted, at the choice of the team's banker: the text is encrypted on a member's device with a key that we never receive. The database, its backups and any leak of that data then contain only encrypted text. This guarantee does not cover the application itself, which we provide, nor a person's device: the PIN that opens the Notebook on a device protects against someone else using the device, not against the extraction of the browser's files. If no team device has access to the Notebook any more, we cannot recover it: its content is lost.
7. Your rights
You may request access to your information, its correction or removal, or the closure of your account by writing to the person in charge (section 1). We reply within 30 days. If you are not satisfied, you may contact the Commission d'accès à l'information du Québec.
8. Privacy incident
In the event of an incident presenting a risk of serious injury, we notify the persons concerned.
9. Changes
The version in force and its date are published on this page. A significant change is announced by email or at login.
10. Curling clubs
When a curling club uses the Platform (club site, members, leagues, lockers, messages, finances), the club is responsible for its members' information: it decides which information to collect, for what purposes and who has access to it. We host and process it on the club's behalf, to provide the service. To exercise your rights regarding your member record, contact the club first; you may also write to our person in charge (section 1).
Who has access to a club's information, according to their role in the club console:
- Site manager: everything in the club console; grants and removes roles, consults the club log and can export the club's basic data.
- Treasurer: member records, memberships and their payments, lockers, messages to members and the club's finances.
- League director: the leagues they are responsible for (teams, registered players, spares, results) and the names of the club's active members.
- Editor: the site content (pages, news, calendar, photos); no member record.
- Tournament organizer: the club's tournaments.
- Clerk: the catalogue, bookings and customers of the club (Customers module); no member record.
- Board of directors: the club's finances, read-only.
- Member: their own record and memberships, and the pages and leagues reserved for the club's members.
The platform administrator does not see member records in their console, only their number. The administrator reaches a club's data only through a support session: reason required, read-only by default, limited duration (60 minutes by default, 4 hours at most), recorded in the club log that the site manager consults.
The club chooses what is published on its site (pages, news, calendar, leagues, photos). A page or league reserved for members can be read only by the club's members and the platform administrator. Club site images are served from a public Cloudflare address; the supporting documents of the finances are in a private space, readable only by the roles that have access to the finances.
The club writes to its members through the Platform. News messages carry an unsubscribe link; messages related to membership are always sent. An address that bounces or reports a message as unwanted no longer receives the club's messages.
When a club is closed, its site stops being published and its data can no longer be modified. The site manager can export a copy of it (member records, memberships, seasons, roles, tournaments and log) whatever the state of the club. The data is not erased automatically: the club can ask for it to be erased by writing to our person in charge (section 1).
11. Version history
1.2 — 2026-11-06: clubs, club finances, service providers, retention periods.