Security

How moss protects your company's data

Last reviewed 15 November 2026.

This page describes the security controls that are live in moss today. Work we have planned is listed separately at the end, without dates. moss does not hold security certifications such as SOC 2 or ISO 27001 today.

How company data is kept apart

Several independent checks stand between one company's data and another's.

  • The server decides which company you are working in from your membership. The browser cannot choose it.
  • Every database query for company data names the exact company and workspace it may touch.
  • The application connects to the database with its own restricted login. It owns nothing, so it cannot change the database structure, switch off protections or delete audit history.
  • For many record types, the database itself refuses a link from one company's record to another company's record.
  • One central permission layer decides what each person may read: their sections, the company's module switches, who a record is shared with, and field rules such as who may see pay.
  • An automated leak test runs two test companies through every role against moss's read paths, exports and search. Any data from the other company fails the test. It is part of the release check we run before publishing a change.

Signing in

  • moss has no passwords. You sign in with a one-time code sent to your email, with Google, or with a passkey.
  • Email codes are stored only as a hash, expire after 10 minutes and work once. Requests and attempts are rate limited.
  • Signing in never creates an account. Unknown email addresses get the same answer as known ones.
  • Two-factor authentication, with an authenticator app or a passkey, is required for owners, the Admin role, any role that can manage members, settings or modules, and moss platform admins.
  • Sensitive actions ask you to verify again first, for example switching off a module, creating a bot, removing a passkey, ending a session or disconnecting Google.
  • Session cookies are HttpOnly and Secure. The database stores only a hash of each session token. A session ends after 30 days without use, and at the latest 90 days after sign-in. You can review and end them in Settings.

Encryption

  • In transit: every connection uses HTTPS, and browsers are told never to fall back to plain HTTP.
  • At rest: the database and its backups are encrypted on disk by our database provider.
  • In the application: credentials you store in moss, bank details, pay, sensitive HR fields, file contents and backups are encrypted with AES-256-GCM before they are saved. Copies of those values in undo history and bot receipts are encrypted the same way.
  • Each encrypted value is bound to its table and column, so it cannot be moved to another field without failing to decrypt.
  • The encryption key is kept in the hosting environment, separate from the database. A copy of the database alone does not reveal these values.
  • Other content, such as names, titles and notes, is stored readable so it can be searched. Permissions decide who sees it. moss servers can decrypt protected fields to show them to people allowed to see them; this is not end-to-end encryption.

Audit log

  • Every change is recorded: who made it (a person, a bot or the system), what changed, which record, when, and from which IP address and device. Edits keep a before and after.
  • The log is append-only. The database refuses edits and deletions, apart from the retention clean-up.
  • Each row is sealed into a hash chain, so a missing, reordered or edited row is detectable. A verification tool reports the first broken link.
  • A fingerprint of each chain is emailed outside the database every day, so the chain can be checked against a copy the database does not hold.
  • Events are kept for 90 days by default. Owners can choose 1, 3 or 7 years, or forever.
  • Owners and admins can read and export the log. Pay, bank details, birth dates, credentials and file contents never appear in it: it records that the field changed, not the value.
  • Unusual patterns of refused access, such as one person probing many records they cannot open or entering many wrong verification codes, alert your owners and admins in their Inbox and by email. Attempts across companies alert the moss team.

Access by the moss team

  • moss platform admins see only the structure of your company's events: the action, record type, ids, time and counts. They do not see names or content.
  • To see names or undo a change while helping you, a platform admin must turn on support mode for your organization, give a reason and choose 15, 30 or 60 minutes. It ends on its own.
  • Starting and ending support mode are recorded in your audit log. Your owners and admins get an Inbox notice and an email saying who started it, why and until when.

Bots and AI assistants

  • A bot follows the same rules as a team member. It sees exactly what the person who created it can see, through the same membership, sections, module switches and field rules. Bot scopes can only narrow that.
  • Bank account numbers, IBAN, BIC and bank codes are always masked in bot answers. A bot cannot send a masked value back to overwrite the real one.
  • Bot tokens are shown once and stored only as a hash. You can revoke a bot at any time, and its changes appear in the audit log as bot actions.

Hosting and service providers

moss uses these providers to run the service. The privacy policy explains what personal data each one processes.

ProviderWhat it doesWhere
VercelApplication hostingFrankfurt, with a global edge network
NeonPostgres database and its backupsFrankfurt
ResendEmail delivery: sign-in codes, notices and the daily audit fingerprintUnited States for stored email data
CloudflareA timer that starts moss's own scheduled jobs. It holds no company data.Global
GoogleSign in with Google. Calendar and Drive are used only if you connect them, and can be disconnected.Google's infrastructure

Tools you connect yourself, such as ClickUp, receive only what that connection needs, and you can disconnect them.

On the roadmap

These are planned and not live today. We will move each one into the sections above when it ships.

  • Database-enforced isolation (row-level security) on every company table
  • An external penetration test
  • Scheduled, encrypted off-site backups and a full restore rehearsal with our database provider
  • Company single sign-on (Google Workspace, Microsoft) with SCIM provisioning
  • A choice of data region
  • Managed-key encryption for stored credentials
  • Sign in with Apple
  • SOC 2 Type II and a bug bounty

Reporting a security issue

If you think you have found a security problem in moss, email security@mossfold.com with the steps to reproduce it. Please do not access other people's data, change data you do not own or disrupt the service while testing. We will confirm we received your report and keep you updated while we fix it.

Need answers for a vendor security review? Email the same address and we will send our questionnaire answers.