Security
A schedule is one of the most valuable documents a project owns. This is how ploteer keeps it.
One client, one database
Every client has its own database, reached through the client’s own link, with the editors and the viewers of the client’s choosing. No client’s data is held in another client’s database.
Hosted in the EU
The service runs in the European Union, and the client’s data does not leave it. Uploaded files, the schedule exports and the drawings behind the boards, are stored in the European Union as well.
Backups
Every database is backed up every day. The backups are kept for thirty days, in a store separate from the running system.
Connections and sign-in
Every connection to the service runs over TLS. A session lives in a cookie that scripts in the browser cannot read. Sign-in offers a second step by email or authenticator app, and the client decides whether it is required. A password is reset by email, never sent in one.
The schedule stays where it is
ploteer reads the .XER export. It holds no connection to the client’s native schedule and cannot change anything in it. The schedule of record stays the client’s.
Notifications and digests are sent through our email service, to the addresses the client’s users registered, and to nobody else.
Who runs it
Project Dynamics B.V. runs the service. The servers are reached by key, never by password, and the key is held by Project Dynamics B.V. alone. Changes to the application pass a review before they reach the service.
Reporting a concern
A security concern, a suspected weakness or a question on any of the above goes to contact@ploteer.com. We answer, and we show what is asked for.