Organizer terms
This is a draft
A lawyer is reworking these terms. They don't apply to anyone yet: organizations can't sign themselves up on Notch today. Words in [square brackets] are still to be decided.
1. Who these terms are between
1.1 These terms are between us and the organization you create on Notch. You accept them for that organization, and you confirm you are allowed to.
1.2 They apply as long as your organization exists on Notch, and some parts continue after it closes (§12, §15.4).
1.3 Every person who signs in to Notch also has their own account. These terms are about what your organization does, not about personal accounts.
2. Words used in these terms
| Word | Meaning |
|---|---|
| Your organization | The club, league or organizer you created. |
| Player | Anyone whose record your organization can see: players, and the guardians and emergency contacts on their records. |
| Guardian | A parent or guardian who manages a player's record while the player is under the guardian age (§6). |
| Personal information | Information about an identifiable person. |
| The shared record | Notch keeps one record per person. Several organizations can see it, each for its own reason. The person (or their guardian) controls it. |
| Access | What your organization sees of a person. It comes only from a reason: they joined you, a club entered them in your competition, they applied to your program, and so on. Each reason gives a level: match (name, public name, national ID, age-grade proof, gender, playing details), contact (adds date of birth, email, phone, address, emergency contact, guardians, consents) or medical (adds medical notes). |
| Your records | What your organization adds: registrations and memberships with you, squads, team sheets, competitions, results, programs, notes and reasons your staff write, your staff list, your settings and your website. |
3. Who is responsible for players' information
3.1 You decide why and how your organization uses players' information, and you are responsible for it. In privacy terms your organization is the controller (in Canadian terms, the organization accountable for it).
3.2 We hold and protect the information for you, as your service provider (a processor). We use it to run the service for you and for no purpose of our own, except as §3.4 says.
3.3 Some rules are ours, and the same for every organization. You agree to work within them:
- each person has one shared record, and the person (or their guardian) controls it;
- an organization sees a person only through a reason, at a level, and the person can see that, lower it or end it;
- what appears on public pages, and how minors are protected there (§6);
- how the guardian age is decided (§6);
- how long the service keeps things (§12);
- how the service is secured (Appendix A).
3.4 We also use information to keep the service running and secure, to keep the shared record correct (for example merging duplicates), to meet the law, and to show the public match record of competitions that were published.
4. What you may do with players' information
4.1 Use it to run your organization's cricket: registration and membership, teams and squads, competitions, fixtures, results and scoring, programs and selection, safety on match days, and contacting players and families about those activities.
4.2 Use only what your organization can see, at the level the player agreed to.
4.3 Ask for contact details only when you need to reach people, and for medical notes only when you need them for someone's safety. The product never makes medical notes compulsory, and you must not make them a condition of playing.
5. What you must not do
5.1 You must not:
- sell, rent or trade players' information, or give it to anyone for their own use;
- use it for advertising, or send players marketing without the consent the law requires (CASL);
- use it for anything unrelated to cricket at your organization;
- copy it out of Notch (into spreadsheets, screenshots, other systems) beyond what you need, or keep copies once you no longer need them;
- show it to anyone outside your staff, unless the law requires it or the player agrees;
- try to see information your organization has no access to, or test the security of the service;
- create a record for someone without their agreement (or their guardian's), or enter details you know are wrong, such as a false date of birth;
- write health or other sensitive details in free-text fields (transfer reasons, notes, messages);
- let several people share one staff account.
5.2 If you copied information out of Notch, these terms still apply to the copy.
6. Minors and guardians
6.1 The guardian age. Below it, a guardian decides for the player: registration, sharing, consents and edits. It is set by the provincial body of the province your organization chose as its home, from 13 to 18, and is 18 where that body hasn't set one or there is no provincial body on Notch. In Quebec it is never below 14. When a player is registered in several provinces, the highest age applies. You can't change the guardian age.
6.2 Registering a minor. When your organization registers a player under the guardian age, Notch emails the guardian, and the registration starts only once the guardian agrees. You must not get around this: for example by registering a child as an adult, giving an email address you control as the guardian's, or entering a date of birth you know is wrong.
6.3 Public pages. Until 18, public pages show a player's initials, not their full name (unless the person in control turns on the full name), and never their age or profile page. When you publish anything about players outside Notch (your own social media, for example), treat minors the same way unless their guardian agrees.
6.4 People who work with minors. You are responsible for choosing, screening and supervising the staff and volunteers you give roles to, under the safe-sport rules that apply to your organization.
6.5 Privacy contact first (proposed). Before your organization registers any minor, you must name a privacy contact (§7).
7. Your privacy contact
7.1 Name a person responsible for privacy at your organization, with a contact email. Use a role mailbox (for example privacy@…) rather than a personal address.
7.2 Keep it up to date. Notch shows it to players: on your website's About page, in players' data exports and in "Who has your profile".
7.3 Your privacy contact answers players' privacy questions and requests (§11) and is our contact for incidents (§10).
8. Telling players what you do
8.1 Notch tells players, by email, when your organization gains or loses access to their record, why, at what level, and until when. Screens that start a share say "What {your organization} will see". You must not suppress or contradict these notices.
8.2 If you collect or use players' information outside Notch, or for a purpose its screens don't describe, you must tell players yourself, clearly, before you do it. Where the law requires it (for example in Quebec), do so in French.
8.3 You are responsible for what you publish on your website and in messages you send.
9. Your staff and security
9.1 Give each staff role only to people who need it, and the smallest role that does the job. Remove people as soon as they leave.
9.2 Each person uses their own account. Administrators must use two-step verification; we ask everyone who sees contact details to turn it on too.
9.3 Keep devices with Notch on them locked, and sign out of lost ones. (Scorers' phones keep match squads, by public name, for offline scoring.)
9.4 Tell us at once if you think a staff account has been taken over (§10).
10. Incidents
10.1 When you suspect one. If personal information from Notch may have been seen, lost, changed or used by the wrong people (a lost staff laptop or phone, an email to the wrong person, a staff account taken over), tell us within [24 hours] at [incident contact], and help us stop it.
10.2 When we find one. If we find an incident affecting your organization's information, we tell your privacy contact [without undue delay / within a set time], with what we know, and keep you informed as we learn more.
10.3 Notifying. As the organization responsible (§3.1), you decide whether the law requires notifying the regulator and the people affected, and you notify them, with our help and the facts we have. For an incident in our own systems, or in the shared record, that affects several organizations, we coordinate the notices with each of them.
10.4 Records. Keep a record of every incident involving your players' information, including minor ones, for at least [24 months].
11. Requests from players
11.1 Most requests players can handle themselves in Notch: see who has their record and the access log, download a copy, lower or end an organization's access, leave, correct most of their details, and erase their record.
11.2 If a player (or guardian) asks your organization, answer within 30 days. Your registrar corrects a player's name, date of birth and gender, which players can't change themselves.
11.3 If a request about your organization's information reaches us, we pass it to your privacy contact and help you answer it.
12. Keeping information, and when your organization closes
12.1 While your organization is active, your access to each person lasts as long as its reason:
- a membership, until the person leaves or you end it;
- a competition entry, until the season ends plus your wrap-up period (0 to 365 days; 90 unless you change it);
- other reasons, as their screens say.
When access ends, history stays: registrations, squads, match records and statistics. The live record (contact details, for example) doesn't.
12.2 The periods we apply to everyone (for example the access log for 24 months, audit records for 7 years) are listed in the privacy assessment (§4). They can't be shortened per organization.
12.3 When you close your organization (proposed):
- give us [30 days'] notice where you can, and tell your members;
- all your organization's access to people ends, and each person gets the usual notice;
- staff roles end; your website is unpublished and any custom domain removed;
- published competitions, results and statistics stay public, as part of the public match record;
- players' records are not deleted: they belong to the players, and other organizations may see them for their own reasons;
- your organization's own records are deleted after [90 days], except the audit log and anything the law requires us to keep;
- before closing, you can ask for a copy of your organization's own records.
12.4 If we close your organization, the same applies (§15).
13. Acceptable use
13.1 Be who you say you are. Your organization's name, French name, website name, logo and about text must be your own. Don't impersonate, or pass yourself off as, a real body, league, club or person. Don't suggest you are official, sanctioned or affiliated when you aren't.
13.2 Notch shows "Sanctioned by {body}" only when a verified body governs your organization. Don't claim it any other way.
13.3 Don't use organizations you create for others, or several accounts, to get around name checks, limits or verification.
13.4 What you publish and send must be lawful, must not harass or discriminate, and must not use other people's names, logos or content without permission.
13.5 Use Notch to contact players only about your organization's cricket.
13.6 Anyone can report a page that breaks these rules through the "Report" link on public pages, or at [abuse contact].
14. Verification
14.1 What it is. We check that your organization is real and that the people running it are who they say.
14.2 What we may ask for: [to be set: for example the organization's legal or society registration, a public website or account in its name, a letter from a body that governs it, the name and role of the person applying, and its home province]. We may refuse to verify.
14.3 What it gives you: a verified badge; your name is protected against look-alikes; you can be a governing body for other organizations; you can use your own web domain; and the daily limit on staff invitations is lifted.
14.4 Until then: at most 20 staff invitations a day; no custom domain; you can't be a governing body; and your competitions show "Not sanctioned" unless a verified body accepts you as a governed member.
14.5 Verification is not an endorsement. It doesn't mean we've checked how you handle information.
14.6 We may remove verification if the facts change or you break these terms.
15. Suspension and ending
15.1 We may suspend your organization if you break these terms, if it impersonates someone, if players (especially minors) are at risk, or if the law or a regulator requires it. Where we can, we tell you first and give you a chance to fix it. Where there is a risk to players, we may act at once.
15.2 While suspended: your organization and its public pages disappear from public view; your staff can't act for it; players keep their records and can still see and end your access. We tell you why and how to respond.
15.3 You may end these terms by closing your organization (§12.3). We may end them, after a suspension that isn't resolved, or if we stop offering open sign-up, with [notice period].
15.4 What continues after the end: your duties about information you copied (§5.2), incident cooperation (§10) and records you must keep.
16. Changes to these terms
16.1 We tell you [30 days] before a change that matters to you, and ask you to accept the new version. If you don't accept, you can close your organization before the change takes effect.
17. Fees, liability and indemnity
Not written yet.
18. Governing law and disputes: flagged
Not written yet.