Privacy · SlongeHoops

Who is responsible

SlongeHoops is operated by slonge solutions (Benjamin Tobler, sole proprietorship, Neugasse 44, 9000 St. Gallen), Switzerland. You can reach us at [email protected].

We will name our representative in the EU here before we offer SlongeHoops to people in the EU.

Two roles: ours, and your club’s

Who is responsible for a piece of data depends on what it is.

We are responsible (the controller) for:

accounts and sign-in;
security: the bot check, the security log and abuse prevention;
the billing records we hold;
the website;
the short notice we send ourselves when a new account is created;
mail you send us, and our answers;
the affiliate programme;
analytics, if you agree to them.

The club is responsible for its teams’ data: rosters, players’ names or nicknames and numbers, who is a member of a team, players’ quiz results, the team’s playbooks, plays and practice plans, and coach invitations. We process that data on the club’s behalf and on its instructions, as its processor (GDPR Art. 28, Swiss revFADP Art. 9). A coach whose team belongs to no club is responsible for that team’s data in the same way.

The terms for that processing are in section 11 of our Terms, “Data we process for clubs and coaches”.

If you are a player or a parent and your question is about team data — a name on a roster, a quiz result, who can see what — ask your club or your coach first. They decide about it. We help them answer, and if you write to us we pass your request on to them and help where we can.

The short version

If you do not make an account, nothing you draw leaves your browser.
We run no advertising trackers and no advertising pixels. Analytics, if we switch them on, load only after you agree to them in the consent banner, and you can change your mind at any time.
A player’s entire record is a display name. No birth date, no address, no phone number, and no e-mail is required.
Names on your roster never leave your team. They are structurally excluded from every share link.
You can export everything we hold about you, and you can delete your account yourself.

Using SlongeHoops without an account

The editor, the library, playback and video export run in your browser. Plays you draw are stored in your own browser’s storage on your own device. We do not receive them. If you clear your browser’s data, they are gone, which is why export exists.

A share link carries the play inside the link itself. Anyone who has the link can open the play. The link is not a secret; treat it as public.

This storage in your browser is strictly necessary for the service you asked for, so it needs no consent.

If you send us feedback from the app without an account, we receive what you wrote, the kind and topic you picked, your language, the screen you sent it from and the app’s version. No name, no address and no plays. Turnstile (see below) checks that a person sent it. We keep it for two years.

Using SlongeHoops with an account

An account exists so your plays sync, so a team can share a playbook, and so a coach can see whether players have learned a play.

While you are signed in, the plays, drills, playbooks, practice plans and teams you make are saved to your account as you work, with no separate upload step; your browser keeps a working copy so the app also works offline. Each account has its own copy on the device, and when you sign out, that copy is removed from the device once everything in it has reached your account. Plays you drew before signing in stay in your browser and are only added to your account if you choose to add them.

What we store, and why:

What	Whose	Why	How long
Display name	Yours	So teammates know who is who	While the account exists
E-mail address, if you signed in with one	Yours	Signing in, and getting back in	While the account exists
An account without e-mail, made to join a team with a team code	Yours	Signing in without an e-mail address	While it is in a team; deleted 30 days after it was made if it never joined a team, or 90 days after it left its last team
Avatar image, if you upload one	Yours	Optional	While the account exists
How you found SlongeHoops, if you answer the one-time question (for example “YouTube”)	Yours	Knowing which channels bring coaches to us	While the account exists
For a new account: where the link you arrived through came from — its campaign tag (for example “youtube / short-hammer”), the website that linked to us and the first page you saw	Your browser, for the open tab only	Knowing which posts and campaigns bring coaches to us	While the account exists
Your plays, drills and playbooks	Yours	The product	30 days after you delete them, then permanently gone
Practice plans: date, time, length, focus, the blocks and the coach’s notes	A team’s practice plans are the team’s; one without a team is yours	The practice planner. Only the team’s coaches and club administrators see them, never its players	30 days after they are deleted, then permanently gone
Roster entries: a player’s name, squad number and position, entered by a coach	The player’s, entered by the coach	The coach’s squad list, and names on the court tokens	Until the coach deletes it, or 30 days after a soft delete
Quiz results: score, mode, timings, the answers	The player’s	So a player can track themselves and a coach can see who has learned a play	3 years after the quiz was finished
Team and club memberships and roles	Yours	Deciding what you may see and do	While the membership exists
Invite codes and share links you created	Yours	Letting people join or view	30 days after they expire or are revoked
Security log: who did what, when	Yours	Investigating abuse and security incidents	2 years, with your identity removed if you delete your account
Monthly usage counters for the AI features	Yours	Abuse and cost control	Indefinitely; a number, not a record of content
Subscription: which plan, the status, the provider’s ids	Yours	Knowing what you paid for	While the subscription exists
Feedback you send from the app: what you wrote, its kind and topic, your language, the screen and the app’s version, and whether we may answer you by e-mail	Yours	Improving the app; answering you if you said we may	2 years after you sent it
Mail you send us, and our notice that a new account was made (its e-mail, display name and sign-in method)	Yours	Answering you; knowing who signed up	2 years after the last message in the conversation

