Mydex Data Services Community Interest Company

Mydex Personal Data Stores (PDS) | Attribute Stores (AtS)

Personal Data Attribute Stores offer a secure channel of engagement with citizens across all aspects of their lives. They enable citizens to deliver proof of claims (identity, entitlement, age, etc.), and collect and share verified information about themselves with services and organisations — empowering digital channels for citizens and services.


  • Secure vault to store information for citizen's entire life
  • Extensible data schema
  • Supports verified, self-asserted and self-collected data
  • Supports any data format (meta, state, transactional)
  • Unique encryption with private key under control of the citizen
  • Can accept data delivered via APIs or entered directly
  • Data shared under GDPR-compliant data sharing agreement
  • Data is portable and exportable under control of the citizen
  • Store certified copies of proofs issued by third party authorities


  • Distributed personal data archive
  • Data Portability, Subject Matter Access Requests and transparency compliance
  • Enables provision of portable roofs of claims and entitlement
  • GDPR compliance
  • Reduced data sparsity
  • Improved data quality
  • Low-cost, simple deployment
  • Simple integration and introduction to users
  • Independently certified to various standards including ISO27001


£3,920 an instance a year

Service documents


G-Cloud 12

Service ID

1 9 5 9 4 7 7 1 6 7 1 8 5 7 9


Mydex Data Services Community Interest Company David E Alexander
Telephone: +442032396245

Service scope

Software add-on or extension
Cloud deployment model
Public cloud
Service constraints
System requirements
  • User access: any device with supported browser (see list below)
  • Backend: any system that supports RESTful APIs

User support

Email or online ticketing support
Email or online ticketing
Support response times
Support response times within 24 hrs
User can manage status and priority of support tickets
Phone support
Web chat support
Onsite support
Yes, at extra cost
Support levels
We can provide on-site support if booked and scheduled in advance through our cloud support services.
Support available to third parties

Onboarding and offboarding

Getting started
We provide getting started guides along with a set of cloud support services to help with planning, roadmapping, etc.
Service documentation
Documentation formats
End-of-contract data extraction
Users hold their own data and can export in a number of open standard formats directly.
End-of-contract process
Service is disabled at their request, archive held for a period of six months which is then deleted after providing notification of impending deletion. All data is encrypted in this archive with no access available either internally or externally.

Using the service

Web browser interface
Supported browsers
  • Internet Explorer 8
  • Internet Explorer 9
  • Internet Explorer 10
  • Internet Explorer 11
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari 9+
  • Opera
Application to install
Designed for use on mobile devices
Differences between the mobile and desktop service
Service interface
Description of service interface
We provide web based documentation that can be accessed with normal accessibility tools We provide API based developer helper functions that allow for automation of access to key specification information
Accessibility standards
WCAG 2.1 AA or EN 301 549
Accessibility testing
We have tested our platform with normal off-the-shelf tools and text help service
What users can and can't do using the API
They can make request using RESTful API Services performing
PUT, POST, GET functions subject to the terms of their connection and the data sharing agreement in place with the individual they have connected to. Data can be transmitted in encrypted form using XML and JSON formats.

Identity protocols supported are SAML and OpenIDConnect 2.0
API documentation
API documentation formats
API sandbox or test environment
Customisation available
Description of customisation
They can specify the datasets and use cases they wish to include within their connection.


Independence of resources
We have a true autoscaling and auto-healing platform environment that allows us to automatically increase capacity on demand, this powered by Amazon Web Services.


Service usage metrics


Supplier type
Not a reseller

Staff security

Staff security clearance
Other security clearance
Government security clearance
Up to Baseline Personnel Security Standard (BPSS)

Asset protection

Knowledge of data storage and processing locations
Data storage and processing locations
United Kingdom
User control over data storage and processing locations
Datacentre security standards
Complies with a recognised standard (for example CSA CCM version 3.0)
Penetration testing frequency
At least every 6 months
Penetration testing approach
Protecting data at rest
Physical access control, complying with another standard
Data sanitisation process
Data sanitisation type
Explicit overwriting of storage before reallocation
Equipment disposal approach
Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001

Data importing and exporting

Data export approach
As above, users hold their own data and can export in a number of open standard formats directly.
Data export formats
Other data export formats
  • XML
  • JSON
Data import formats
Other data import formats
  • XML
  • JSON

Data-in-transit protection

Data protection between buyer and supplier networks
  • TLS (version 1.2 or above)
  • Other
Other protection between networks
We use a combination of TLS (Version 1.2 or above) and PKI for secure two-way data exchange.
Data protection within supplier network
IPsec or TLS VPN gateway

