Security
Built to protect school data
Student records, financial data, and staff information are among the most sensitive data an organisation holds. RedeemOS is architected with security as a default — not a feature tier.
Security architecture
Per-School Data Isolation
Every school on RedeemOS runs on a completely separate, dedicated PostgreSQL database. Your school's student records, financial data, and staff information are physically isolated from every other school on the platform. A security incident affecting one school cannot propagate to another.
Encryption in Transit and at Rest
All data transmitted between the RedeemOS application and your browser is encrypted using TLS 1.3. Data stored in the database is encrypted at rest using AES-256. File uploads (documents, images, reports) are stored in encrypted object storage. Encryption is not a configuration option — it is enforced universally.
Secure Authentication
RedeemOS uses database-backed sessions with opaque session tokens. Cookies are HttpOnly (inaccessible to JavaScript), Secure (HTTPS-only), and SameSite=Lax (CSRF-resistant). Sessions have absolute expiration of 14 days and are automatically refreshed on activity. Password hashes use bcrypt with a minimum work factor of 12.
Role-Based Access Control (RBAC)
Every user on RedeemOS is assigned a role with a defined permission set. Permissions are granular to the module and action level — read, write, approve, delete. A teacher can only access their own classes. A finance officer cannot access HR records. A parent can only see their own child's data. Administrators configure roles without vendor involvement.
Signed Audit Logs
Every action taken on the platform — login, record creation, edit, deletion, payment, report generation — is written to a tamper-evident audit log. Audit logs record the user, action, timestamp, IP address, and affected record. Logs are immutable: they cannot be edited or deleted by school administrators. They are available for compliance review and incident investigation.
Cloud Infrastructure
RedeemOS is hosted on enterprise-grade cloud infrastructure with geographic redundancy. The platform targets 99.9% uptime. Deployments are zero-downtime rolling updates. Infrastructure is monitored 24/7 with automated alerting for anomalous activity, performance degradation, and potential security events.
Backup Strategy
Every school database is backed up daily with encrypted snapshots retained for 30 days. Critical data is backed up to geographically separate storage regions. Backups are tested regularly for restoration integrity. In the event of data loss, each school's database can be restored independently without affecting other schools.
Disaster Recovery
RedeemOS maintains documented disaster recovery procedures with defined Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO). Recovery procedures are tested periodically. Enterprise plan customers receive a documented SLA with explicit uptime commitments and communication procedures for incidents.
What "per-school database isolation" means — and why it matters
Most cloud-based school management systems use a multi-tenant architecture where all schools share a single database, separated only by a school identifier column. This is cheaper to operate but creates a significant risk: a misconfigured query, a software bug, or a security breach can expose one school's data to another.
RedeemOS uses a dedicated database architecture. Every school has its own PostgreSQL database, provisioned at sign-up. No data from your school ever enters another school's database. No data from another school can be returned by a query against your school's database.
This is a foundational architectural decision that cannot be retrofitted. It is one of the primary reasons RedeemOS is the correct choice for schools, school groups, and ministries who take data protection seriously.
Security FAQ
Can RedeemOS staff access my school's data?
RedeemOS staff can access school data only for authorised support purposes with explicit school consent. All internal access is logged and auditable. We do not access school data for any commercial purpose.
What happens to our data if we cancel?
If you cancel your subscription, your school's database is retained for 90 days. During this period, you can request a full data export. After 90 days, the database is permanently deleted. We provide data in standard formats on request.
Is student data protected under data protection laws?
RedeemOS processes student data strictly for the purposes of school administration as instructed by the subscribing school. Schools remain the data controllers. RedeemOS acts as a data processor. Our privacy policy documents all data processing activities.
Does RedeemOS support two-factor authentication?
Two-factor authentication (2FA) is available for administrator accounts on Professional and Enterprise plans. We recommend enabling 2FA for all accounts with administrative or financial access.
For detailed security documentation or to report a vulnerability, contact security@redeemos.com or view our security.txt.
Have security questions before signing up?
Our team is happy to discuss our security architecture with your IT team or procurement office.