Rosters, quiz results, team memberships, team playbooks, plays and practice plans, and coach invitations are team data: we hold them for the club or the coach, as explained above.

Backups of the database expire on their own schedule after the periods above, and deleted data disappears from them when they do.

We never store: a card number, a billing address, an invoice, a date of birth, a phone number, a postal address, a health record, or a photograph you did not choose to upload as an avatar.

Why we are allowed to

Under the GDPR (Art. 6):

Contract (Art. 6(1)(b)): your account, syncing, teams and subscriptions. We need the data to give you what you signed up for.
Legitimate interests (Art. 6(1)(f)): security, the bot check, the security log, abuse prevention, the new-account notice we send ourselves, and answering support mail. Our interest is keeping the service safe, knowing who is using it and helping you. You can object to this; see “What you can do”.
Legal obligation (Art. 6(1)(c)): keeping accounting records for 10 years.
Consent (Art. 6(1)(a)): analytics, and only after you agree in the consent banner.
Team data we process for a club or a coach rests on the club’s or the coach’s own legal basis. They are responsible for it.

Under the Swiss data protection act (revFADP), we follow its principles: we process only what we need, for the purposes stated here, openly and securely. We ask for consent only for analytics.

Children

Most players using SlongeHoops are minors, and the design answers that by collecting almost nothing.

Players under 16 — or under the age of digital consent in their country — join only through a coach’s team code. The club or the coach is responsible for having their parents’ consent before inviting them, and confirms this in the app when creating a team code.
We ask for no age and no birth date. A player needs only a display name. No e-mail address is needed at all.
No advertising, no public profiles, no messaging between players, no tracking of children.
Minors cannot buy subscriptions. Purchases are made by adults: coaches and clubs.
The United States. SlongeHoops is not directed at children under 13 in the United States. If we learn that a child in the United States under 13 is using it without verifiable parental consent, we delete that child’s data.

A parent who wants a child’s data corrected or deleted can ask the child’s club or coach, or write to us.

Who processes data for us

