Privacy Policy
Effective: September 25, 2026. Revised: November 17, 2026
This English version is a reference translation. If it differs from the Japanese version, the Japanese version prevails.
ScrimLink (the "Operator") handles personal information in the Service in accordance with Japan's Act on the Protection of Personal Information (the "APPI") and other applicable laws, as described in this Privacy Policy.
1. Operator
Name: ScrimLink. Contact: support@scrimlink.com.
The representative's name and the address are provided without delay on request.
2. Information we collect
Account: school email address (for external coaches, the personal email address entered by the inviting program lead), password (hashed by the authentication provider; the Operator cannot read it), display name (a handle), school, and account type (program lead or external coach). If the school is not in the list, or if several schools share the domain, the school name and country entered at sign-up. For program leads who sign up themselves, the date and time you confirmed you are the program lead and agreed to the Terms, and the version of the Terms you agreed to.
Optional settings: time zone, display language, and the in-game ID of the team's lobby contact (such as a Riot ID, BattleTag, Epic ID, friend code or player tag, matching the team's game; one per team).
Activity: teams (name, logo, and optionally a skill band and a stream channel URL) and their program leads and external coaches, scrim posts (title, time, format, server) and applications, coordination threads (proposal cards, messages, preset phrases and reports), match times, formats and results, ratings, team claims, and in-app notifications. Screenshots of match results submitted when the two reports disagree, and any note added to them (seen only by the Operator; in-game names may appear in them).
Access logs: IP address, browser type, access time and similar data, used for troubleshooting and abuse prevention.
We do not ask for real names, home addresses, phone numbers, dates of birth or parents' contact details.
3. How we use it
(1) Verifying identity with a school email and managing accounts; (2) finding opponents, agreeing on terms, confirming matches, recording results and ratings, and reviewing disputed results; (3) in-app notifications and emails (sign-up confirmation, invitations, password resets, match updates and team claims); (4) adjusting language and time display; (5) showing the lobby contact's in-game ID after a match is confirmed; (6) preventing abuse, checking messages on send so that outside contact details are not shared in coordination threads, reviewing records for safety and answering inquiries; (7) producing aggregated statistics that do not identify individuals, and improving the Service; (8) confirming eligibility to register, and recording consent to the Terms and this Policy.
We will ask for your consent before using personal information for any other purpose.
4. What other schools can see (provision to third parties)
Because the Service connects schools, the following is shown to users at other schools and others.
Program leads consent to this when they sign up.
Everyone, including people who are not signed in: on the home page, team name, school name, team logo or school icon, region, game, time and format. On the scrim list, the title, game and time. On a scrim post page, the title, team name, school name, region, game, time, format and server. On the rankings, school name, team name, team logo or school icon, rating and record. In the match results section at the top of public pages shown to people who are not signed in, both teams' names, school names, team logos or school icons, regions, the game, time, winner and score. This section also shows matches in progress (started within the last 3 hours, with no confirmed result yet): both teams' names, school names, team logos or school icons, and the game. For a team that has registered a stream channel, a link to that channel is added to the in-progress entry.
Signed-in users at other schools: the above except the match results section, plus the team's skill level (optional, chosen by a program lead). Applications and coordination threads (including the display name of whoever wrote a message) are shown only to the two schools involved.
The opponent team of a confirmed match: in addition, the display names of the team's managers (program leads and external coaches) and the in-game ID of the team's lobby contact (such as a Riot ID, BattleTag, Epic ID, friend code or player tag).
School email addresses are never shown to other schools. Otherwise, we do not provide personal data to third parties without consent except as permitted by law, and we keep records of third-party provision as the law requires.
5. Service providers
We entrust the handling of personal data to the following providers only as needed for the purposes above. They handle it under contract, and we supervise them appropriately.
Supabase, Inc. (United States): database, authentication and image storage. Data is stored on servers in the Tokyo region.
The Constant Company, LLC (Vultr, United States): the servers that run the application, in a Tokyo data center.
Resend, Inc. (United States): delivery of emails such as sign-up confirmations, invitations and password resets. It handles recipient addresses and email content.
6. Provision to third parties in a foreign country
In the following cases personal data is provided to third parties in the United States.
Program leads consent to this when they sign up.
(1) In matches with US schools (Connect globally), the information in section 4 is shown to users at US schools. They are individuals, and measures equivalent to the APPI are not guaranteed. (2) Resend, Inc. (section 5) delivers email, handling data under its privacy policy and data processing agreement.
The US system: the United States has no general federal law equivalent to the APPI that applies to all businesses. There is regulation of unfair or deceptive practices under Section 5 of the FTC Act, sector-specific federal laws (such as COPPA and FERPA), and state laws (such as the California Consumer Privacy Act). See the survey of foreign systems published by Japan's Personal Information Protection Commission for details.
Supabase, Inc. and The Constant Company, LLC store data on servers in Japan (Tokyo) and are contractually barred from handling personal data beyond our instructions, so their role is not a provision in this sense. That they are US companies is covered under understanding the external environment in section 7.
7. Security measures
Basic policy: we have set out this Privacy Policy to handle personal data properly.
Handling rules: we define who handles personal data and how, at each stage from collection to deletion.
Organizational measures: a person is responsible for personal data. Any leak, or suspected leak, is reported to that person, and we report to the Personal Information Protection Commission and notify affected people as the law requires.
Personnel measures: everyone handling personal data has committed to confidentiality.
Physical measures: data is kept in the cloud providers' data centers, and we do not store personal data on the Operator's own devices.
Technical measures: encryption in transit (TLS), password hashing, row-level security in the database, administrative keys used only on the server, and least-privilege access.
Understanding the external environment: our providers Supabase, Inc., The Constant Company, LLC and Resend, Inc. are US companies. Database and application data is stored in Japan (Tokyo). For email delivery, Resend, Inc. handles recipient addresses and content in the United States. We take our security measures with the US system described in section 6 in mind.
8. Retention and deletion
We keep personal data while the account exists. When you close it from Settings, ask us to close it, a manager removes from a team a program lead who never opened the invitation link, or an external coach is no longer on any team, we delete the account and its personal data (email and display name) without delay. The date and time you confirmed you are the program lead and agreed to the Terms, and the version of the Terms you agreed to, are also deleted when the account is deleted. An email address entered on the contact form stays until the operator has replied. Copies in backups are erased in the normal backup cycle.
To keep other schools' records and ratings consistent, match results remain linked to the team name. Coordination threads (including message text) also remain, without the closed account's name. Screenshots and notes submitted for a disputed result are deleted 30 days after the Operator's ruling.
Access logs are kept only as long as needed for troubleshooting and abuse prevention.
9. Students and schools
The Service is for high-school-age students and older and is not directed at children under 13. If we learn we have collected information from a child under 13, we delete it promptly.
Students do not have accounts, and the Operator does not collect students' names, in-game IDs, email addresses or other information. If something concerns you, for example a team logo that shows a student, parents and guardians can tell us through the program lead or directly at support@scrimlink.com.
We do not sell users' information, use it for advertising, or show targeted advertising.
10. Cookies
The Service uses cookies to keep you signed in and to remember your display language (locale) and time zone (tz). All of them are needed to provide the Service.
We do not use advertising cookies or tags. To count page views and improve loading speed, we use Cloudflare Web Analytics. It sets no cookies and creates no information that identifies or tracks you.
External transmission (Telecommunications Business Act): when you open a page of the Service, your browser sends Cloudflare, Inc. (United States) the page URL, the referring URL, your browser and device type, screen size, and how long the page took to load. Your IP address is also sent as part of the connection. Cloudflare, Inc. uses this to count views and measure loading speed per page, and we see only the totals. We use no other program that sends user information to outside companies. If we add one, we will announce it on this page in advance.
11. Your requests
You may ask us to notify you of the purposes of use, to disclose your retained personal data (including records of third-party provision), to correct, add to or delete it, to stop using or erase it, or to stop providing it to third parties.
Send your request from your registered email address to support@scrimlink.com. We will respond without delay after confirming your identity, free of charge. For requests through an agent we may ask for documents showing their authority.
12. Contact and complaints
Questions and complaints about how we handle personal information go to support@scrimlink.com.
13. Changes to this policy
We may change this policy when laws or the Service change. We will show the new content and the effective date in the Service, and ask for consent in advance where the law requires it.
Effective: September 25, 2026
Revised: September 27, 2026 (lobby contact in-game IDs by title; scrim post descriptions removed from the information we collect)
Revised: November 7, 2026 (more game titles; their lobby contact in-game ID types added)
Revised: November 10, 2026 (Cloudflare Web Analytics for page view counts, and what it sends, added)
Revised: November 10, 2026 (information shown in the match results section at the top of public pages added)
Revised: November 10, 2026 (matches in progress and links to teams' stream channels added)
Revised: November 11, 2026 (coordination thread messages added to the information we collect; coach Discord IDs are no longer collected or shown, and stored ones were deleted)
Revised: November 15, 2026 (account types are now called program lead and student; the school name and country entered at sign-up, when the school is not in the list, were added to the information we collect; the date and time you confirmed you are the program lead and agreed to the Terms, and the version of the Terms you agreed to, were added to the information we collect)
Revised: November 17, 2026 (student accounts were discontinued and student and player information is no longer collected; personal avatar images and team descriptions were removed from the information we collect and show; external coaches' personal email addresses, team skill bands, screenshots for disputed results and team claims were added; the match results section is shown only to people who are not signed in; when accounts are deleted was revised)