For disability services offices
Where accommodation data lives, who can reach it, what is logged, and why nothing is disclosed to an institution without the student choosing it.
The question you actually have
Not whether the interface is nice. Whether a student’s disability documentation is going to end up somewhere it should not be, and whether your office is going to hear about it.
Where the data sits, and who can reach it
Accommodation records, energy history, focus observations, and consent records are stored encrypted at rest, and every one of those tables carries forced row-level security. That means the check is in the database, not in the application code that reads it. A query that forgets to filter by owner does not return somebody else’s row; it returns nothing.
The runtime account the application connects with cannot bypass that. The system refuses to start if it can.
What can be shared today
One category: planning items — assignments, tasks, and courses. A student can grant that to a named person, choose view or edit, set an expiry, and revoke at any time.
Accommodation records, energy history, focus observations, grades and profile are not shareable at present. Not switched off — not built. They are outside the sharing mechanism rather than inside it and disabled.
We would rather tell you the direction than let you infer a permanent boundary: the intent is that a student can share whatever they choose. Each category will arrive with its own explicit opt-in and its own enforcement, and nothing becomes shareable quietly.
Disclosure is an act, not a default
There is no automatic sync to a learning management system, no institutional data feed, and no report that leaves the student’s control on its own.
Consent is granular and per-category. A student can share one thing without sharing another. They can see every category they have granted, in one place, and revoke any of it. Every consent change is written to an audit log, so the question “when did this student agree to that, and did they take it back” has an answer.
What we are not
We are not a replacement for your office and we do not want your case management. We hold no institutional relationship with the school, which means we also hold no obligation to report to it.
Practically: a student can use this without their institution knowing they use it. That is deliberate. For a student weighing whether registering with your office will follow them, a tool that is unambiguously theirs is sometimes the thing that gets them to register at all.
If you want to look closely
We would rather be examined than trusted. Write and ask for specifics — what is stored, what is encrypted, what is logged, what leaves.
The email above is pre-filled with the three questions offices usually ask. Add your own, or delete them and write your own — either is fine.