Privacy
What we keep, and what we can't read.
Last updated
CurbCall is made by Ampersand Software LLC, a Kansas limited liability company. On this page, "we" means Ampersand Software LLC.
This page has two parts, and they are different kinds of statement. The first is our privacy policy for this website: what it collects from you when you visit it or book a walkthrough. The second describes how the CurbCall service handles student data. It describes, and does not govern: a school's use of CurbCall is governed by its agreement with us.
When this page changes, the date at the top changes with it, and material changes are noted on the page. Questions about either part go to [email protected].
This website
This website sets no cookies. There are no tag managers, advertising pixels or chat widgets on it, the walkthrough form does not go through a form service, and the fonts are served from this site rather than a font service.
We count visits with Cloudflare Web Analytics. It sets no cookies and passes no visitor data to third parties, which is why this site has no consent banner: nothing on it needs one.
If you book a walkthrough, we keep what the form asks for — your name, work email, school and role, and your phone number if you give one — and the time you sent it. Nothing else. We use it to reply to you and set up the call.
We don't store your IP address with your enquiry. The server that receives the form sees it, as every server does, and discards it.
Ampersand Software LLC is the data controller for your enquiry. It is stored on Cloudflare's infrastructure in North America. We do not sell it or rent it, and we do not share it for advertising.
These details are not locked the way a school's roster is, below. They are ordinary records, and we can read them.
To have your enquiry deleted, email [email protected] and we will delete it.
The CurbCall service
This part describes how CurbCall handles student data. It is a description, not the terms. CurbCall is provided to schools under an agreement that covers student-data obligations, and that agreement is what governs your school's student data. Schools remain responsible for their own obligations, including under FERPA. If your district has its own data privacy agreement, we will review it.
Your school is the data controller for its students' data. Ampersand Software LLC is a processor, acting on your school's instructions.
Student names are locked in your school's own browser before they reach our server, and so are each student's ID, grade and car tag numbers. Our server stores no student details it can read: it stores the locked records, a random reference for each student, the order of the queue, and timestamps.
The key that unlocks the roster comes from the roster passphrase, which your school sets and holds. It is used in the browser and never reaches us. There is no support access to student data.
That has a cost, and it is the same fact from the other side. We cannot read your roster, and we cannot reset it for you. If your school loses the roster passphrase, the recovery sheet printed at setup sets a new one. If the passphrase and the recovery sheet are both lost, the roster cannot be recovered — by your school or by us.
Locking protects the roster wherever it is stored: in a copy of the database, or a backup, the roster is still locked. It has limits. On an instance we host, the code that unlocks the roster in your browser is served by us, so the protection depends on that code doing what it says. And a device that has been unlocked holds the roster in readable form while it is open, so your school's own controls — managed devices, screen locks, physical security — still matter.