Skip to content
14-day free trial, no card9 languages176 business types · 50 apps
EN· USD
Try a live demoStart free trial

Security at zmle

What we do to protect your business data, what is not certified yet, and how to reach us about a security problem.

Who can see your data

Party by party: who can open what, and what stops everyone else.

  • Your own staff

    Each person sees only what their role allows, and can be limited to their own branch. You decide who must use two-step sign-in, and you can limit the admin to approved IP addresses.

  • zmle support

    Only with your grant, at the level and for the time you chose. Every support session appears in your activity log.

    Support access only with your permission
  • zmle engineers

    The database is not reachable from the internet. Every operator action is written to the platform audit log, and opening a workspace follows the same support access rules.

  • Sub-processors

    Providers that process data for us, such as hosting and email delivery, are listed with their location.

    Sub-processors
  • AI providers

    Only the providers your workspace connects with its own keys. A workspace without a key sends nothing to any AI provider.

What nobody at zmle can read

  • Card numbers: they are typed on the payment provider's own page and never reach zmle.
  • Passwords and API, MCP and SCIM tokens: stored only as hashes, so even we cannot turn them back into the original.
  • Provider secrets and two-step sign-in seeds: encrypted with AES-256-GCM under a separate key for each workspace.
  • Clinical notes: encrypted field by field, and opening a chart needs explicit chart rights.
  • Private files: sent with “no-store”, so browsers and proxies do not keep copies.
  • Bulk exports: need the permission plus a fresh “confirm it's you”, and every export is logged.

What we do

How your business data is kept apart, protected, backed up and checked — in plain words.

Your data

  • Each workspace walled off in the database

    Each workspace has its own database schema and its own database role. PostgreSQL itself refuses a query that reaches into another workspace, even if application code has a bug. Tables that several workspaces share use row level security, and the database is not reachable from the internet.

  • Encryption

    Connections use HTTPS, and browsers are told to use nothing else (HSTS). Passwords are stored only as hashes. Provider secrets and two-step sign-in seeds are encrypted with AES-256-GCM under a separate key for each workspace. Backups are encrypted with AES-256 and carry an integrity check, so a changed file is caught before a restore. Clinical notes of health workspaces are encrypted field by field.

  • Data location

    Workspaces are stored with our hosting provider. The provider and its region will be listed on the sub-processors page; until then, ask us and we tell you where your workspace will be stored. If your data must stay in a particular country, tell us before you start.

Access and sign-in

  • Two-step sign-in

    Owners and staff can use an authenticator app or a passkey (fingerprint, face or a security key) — a passkey can also replace the password. A workspace can require two-step sign-in for chosen roles; our own staff must always use it. Repeated failed sign-ins are slowed down and locked.

  • Support access only with your permission

    zmle support can open your workspace only after the owner grants access under Security → Support access: View-only by default, or Full, for 1 hour, 1 day or 7 days. You can revoke it at any time, and revoking signs the support person out on their next request.

  • Audit logs

    Each workspace keeps an activity log of who did what and when. Every action of our staff is written to a platform audit log, and every support session appears in your workspace's own activity log.

  • Tamper-evident activity log

    Each entry of the activity log is chained to the entry before it with a hash. Editing, reordering or deleting an entry breaks the chain, and the check shows exactly where.

  • Card payments

    Card details are entered on the payment provider's own page. They never reach zmle servers.

Backups, updates and special data

  • Backups and tested restores

    Your data is copied to an encrypted backup every hour, and every night together with your files. Database changes are archived continuously for point-in-time recovery, a copy is kept off-site with a different provider than the server, and a copy is made before every release. Restores are tested automatically.

  • Signed updates

    Every software release is signed, and the signature is checked before an update is installed.

  • How the platform is protected

    Uploaded files are scanned for viruses (ClamAV). Pages send a content security policy and other security headers, and public forms are validated and rate-limited. Release images and update bundles are signed, and dependencies and code are scanned for known vulnerabilities and leaked secrets.

  • Health data safeguards

    Clinical apps encrypt notes, log every chart access, record patient consent and keep AI features away from clinical notes unless consent is recorded.

For IT and security teams

  • Single sign-on (SAML 2.0 and OpenID Connect)

    On the Pro plan, staff can sign in with Microsoft Entra ID, Google Workspace, Okta or any SAML 2.0 or OpenID Connect provider. SAML assertions must be signed with a certificate the workspace pinned; audience, recipient, expiry and replays are checked. Company domains are verified with a DNS record. A workspace can require company sign-in, while the owner keeps a password with two-step sign-in as the break-glass account.

  • User provisioning (SCIM 2.0)

    Your identity provider can create, update and switch off users and map groups to roles through a SCIM 2.0 endpoint protected by a bearer token that is stored only as a hash. Switching a user off ends their sessions; no data is deleted.

  • Audit log export and SIEM stream

    Admins can filter the workspace’s activity log (who, what, when, IP address, browser), export it as CSV or JSON, set how long it is kept and stream new entries to their SIEM as signed HTTPS batches.

  • Security policies

    Each workspace can require two-step sign-in for all staff, set password rules, an idle timeout and a session lifetime, limit the admin to approved IP addresses and choose which sign-in methods staff may use.

