Skip to content

Privacy Policy

Swing to Smash — Privacy Policy

Version 1.7

Document Information

Version: 1.7 Operator: 11219235 Canada Incorporated, Ontario, Canada ("Swing to Smash", "we", "us"), which runs the Service. Each event is run by its organizer (the "Organizer"), who decides what their event collects and why. Contact: info@swingtosmash.com Service: the Swing to Smash website and apps at swingtosmash.com (the "Service"), and the badminton tournaments and ladders run on it (each an "Event").

Who is responsible for what:

  • Swing to Smash is responsible for your account, sign-in and profile, your help chats and support requests, your acceptances of our terms and policies, the public portal itself, organizer billing (Event passes) and our security logs, and decides how that data is used.
  • Each Event's Organizer is responsible for that Event's own data — its registrations, teams, check-in, scores, waivers and fee tracking — and decides how it is used. Swing to Smash processes that data for the Organizer, to provide the Service, and keeps signed waivers for their retention period (section 8).

1. What We Collect

  • Account & profile — your name, email address, gender (used only to determine which disciplines you can enter — men's, women's and mixed events), preferred language, your answer to "I'm 18 or older" (see section 11), and your profile photo. If you created your account with Google or Microsoft and that account has a photo, it is your profile photo to begin with: from Google we keep the photo's web address (the photo itself stays on Google's servers); from Microsoft, a small copy of the photo, kept with your account. Apple doesn't share a photo, and an account made with an email and a password starts without one. You can upload or take a photo of your own instead, which we resize and keep, or remove your photo; without a photo, your initials are shown. The Google address or Microsoft copy stays with your account, so you can switch back to it.
  • Sign-in — you sign in with Google, Microsoft, or Apple, or with your email address and a password. From Google, Microsoft, or Apple we receive your basic profile (name, email, provider account identifier and, from Google or Microsoft, the account's photo if it has one); they never share your password with us. If you choose a password with us, we store only a salted, one-way hash of it (never the password itself), and we email you one-time codes to confirm your address or reset your password.
  • Registration & teams — the teams you create or join, your discipline, and the name and email of a partner you enter when inviting them (see "Partner invitations" below).
  • Tournament data — check-in status, match assignments, scores, results, standings, and placements.
  • Waiver records — each Event's waiver is between you and its Organizer, who chooses how it is signed. When you sign one in the app, we record your typed legal name, your signature (a drawn image, or your typed name if you choose to type it), the signed PDF, and acceptance metadata: the Event, the version accepted (and, for a waiver the Organizer uploaded as a PDF, the file's name and fingerprint), date/time, IP address, and browser user-agent, and, if a parent or guardian signs for you, their name. If the Organizer collects waivers on paper at check-in, we record only that yours was received, who ticked it and when; the paper form stays with the Organizer.
  • Payment reconciliation — if the Event charges a registration fee, you pay the Organizer directly, outside the Service (for example by e-transfer, bank transfer, a payment app or cash). We record only whether your payment was received and reconciled. We do not collect or process card numbers or bank credentials.
  • Organizers and Event passes — if you run or help run Events, your role in each one (organizer or scorer), who gave it to you, and the Events you own. If you buy an Event pass, we record the Event, your account, your name and email address at the time, the amount, currency and date, whether it was paid, cancelled or refunded, and Stripe's reference numbers for the payment. Your card details go to Stripe, our payment processor, and never to us.
  • Technical data — server logs (IP address, user-agent, timestamps) used for security, abuse prevention, and rate limiting.
  • Help assistant — if you ask the help assistant a question while signed in, we keep the chat with your account: your questions and its answers word for word, the help articles each answer drew on, the page or event the chat started on, and whether you marked an answer helpful. Only you and our platform administrators can read your chats, and each time an administrator opens someone's chats it is recorded in the audit log; event organizers, scorers and other admins cannot see them. You can read, delete (one or all) and download your chats under Your help chats in the account menu, and closing your account deletes them too. If you are not signed in, your chat is not kept. Separately, every question asked, signed in or not, goes into a log we use to improve the help and to prevent abuse. It keeps the question (with email addresses, phone numbers and names removed), the answer it got, whether you marked it helpful, whether you were signed in, the page it was asked on, and technical details: your IP address, your browser and device (from the user-agent string your browser sends), and the time zone and language your browser reports. It holds no account details, only platform administrators can see it, and it is deleted after 30 days.
  • Support requests — when you contact support, we keep your email address, the name you give, your messages and the photos or videos you attach, our replies, the page and event you wrote from, the site language, your browser's user-agent string, your IP address and, if you're signed in, your account. We use them only to answer you and to prevent abuse. A request sent without signing in can be read by anyone with its private link, so keep that link to yourself.
  • Policy acceptances — when you accept the Terms of Service or confirm you've read the Privacy Policy (and, if you run events, accept the Organizer Terms), we record your account, the document, its version, the time, your IP address and your browser.

