Skip to content
IntellSchool IntellSchool
Sign in Book a demo
Isolation is architecture, not a setting

Security and privacy a separate database for every school

No two schools share a database: every school runs on its own isolated database, reached only by its own team.

A separate database for every school

Your school host, the platform console and the marketing site are three separate doors, and every school's data lives in its own database.

  • Schools fully separated
  • Its own database
  • File isolation
  • Domain ownership verification
  • The right access for every role
  • Activity log
  • Lifecycle controls

Protection controls

Schools fully separated

Your school's scope is established first, so no session can cross into another school.

Its own database

A separate database per school, with credentials configured server-side and never accepted from input.

The right access for every role

Every role sees and does only its own work — no excess access.

Activity log

Sensitive actions are recorded with the user, role and timestamp.

Bounded support access

An approved support session, limited in duration and scope, fully logged, with a banner visible to school users.

Domain ownership verification

A school's own domain does not route until DNS ownership is proven with a TXT record.

File isolation

Your school's files are kept in an isolated space that never mixes with other schools' files.

Lifecycle controls

Suspension, cancellation and retention are separate, reviewed steps — not an immediate delete.

Hosting modes

Standard cloud hosting

Your school's own database on managed cloud infrastructure.

Fully isolated hosting

Isolated infrastructure for large education groups.

Your own domain

Live after DNS verification, with a TLS certificate.

Protection controls

Your school host, the platform console and the marketing site are three separate doors, and every school's data lives in its own database.

  • Schools fully separated
  • Its own database
  • The right access for every role
  • Activity log
  • Bounded support access

The school account lifecycle

  1. 1 Provisioning
  2. 2 Active
  3. 3 Suspended
  4. 4 Cancelled (90-day retention)
  5. 5 Reviewed permanent deletion
We do not claim certifications we do not hold — The platform has not yet completed an external security assessment, and we will not publish a certification badge or an uptime figure before it has. Everything shown here is a control that exists today and can be reviewed with you in the demo.

Frequently asked questions

How can we verify the isolation?
We can walk you through these controls in the demo: full separation between schools' databases, an activity log for every action, and automated tests that assert no data leaks between schools.
Can your team see our data?
Only through an approved support session that is limited in duration and scope, fully logged, and shown to your users with a visible banner while it is active.
Where is the data hosted?
The hosting location is set in the contract. We do not publish a regional guarantee on the website before it is contractually fixed for your school.
Can all the data be exported?
Yes — a full export at any time, with no exit fee.
What happens when a subscription ends?
Data is kept for a retention window (90 days by default) so export and recovery remain possible; permanent deletion is then a separate, reviewed operation.

See it running against your own numbers

Show us your school's size and priorities, and we will demonstrate the platform on data shaped like yours — then hand you an implementation plan and a written quote.