Who	What they process	Where
Supabase	The database, sign-in, file storage and server functions — everything an account touches	EU: Frankfurt, Germany (`eu-central-1`). Supabase is a US company; its data processing agreement with us includes the EU Standard Contractual Clauses.
Stripe	Payment, as the seller on record. Stripe is an independent controller for the sale.	Global. Stripe is certified under the EU-US and Swiss-US Data Privacy Framework.
Cloudflare	Turnstile, the check that you are not a bot, which sees your IP address and some request metadata when a sign-in sheet, a join link or, without an account, the Feedback dialog opens	Global. Cloudflare is certified under the EU-US and Swiss-US Data Privacy Framework.
DeepSeek, or Anthropic if configured instead	Only the AI quiz writer, and only when a coach presses it. See below.	DeepSeek: People’s Republic of China. Anthropic: United States. See below.
Resend	E-mail addresses and the content of the mails we send: sign-in codes, coach invitations, and a short notice to the operator when a new account is created (its e-mail address, display name and sign-in method)	EU: Ireland (`eu-west-1`). Resend is a US company, certified under the EU-US and Swiss-US Data Privacy Framework, and its data processing agreement includes the Standard Contractual Clauses.
Cloudflare (Pages)	Hosting the website and the app: your IP address and the usual web-server request metadata	Global. Data Privacy Framework, as above.
Cloudflare (Web Analytics), only if you accept analytics	Which page you opened, where you came from, your browser, device type and country, and how fast the page loaded. No cookie, no identifier, no profile; your IP address is used for the country and not stored.	Global. Data Privacy Framework, as above.
Better Stack, only if you accept analytics, and only in the app	How fast the app loaded for you (web vitals), JavaScript errors with the page they happened on, page views, your browser and device type, your IP address (which every request carries) and the approximate location derived from it, and a random visit id from the `_bs` cookie. No recording of your screen, no clicks, no console output, no browser fingerprint, and no name or e-mail address. Kept 3 days (page views and timings) and 90 days (errors).	United States. Better Stack’s data processing agreement relies on the EU-US and Swiss-US Data Privacy Framework and, where that is not available, the Standard Contractual Clauses.
Cloudflare (Email Routing)	Mail you send to hello@ or login@ slongehoops.com, forwarded to the operator’s mailbox	Global. Data Privacy Framework, as above.
Hostpoint	The operator’s mailbox, where those mails and the new-account notices arrive	Switzerland
Google, Microsoft or Apple, only if you choose to sign in with them	They tell us your name and e-mail address and that you signed in; they learn that you use SlongeHoops. Each is an independent controller for its own account.	Global. Each is certified under the Data Privacy Framework; their own terms apply to that account.

We do not sell data, and we do not share it with anybody not on this list.

Payment

Payments are handled by Stripe Managed Payments. Stripe is the seller on record — the merchant of record — not merely our payment processor. For the sale itself Stripe is an independent controller: its own privacy policy applies to what it collects at checkout. In practice that means:

Your card statement will read LINK.COM* followed by our product marker, because Link is the brand Stripe uses with customers.
We never see your card. We never see your billing address. We never see the invoice.
When you press a plan, we hand Stripe your user id, the id of the account, team or club the plan is for, our product marker, the price id, and the e-mail address on your account so their form is filled in. Nothing else — no play, no roster, no team name, no player’s name.
If you change the e-mail address at Stripe’s checkout, the address Stripe then holds is theirs and not ours.
Stripe may refund a customer within 60 days at its own discretion.
If you ask Stripe to delete your data, Stripe cancels your subscriptions and deletes its own records, including records held in our account. Our copy of a subscription is a mirror of theirs, never the record. To ask Stripe to delete what Stripe holds, you have to ask Stripe.

The AI quiz writer

If a coach presses the AI quiz writer, one request is sent to a model vendor containing the play as text a coach could read: its name, description, tags, situation and formation; each phase with its coaching note; each action in order with its timing; where each player stands, named as a court spot; and the simulated-defense settings if they are switched on. Players appear as the numbers 1 to 5.

Not sent: roster names, squad numbers, lineups, team or club names, user ids, e-mail addresses, account data, or any image.

The vendor is DeepSeek, in the People’s Republic of China, by default, or Anthropic, in the United States, if we have configured it instead. Nothing is sent unless a coach presses the button.

There is no adequacy decision for China. That means the law there does not give your data the same protection as Swiss or EU law. That is why we send no roster names and no account data. But coaching notes are free text, and nothing removes names from them. If you type “Mika waits here” into a phase note, that sentence goes to the vendor. So: use nicknames or numbers in coaching notes, not players’ full names.

Cookies and analytics

The website sets no advertising cookie, runs no third-party tracker and carries no social pixel.

Analytics are off unless we switch them on. When they are on, the website and the app show a consent banner, and the analytics script is loaded only after you choose “Accept analytics”. “Reject” is just as easy and changes nothing about the website or the app. The analytics count page views and clicks, not people, and do not track you across other sites. As long as no analytics tool is configured there is nothing to consent to, and no banner is shown. On the website the tool is Cloudflare Web Analytics (see the list of processors above): it sets no cookie of its own and counts visits, not visitors. In the app, the same “Accept analytics” also turns on Better Stack, which measures how fast the app loads for you and reports the errors it runs into, so we can fix them. It keeps a random visit id in a first-party cookie called _bs on app.slongehoops.com (with a copy in the browser’s local storage if cookies are blocked) for up to two years, and nothing else about you.