2. Why We Use It

  • To operate the Event: registration, team building, scheduling, check-in, live scoring, standings, and brackets.
  • To publish the public tournament portal (see "What is public" below).
  • To send transactional email necessary to run the Event (see "Email" below).
  • To create and retain the legally required record of your waiver acceptance.
  • To bill organizers for Event passes, and keep the records the law requires for that (tax and accounting).
  • To keep the Service secure: authentication, role checks, rate limiting, and abuse detection.
  • To answer your support requests.
  • To remember your preferences (language, theme).

We do not sell your personal data, and we do not use it for advertising.

3. Partner Invitations

When you register a team, you may enter your partner's name and email so we can invite them. We use that information only to send the invitation and connect them to your team, we identify you as the sender in the message, and we do not send them marketing. Invitations are rate-limited to prevent abuse.

4. Cookies & Local Storage

We use only what the Service needs to function — no advertising or third-party analytics cookies:

  • Session cookie — set by our sign-in system (Auth.js) to keep you signed in. Essential.
  • Sign-up cookie — remembers, for up to a day, a sign-up started in this browser, so the emailed code can finish it there. Essential.
  • Locale cookie — remembers the language you chose.
  • Theme preference — your light/dark choice, stored in your browser's local storage.
  • Help panel — while you use the help panel, the current chat and a random code used only to limit how many questions are asked are kept in this browser tab's session storage, and are gone when you close the tab.

5. What Is Public

The tournament portal shows each Event's pages so players and spectators can follow it. Who can see them is the Organizer's choice: anyone (the Event is listed on Swing to Smash, and search engines may show its pages), only people with its link (unlisted, and kept out of search engines), or only its players and staff, signed in (private). It shows your name, team, discipline, group, schedule, match scores, standings, and placements — including a per-player page listing your matches and results. A ladder's Organizer can choose to show first names and initials instead of full names. It also shows your profile photo (see section 1), or your initials if you have none, on its teams list and on each player's page, to anyone who can see the Event's pages. It always shows your current photo, so changing or removing it changes it everywhere, past Events included. When someone views a Google photo there, their browser loads it from Google's servers.

Your email address, waiver records, payment status, and any data beyond the above are never shown publicly.

6. Email

We send email via Azure Communication Services from our own domain. Messages are transactional: partner invitations, registration confirmations, schedule and result notifications, staff-role claim links, and your signed waiver PDF. If you buy an Event pass, Stripe emails you a receipt, and we email the Event's other organizers that a pass was bought, naming who bought it. Event announcements from the organizer include an unsubscribe option; essential transactional messages do not, because the Service cannot operate without them.

7. Where Your Data Lives

