Privacy Policy
Last updated: October 29, 2026 · Effective: October 29, 2026
This policy explains what information RefSynced LLC ("RefSynced", "we", "us"), an Indiana limited liability company, collects, why, who it goes to, and the choices you have. It covers refsynced.com, app.refsynced.com, our notifications, and the RefSynced service. It's part of our Terms of Service.
The short version
- We collect what we need to keep your referee schedule in sync: your email, your games, your platform connections, and a record of what RefSynced did.
- We never ask for or store your passwords.
- The most sensitive items (signed-in sessions, access tokens, Google access and calendar feed links) are encrypted before they're saved.
- We don't sell your data, there are no ads, and we don't use your data to train AI models.
- You can get a copy of your data or delete your account at any time: support@refsynced.com.
What we collect
| What | Examples | Where it comes from |
|---|---|---|
| Account details | Your email address, time zone, notification choices and blackout rules | You, and Google when you sign in with Google |
| Home location | The address you enter and its map coordinates | You |
| Schedule and games | Date, time, game title (often teams and level), venue, status (accepted, offered or cancelled), which platform it's on, and a link to the game | Your connected platforms and calendar feeds |
| Personal busy times | Only if you turn it on: the start and end times and titles of events in the Google calendars you choose | Google Calendar |
| Blackouts and approvals | Each proposed blackout, whether you approved or skipped it, and its status on each platform | RefSynced and you |
| Platform connection data | Which platforms you connected, connection status, when we last checked, error messages, and your user ID on platforms that need one | You and your connected platforms |
| Encrypted sessions, tokens and keys | The "stay signed in" cookies and site data a platform gives you after you sign in; Assignr API keys; Google access tokens | The platforms and Google, after you sign in or connect |
| Calendar feed links | Your Assignr calendar feed and RefInsight Calendar Sync feed | You |
| Proof screenshots | A picture of the platform's page after RefSynced saves a change. It can show your name, your schedule and anything else on that page. | RefSynced |
| Activity log | A running story of what RefSynced did: games found, blackouts proposed, approved, posted or removed, failures and reconnects | RefSynced |
| Phone notification settings | The ntfy server and private topic names you give us (encrypted) | You |
| Messages to us | Support emails, feedback and beta invite requests | You |
| Technical data | IP address and browser type in server logs, and error reports | Your browser and our servers |
What we don't collect: your platform passwords, your Google password, or payment details (there's nothing to pay during the beta).
Passwords: we never ask for or store them
- RefInsight, GotSport and RefQuest. You sign in yourself, on the platform's own sign-in page, inside a live cloud browser shown on our Connect screen. Your password goes to the platform, just as it would from your own computer. If the platform sends you a verification code, you type that in yourself too. Session recording is turned off, the browser can only open that platform's own websites, and it closes when you're done. What we keep is the signed-in session the platform gives you afterwards: the same "stay signed in" cookies your own browser would keep.
- Assignr. RefSynced uses Assignr's official API with keys you provide from your Assignr account, never your password.
- Google. You sign in on Google's own page. Google tells us your verified email address and, if you connect Google Calendar, gives us an access token. We never see your Google password.
Google user data
RefSynced uses Google in two ways, each only after you choose it:
- Sign in with Google. We receive your Google account's email address and whether Google has verified it. We use it only to sign you in to RefSynced. We don't receive your contacts, files or anything else.
- Google Calendar. If you connect Google Calendar, RefSynced:
- creates and keeps up to date a calendar named "Ref Games" (or the name you choose) with an event for each of your games, and removes events for cancelled games;
- lists your calendars so you can choose which ones count as busy times;
- reads events from only the calendars you choose, if you turn on busy-time blocking: their start and end times and titles, so RefSynced can propose blackouts for times you're busy. All-day events and events marked "free" are ignored.
Your Google access token is encrypted before it's saved. Busy times read from your calendars are used only to propose blackouts for you. They're kept only while they're still on the calendars you chose: when an event is removed, or you turn busy-time blocking off, we delete them.
We don't sell Google user data, share it with anyone except the service providers listed below that run RefSynced, use it for advertising, or use it to train AI or machine-learning models. People don't read it, except with your permission, to fix a problem you report, for security, or when the law requires it.
RefSynced's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
You can disconnect Google Calendar at any time on RefSynced's Setup page, which revokes our access at Google and deletes the token. You can also remove RefSynced's access in your Google Account under Security → Third-party connections.
How we use your information
- To run RefSynced for you: read your games, work out blackouts, ask for your approval, post or remove the blackouts you approve, check they saved, keep proof screenshots, and keep your Ref Games calendar up to date.
- To keep your connections working: regular checks that each connection still works, and a notice on your dashboard (and a phone notification, if you've set them up) when you need to reconnect.
- To contact you: approval requests, "Blackouts posted", "Do by hand" and "Reconnect" notices, plus beta news and important changes.
- To support you and fix problems: troubleshooting your account when you ask, and error monitoring.
- To keep RefSynced secure: preventing abuse and protecting accounts.
- To improve RefSynced: overall numbers such as how often changes succeed on each platform and what RefSynced costs to run.
- To follow the law and enforce our Terms.
We don't use your information for advertising.
Who we share it with
The platforms you connect. To act for you, RefSynced sends each connected platform what's needed, such as the times of a blackout, using your signed-in session or API keys. Each platform's own privacy policy covers what it keeps.
Our service providers. These companies run parts of RefSynced for us. They may use your information only to provide their service to us.
| Provider | What it does for us | What it handles |
|---|---|---|
| Railway | Hosts the RefSynced app, database, background jobs, screenshots and encrypted backups (United States) | Everything RefSynced stores |
| Browserbase | Runs the live cloud browser you sign in through. It's used only while you sign in; the browser is closed afterwards. | The platform pages you use while signing in |
| Sign in with Google, and Google Calendar if you connect it | Your email address, and your calendar events as described above | |
| ntfy.sh | Delivers phone notifications, if you set them up | The text of each notification, such as "Block Sat Nov 7?", and your Approve or Skip taps |
| Sentry | Error monitoring | Technical details about errors. We remove email addresses, links and sign-in details before reports are sent. |
| Vercel | Hosts the refsynced.com website | Website visits |
| Porkbun | Forwards email sent to support@refsynced.com | Emails you send us |
| Stripe (after the beta) | Payments, if you choose a paid plan | Your payment details. Stripe handles them; we never store your full card number. |
When the law requires it, or to protect people. We share information if we must by law, or if we believe it's needed to protect someone's safety or RefSynced's rights.
If RefSynced changes hands. If RefSynced is sold or merged, your information may move to the new owner. We'll tell you first, and this policy will keep applying to it.
With your permission, in any other case.
We don't sell your data
We don't sell your personal information, and we don't share it for targeted advertising. RefSynced has no ads.
How we protect it
- Everything travels over encrypted connections (HTTPS).
- Signed-in sessions, access tokens, API keys, Google access, notification topics and calendar feed links are encrypted by RefSynced before they're saved, with a key kept separately from the database. Keys are versioned, so they can be replaced.
- Every account's data is kept separate, and we test that one user can never see or act on another's.
- The cloud browser you sign in through is locked to the platform's own websites, session recording is turned off, and it closes when you're done.
- Only RefSynced's owner has access to RefSynced's systems, and uses it only to run RefSynced, help you, or keep it safe.
- The database is backed up every night. Backups are encrypted with a key that's kept offline, and each one is test-restored before it's saved.
No system is perfectly secure. If a breach affects your information, we'll tell you by email promptly, as the law requires. More detail is on our security page, How we protect your accounts.
How long we keep it
| What | How long |
|---|---|
| Proof screenshots | Up to 30 days, then deleted automatically |
| Your RefSynced sign-in | 30 days, then you sign in again |
| Google sign-in attempts | Until used, or 10 minutes; each works once |
| Live sign-in browsers | Closed as soon as you're signed in, or after about 15 minutes |
| Signed-in sessions, tokens and keys | Until you disconnect, the session expires, or you delete your account |
| Personal busy times | Until the event leaves the calendars you chose, or you turn busy-time blocking off |
| Account details, games, blackouts, activity log and calendar links | While your account is open |
| Error reports and server logs | Up to 90 days |
| Database backups | 30 days, so deleted data is gone from backups within 30 days |
| Support emails and feedback | As long as needed to help you |
| Beta invite requests | Until we invite you or you ask us to remove it |
We may keep something longer if the law requires it.
Your choices and rights
- See and update your information on your dashboard and Setup page.
- Get a copy. Ask for an export of your settings, games, blackouts and activity by emailing support@refsynced.com.
- Delete your account by emailing support@refsynced.com. Within 30 days we delete your data, revoke our Google access and delete your saved sessions. Deleting your RefSynced account doesn't remove blackouts already posted on the platforms, or anything the platforms themselves keep.
- Disconnect Google Calendar on Setup at any time. To disconnect a platform during the beta, email us and we'll delete its saved session right away. Changing your password on a platform usually signs out every saved session too.
- Choose your notifications. Phone notifications are optional; remove the ntfy settings to stop them.
- Ask us to correct anything that's wrong.
To protect your account, we'll confirm a request comes from your account email before acting on it. We won't treat you differently for using these rights. Some state laws, including Indiana's, give their residents rights like these. We offer them to everyone.
Children
RefSynced is for adults 18 and older during the beta. We don't knowingly collect information from anyone under 18. If we learn we have, we'll delete that account and its data. RefSynced will never be for children under 13.
Information about other people
Platform pages and calendar feeds can include other people's information, such as fellow officials' names, team names or assignor contact details, because it's part of your schedule. RefSynced uses it only to show you your schedule. We don't contact those people or use their information for anything else.
Where your information is stored
RefSynced is built for referees in the United States. RefSynced's servers and database are in the eastern United States, and our providers process information in the United States.
Cookies
On app.refsynced.com we use only the cookie that keeps you signed in, and a short-lived cookie while you sign in with Google. We don't use advertising, analytics or tracking cookies, and refsynced.com sets no cookies at all. The platforms' own cookies, which make up your signed-in session, belong to those platforms. We store them encrypted and use them only to act for you there.
Changes to this policy
When we update this policy, we'll change the date at the top. If a change is significant, we'll email you before it takes effect. We won't use your information in a significantly new way without telling you first, and asking you where the law requires it.
Contact
RefSynced LLC · Noblesville, Indiana · support@refsynced.com