Skip to content
Tablore
TR

Security

Clear safeguards. Traceable actions. Honest explanations.

Your Excel files can contain highly sensitive business data. This page explains our safeguards in verifiable terms and identifies work that is still planned.

Data residency

  • Designed with Turkey's KVKK requirements in mind: data stays in Turkey by default.
  • Data residency protection is enabled by default in organization settings. Disabling it requires administrator approval and separate consent.
  • While protection is enabled, no file content or cell values are sent to third-party services.

Encryption

  • All traffic is transmitted over TLS.
  • File content is designed to be stored using AES-GCM envelope encryption with a separate data key for each file.
  • Passwords are hashed with argon2id. Plain-text passwords are never stored.

Organization isolation

  • Each request runs in the session's organization context. One organization cannot query another organization's data.
  • Isolation is enforced at the application layer. A second layer using database row-level policies is planned.
  • Cache, queue, and object storage keys include the organization identifier.

Audit trail

  • Critical operations such as sign-in, file uploads, rule approvals, and role changes are designed to be written to the audit log.
  • Records are linked in a hash chain. Later changes break the chain and can be detected.
  • Support staff cannot view customer files, rules, or analysis content. There is no impersonation feature.

Identity and access

  • Role-based authorization with viewer, editor, administrator, and owner roles.
  • Critical changes follow the four-eyes principle: nobody can approve their own request.
  • Two-step verification and session management are on the roadmap and will be required for the administrator panel.

AI usage

  • Formula analysis, health findings, and rules are produced by a deterministic rule engine, without AI.
  • Smart Columns run on a locally hosted model on our own servers by default.
  • A cloud language model is used only with administrator permission and only for draft rule explanations. Drafts are not saved to rules without approval.