The Service runs on Microsoft Azure: the application on Azure App Service, structured data in Azure Database for PostgreSQL, and files in Azure Blob Storage. Signature images live in a private storage container, accessible only through the application. A profile photo you upload is kept in our storage, and the application serves it to anyone viewing a page that shows it; when you remove it, or switch back to your Google or Microsoft photo, we delete it (our storage keeps deleted files for 7 days, then removes them for good). A Microsoft photo's small copy is kept in the database with your account; a Google photo stays on Google's servers. Signed waiver PDFs are archived in a write-once (WORM) immutable container with versioning, so a signed record cannot be altered or deleted during its retention period. Admin access to archived waivers uses short-lived, authorized links — never public URLs. Payments for Event passes are processed by Stripe, which stores payment details in its own systems under its own privacy policy (stripe.com/privacy).

8. Retention

  • Account & tournament data — kept while your account is open and for 2 years afterwards, then deleted or anonymized. Closing your account removes your account data at once (section 9); your name on the results of the events and ladders you played stays with each event, as part of its record.
  • Signed waiver PDFs and acceptance records — retained for 10 years in immutable storage, even if you close your account, because they are a legal record of the release you signed.
  • Event pass purchase records — kept for six years after the end of the tax year of the purchase, as Canadian tax law requires, even if you close your account.
  • Server logs — retained for 90 days.
  • Help assistant chats — kept until you delete them, or close your account. The help assistant's question log (including IP addresses and browser details) — 30 days.
  • Support requests and their files — kept until you close your account or ask us to delete them. Closing your account also deletes the requests sent from its email address without signing in.

9. Your Rights — Export & Deletion

You may at any time:

  • Download a copy of your data: Profile → Download my data gives you one ZIP file with your profile, your sign-in methods (their names only), your preferences, the terms and policies you accepted, your events and teams with their fees, your matches and scores, your ladder places and games, your waiver records and the waiver PDFs you signed, and your help assistant chats.
  • Correct your profile information in the app.
  • Close your account: Profile → Close account. It takes effect at once and can't be undone.

Closing your account removes your sign-in (Google, Microsoft, Apple, and email and password), your email address, your photo and profile details, your notifications, your help assistant chats and your support requests, and signs you out everywhere. It also unlinks your account from your history: signing in again later, even with the same email address, starts a new, empty account. Some things stay, because they are part of other people's records too:

  • your name on the teams, matches and standings of the events and ladders you played in, as each event's record — without your photo or contact details;
  • your signed waivers and their acceptance records, for their retention period (section 8);
  • the records of any Event passes you bought, which tax law requires us to keep;
  • the events' records of your registration fees, and the log of changes made in events (the audit log).

If you're on a team or a ladder in an event that isn't over, your place stays under your name, and the event's organizers are told by email that you closed your account. If you're the only organizer of an event or ladder that isn't finished, you'll be asked to add a co-organizer first. Depending on where you live, you may have more rights — see section 13 if you are in the EU, EEA, UK or Switzerland. To exercise any other right, contact us using the details below.

Requests about an Event's data (for example a registration) go to its Organizer, through the contact details on the Event's About page when they've added them, or to us at info@swingtosmash.com: we'll pass them on and help. Requests about your account go to us.

10. Sharing

We share personal data only with:

  • Service providers — Microsoft Azure (hosting, database, storage, email delivery), acting on our instructions. Support requests are emailed to our support inbox through Azure Communication Services too.
  • Stripe — payment processing for organizers who buy Event passes. We give Stripe the buyer's email address, the Event's name and the amount, with our own references for the Event and the buyer's account; Stripe collects the card details itself. Players never pay through Stripe.
  • An Event's Organizer and the staff they appoint — to run the Event, they see its players' names, email addresses, gender, whether they're under 18, teams, check-in, fee status, waiver status and signed waivers (scorers see only what scoring and check-in need). They don't see your data from Events they don't run, beyond those Events' public pages. To add a player to their Event, an organizer can look up the people who take part in, or help run, an Event they run, by name or email address. Anyone else they can find only by typing that person's full email address, and then they see only the account's name.
  • Sign-in providers — Google, Microsoft, or Apple, when you use them to sign in, per their own privacy policies.
  • Authorities — if required by law, or to protect the safety of participants or the integrity of the Service.

