Skip to content
Use casesHow it worksPricingStill building this project.Book a demo

Security

Built for IT teams who ask hard questions.

How Scannable protects your assets, your people and your data.

How we hold the data

  • Encryption

    HTTPS on every connection. TLS 1.2 or newer in transit. AES-256 at rest.

    TLS 1.2+ · AES-256

  • Access

    SSO with Google or Microsoft on Business+. SCIM on Enterprise. Roles decide who can change memory, approve spend, or wipe an object.

    Google · Microsoft · SCIM

  • Data residency

    Enterprise workspaces can run in the UAE. Other regions on request.

    UAE · Enterprise

  • Audit logs

    We record every scan, message, and action. Exportable audit logs are on Enterprise.

    scan · message · action

  • Backups

    Encrypted backups of workspace data every day.

    Daily · encrypted

  • UAE PDPL

    IN PROGRESS

    How we collect, store, and delete personal data under UAE law.

    Personal data · UAE

How the AI handles your data

  • Your data is never used to train AI models.
  • Objects only answer from their own memory, your uploaded manuals, and cited web sources.
  • Admins can view, edit or delete any object's memory at any time.
  • Enterprise can run a private LLM deployment.
Employee phone connects over TLS to Scannable (UAE / cloud), which sends SCOPED CONTEXT to LLM provider (no training, zero retention where available).
Employee phone
Scannable (UAE / cloud)
LLM provider (no training, zero retention where available)

Actions have limits

Objects can open tickets and request purchases. They cannot spend on their own. Named people still sign off.

  • Purchases always require a named approver.
  • Per-object spending limits on Enterprise.
  • Actions are restricted by role.
  • Staff-only tools require sign-in.
  • Rate limits on every tag to stop abuse.

What employees see and share

A scan is a conversation with one object. It does not expose other people’s questions, and it does not reach into the phone.

  • Scanning needs no account.
  • We log time, asset and message.
  • No location tracking. No contacts access.
  • Name and email are optional, and only collected when someone wants updates.

Subprocessors

  • Hosting

    Application hosting

    On request

  • Database

    Primary database

    On request

  • Email delivery

    Transactional email

    On request

  • LLM provider

    Object chat completions

    On request

  • Auth

    Sign-in and SSO

    On request

  • Analytics

    Product usage analytics

    On request

Full list on request.

Responsible disclosure

If you find a vulnerability, email us. Do not post it publicly. We acknowledge reports within two business days. Policy: /.well-known/security.txt.

FAQ

Tags are meant to be scanned. Rate limits cap traffic on every tag. Staff-only tools stay behind sign-in. Every scan is logged. Mark a tag staff-only if it sits on something sensitive.

Yes. Admins can mark a tag staff-only. Anyone can still open the page; actions that change anything require a signed-in account.

You can export workspace data first. After cancel, we delete it within 30 days, except records we are required to keep.

Yes, on request. Ask with the security pack or email us.

Need our security pack?

Architecture notes, policies, subprocessors, and a DPA.