What CSent records — and what it does not prove
It helps to be precise about a record's contents and its limits, before anyone relies on it.
What a CSent record contains
- The choices each person selected in the app.
- Confirmations that each person took part.
- Which selections were mutual and which were not.
- Changes made to choices during a session.
- Withdrawal and session-end events.
- Timestamps for those actions.
- Messages and interactions that happened inside CSent.
- Private records you create yourself, such as incident notes and preserved files.
What a record does not show
- That consent existed throughout an encounter.
- What happened outside the app.
- Whether an offence did or did not occur.
- That anyone is innocent or guilty.
- Whether an account is true or false.
- Anything that replaces an investigation, professional advice or a court's decision.
Fingerprints on preserved files
Files you preserve are stored with a SHA-256 fingerprint of their contents, so you can check later whether a copy matches what was uploaded.
That shows a file has not changed since upload. It does not establish where the file came from, when the events in it happened, or whether it would be accepted anywhere.
Who can see it
A consent session record is visible to the two participants in that session.
Incident records, preserved files and post-session feelings are private to the person who created them.
CSent shares general educational information only. It does not determine whether consent legally existed, and it is not medical or legal advice.