Your choice itself is kept in a first-party cookie called sh_consent on slongehoops.com and its subdomains (so the website and the app share it), for 12 months. It holds only your answer, for example v2.analytics=0, and is strictly necessary to respect it. The iPhone and iPad app cannot keep cookies, so there the same answer and the date you gave it are kept in the app’s own storage on the device instead. After 12 months, or when we change what we ask, the banner asks again.

To change or withdraw your choice, open “Privacy settings” in the website’s footer or on the account screen in the app, switch analytics off and save. The app deletes the _bs cookie at once, and from the next page you open, no analytics script is loaded. Deleting your cookies for slongehoops.com also withdraws it and makes the banner ask again.

The app itself stores things in your browser that it needs to work: your plays, your settings, your sign-in session and, if you arrived through a referral link, the referral code. These are first party, on your own device, and need no consent. The referral code is kept only until you close the tab, on the website and in the app alike, and so is where your visit came from (a link’s campaign tag and the website that linked to us), which a new account keeps as described above.

The affiliate programme

If you arrive through an affiliate’s link, the referral code is kept in your browser for that visit only. If you start a subscription in that visit, or type an affiliate’s discount code at the checkout, we record which affiliate referred you, when, and whether it was by link or by code. The affiliate never learns who you are: they see counts, dates and amounts, never a name, an e-mail address, a club or a user id. That record is deleted with your account. A click on an affiliate’s link is counted per day and page, with nothing that identifies you.

If you apply to be an affiliate, we keep your application (name, e-mail, audience and what you tell us). If we turn it down, we delete it after 12 months. If you become an affiliate, we keep your details, commissions and payouts for 10 years after the last payout, because they are accounting records.

What you can do

You have the right to:

See everything we hold about you. In the app, “Export my data” gives you a file with everything keyed to you and nothing about anybody else. You can also ask us.
Take it with you. The same export is in a machine-readable format.
Correct anything. You edit your own profile; a coach edits their roster.
Delete your account. In the app, “Delete my account” does it. Your personal plays and practice plans are deleted. Your quiz results are deleted everywhere. If you were the only coach of a team and there is no club administrator, the team, its playbooks, plays, practice plans and roster are deleted too and everyone loses access at once. If there is another coach, your team content passes to them. Roster entries linked to you are unlinked and the name replaced. Links and invites you created are revoked. The security log keeps what happened but not who you were. Accounting records we must keep are kept for the legal period.
Restrict how we use your data while a question about it is being settled.
Object to what we do on the basis of legitimate interests.
Withdraw your consent to analytics at any time, under “Privacy settings”.

A coach can delete a roster entry and a player’s quiz results at any time.

A live subscription cannot be left billing quietly: on deletion we try to cancel it at Stripe and record whether that worked. If it could not be reached, we cancel it by hand.

For anything the app does not do by itself, write to [email protected]. We answer within 30 days. For team data we pass your request to the club or the coach responsible and help them answer.

Complaints. You can complain to the Swiss Federal Data Protection and Information Commissioner (FDPIC / EDÖB, www.edoeb.admin.ch), or, if you live in the EU, to the data protection authority where you live. We would like to hear from you first, but you do not have to write to us before you complain.

Security

Access to every row is decided by the database, not by the app: default deny, with a policy per table. Codes for invites and share links are high-entropy, expire, can be revoked and are rate limited. Administrators of a club must use a second factor for sensitive operations. Data is encrypted in transit and at rest by our hosting provider. Avatars sit in a private bucket with one folder per user.

None of this makes a share link private. A share link is a capability: whoever holds it can open what it points at.

If something goes wrong. If there is a data breach, we tell the FDPIC as soon as possible and, where the GDPR requires it, the EU supervisory authority within 72 hours. We tell the people affected directly where the breach is likely to put them at high risk. If it concerns team data, we tell the club or the coach responsible without undue delay.

Changes

If this policy changes in a way that matters, we tell you at least 30 days ahead, by e-mail or in the app, and update the date at the top. Smaller corrections just update the date.

Contact

[email protected]