Version —

Privacy & Terms of Service

This is the actual agreement between you and Pivot — written to be read, not just clicked past. If anything is unclear, ask (see "Contact" at the bottom).

1.Acceptance of these terms

By creating a Pivot account, you agree to this document as it stands on the date you accept it. We keep a dated, versioned record of that acceptance — not just a checkbox that gets forgotten, an actual log entry: who, when, which version. If we change these terms in a way that matters, we'll ask you to accept the new version before you can keep using your account (see section 9).

2.Who's responsible for what

Pivot is used by clubs all over the world — and data protection law isn't the same everywhere. Pivot doesn't decide which law applies to you: the laws of your own country do, whether that's an EU country, Switzerland, Bangladesh, or anywhere else. This document can't list every country's rules, so instead here's the chain of responsibility that holds regardless of where you are:

Player / family  →  Club  →  Pivot  →  Infomaniak (hosting)

• Your club is the data controller for the sporting data it enters — rosters, assessments, attendance. Your club decides which players to register, what to record about them, and why. That's true whether the data lives in Pivot, a spreadsheet, or a paper folder — the club, through its admin and coaches, is responsible for having a valid reason (and where required by the law that applies to you, valid consent) to hold that data in the first place.
• Pivot is the data processor for that same sporting data — we act on your club's instructions, we don't sell it, and we don't use it for advertising or our own purposes.
• Pivot is itself the controller for a narrower set of data: your own login/account details, security logs, and anything related to billing or subscriptions — data Pivot needs to run the platform and keep it secure, independent of any single club's instructions.
• Infomaniak, our hosting provider, is Pivot's sub-processor. They host the infrastructure Pivot runs on, under their own data-processing terms with Pivot. If Pivot ever adds another vendor that touches personal data (email delivery, analytics, AI features), it gets added here too — see section 6a.

Practically: if you're a club admin or coach adding a player, you're confirming you already have the right to hold that player's information under the law that applies where you are — through the club's own registration process, a parent/guardian's consent, or however that normally works in your country or federation. Pivot doesn't verify this for you, the same way a spreadsheet or a paper folder never did either.

Two examples of what "the law that applies to you" can look like, since they come up often for clubs using Pivot: the EU's GDPR generally requires parental consent for a child's data below age 16 (countries can lower this to 13); Switzerland's data protection act treats a child's own consent as valid only once they have "capacity of judgement" (usually around 13), with a parent or guardian deciding below that. These are examples, not a summary of every country's law — check what applies to you specifically if you're unsure.

3.Acceptable use — what's allowed, what isn't

Pivot is built for one purpose: running a basketball team or club. That means:

Allowed

• Adding data about players you or your club actually coach or manage.
• Sharing your own exercises, plays, and content with your team, your club association, or the wider Pivot community, at whatever circle you choose.
• Using another club or coach's shared content (exercises, plays) within Pivot, the way it's meant to be used — for your own coaching.

Not allowed

• Adding data about someone you don't have the right to hold data about (see section 2).
• Copying another club's shared content and republishing it outside Pivot as if it were your own.
• Using Pivot to store or share anything unrelated to coaching a team — this isn't general-purpose file storage.
• Trying to access another club's private data, or another account's credentials, without authorization.

We can suspend or remove an account that breaks these terms, particularly anything touching a minor's data inappropriately.

4.What Pivot stores, and what it doesn't

We try to collect the minimum needed to run a team, not everything that's technically possible to collect. A few concrete choices:

