Access is decided in the database.
How Riven decides who can see and change each record, and what it keeps about you.
Work and institutional emails only
- Sign-up turns away personal inboxes such as Gmail, Outlook.com, Yahoo and iCloud, and throwaway inbox services.
- Your email domain links you to your organization. A matching domain verifies you in one click.
- Organizations themselves are reviewed by an admin before they are marked verified.
Access is enforced in the database
- Every table carries row-level security. A person only receives the rows the policies allow.
- Permissions are checked on the server for every request, under that person’s own identity.
- Hiding a link in the interface is a convenience. The database policies are what decide access.
Accounts have a clear origin
- Open sign-up creates student accounts, with a work or institutional email. Staff roles come by invitation or by an admin-reviewed request.
- The admin role cannot be granted by invitation.
- Role changes are written to an audit log that admins can read.
Age and consent are on record
- Riven is for people aged 18 and over. Age confirmation is recorded.
- Privacy consent is recorded with the version of the notice you agreed to.
- Privacy settings in the app show what is held and let you manage it.
Mentoring has limits by design
- Mentoring is opt-in.
- A mentor’s capacity is checked when a team asks, so the cap holds under concurrent requests.