PaddlePolicy version 1 · 26 October 2026. Contact: hello@paddlepot.app.
Sessions and player information
A session can contain player names or numbers, ability ratings, availability, pairings, scores, results and organiser settings. Group features can also hold rosters, memberships and session histories. Use a nickname or player number when a real name isn’t needed. Only add information you have permission to share.
People with a session code can access that session. For free public sessions, code holders can also manage it. Group access and editing depend on the Group’s settings and permissions. Personal session links may display player-specific information. Treat codes and links as shared access, not as a private conversation, and don’t publish them unnecessarily.
Google sign-in
Group administrators use Google sign-in through Firebase Authentication. PaddlePot verifies the Google identity and stores the account’s Firebase identifier and verified email to recognise the account and check access. PaddlePot does not receive your Google password. The application saves its own sign-in token in browser storage to keep you signed in.
Browser storage
PaddlePot uses local browser storage for features such as sign-in, session preferences, starred Groups and access information where applicable. Learn saves lesson progress and sound preferences. Rally remembers your best scores, name entry, introduction preference and a randomly generated browser identifier used for leaderboard runs.
You can remove this information through your browser’s site-data controls. Doing so may sign you out or reset progress and preferences. It does not by itself delete information already stored by the service.
Rally leaderboard
Ranked Rally runs send run information and the browser identifier to the leaderboard service. If you submit a score, your chosen display name and score can appear publicly on the monthly leaderboard. Use a nickname rather than personal contact details. Monthly board resets do not mean that all related service records or backups are immediately erased.
Hosting, security and service providers
PaddlePot uses Google/Firebase services for hosting, sign-in and API hosting, and Supabase for database and leaderboard services. Google Fonts supplies the site’s web fonts. Loading a remote service sends technical information such as your IP address and browser request details to that provider.
Technical request records, security and rate-limiting information, and administrative audit records help operate the service, investigate faults and prevent abuse. Providers process information on their infrastructure, which may be outside your country. Their own terms and privacy notices also apply: Google privacy policy and Supabase privacy policy.
Analytics, marketing and advertising
PaddlePot does not currently use a separate audience analytics service, marketing mailing list or third-party error-tracking integration. Operational logs are different from audience analytics.
Google advertising is not currently enabled in the site’s advertising configuration. If advertising is introduced, this page will be updated and any required consent controls put in place before it is enabled. Google advertising can use cookies, web beacons, IP addresses and other identifiers for ad delivery, measurement and, where permitted, personalisation. See how Google uses information from sites that use its services.
Retention and your choices
Free public sessions expire 24 hours after creation and are subject to server cleanup. Expiry ends access; it does not guarantee immediate erasure from every backup or technical log. Group information and histories can remain while the Group uses the service, subject to its management and retention settings. Local progress remains until it is cleared or your browser removes it.
Email hello@paddlepot.app to ask about access, correction or deletion of information relating to you. We will consider the request, verify it where necessary and explain any limits, including records needed for security or other obligations. Avoid adding sensitive information to names, comments or public leaderboard entries.
Changes and questions
When features or information practices change, this page should change with them. The version and date above identify this policy. Please contact PaddlePot if an explanation is unclear.