Security & compliance

Security lives in the database, not just in the app.

The guarantees that matter, like isolation between companies and the protection of the signature log, are enforced at the data layer. Application checks still sit on top: two lines of defense instead of one.

Privacy by design

The guarantees, enforced at the root.

  • Tenant isolation

    PostgreSQL Row-Level Security keeps each company's data separate even if a query forgot the company filter.

  • Append-only log

    Signatures, goal events and sensitive operations stay on record: the database lets the application only add entries. The one exception is erasure required by the GDPR, which goes through a dedicated procedure.

  • Anonymous surveys by design

    In the database an answer isn't linked to the employee: anonymity doesn't depend on a setting.

  • Protected whistleblowing

    Reports can be anonymous, the reporter's identity is encrypted, and handling is entrusted to a dedicated compliance role.

  • Confidential pay data

    Visible only to authorized roles, with the most sensitive values encrypted at rest.

  • Right to erasure

    Full deletion of an employee's data on request. Only the operations log remains, as the GDPR allows.

  • Data export

    A complete export of an employee's personal data, to answer an access request.

  • Protected sign-in

    Two-factor authentication, revocable sessions and lockout after repeated attempts.

Compliance for Italy

Built around Italian and European rules.

Orgable is designed for mid-to-large Italian companies and the rules they have to follow, and that shows in its compliance choices.

  • D.Lgs. 24/2023

    The whistleblowing module is built on the requirements of the decree that transposes the EU Whistleblowing Directive: internal channel, confidentiality, trackable status. The organizational procedures the decree requires remain the company's responsibility.

  • GDPR

    Role-based access to data, export and deletion on request, an operations log.

  • E-signature

    PDF signature with a signature log: a simple electronic signature under the eIDAS regulation, admissible as evidence, with its weight left to the court. Documents that legally require written form need an advanced or qualified signature.

  • Processing agreement

    Data processing agreement (DPA) and list of sub-processors: in preparation, shared with you before the pilot is signed.

For your IT team

How it works, in brief.

The questions that usually come up in security questionnaires, with answers you can verify.

AreaHowWhat it guarantees
IsolationPostgreSQL with forced Row-Level SecurityNo company sees another's data, even if a query forgot the company filter
PermissionsRoles and scope within the org chartManagers decide only within their branch, never on themselves
Sign-inSecond factor, revocable sessions, attempt lockoutProtected accounts; company SSO already built, to be tested and enabled for Enterprise customers
EncryptionHTTPS, field-level encryption, backups encrypted before they leave the serverCore pay figures, whistleblower identities and second factors protected at rest
ReleasesBackup before every release, automated checks, a review separate from whoever wrote the codeEvery release can be rolled back

Where we stand today

The real status, plainly stated.

What's done, and what we're preparing ahead of the first contracts.

  • DoneIn production over HTTPS since July 2026
  • DoneEncrypted off-site backups, with a tested restore and automatic alerts
  • DoneTwo full code reviews, with every numbered finding closed
  • DoneEvery release goes through a review separate from whoever wrote the code, which can block it
  • In preparationData processing agreement (DPA) and list of sub-processors
  • In preparationFact sheet on providers and data location

Questions about compliance?

Let's talk about your context and how Orgable fits into your data-protection processes.