Your data from start to finish

What happens to your data at each step, with the times our system enforces.

  1. Stored

    In your workspace's own schema in the database, walled off from every other workspace.

  2. Backed up

    Encrypted copies every hour and every night, plus continuous point-in-time recovery.

  3. Exported

    The owner can download the whole workspace at any time: every table plus your files.

  4. Closed

    Data is erased 30 days after the owner closes the workspace, or 90 days after a subscription ends in another way.

  5. Erased

    The export copy made before the erasure is deleted 90 days later.

  6. Backups purged

    Backup copies of the erased workspace are deleted 30 days after the erasure.

Controls you have

  • Export everything

    Download the full workspace as NDJSON plus your files. Your password is asked again, and the export is logged.

  • One person's data

    Export or erase the data of one customer or employee when they ask.

  • Activity log retention

    Choose how long your activity log is kept.

  • Account deletion

    Delete an account or close the workspace; each case is explained on the account deletion page.

Data processing agreementAccount deletionPrivacy policy

AI and your data

What reaches an AI provider, and what never does.

  • Your workspace's AI features use only the AI provider keys your workspace connects itself. A workspace without a key sends nothing to any AI provider.
  • Clinical notes stay out of AI features unless the patient's consent is recorded.
  • Prompts and answers of your workspace's AI are deleted after 180 days.
  • The chat on zmle's own website is answered by AI providers we engage, and conversations are deleted 90 days after the last message.

If something goes wrong

A written procedure, followed every time.

  • We detect and investigate problems under a written incident response procedure.
  • Affected customers are told without undue delay: by email to the workspace owner, on the status page and with a notice in the admin.
  • After every incident we review what happened and what we change, and we follow the changes through.

How zmle controls its own staff

The same rules we ask of you, applied to ourselves.

  • Each staff member gets only the capabilities their job needs.
  • Every staff account must sign in with an authenticator app.
  • Sensitive actions ask staff to confirm it's them again.
  • Every operator action is written to the platform audit log.

What we do not claim yet

We would rather tell you what is missing than let you assume it.

  • zmle is not certified to ISO/IEC 27001 and has no SOC 2 report.
  • No independent penetration test has been published yet.
  • SAML sign-in does not accept encrypted assertions and does not sign its sign-in requests yet.
  • Full-disk encryption of the database server is not confirmed yet.
  • When certifications or test results exist, they will be listed here with their dates.

Found a security problem?

Please tell us privately. We reply quickly and keep you informed until it is fixed.

For IT teams: security documents on request

Send us your security questionnaire. We answer in writing and send the documents that exist, with their dates.

Questions, answered

Short answers to what owners and IT teams ask us most.

Where is my data stored?

Workspaces are stored with our hosting provider. The provider and its region will be listed on the sub-processors page; until then, ask us and we tell you where your workspace will be stored. If your data must stay in a particular country, tell us before you start.

Can zmle staff see my data?

No, not without your permission. The owner grants access under Security → Support access: View-only by default, or Full, for 1 hour, 1 day or 7 days. It can be revoked at any time, and revoking signs the support person out on their next request. They also need a ticket id and a fresh authenticator code, and every session appears in your activity log. Without a grant, access is possible only for a declared security incident: the owner is told at once, and the access is reviewed within a day.

Does AI see my data?

Only if you connect it. Your workspace's AI features use only the AI provider keys your workspace connects itself; without a key, nothing is sent to any AI provider. Clinical notes stay out of AI unless consent is recorded.

Do you support SSO and SCIM?

Yes, on the Pro plan: sign-in with SAML 2.0 or OpenID Connect, and user provisioning with SCIM 2.0. The section for IT and security teams lists the details and the limits.

SSO and SCIM details

How are backups made and tested?

Encrypted copies every hour and every night, continuous point-in-time recovery, an off-site copy with a different provider, a copy before every release, and restores tested automatically.

Is zmle certified?

Not yet. zmle has no ISO/IEC 27001 certificate, no SOC 2 report and no published independent penetration test. When that changes, it is listed on this page with its date.

How do I report a security problem?

Use the form on the vulnerability page or the email address in our security.txt file. Please do not share details publicly until we confirm the fix.

How do I report spam, phishing or malware from a zmle customer?

Forward the message (with its headers) or the web address to abuse@zmle.com. Every report gets a case with a deadline: phishing and malware within 24 hours, spam within 3 days. We can pause a workspace's sending or take a site down while we check.

Questions about security?

Ask us before you start. We answer in writing, and we tell you what we do not do yet.