Security & data
Before connecting a service to your workflow, you need to understand what information it uses, how access is controlled and what supports its assurance claims. This page explains Sustema's approach, our public website and the ENTITY service we are developing.
Designed with future assurance in mind
We designed ENTITY's architecture to support future independent security assurance. The design includes controlled access, traceable company information, protection of sensitive operational information and defined recovery requirements.
Architecture design is not a certificate or an independent audit. Formal assurance investment is phased with the service’s development and customer requirements.
Company lookup inputs and source data
ENTITY's service design distinguishes the information supplied in a lookup from the evidence used to maintain its company information.
Customer-submitted identifying details are lookup inputs. They are not automatically evidence used to construct ENTITY’s corpus and are not automatically contributed to a shared corpus.
Check the applicable service information and terms for processing, retention and deletion arrangements.
Visiting the website or contacting us
See our website Privacy Policy for information about visiting sustema.io or sending an enquiry, including providers, retention and how to contact us about your data.
The website policy covers the public site and enquiry process. Separately contracted product services have their own applicable information and terms.
Questions about data or security
For privacy questions, contact privacy@sustema.io. To discuss security or procurement requirements for an ENTITY workflow, use Discuss your workflow. Please do not include passwords, API keys, confidential datasets or customer records in an enquiry.