Language choice and the country-based default
At the neutral address (/), your saved language choice takes priority. If you have not chosen a language, approximate country metadata already supplied by our host, Cloudflare, recommends Korean for South Korea and English for other recognized countries. A VPN or proxy can make this differ from your actual location. If country information is unavailable or the request times out, the app falls back to your browser’s preferred language. Browser language is not country information.
This language feature does not request device-location permission or contact an external geolocation service. The app does not store IP addresses or country values; it receives only a Korean/English recommendation. The response is not stored in a shared cache. The Cloudflare Privacy Policy linked below explains the provider’s general request handling and technical logs.
Your manual choice is remembered as ko or en in this browser’s local storage. Explicit /ko/, /en/ and language-specific guide URLs always open in that language, regardless of your saved choice or country. When requesting a sign-in link, the app separately stores the return-screen language and a one-hour expiry time. This language value is used only when you return through the sign-in link within one hour. The stored value is removed when the app processes the sign-in return or you clear the site's browser data; it is not automatically removed after one hour. No credentials or return URL are stored. Changing language never translates player or event names or changes schedules and scores.
What this guide covers
This guide explains where the current MatchMaker features store information and when it is shared. Use only the display names needed to distinguish participants in a schedule. Do not enter information that is unnecessary for running matches, such as contact details or health information.
Information stored in your browser
Participant names and gender selections, schedule settings and match assignments, completed scores, event names and dates, saved rosters and the display theme are kept in your browser’s local storage. If you use sharing, the event’s sharing connection details, participant links and pending synchronization records are also stored in that browser.
This information lets you reopen events and keep their schedules and results. Local records are separate for each browser and site origin, so they do not automatically appear on another device. Clearing the site’s data in your browser removes the records held in that browser. Records can also be lost if storage runs out or the browser clears data, so back up important records as JSON files.
Optional sign-in and server sharing
For an event that has not been shared to the server, the information you enter is processed in that browser to create and save its schedule. Sharing requires an approved organizer account. Public sign-up alone does not grant organizer access.
When an organizer requests a sign-in link, the email address they enter is sent to the Supabase authentication service. The authentication token is kept only in the current tab’s memory. After refreshing the page or when authentication expires, the organizer must sign in again. Signing out does not delete event records stored in the browser or on the server.
When an organizer starts sharing an event, that selected event’s participant information, schedule conditions and match assignments, display colors, scores and results are stored on Supabase servers. Saved changes to a shared event are synchronized depending on sign-in and connection status. It does not upload other events or your separately saved rosters along with it. To manage access and synchronization, the server also stores the organizer’s account identifier, a hash of the participant-link token, version numbers, modification timestamps and request identifiers.
Participant links and what is visible
Anyone with a participant link can read the published schedule without signing in. The participant view shows the display names and match assignments that appear in the schedule, plus completed scores and standings when scoring is enabled. The data returned for this view also includes those participants’ identifiers and the match formats.
The data returned for the participant view does not include organizers’ settings such as gender selections, excluded-partner conditions or the draw seed, or players who do not appear in the schedule. However, match formats such as men’s, women’s and mixed doubles can reveal information about team composition.
Before sharing, tell participants what will be visible and use suitable display names. Someone who receives a link can forward it to others or save a copy of the screen. Search-indexing restrictions or deactivating a link cannot recall copies that have already been shared.
Optional score helpers
An organizer can create a score-helper link for a server-shared event with scoring enabled. Without a separate account or email entry, a helper can view the same display names, participant identifiers, matches, match formats and scores as the participant view, and enter, edit or clear scores for that event. The response also includes match references, revision and update time, and the helper link’s identifier, number and expiry time. Helpers cannot change the roster, schedule conditions or assignments, or sharing settings.
Anyone with the link can use this access. Forwarding it also forwards score-editing access, so send it directly only to someone you trust and do not post it publicly. A link works for up to 24 hours after creation, and the organizer can end it sooner. Only one is active per event; creating a new helper link ends the previous one.
The app keeps the original helper token only in the current tab’s memory, not in local or session storage or backups. Opening a link immediately removes the token portion from the address. Read and save requests send the token to Supabase to check access. After refreshing or leaving the helper view, reopen the original link while it is still valid. Closing the organizer’s link-creation panel clears the original link from that panel; it cannot be recovered and must be replaced if needed. This does not erase copies already made or shared.
To check access and prevent duplicate saves, the server stores event and helper-link identifiers, a hash instead of the original token, the link number and creation, expiry and deactivation times. Accepted score requests record request identifiers and hashes, match references and positions, before-and-after scores, revision numbers and processing times. These helper access and request records do not additionally store participant names or a helper’s email, IP address or browser identification. This does not describe all general request handling or technical logs of the external providers linked below.
Only the event’s organizer can view helper change history in the app. A helper number identifies a link, not a verified person. Organizer score edits and accepted saves that leave the score unchanged do not appear in this list, so it is not a complete event-edit history. Match positions refer to the schedule at the time of the change and are not displayed alongside player names from the current schedule.
Each event is limited to 100 helper links issued and 2,000 accepted score-save requests in total. Requests that leave the score unchanged also count toward the request limit. Reaching these limits does not prevent the organizer from editing scores directly.
Retention, link deactivation and deletion
Browser records remain until you delete them or the browser clears them. The current sharing server has no automatic expiry or deletion of event records, and there is no permanent-deletion screen in the app. Shared events and helper access and request records may remain on the server until a separate deletion process is carried out. Helper records have no age-based automatic deletion either. A helper link’s 24-hour expiry ends access; it does not delete the event, scores or change history after 24 hours. Using “Delete event” in the app or clearing the site’s browser data does not delete shared server records or deactivate participant or helper links.
Once “End participant-viewing link” succeeds on the server, the old participant link can no longer be used to read the event. Ending participant viewing or pausing automatic sync does not end helper access; end the helper link separately. Ending a helper link does not end participant viewing or erase scores already saved. Deactivating a link does not delete the event record on the server. If “Link deactivation not confirmed” appears, the old link may still work because deactivation has not been confirmed. Check your connection and access, then try again.
Send requests to delete shared records and other privacy requests to goople.js@gmail.com. Include only the minimum information needed to identify the event, such as its name and date. Do not send sign-in or helper links or passwords. Downloaded images, backups and copies held by other people must be managed separately.
Exports and backups
Images, CSV files and JSON files include participant names, schedules and results according to the export type you choose. JSON also includes the participant information and settings needed to restore records. “Back up all records” includes multiple events and saved rosters.
Existing completed scores remain in JSON and CSV exports even when scoring is turned off on screen. Check a file’s contents before sending it to someone else. Saving an image is different from making a JSON backup that can restore your records.
External services and current advertising status
MatchMaker uses Cloudflare Pages to serve the site, and Supabase for optional authentication and event sharing. You can read each service’s privacy information below.
The current MatchMaker application contains no code that displays advertisements and no separate visitor analytics or session-recording tools. The site’s AdSense ownership-verification information and search-engine ownership-verification meta tags do not enable advertising or visitor analytics. Before introducing advertising, we will explain which pages are affected, how information is processed and what choices users have.
Operator and contact
Operator: 제이에스
Service name: MatchMaker
Service and privacy questions or deletion requests: goople.js@gmail.com