Security & data

Your data is yours. We keep it separate.

Four controls do most of the work: brand isolation, role-based access, an audit trail that covers agent actions, and consent enforced at the point of sending.

The controls

What is actually in place

Brand isolation

Each brand is provisioned as its own workspace with its own separated data store, branding, currency, timezone and team. Contacts, campaigns, content and analytics never mix between workspaces — which is what lets one agency run several client brands from a single login.

Role-based access

Permissions are set individually rather than in fixed bundles, so a contractor, an analyst, a client and an administrator each get exactly what the work requires. Roles are scoped per brand, and removing someone is immediate and complete.

Audit trail

Every action is recorded, including the actions an agent took rather than a person. That distinction matters more in a platform where software can publish, spend and message on your behalf — and it is the question that actually gets asked in a review.

Consent enforced in the mechanism

A global unsubscribe blocks everything. Email, SMS and WhatsApp each require their own opt-in, checked at the point of sending. Skips are reported honestly as consent skipped rather than silently dropped, and the models return “wait” instead of recommending contact with someone who has not opted in.

Visitor consent

A consent platform, not a cookie banner bolt-on

Built into the tracking library rather than bought separately, and themed to match your brand.

  • Categories for necessary, analytics, session recording and heatmaps, and marketing
  • Configurable default state and required flag per category
  • Enforcement mode and consent expiry
  • Support for the browser's Global Privacy Control signal
  • Versioning with a policy hash, and an action that requires visitors to re-consent when the policy changes
  • Storage strategy options, a floating privacy control, and a live preview
What is collected

What the tracking library sees, and why

Only what you switch on. Action tracking, heatmap tracking and session recording are three independent toggles.

  • Semantic events Around 40 meaningful action types across nine groups, each with a state such as selected, submitted, succeeded or failed. Used for funnels, conversion measurement and segment conditions.
  • Attribution parameters Source, affiliate and referral parameters carried from the click. Used to attribute conversions back to the campaign that produced them.
  • A persistent visitor identity An anonymous browser identity that can be linked to a known user once they sign in. This is what lets an anonymous session become part of a real contact's history.
  • Session recordings Replayable sessions with input masking, so what people type into fields is not captured. Used to diagnose where visitors get stuck.
Ownership and exit

What is yours, and what you can take with you

  • Your ad accounts, social accounts and website remain yours — Nommos connects to them rather than owning them
  • Contact data can be exported
  • Content and media you upload remain yours
  • Historical performance data that exists only inside Nommos is worth discussing before you commit — we would rather raise it than let you discover it later

What we do not claim

Nommos does not currently hold ISO 27001 or SOC 2 certification, and we would rather state that plainly than imply otherwise on a badge. If your procurement process requires either, tell us early so we can be straight with you about timelines rather than about status.

Questions we answer directly

Data hosting location and regional options, retention and deletion policy including session recordings, and whether customer data is used to train models — these depend on your contract and deployment, so we answer them in writing during procurement rather than generalising on a marketing page.

Send us your security questionnaire

We would rather answer the specific questions your process asks than publish a page of reassurance.