Privacy policy

About this policy

Racquet Leagues is operated by CEG Solutions, a registered Australian business name used by its sole-trader operator. In this policy, “we”, “us” and “our” refer to that operator. The service provides apps and a website for organising racket-sport clubs and sessions. This policy describes how personal information is handled through those features. Contact info.racquetleagues@gmail.com about privacy, access, correction, deletion or a complaint.

Clubs and organisers also decide what information they collect for their own activities and how they use it outside this service. Ask your organiser about external attendance lists, WhatsApp groups, bank transfers, photos or venue records they manage.

Information used by the service

Account and profile information includes your sign-in email, authentication/account identifiers, verification status, display name and any optional profile photo you choose to upload. Authentication is handled through Firebase Authentication. Do not send passwords to organisers or support.

Club and sporting information includes memberships and roles, email invitations and join requests, club details and settings, session dates/times and venues, attendance responses and waiting lists, schedules, player/guest names, results, ratings and statistics. Owners can override attendance and add session guests. Attendance changes record who made the change and when; adding a guest does not create an account or club membership for that person.

Payment administration includes requested shared costs, payer/collector identities, allocations, amounts, payment dates, confirmation/rejection states, references/notes, changes and any payment instructions supplied by an organiser. The service records payments made externally; it does not receive bank-login credentials or process those member-to-organiser transfers.

Communications and technical information includes session messages and mentions, notification inbox/read state, push-device registration tokens, platform/device information needed for alerts, local preferences, support correspondence and service/security records such as request times, IP addresses or error logs handled by our hosting providers.

Where information comes from

You supply information through forms, profile updates, attendance responses, scores, chat and payment reports. Organisers and other authorised users can supply information about you, such as an invitation, attendance entry, recorded match, cost share or guest replacement. Devices and service providers supply the technical information needed to authenticate requests and deliver notifications.

Provide only what is needed. The app does not require a phone address-book import to share a join link. A profile photo is optional. Avoid putting sensitive health information, identity documents, full card details or bank-login information in chat, notes or support requests.

Why information is used

Information is used to provide and secure account access; administer membership and invitations; organise attendance, sessions and recurring invitations; generate schedules; calculate statistics; keep shared-cost records; display conversations to their authorised audience; deliver requested service messages; investigate faults and misuse; and meet applicable legal obligations.

If you do not provide information required for a particular feature, that feature may not work—for example, a verified account is needed for protected club actions and a device registration/permission is needed for mobile push. Optional profile-photo information is not required to participate.

Who can see or receive information

Your club’s authorised members can see the information exposed by its member, session, attendance, chat and sporting-record screens. Owners/Admins can access additional membership, invitation and payment-management information needed for their role. Members’ payment views are limited to their own authorised records; organisers can review member balances for clubs they manage.

Messages are shared with current club members with access to that session conversation, not only those attending. Guest names entered by organisers can appear in schedules/results. This is not an end-to-end encrypted private messenger. Do not post something you are not entitled to share with that audience.

Push alerts, email and device lock-screen previews can reveal a message or activity summary to people able to view that device or mailbox. Your own device settings control previews. Removing a message or record cannot recall screenshots or copies already received.

Information may also be disclosed to service providers operating the service, authorised people handling support/security, or a recipient where you direct sharing or disclosure is required or otherwise permitted by applicable law. Share invitation links and exported schedules carefully.

Service providers and overseas processing

Google Firebase/Google Cloud provide services including authentication, database/hosting, backend processing and mobile messaging. Apple’s push service is involved in delivering iOS alerts. Transactional email uses the configured delivery provider, currently Brevo. Providers receive the account, recipient, message or technical information needed for their role.

Processing is not confined to Australia. The current backend functions run in Singapore; authentication, messaging, email, support and other infrastructure may be processed in other countries where the relevant provider operates, including the United States. Provider arrangements and services affect the specific locations. We use these providers to deliver the service rather than promising that all records stay in one country.

Storage, local settings and security

