The short version
Computer Hall Pass is used to keep school Chromebooks on task. Because it is used by children, we designed it to collect as little as we possibly can while still doing the job.
example.com.1. Who we are
Computer Hall Pass ("we," "us") provides web-filtering software licensed to schools. The school or district that deploys our software is the party that decides what is filtered and who may see the records. In data protection terms, the school is the controller of that information and we act as a service provider on the school's behalf and under its instructions.
2. What the extension collects
When a Chromebook is enrolled by a school, the extension records only the following:
| What | Why we need it |
|---|---|
| Site name of a blocked attempt e.g. example.com |
So the school can see what is being attempted and adjust their approved list. Also supports the monitoring records schools need for CIPA and E-Rate. |
| Time of the attempt | To make the records meaningful and to allow automatic deletion after the retention period. |
| A random device identifier e.g. a3f9c2e1… |
So a school can tell one Chromebook from another. It is generated at random and is not linked to any person. |
| An optional device label e.g. "Cart 3 / Unit 12" |
Set by school staff to identify hardware. Schools are instructed to use asset labels, not student names. |
What never leaves the device. The extension must read the address of a page in order to decide whether to allow it — that check happens locally, on the Chromebook. Only the site name of a blocked attempt is transmitted. Pages that are allowed are not reported at all, and the path and query string are stripped before anything is sent, then stripped a second time on our server as a safeguard.
Permissions the extension requests, and why
webNavigationandtabs— to see the address a tab is about to open, so it can be blocked before it loads.host permissions— the filter must be able to act on any address, because any address might be one that needs blocking.storage— to keep the approved-site list on the device so filtering keeps working without a network connection.idle— to lock the screen after a period of inactivity, if the school turns that on.alarms— to check periodically for updated settings from the school.
3. What we collect from school staff
Staff who administer the service have accounts. For them we store a name, a work email address, their role, and the grade levels they manage. We also keep an audit record of administrative actions, such as changing a filter, so schools can see who changed what.
4. What we never collect
- Student names, emails, usernames, or student ID numbers
- Search queries or anything typed into a page
- Full URLs, page content, screenshots, keystrokes, webcam, microphone, or location
- Browsing history of sites that were allowed
- Anything at all from a Chromebook that has not been enrolled by a school
5. How we use it
Only to provide the service to the school that licensed it: enforcing that school's chosen settings, showing that school its own records, and keeping the service working and secure. We do not use it for anything else.
Specifically, and permanently: we do not sell or rent it, do not use it for advertising or to build advertising profiles, do not use it to train machine learning or AI models, and do not combine one school's data with another's to produce analytics or research.
6. Who we share it with
We do not sell or trade information. It is shared only with:
- The school it belongs to. Each school sees only its own data. Teachers see only the grade levels they are assigned.
- Our hosting provider, which stores the database on our behalf under contract and may not use it for its own purposes.
- Legal authorities, if we are legally compelled. Where we are permitted to do so, we will notify the school first.
If our business is ever sold or transferred, school data remains subject to this policy, and schools will be notified with an opportunity to have their data deleted instead.
7. How long we keep it
Blocked-attempt records are deleted automatically after the retention period the school selects, which is 30 days by default and can be set as low as one day. Deletion runs on a daily automated job — it is not a manual promise.
Staff account records are kept while the school's licence is active. When a licence ends, we delete the school's data within 30 days unless the school asks us to do it sooner.
8. Rights, access, and deletion
Because the school controls this information, requests from parents and students should go to the school first — they can see, export, or delete the records directly, and can also instruct us to do it.
Schools can, at any time:
- See every record we hold for them, in the console
- Purge all their records immediately, with one action
- Change how long records are kept
- Ask us to delete everything, permanently, including backups
To make a request, contact privacy@computerhallpass.com. We respond within 30 days, and usually much sooner.
9. Children's privacy
This service is used by children, including children under 13. Our approach is to avoid collecting children's personal information in the first place rather than to collect it and promise to be careful. Students have no accounts, and we do not receive their names or anything they type.
We provide this service only to schools for educational purposes, under the school's direction. We do not treat a school's agreement as a substitute for our own obligations, and we do not use any information obtained through a school for commercial purposes of our own.
10. Security
Data is encrypted in transit. Each school's records are isolated from every other school's at the database level, so the separation does not depend on our application code being bug-free. Access to production data is limited to staff who need it. Device identifiers are random values rather than anything derived from a person.
If a breach affecting a school's data occurs, we will notify that school without undue delay and cooperate with any notifications they are required to make.
11. Where data is stored
Data is stored on servers in the region selected for the school's deployment. Schools with specific data residency requirements should raise them before purchase so we can confirm we can meet them.
12. Agreements with schools
We are glad to sign a district's data privacy agreement, including the standard National Data Privacy Agreement (NDPA). Where such an agreement conflicts with this policy, that agreement governs for that school. Contact privacy@computerhallpass.com.
13. Changes to this policy
If we make a material change — particularly any change that would expand what we collect — we will notify licensed schools by email before it takes effect. We will not begin collecting a new category of information about students without telling schools first.
14. Contact
Privacy questions and data requests: privacy@computerhallpass.com
General enquiries: hello@computerhallpass.com