Trust
Data processing
Who is responsible for what, in plain words, before the contract says the same thing in longer ones.
Version 1.0 · 31 July 2026
Who is the controller
The institute is. A school, college or coaching centre running Algoryq Learn decides what to collect about its learners and staff, and why — so it is the data controller, and the party a subject-access or erasure request is made to.
That is not a legal nicety here; it is how the software is built. Retention policies, legal holds and data-subject requests sit behind a permission held by the institute's administrator, not the platform operator. Suspending an institute is the operator's call; deciding what happens to its data is not.
When we are a processor
If we host your instance, we process personal data on your instructions: storing it, backing it up, letting your people reach it. We do not train on it, sell it, or look at it except when you ask for help — done through impersonation, recorded in the audit log with dual attribution, so you see who acted and on whose behalf.
When we are neither
If you self-host, we never see your data. No telemetry, no phone-home, no licence check. The compose file boots the whole platform with no account of any kind, and that is deliberate.
What we do to protect it
In full on the security page, with the file each one lives in. Summarised: isolation between institutes is a forced row-level security policy in PostgreSQL on a non-owner, non-superuser role; every route is permission-checked; every mutation lands in a hash-chained audit log; passwords are Argon2id; tokens never reach client JavaScript.
Subject requests
Export and erasure are built-in flows. Erasure tombstones the record rather than rewriting the audit chain that proves it happened — a chain that could be rewritten is evidence of nothing. A legal hold overrides retention; retention overrides erasure.
If something goes wrong
We tell you quickly, with what we know and what we do not yet know. An incomplete notification early beats a tidy one late.
The actual agreement
A signable data-processing agreement is available on request — learn@algoryq.com. This page describes it honestly; it does not replace it.
One thing this page will not claim
We will never describe ourselves as “GDPR compliant”. Compliance is a property of how an organisation operates, not a badge a vendor hands over. What we can tell you is what we built: subject-request flows, retention policies, legal holds, an erasure job that respects the audit chain, and an isolation model you can inspect. Those are facts; the adjective is not ours to award.
Questions your legal team will ask next
Sub-processors, responsible disclosure, and the accessibility conformance statement.
Or open the sandbox (opens in a new tab) and click around first. No form.