Sign in Request access

Privacy notice

What we collect when you use ResGeek, why we need it, and what you can ask us to do with it. Written in plain English.

Draft. This notice describes how ResGeek works today, but it hasn't been reviewed by a lawyer yet. Highlighted parts still need a decision. It will be finalized before ResGeek opens to the public.

What we collect

If you request early access

Your name, email, and anything else you choose to tell us in the form (organization, kind of place, number of screens, message). We also record the network (IP) address the request came from, to stop spam.

If you have an account

  • Account details: your name and email, and your password stored in a scrambled form we can't read back. If you turn on two-step sign-in, we store the secret that makes your codes work.
  • Sign-in sessions: when you signed in, the network address and the browser you used, to keep your account secure.
  • Activity log: who changed what and when, with the network address it came from, so your admins can see what happened on their screens.
  • Your content: the images, videos, links, playlists, schedules and events you add.

From your screens

  • Device details: the model, software version, network address and when each screen was last online.
  • Screenshots of what each screen is showing, taken when you ask or on a schedule you set. If a screen faces a camera feed or shows personal information, its screenshots will too.
  • Play history: what played on each screen and when, for your reports.

ResGeek's player doesn't use cameras or microphones and doesn't collect anything about people walking past a screen.

How we use it

  • To run the service: show your content on your screens, keep you signed in, and send the emails you need (invitations, password resets, alerts you set up).
  • To keep it secure: stop spam and misuse, and investigate problems.
  • To reply to you if you request access or contact us.

We don't sell your information, show you ads, or use your content to train anything.

Who else is involved

We use a few other companies to run ResGeek. They handle data only to provide their service to us:

  • Hosting: Railway runs ResGeek's servers and stores its database and files. Region to confirm.
  • Email: Resend delivers ResGeek's emails, so it sees the address and contents of each email it sends.
  • Weather: if you add a weather widget, ResGeek asks Open-Meteo for the forecast at the place you entered. It doesn't receive anything about you.

If you put a web page or YouTube video on a screen, the screen loads it directly from that site, and that site's own privacy policy applies.

The people in your organization who have access to ResGeek can see your name and email, and what you've changed. Platform administrators at ResGeek can see accounts to provide support.

We'd only share anything else if the law requires it.

Cookies

ResGeek uses one cookie, to keep you signed in. This website has no analytics, advertising or tracking cookies.

How long we keep it

We keep your account and content for as long as your account is open. Retention periods for screenshots, play history, the activity log, sign-in sessions and early-access requests are still to be decided, along with how long data is kept after an account closes.

Your choices

You can change your name and password, and turn two-step sign-in on or off, in your account settings. You can also ask us for a copy of your information, to correct it, or to delete it, by contacting us. If you're in a place with specific privacy laws (such as the EU, UK or California), you have the rights those laws give you, and we'll honor them.

Contact

Questions about privacy: contact email to add.

Last updated: date when finalized.