We are doing what we can to prevent your data from getting lost or stolen.
What do we do to prevent you losing Data
- Users can create new versions of their guideline, while having their previous versions easy accessible in their version history. For each new version we save a web version, a PDF and a data file. All these different formats will remain available for each version.
- Non destructive deletes of data. For all critical data we only mark it deleted and not actually delete it. This has enabled us to recover deleted PICOs and recommendations in cases of mis-deleting. Currently this can be done by contacting support, but users will soon be getting access to to this themselves.
- Daily snapshots/backup of the database. Keeping the last 35 days.
- The use of relationships and constraints in our RMDBS helps to maintain data integrity
- JSON exports (via the UI and API). Users can at any point generate a data-file copy of their whole guideline, or parts of it, and store that on their own machines
- PDF exports (via the UI and API). Users can at any point generate a PDF copy of their guideline, and store that on their own machines
- Word export (via the UI and API). Users can at any point generate a PDF copy of their PICO questions or recommendations, and store that on their own machines
What do we do to protect your data
- We have an overall Terms of service that all users must adhere to.
- Users can also set their own copyright statement and disclaimer.
- We save no personal data.
- We don't even have access to passwords. Passwords are encrypted with bCrypt.
- ACLs at the section level.
- Audits of every change is saved.
- We only support SSL (encrypted) connections to the server.
- CSRF enabled to prevent clicks jacking attacks for logins.
- All db queries are protected from injection attacks.
- All servers are behind at least 1 firewall.
- All application logs are shipped to a logging server.