Protecting development data through layered controls.
Pridmora is designed around a defence-in-depth security model, combining authenticated access, organisational and role boundaries, controlled data access, secure development practices and wider operational governance.
Pridmora combines application permissions, organisation and assignment checks, database controls and storage tenancy controls so that access is reinforced at multiple layers.
Access is controlled at more than one layer.
Authenticated access
Protected Platform areas require authenticated access rather than relying on obscured or publicly available URLs.
Organisation membership
Organisation membership and the active workspace context help determine which organisational environment a user can access.
Role-based permissions
Different roles receive access appropriate to their responsibilities rather than every organisational user receiving the same permissions.
Assignment boundaries
Private relationship and development content is restricted by authorised assignment for content-capable users.
Tenant-aware data controls
Database and Development Evidence storage controls are designed around organisational tenancy rather than relying only on the user interface.
Controlled evidence access
Authorised Development Evidence downloads use short-lived signed access rather than exposing unrestricted permanent file links.
One failed control should not be the whole security boundary.
Pridmora's current Platform architecture combines multiple complementary controls.
- authenticated application access;
- role and organisation checks;
- assignment restrictions for private development content;
- database row-level access controls;
- tenant-aware Development Evidence storage;
- server-side construction and validation of evidence-storage paths;
- short-lived signed access to authorised evidence files;
- server-side handling of privileged service credentials;
- workflow-specific privacy controls for authorised person-level external AI processing; and
- audit and operational logging appropriate to the Platform.
Organisational access does not mean unrestricted access to managers' development.
Restricted by role and relationship
Private manager-development content is intended for the authorised manager or practitioner relationship. Organisation oversight does not automatically grant access to private development content.
Collective rather than unrestricted individual access
Organisation Development Intelligence is designed to surface collective patterns using privacy safeguards rather than exposing underlying private manager records.
For defined authorised person-level AI workflows, Pridmora assembles workflow-specific context rather than giving the external AI model unrestricted access to the Pridmora database. Identifying profile information held in the Identity Vault is kept separate from this external AI processing path. Pridmora also applies data-minimisation and pseudonymisation controls intended to reduce unnecessary disclosure of names and certain other identifiers wherever feasible. These controls reduce privacy risk but are not a claim of complete anonymisation.
Uploaded evidence receives additional access controls.
Development Evidence may contain information relevant to a manager's development. The Platform therefore applies controls to the way evidence is stored and accessed.
Evidence storage paths are constructed and validated server-side rather than trusting organisation or client identifiers supplied directly by the browser.
Evidence storage controls are designed around organisational tenancy and authorised access.
Authorised evidence downloads use short-lived signed access rather than general public file URLs.
The offboarding model is designed to remove the associated stored Development Evidence object before clearing or soft-deleting the related evidence metadata.
Privileged credentials are intended for controlled server-side use.
Service-role credentials used for privileged Platform operations are intended to remain server-side and are not designed to be exposed in browser application bundles.
Privileged access should be limited to the technical and operational purposes for which it is required.
Security-sensitive behaviour is tested before pilot deployment.
Pridmora's development process includes technical checks intended to reduce the risk of changes unintentionally weakening access or privacy boundaries.
Automated tests
Changes are subject to automated testing within the development workflow.
Type checking
TypeScript/typechecking forms part of the development workflow.
Privacy regression coverage
Role, organisation, assignment and privacy boundaries have dedicated regression coverage.
Security-sensitive testing
Security-sensitive changes are tested before deployment into the pilot environment. This includes targeted privacy and adversarial verification where a change affects person-level external AI processing or identity boundaries.
Controlled environments
Pilot and production-like environments are treated as controlled environments.
Pre-pilot UAT
Manager, organisation and Development Intelligence workflows have undergone extensive pre-pilot user-acceptance testing.
Security operates within the wider data-protection framework.
For Customer Personal Data processed to provide the Platform for an organisational customer's purposes, the intended contractual model is that the customer acts as Controller and Pridmora acts as Processor.
Pridmora may separately act as Controller for limited supplier-side purposes such as account administration, billing, security, legal compliance and direct support.
Customer responsibilities also matter
Organisational customers remain responsible for their own lawful basis, transparency, internal employment and governance obligations and any DPIA or consultation required for their deployment.
Pridmora uses established providers to deliver the service.
Supabase
Supports Platform authentication, database services and Development Evidence storage. The current pilot infrastructure is configured in an EU AWS region.
Vercel
Provides application hosting and deployment infrastructure for the Pridmora Platform.
OpenAI
Provides AI model/API infrastructure used for authorised AI-supported functionality within Pridmora. For defined person-level workflows, Pridmora controls the context assembled before external processing; the external AI model is not given unrestricted access to Pridmora's database or Identity Vault.
Stripe
Supports payment and billing processing where applicable. Detailed payment-card information is handled through Stripe rather than stored as private manager-development content.
Relevant providers are managed within Pridmora's data-protection, supplier and subprocessor governance framework.
Security also means being prepared when something goes wrong.
Incident response
Pridmora maintains governance for the identification, investigation and response to security and data-protection incidents.
Personal data breaches
Material personal data breaches affecting Customer Personal Data are handled under the applicable DPA, including customer notification without undue delay after Pridmora becomes aware of the breach.
Business continuity
Pridmora's continuity approach combines established cloud-provider resilience with controlled deployment, backup/recovery arrangements and documented operational response.
Security includes what happens when service ends.
Customer Personal Data is handled at the end of service in accordance with the applicable agreement, Data Processing Agreement and agreed return or deletion instructions.
Applicable legal obligations and technically necessary backup cycles may affect the timing of complete deletion from resilient storage.
Organisations can request proportionate due-diligence information.
Pridmora maintains a wider governance library behind this public overview. Depending on an organisation's procurement, Information Governance or security review requirements, relevant assurance information may include:
- Information Security governance;
- Data Protection and Privacy governance;
- AI Governance;
- Access Control;
- Secure Development;
- Incident Response;
- Business Continuity and Backup/Recovery;
- Data Retention;
- Logging and Monitoring;
- Vulnerability Management;
- Supplier/Subprocessor Security;
- Data Processing Agreement; and
- Subprocessor information.
Security is part of the wider Pridmora governance model.
See also our Privacy Notice, Responsible AI & Human Oversight, Cookie & Browser Storage Notice and Trust & Governance page.
Security or procurement review?
Organisations can contact Pridmora for proportionate additional information to support procurement, Information Governance, privacy or security due diligence.
Contact Pridmora