Availability and resilience

Guaranteed availability
Approach to resilience
Amazon Web Services offer us a true 'auto-scale' platform. We can also manually scale-up e.g if expecting a big surge in traffic.

We have Resilience Self-Healing: as well as 'scaling', the platform indirectly improves business continuity because it 'self-heals', replacing failed app servers with healthy ones without any human interaction. We use 'multi-availability zones': our platform is spread across geographically-separate datacentres in Amazon's eu-west-1 region, reducing dependency on one physical location, giving us proper high-availability.

Management and automation has always been a strength of our platform and approach. Using AWS Terraform as an infrastructure management tool, we control all changes to the infrastructure, virtualisation-level through code, making it fully auditable, better open to peer-reviews, and are able to easily 'undo' any mistakes not found in testing by enforcing the last known 'good' configuration.

Terraform also automates the provisioning of new infrastructure, reducing margin for user-error, something we have done for our core code for many years but can now do at infrastructure layer.

We have snapshot and backup technologies, enhanced at AWS, allowing faster, flexible options for disaster recovery, in addition to our own offsite-DR at Rackspace as triple protection.

Increased flexibility and expansion support thanks to constant AWS innovation.
Outage reporting
We use for reporting any service scheduled or unplanned outages.

Identity and authentication

User authentication needed
User authentication
Public key authentication (including by TLS client certificate)
Access restrictions in management interfaces and support channels
All management interfaces are behind our VPN and individuals have specific access profiles within the VPN environment.
Access restriction testing frequency
At least every 6 months
Management access authentication
  • 2-factor authentication
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Username or password

Audit information for users

Access to user activity audit information
Users have access to real-time audit information
How long user audit data is stored for
At least 12 months
Access to supplier activity audit information
Users contact the support team to get audit information
How long supplier audit data is stored for
At least 12 months
How long system logs are stored for
At least 12 months

Standards and certifications

ISO/IEC 27001 certification
Who accredited the ISO/IEC 27001
British Standards Institute (BSi)
ISO/IEC 27001 accreditation date
What the ISO/IEC 27001 doesn’t cover
ISO 28000:2007 certification
CSA STAR certification
PCI certification
Other security certifications
Any other security certifications
  • FairData certification
  • FairData Enabler
  • ISO270018 compliant for management of personal data in the cloud

Security governance

Named board-level person responsible for service security
Security governance certified
Security governance standards
ISO/IEC 27001
Information security policies and processes
All Mydex work is conducted in accordance with a set of policies and processes which make up the ISMS.

Operational security

Configuration and change management standard
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Configuration and change management approach
All changes to the Mydex Platform are subject to approval by the Head of Development Programmes, in accordance with the IT infrastructure management policy, a key component of the ISMS. Any proposed changes are defined in the PivotalTracker tool, approved by the Head of Development Programmes, developed and tested in an isolated environment, before final pre-deployment testing much of which is automated and controlled by tools such as the Jenkins continuous integration and Puppet CM systems. Deployment to the operational environment is dependent on approval by the Head of Development Programmes, recorded on PivotalTracker.
Vulnerability management type
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Vulnerability management approach
Security vulnerabilities are managed in accordance with processes defined in the ISMS independently certified under ISO27001:2013. These include: prompt application of system software updates as issued by suppliers, subject to the change management processes above; membership of security alert distribution lists; use of tools such as the OSSEC monitoring tool.
Protective monitoring type
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Protective monitoring approach
Protective monitoring of the Mydex Platform is conducted as defined in the ISMS and ensures that only authorised users are granted access, that all access activity is recorded and any unusual activity reported via realtime alerts. This is achieved via an integrated set of tools including OSSEC, Nagios and Munin.
Incident management type
Conforms to a recognised standard, for example, CSA CCM v3.0 or ISO/IEC 27035:2011 or SSAE-16 / ISAE 3402
Incident management approach
Incidents are managed in accordance with Mydex's incident management procedure which requires any incident to be reported and recorded on the PivotalTracker system and promptly actioned according to the severity. Corrective actions not only address the incident and the immediate consequences but also investigate and eliminate the root cause.

Secure development

Approach to secure software development best practice
Independent review of processes (for example CESG CPA Build Standard, ISO/IEC 27034, ISO/IEC 27001 or CSA CCM v3.0)

Public sector networks

Connection to public sector networks


£3,920 an instance a year
Discount for educational organisations
Free trial available
Description of free trial
Use of our Sandbox for testing and experimentation, no limited time period.
Link to free trial

Service documents