Privacy by design
We aim to make purpose, data minimisation and appropriate retention part of product design. A workflow should ask for the information it needs and make its use understandable.
Trust & platform principles
Responsible technology
starts with deliberate choices.
Clear responsibilities. Appropriate access. Thoughtful data handling. These principles guide how we build the Grid family.
This page describes our corporate product principles. Specific safeguards, features and service commitments depend on the product and its stage of development.
Roles & least privilege
Our platform principles include access based on responsibilities, with the aim of limiting what each person can see or change to what their work requires.
Secure transport
We design around encrypted transport for information moving between users and services, with appropriate configuration reviewed as each product progresses.
Auditability
Important changes should be traceable. Our direction includes records of relevant activity so teams can understand what happened and follow up responsibly.
Documents & data
We aim to handle operational documents with appropriate access, purpose and lifecycle controls, rather than treating every record as information for everyone.
Backups & resilience
Our development principles include recovery planning, appropriate backups and restoration checks. Specific recovery commitments must be defined for each product.
Incident management
We aim to assess issues promptly, contain their impact, investigate the cause and communicate with affected parties where appropriate. Lessons should inform improvements.
Vendors & partners
Third-party services should be selected with attention to their role, data access and responsibilities. Payment-related features should use regulated or licensed partners where applicable.
Ask about our approach
Trust starts with
a clear conversation.
For questions about a product’s safeguards or data responsibilities, contact our team. For a security concern, choose General enquiry and identify the affected page or product in your message. Please describe the concern without attaching sensitive operational, learner or patient records.
Your next chapter