Loading…
Privacy
Effective September 19, 2026 · Written to be read by the students it is about, most of whom are under 18.
The rest of this page is the same promises written out in full, in the order a school will look for them.
OrbitWorks (“OrbitWorks,” “we,” “us,” or “our”) is the software your school uses to run its clubs: club pages, meeting schedules, rosters, attendance, announcements, and the questions students ask about all of it. This Privacy Policy applies to that software and to every page, feature, export and calendar feed offered through it, which this Policy calls the “Services.” By using the Services you acknowledge the practices described here. The Services are hosted in the United States, and using them means your information is stored and processed there.
A few terms are used throughout and are worth fixing here. Your “School” is the institution whose Google Workspace domain you sign in with. A “Club” is any club, team or student organization with a page in the Services. A “Club Leader” is a student recorded as leading a Club, an “Advisor” is the faculty member responsible for it, and an “Administrator” is a student in student government or a faculty member your School has given school-wide access.
You are responsible for what you post through the Services. We restrict who can see rosters, attendance, meeting logs and contact details, and those restrictions are written into the database queries rather than only into the page, so a change to how a page looks cannot reveal a roster by accident. No restriction stops someone already allowed to see something from copying it, and no security measure is perfect. Please do not put personal information into the Services beyond what they need in order to work.
Content you remove may remain for a period in backups and in our host’s server logs, and it may remain wherever another person has already copied it. We will remove what is under our control when you ask, as described in section 20.
Collecting information about other students through the Services, or using anything you can reach here to harass someone, is a misuse of the Services. Report it to george_zhan@ryecountryday.org.
In this Policy, “personal information” means information that identifies you or that can reasonably be connected to you. The Services collect the following kinds of it.
Your grade, your outside organizations and an Orbit profile are all optional, and you may leave them blank. The rest is not optional in the same way: a Club cannot take attendance for someone it cannot name, so an account that withholds its name cannot be on a roster.
This Policy covers only the Services. It does not cover a website or service we do not operate, including one you reach from a link here.
The Children’s Online Privacy Protection Act (“COPPA”) requires an online service to obtain verifiable parental consent before it knowingly collects personal information from a child under 13.
The Services are built for Upper School students, and accounts exist only for people whose School has enrolled them. We do not seek verifiable parental consent, because we do not intend to collect personal information from anyone under 13 at all. If you are under 13, please do not use the Services. If we learn that we hold personal information about someone under 13, we delete it. If you believe a student under 13 has an account, write to george_zhan@ryecountryday.org and we will remove it.
Sign-in is Google only, so there is no password here to be stolen. Only ryecountryday.org accounts can sign in, plus a short list of addresses an Administrator has named one at a time. The check runs on our server, and it refuses anything it cannot confirm.
Google tells us three things: that you signed in, your School email address, and your name and profile picture as your School’s directory has them. We ask for nothing else. We cannot read your Gmail, your Drive files or your Google Calendar, and we cannot act as you.
Most of the Services can be read without an account, which is deliberate: a club fair poster with a link on it has to work for a visiting family as well as for a student. What is visible depends on whether you have signed in. Signed out, a student’s name is shortened to a first name and a last initial, and no student email address appears at any privilege level. Signed in, students at your School see full names.
None of these limits live on the page alone. Each is part of the query that fetches the data, so a change to how a page looks cannot accidentally reveal a roster.
We receive and store what you knowingly enter into the Services, and we use it for the following purposes.
We do not use your information for advertising, we do not sell or rent it, and we do not use it to train machine learning models.
Our host records ordinary server logs whenever a page is requested. Those logs include IP addresses, and they are kept for security and troubleshooting. Attendance records note who marked you present, whether that was you with a check-in code or a Club Leader ticking you off a list.
If you never sign in, the Services hold nothing that identifies you. The server logs still exist.
We count how many times each page is opened and how fast it loaded. That is how we can tell whether anybody actually reads the club directory, and whether it is slow on a phone on school wifi.
This counting is deliberately blunt. There is no cookie and no identifier that survives the page you are on, so we cannot tell one visit from another, tell a signed-in student from a signed-out one, or follow you anywhere. What we get is a number per page, plus the rough things any web server already sees: the page you came from, your country, and whether you are on a phone or a laptop. It is never joined to your account, and no report we build from it can name you.
It is done by Vercel, who already host the site, and it runs from this domain rather than from an advertising network. Nobody is paid for your attention here, and this data is not sold, shared, or used for advertising.
We set a cookie to keep you signed in and to keep that session secure. It is necessary rather than optional: without it, every page would ask you to sign in again. We set no advertising cookies, and no cookie here follows you to another site.
Your browser’s local storage holds a small number of preferences, such as whether you last saw My Clubs as an orbit or as a list. It also holds a club fair join request for a moment when the network is bad, so that a tap in a crowded gym is not lost. Local storage stays on your own device, and clearing it costs you those preferences and nothing else.
We do not email you and we do not text you. Everything the Services have to tell you, they tell you inside the app: your inbox collects announcements from Clubs you are in, invitations, and tasks waiting on you, with notifications alongside them. We record which announcements you have read, so the inbox can stop marking them new.
Announcements are written by Club Leaders, Advisors and Administrators, and reach the students in that Club or, where your School allows it, the whole School.
There is no private person-to-person messaging anywhere in the Services. That is a decision, not a feature we have not got to yet.
Signing in associates your account with your School, and joining a Club associates it with that Club. In doing so you acknowledge that:
You can ask a question without your name on it, and here is exactly what that does and does not mean.
We always record who asked. Without that, someone could use the form to harass people and there would be no way to stop them.
Club Leaders never see who asked an anonymous question. They are students like you, and telling them would defeat the promise the form made. Administrators can see it, which is what makes moderation possible.
Orbit is the part of the Services where students from different schools find work to join. Nothing about you appears there until you publish a profile, and unpublishing takes it back down.
Being findable and being contactable are two separate switches. Contact details you add, like an Instagram handle or a personal email address, are shown only to someone whose connection request you accepted. There is no private messaging anywhere in Orbit, on purpose.
If you subscribe to your club schedule from your own calendar app, we make you a private feed address with a long random token in it. Treat that address like a password: anyone holding it can read your club schedule without signing in. You can replace it at any time from calendar settings, which breaks the old one immediately.
If you point the Services at an outside calendar of your own, we store only the feed address, never the events. The events are fetched when your week is drawn, and shown to you alone. No Club page, no school-wide list, and no Administrator ever sees them.
We do not sell, rent or trade your personal information, and we do not share it for advertising. We share it in the circumstances below and in no others.
Service providers. These companies process information on our behalf, and may not use it for anything other than running the Services.
Your School. Once a day the app writes an export into a Google spreadsheet your School controls, so the activities office can work in a tool it already has. That export includes Club rosters with names and School email addresses. It only ever writes, and nothing typed into the spreadsheet can reach the app. Who is allowed to open that spreadsheet is a question for your School, not for us.
Legal obligations. We may disclose information when we believe in good faith that it is necessary to comply with the law, to enforce the terms on which the Services are offered, or to protect the rights or safety of students, your School, or the public.
Change of operator. If responsibility for the Services ever passes to someone else, the information held in them may pass with it. We would tell your School and the people affected before that happened, and this Policy would keep applying until a new one was published.
We take the security of your information seriously, and we are not going to claim it is perfect. No way of sending or storing information is completely secure. What we can say concretely is that sign-in is Google only, so there is no password here to be stolen; that the database is not reachable from the public internet; and that the connection to it is encrypted.
If a problem exposes your information, we will tell your School and the people affected rather than quietly fixing it, and we will do it as soon as we understand what happened.
Two outside services touch the Services only because you chose to point them here: the calendar app you subscribe to your schedule from, and any outside calendar you import into your week. We do not control how those services handle information, and their own privacy policies govern them. Read those before you connect one.
A link from a Club page to a site we do not run is the same situation. This Policy stops at our edge.
From settings, at any time, you can:
You may also ask what personal information we hold about you and what we have done with it. Write to george_zhan@ryecountryday.org and we will send you a copy. In narrow cases we may not be able to hand over all of it, for instance where the same record is also about another student, and we will say so and explain why.
If a Club Leader or an Administrator entered something about you, such as a roster import or an attendance mark, ask them to correct it, or write to us and we will.
We keep personal information only as long as the purpose it was collected for requires.
Write to george_zhan@ryecountryday.org and ask. Being straight about it: there is no delete button yet. A person removes the account by hand, and we aim to finish within 30 days of your request.
Some things outlive the account. Anything you posted on behalf of a Club you led may stay as part of that Club’s record with your name taken off, and attendance for meetings you attended stays. Copies may sit in backups and server logs for a while after that, and they age out on the ordinary schedule rather than being reached into and picked out.
If what you want removed was entered by your School, a roster import for example, ask your School too. Otherwise the next import puts it back.
We run the Services largely on your School’s behalf. If your question is about information your School gave us, your School is the right place to start.
If you live in a state with a general privacy law, including California, Colorado, Connecticut and Virginia, you may have the right to know what personal information we hold, to have it corrected, to have it deleted, and not to be treated worse for asking. Sections 18 through 20 describe how to do each of those, and they are open to everyone rather than only to residents of those states.
To make a request, write to george_zhan@ryecountryday.org with “Privacy request” in the subject line. We may need to confirm who you are first, which for a student account normally means writing from the School address the account uses. OrbitWorks does not sell personal information and does not share it for targeted advertising.
We may update this Policy as the Services change or as the law requires. If we change it in a way that matters, the effective date at the top changes and we say so in the app. Where a change is significant enough to need it, we tell your School before it takes effect. We encourage you to read this page again from time to time.
Email george_zhan@ryecountryday.org with anything on this page: what we hold about you, a correction, a deletion, or a part of this document that is not clear.
If you are signed in, Questions works too. Address it to student government and it reaches the people who administer this site.