We never sell personal data or share it for advertising.

11. Minors

You must be at least 13 years old to use the Service. If you are under 18, or under the age of majority where you live, you may use it only with the permission of a parent or legal guardian (see the Terms of Service). When you create your account, we ask whether you are 18 or older and keep your answer; if you don't confirm it, a parent or legal guardian signs every Event waiver for you, and their name is kept with it. We do not knowingly collect personal data from children under 13; contact us to have it removed.

12. Changes to this Policy

We may update this policy. We will update the version above, and for material changes we will notify you in the app or by email.

13. If You Are in the EU, EEA, UK or Switzerland

If you are in the European Union, the European Economic Area, the United Kingdom or Switzerland, the GDPR (or the UK GDPR, or the Swiss Federal Act on Data Protection) applies, and the following also applies to you.

Who is the controller: Swing to Smash is the controller for your account, sign-in and profile, your help chats and support requests, your acceptances of our terms and policies, the portal itself, organizer billing (Event passes) and our security logs. For an Event's own data — its registrations, teams, check-in, scores, waivers and fee tracking — the Event's Organizer is the controller, and Swing to Smash processes that data on the Organizer's behalf (as its processor), keeping signed waivers for their retention period (section 8). You can reach us at info@swingtosmash.com, and an Organizer through the contact details on their Event's About page when they've added them.

Why we may use your data (legal bases):

  • To perform our agreement with you (Art. 6(1)(b) GDPR) — your account, registration, teams, schedule, scores, results, payment reconciliation, and the emails needed to run the Event.
  • Organizer billing (Event passes) — to perform our agreement with the organizer who buys a pass (Art. 6(1)(b)), and to keep the purchase records tax law requires (Art. 6(1)(c)).
  • For legitimate interests (Art. 6(1)(f)) — publishing the tournament portal so players and spectators can follow the Event; sending a partner invitation a teammate asks for; keeping the Service secure; improving the help assistant and preventing its abuse, through its question log; answering support requests and preventing abuse of the support form; and keeping waiver records to establish or defend legal claims.
  • Your profile photo — the photo from your Google or Microsoft account, shown by default, is based on legitimate interests (Art. 6(1)(f)): it helps players recognise one another at the Event. A photo you upload or take yourself is based on your consent (Art. 6(1)(a)). You can remove either at any time in your profile, and your initials are shown instead.
  • To meet a legal obligation (Art. 6(1)(c)) — where a law requires us to keep or disclose data.

Your name and email address are needed to take part; your gender is needed only to enter men's, women's or mixed disciplines. Everything else is optional. If a teammate invited you, we received your name and email address from them (see section 3).

Transfers: the Service runs on Microsoft Azure, and your data may be stored or processed outside your country, for example in Canada or the United States. We rely on an adequacy decision where one exists (the European Commission recognises Canada as providing adequate protection) and otherwise on the European Commission's Standard Contractual Clauses in our agreement with Microsoft. Payments for Event passes are processed by Stripe, Inc. (United States) under the EU–US Data Privacy Framework or Standard Contractual Clauses.

Your rights:

  • Access your data and get a copy in a portable format.
  • Correct it, have it erased, or restrict how we use it (within the limits in section 9).
  • Object to processing based on legitimate interests — including appearing in the public portal.
  • Withdraw consent at any time, without affecting earlier processing.
  • Complain to the data protection authority where you live or work. We'd appreciate the chance to address your concern first.

We make no decisions about you based solely on automated processing that have legal or similarly significant effects.

14. Contact

Questions, export requests, or deletion requests: info@swingtosmash.com. For a specific Event, you can also contact its Organizer, through the contact details on the Event's About page when they've added them.