• No player photos. Pivot doesn't store or upload pictures of players.
• No license documents, no scanned IDs, no national identification numbers (like Switzerland's AVS number) in Roster. A license number (just the reference number, nothing behind it) and a simple "Ready" checkbox are as far as that goes.
• Everything else in Roster (name, birth year, category, gender) is there because a club needs it to run a team — and every field is optional except a first and last name.

5.Data about minors specifically

Most players in a youth basketball club are minors, so this matters more here than in most software. A few things worth knowing:

• Player assessment — technique, game IQ, personality, and attitude scores — counts as evaluative data about a minor. Get comfortable with your club's own policy on this before filling one in; it's not something to enter casually.
• Adding a minor's data may legally require a parent or guardian's consent before you enter it, depending on where your club and its players are based — see the examples in section 2. This is the club's responsibility to obtain, not something Pivot checks for you.
• A parent or guardian can ask their club to show them, correct, or delete everything Pivot holds about their child — see section 7.

6.Who can see what

Nothing in Pivot is shared more widely than you choose. Almost everything you create has its own "Who can see it?" setting:

• 🔒 Only me — private, not even your own teammates see it.
• 👥 My team — everyone active in your club (the default for most things).
• 🤝 My club association — a small group of clubs who agreed to share, needs approval.
• 🌐 Pivot Community — every club on Pivot can see it (view only).

Two things this circle system does not apply to, on purpose: Player assessment never gets shared in bulk with a "player" account, even if a coach sets it to "My team" — a linked player can only ever see their own. And a player account never sees anything just from being on the team — a coach has to explicitly choose to share it with them (for example, turning on "Show to players" on a specific play).

7.Who else touches your data

Pivot doesn't run its own servers — like almost every online service, it runs on infrastructure operated by someone else, under a contract that limits what they can do with what passes through it. Right now, that's:

• Infomaniak — hosting and infrastructure. Their published documentation states their data centers are located and operated in Switzerland.

If Pivot ever adds a vendor that can access personal data — email delivery, analytics, an AI feature — it gets added to this list before it goes live, not after. We don't quietly add data-touching vendors.

8.Access, correction, and deletion

A parent, guardian, or player old enough to act for themselves can ask their club (or Pivot directly — see Contact) for:

• A copy of everything held about that player.
• A correction to anything inaccurate.
• Deletion of that player's data. A club admin can remove a player from Roster at any time, which removes their record and everything tied to it (assessments, attendance, match stats).

For your own account: Settings → "Delete my account & data" lets you leave any club instantly (its data stays intact for other members), or delete a club entirely if you're its only admin — that removes everything in it immediately. Deleting the login itself (your email/password) needs a person on our side to complete, since that's not something the app can do on its own for security reasons — the same page sends that request directly.

We aim to act on these within a reasonable time, and always within what local law requires (for example, one month under GDPR).

9.Security

Data is stored with row-level access rules, meaning the database itself — not just the app's interface — enforces who can read or write what, based on their role in the club. Passwords are never visible to us; authentication is handled by our database provider's standard login system.

If something goes wrong, here's who does what:

• A security incident inside Pivot's own systems — Pivot investigates, contains it, and notifies affected clubs as required by law.
• An incident at a hosting/infrastructure provider (section 7) — Pivot coordinates with that provider and passes on what clubs need to know.
• A correction or export request from a parent — the club handles it, with Pivot providing the technical means to do so.

10.Changes to these terms

We keep a version history — this page shows the current version's date at the top. Small clarifications don't require re-acceptance. If we change something that materially affects how your data is handled, existing accounts will be asked to review and accept the new version before continuing to use Pivot, and the acceptance log (section 1) will reflect exactly which version each person agreed to and when.

11.Liability

Pivot is provided as-is, without warranties beyond what the law where you are requires. We aren't liable for how your club chooses to use the data it enters, or for decisions made based on the app's assessments or statistics. This document is written to be clear and fair, not to be a substitute for a lawyer's review — if you're operating Pivot commercially or at scale, get this reviewed by counsel familiar with data protection law in the jurisdictions you serve.

12.Contact

Questions about your data, or a request to access/correct/delete something? Use the "💬 Contact us" link at the bottom of the Dashboard to message the Pivot team directly, or ask your club admin — they can usually resolve most of this themselves, right from Settings.