TMS

Security

Last updated: 2026-10-20.1 · Version 2026-10-20.1

This is a translation. If it differs from the Bulgarian text, the Bulgarian text prevails.

These are the measures we apply at the date of the version. They are an annex to the Data Processing Agreement. Version: 2026-10-20.1.

1. Access and identity

  • Passwords are stored only as a hash, never in plain form.
  • The session is an encrypted cookie (httpOnly, Secure); access tokens are short-lived and renewed automatically.
  • We limit attempts to sign in and to do other sensitive actions.
  • Access is separated by role (owner, administrator, dispatcher and so on) and by company: a user sees the data only of the companies they are a member of.
  • Accounts and companies can be blocked, which ends sessions at once.
  • An audit log of important actions.

2. Transport and storage

  • All connections to the Service use HTTPS.
  • Files are kept in private storage; download links are signed and expire.
  • Credentials for external systems (for example tracking) are stored encrypted.
  • Daily backups encrypted with AES-256; we keep the last 14, stored on the server and in separate storage.

3. Organisation

  • Only a limited group of people can reach the production environment, by key, without a password.
  • We develop with automated tests; changes are deployed through a defined process.
  • Sub-processors are selected and bound by contract (see Sub-processors).
  • Breach procedure: detecting, containing, notifying the customer and, where needed, the CPDP and the people concerned.

If you find a vulnerability, write to us at office@pintletms.eu — please give us a reasonable time to fix it before disclosing it publicly.