Tenant isolation
Organization-scoped records and role-aware access reduce unnecessary exposure across environments.
Enterprise trust designed into the operating model.
Restora is built for responsible public-institution operations, with least-privilege access, explicit human accountability, and clear environment boundaries.
From insight to completed action.
Audit-ready operations
Material updates can preserve ownership, timestamps, evidence references, and decision history.
Human-reviewed automation
Risk signals and AI-supported work inform authorized professionals rather than making final student decisions.
Data governance
Support configurable retention, archival, minimization, and district-controlled operating policies.
Accessible delivery
Interfaces are designed for keyboard access, readable status communication, and WCAG-aligned interaction.
Environment separation
Demonstration, training, testing, and production contexts remain clearly identified.
Readiness supports, not replaces, governance.
Technical controls must be paired with district policy, legal review, staff training, incident response, and ongoing access reviews appropriate to each deployment.
Security facts.
Only controls that are implemented and verified are listed here. No certification, standard, or control is claimed unless it is documented and available for review under procurement.
Data protection
Records are stored in the platform’s managed database. File uploads are handled through platform upload services, and private files require a signed URL to access.
Identity and access
Access is authenticated by the platform. Role-based access control limits each user to the operations permitted for their role (for example family, provider, navigator, principal, district executive, state administrator).
Tenant separation
Each record carries a tenant identifier, and row-level security restricts reads and writes to a user’s own tenant and role. Demonstration, training, and production environments are separately identified.
Audit logging
Material record changes are written to an audit trail that captures ownership, timestamps, and audit references. Audit events are appended through dedicated functions and workflows.
Data retention and deletion
Records support archival flags and deletion. Archival and deletion are governed by the customer’s operating policy; the platform provides the controls to act on those decisions.
Incident response
Security incidents are handled under the platform’s operational practices and customer-specific agreements. Notification and resolution terms are addressed in customer contracts.
Infrastructure and hosting
The application is hosted on the Base44 platform infrastructure and published from it. Detailed hosting information is provided to customers as part of procurement.
Subprocessors
A current subprocessor list is provided to customers under contract and reviewed during procurement. No subprocessor is engaged for customer data without an appropriate agreement.
District data control
District customers retain governance of their records, including lawful use, correction, archival, and deletion. Restora processes customer data on the customer’s instructions under agreement.