Club records are stored through the service’s backend. Apps/browsers also store session/authentication state, caches or preferences needed to run the service. For example, your app appearance preference is local to an installation, while your chosen default club is an account preference. Device/browser privacy or storage controls may clear local data but do not by themselves delete shared backend records.

We use the service’s authentication, access rules and provider infrastructure to restrict access and support security. No online service can guarantee complete security or uninterrupted availability. Keep devices and credentials secure, sign out on shared devices and tell us about suspected unauthorised access.

Chat safety and reports

We check chat text for a basic set of offensive terms before it is posted. Reports store a copy of the reported message, its author, your account ID, the selected reason and review actions. Racquet Leagues can review reports for safety purposes. Club owners can review reports about other members, but cannot see the reporter’s account ID or reports about themselves.

Your blocked-user list is private to your account and the service. Blocking hides that user’s messages for you and stops new chat alerts between you across clubs; it does not remove either person from a club or prevent them reading shared club conversations. Owners can restrict posting in their club’s chat, and Racquet Leagues can suspend chat access across the service. Safety reports may retain a message snapshot after the original is removed, while needed to investigate or protect users. Account deletion removes snapshots of messages authored by that account and removes or de-identifies its report and block records as described below.

Retention and deletion

Account and activity records are kept for as long as reasonably needed to operate the relevant clubs/features, handle corrections or disputes, protect the service and meet applicable obligations. The service does not currently promise one automatic deletion period for all information. Ranking histories may be summarised into checkpoints rather than retaining every detail indefinitely.

Removing club access, signing out or disabling notifications does not automatically erase historical results, messages, payment records or copies held by other participants. A shared record may need to be retained, corrected or de-identified rather than simply removed. Provider logs, backups and legally required records can have separate retention periods.

Use available profile/message controls for supported changes. In the mobile apps, open App settings and select Delete account. The confirmation explains that deleting your account also permanently deletes every club/group you own and its sessions, schedules, results, statistics, invitations and payment records for all members. Clubs owned by others remain: your membership, profile, authored session messages and personal account records are removed, and shared sporting/payment history is de-identified where retained for other participants. You may need to confirm your password. If cleanup is interrupted, the service retries it automatically. A minimal account-deletion marker is kept for up to approximately 24 hours after completion, plus the next cleanup interval, to block still-valid sign-in tokens; it contains no name, email or profile photo. For corrections, other removal requests or help with deletion, contact us using your account email. Provider backups, logs and lawful retention obligations may be handled separately.

Feedback you send

Settings includes an optional feedback form. Your chosen feedback type, message and platform are sent to our support inbox through Brevo, our existing email provider. Your account email is included in that message only if you choose to allow a reply. Do not include passwords, payment details or other people’s private information. Firebase stores limited delivery and rate-limit metadata, not a separate copy of the message, to support retries and prevent abuse. Account deletion removes that metadata; support correspondence and provider records are handled under the retention and privacy-request provisions below.

Access, correction and privacy requests

You can review information available through your profile and club/session screens and ask us to provide access, correct inaccurate information, or consider deletion or other rights applicable to your circumstances. Contact info.racquetleagues@gmail.com with the account email, the request and enough detail to identify the records. Do not include your password or unnecessary financial documents.

We will review the request and respond within the time required by applicable law, taking account of identity checks, other people’s information and any lawful limits. If we cannot fulfil a request in full, we will explain the relevant reason where permitted and how to raise a concern.

Children and information about others

Organisers arranging activities for children must consider parental permissions, supervision and appropriate information sharing. Do not submit information about another person without the authority or permission needed for that activity. Contact us if you believe a child’s information or another person’s details have been included inappropriately; we will review the circumstances.

Complaints and policy updates

If you have a privacy concern, contact info.racquetleagues@gmail.com with the issue and the outcome you seek. We may request information needed to investigate and will respond under the applicable requirements. You may also contact an appropriate privacy regulator; in Australia this includes the Office of the Australian Information Commissioner where it has jurisdiction.

We may update this policy as the service or its providers change. The current version and date are published here. Where law requires additional notice or consent, that process will be handled separately.

Provider and regulator information

Firebase privacy and security · Brevo privacy information · Apple privacy information · OAIC privacy information