Security
How the platform itself is secured.
A compliance product should be able to answer the questions it asks of others. This page is what is actually in place today, including what is not.
Tenant isolation at the database
Every tenant-scoped table has PostgreSQL row-level security enabled and forced. The application connects as a restricted role with no bypass privilege; a query outside the tenant context returns nothing.
Sessions
Signed JSON Web Tokens in HTTP-only, same-site cookies, marked secure in production. Company sessions expire after seven days, admin sessions after twelve hours. Passwords are stored as salted hashes.
Read-only connectors
Connectors read the systems they check; they never write to them. Credentials live in environment configuration, not in the database.
Append-only evidence
Evidence records carry a hash chained to the previous record. History is added to, never overwritten, so a verdict can be traced back to what was known at the time.
Audit log
User actions on tenant data are recorded with the actor, the action, the entity and a timestamp.
Read-only public demo
The live demo signs visitors into a seeded organisation with a session that every mutating action refuses at a single choke point.
Where things run
- Database
- PostgreSQL on Supabase, Frankfurt (AWS eu-central-1). Data at rest is in the EU.
- Application compute
- Vercel serverless functions, currently in the US East region (iad1). Requests are processed there; data is stored in Frankfurt.
- Contact-form notifications go through Resend when configured; the submission is always stored first.
- Certifications
- None yet. We have not completed ISO 27001 or SOC 2 and do not claim to. Ask us for the current state of the controls above.
Reporting a vulnerability
Write to info@digimindsphere.com with the steps to reproduce. We acknowledge within two working days and will not take action against good-faith research.