Privacy policy

Effective date: October 27, 2026.

ETP Campus is made by Education Technology Professionals LLC ("ETP", "we", "us"). It is a set of tools for schools: the Down Dashboard, Games and ETP Sites, behind one sign-in. This policy says what each of them collects, why, who else handles it, and how long we keep it. If something here does not match what you see us do, tell us at support@educationtechpros.com.

The short version

• Students never make an account. In Games a student types a first name and a last initial, and that is all we ask.
• We do not sell personal information, show ads, or use what we collect to build profiles of anyone. Nothing we collect about students is used for anything but running the game they are in.
• Our own website, etpcampus.com, and the school websites we host run no scripts and set no cookies. We use no advertising or analytics trackers anywhere.
• We keep things only as long as the tool needs them. Each tool's section below gives the numbers.
• A school decides who belongs to it. Its owners and admins approve each new member.

Who this policy covers

• School staff who sign in to ETP Campus: teachers, administrators and IT staff.
• Students and other players who join a game with a code, without an account.
• People who visit a school's Down Dashboard page, a school website we host, or etpcampus.com.

Your ETP Campus account

ETP Campus accounts are for school staff and other adults. When you sign in we keep:

• Your email address. If you sign in with Google or Microsoft, we also receive the basic profile they share for sign-in, such as your name.
• The schools you belong to and your role at each (owner, admin or staff).
• Requests to join a school: the email address you asked with, an optional note, and whether it was approved. The person who asked and the school's owners and admins can see a request.
• A record of changes to who belongs to a school, such as an approval, with the email address of the person approved. This is so a school can see who changed what.
• Two-step verification, if you set it up. The authenticator app's secret is kept by our sign-in provider. We never see your codes.

If your school is part of a group on ETP Campus, such as a diocese, that group's admins can see the school's members, requests to join and record of changes.

A cookie keeps you signed in. With shared sign-in turned on, the same cookie signs you in to every ETP Campus tool at etpcampus.com.

We keep the record of changes, and requests to join once they are decided, for three years. A request still waiting is kept until someone decides it or the person withdraws it.

If a student under 13 makes an account, and we learn of it, we delete it.

Games

Teachers host games from their ETP Campus account. Players join on a phone or laptop with the game's code and do not have an account.

What we keep about a player in a game:

• the first name and last initial they type (for example "Jordan R."), and an emoji if they pick one;
• their answers, how long each took, their score and team, and a 1 to 5 star rating of the game if they give one;
• a pass that lets their device rejoin the game. The device keeps the pass for up to 12 hours; we keep only a scrambled form of it (a hash) that cannot be turned back into the pass.

Who sees it: everyone in the game sees the players' names and scores. The teacher also sees how many players chose each answer, not who chose what. Someone with only the game's code sees whether the game is running, and no one's name.

We use a device's network address to stop one network from guessing game codes or flooding a game. We store only a keyed, one-way scramble of the address, never the address itself, and delete it within two days.

In the drawing game, the artist's lines are passed live to the big screen and to every player's screen, through our relay at Cloudflare. The relay keeps only the current round's lines, so a screen that joins late sees the drawing so far, and deletes them when the next round starts or the game ends, and in any case within six hours of the last screen leaving. It knows players by a code number, never by name.

Games a teacher makes. A teacher can write their own questions or drawing words, or have AI draft them. Saved games belong to the school and are kept until the teacher or a school admin deletes them. When a teacher drafts with AI, the topic they type and anything they paste to base the game on are sent to Anthropic, which writes the draft. No player's information is ever sent.

How long we keep it: a game that nobody has used for 7 days is deleted. A finished game, with its players, answers and ratings, is deleted 30 days after it ends.

The player's device keeps the pass and the player's name in its browser storage for up to 12 hours. If a teacher blocks a player, the device keeps a note of that for the game.

The Down Dashboard

The Down Dashboard shows whether the services a school relies on are working.

What a school gives us, and we keep while the school uses the Down Dashboard:

• the school's dashboard settings, a contact email address and any notice it posts;
• the staff email list it sends outage notices to (only addresses at the school's own verified domain), with each person's unsubscribe status;
• where alerts go: email addresses, or Slack or Microsoft Teams links;
• invitations to its other admins, and the notices it has sent and who sent them.

Sign-in checks. A school can store a sign-in for one of its own services (for example its student information system), so we can check that signing in works. We store that password encrypted. To check, our system signs in as the school's account and reads the page it lands on. That page may show student information. We read it only to see whether the sign-in worked, and we do not store what it shows.

"Is it working for you?" Visitors to a school's dashboard can say whether a service is working for them. We store each report only as one-way scrambles of the visitor's network address and a random id their browser keeps, mixed with a value that changes every day. Reports are deleted after 2 days, and so is each day's value, so an old scramble cannot be traced back. We show only totals, and only once at least five people have reported.

If someone visits a dashboard address that does not exist, we keep their network address for up to two days to limit how fast addresses can be guessed.

Payments. We do not offer paid plans yet. If we do, Stripe will handle payment: it would receive the admin's email address and the school's account id, and we would never see card numbers.

Email. We send the alerts, daily summaries and staff notices a school sets up. Every staff notice has an unsubscribe link, and replies go to the school's contact, not to us.

How long we keep it: the status history of each service for 24 months; the staff notices a school sent, and records of the alerts we delivered, for 12 months; sign-in and reachability checks for 90 days; records of incoming notifications from services for 30 days.

The Down Dashboard sets one cookie for every visitor, which remembers which of our web addresses they first came to, for 30 days.

ETP Sites

The school websites we host run no scripts, set no cookies and have no forms. They show what the school publishes, which may include staff names, roles and email addresses. The school decides what is on its site. Cloudflare hosts them, and keeps standard request logs, which include visitors' network addresses.

etpcampus.com

Our website runs no scripts, sets no cookies, has no forms and loads nothing from anywhere else. The company that hosts it keeps standard request logs, which include visitors' network addresses.

How we use information

We use what we collect only to:

• run the tools and show each person what they are allowed to see;
• keep the tools secure and working, for example by limiting repeated attempts;
• send the email that a person or their school has asked for;
• answer questions people send us.

We do not use it for advertising, we do not sell it, and we do not use students' information for anything but the game they are in. We do not use anyone's information to train artificial intelligence.

Who else handles it

We use these companies to run ETP Campus. Each handles only what its job needs.

• Supabase: our database and sign-in, in the United States.
• Vercel: hosts our websites.
• Cloudflare: passes a game's live updates and drawing between the screens in it, and runs the check on our sign-in forms that stops automated sign-up attempts. Like any network service, it sees the network addresses of the devices that connect. A game's relay normally runs in the Cloudflare data center nearest the first screen that connects to it.
• Railway: runs the Down Dashboard's background checks.
• Resend: delivers our email.
• Anthropic: drafts a game when a teacher uses AI, from only what the teacher typed or pasted for it. Its commercial terms do not allow it to train its models on what we send.
• Google and Microsoft: only if you choose to sign in with them.
• Slack and Microsoft Teams: only if a school sends its alerts there.

We may share information if the law requires it, and we will tell the affected school unless the law does not allow it.

Schools and students

When a school uses ETP Campus, we handle its information on the school's behalf and under its direction. For student records covered by the Family Educational Rights and Privacy Act (FERPA), we act as a school official with a legitimate educational interest, and we use those records only to provide the service.

A parent or student who wants to see, correct or delete a student's information should contact their school first. We help the school do it.

Keeping it secure

• Every connection to ETP Campus is encrypted, including the connection between our servers and our database.
• Each school's information is kept apart. For accounts, schools and the Down Dashboard, rules in the database itself enforce it. Games' information can be reached only by our games server, which checks the school on every request.
• Changing who belongs to a school needs two-step verification.
• Game passes are kept only as hashes. Stored sign-ins for the Down Dashboard's checks are encrypted.

No system is perfectly secure. If we learn that someone got at personal information they should not have, we will tell the affected schools and people without undue delay, and within 72 hours of confirming it.

Your choices

• You can ask us for a copy of your information, to correct it, or to delete your account, at support@educationtechpros.com. We answer within 30 days.
• A school's owners and admins can remove members and staff email addresses.
• Anyone can stop the Down Dashboard's staff notices with the unsubscribe link in each one.

Changes to this policy

We will post any change here with a new effective date. If a change affects students' information, we will tell schools 30 days before it takes effect.

Contact

Education Technology Professionals LLC, 309 Fellowship Rd., Suite 200, Mt. Laurel, NJ 08054. Email: support@educationtechpros.com.