The privacy packet.
What we publish, what we sign, and what we are still writing — for the person who approves tools at your school.
Where should we send it?
A founder answers, not an autoresponder. Forward it to whoever says yes.
One step left.
Your email app just opened with the request filled in. Send it, and a founder replies with the published documents as files and a plain answer on where each unfinished one stands.
Nothing arrived? Write to admin@assignhq.org and a person answers.
The binding text, sent as files your office can save. The terms carry the FERPA school-official and New York Education Law §2-d commitments.
Every kind of data, in a table, with how long we keep it.
What we collect from students, how to review or delete it, and a one-page note your school can send home.
Send us your form and we review and sign it. We do not yet have a template of our own, so we work from yours.
The two documents Education Law §2-d asks a contractor to provide. Both are drafted and under review, not yet issued.
Architecture, encryption, subprocessors, what we never collect, and the gaps we have not closed yet. In review; the security page covers the substance today.
Available from the business office once a pilot is agreed.
We would rather this page under-promise than have your review find otherwise. If a document you need is not listed, ask — the answer will be a date or a no, not a maybe.
Want the technical half first? The security page covers lockdown, the vault, and what we never collect.
Read how security works