Workflow

  • Build in your AI toolKeep reports exactly as made
  • CollaborateTalk it over on the draft
  • Review and publishPush is not publish
  • ContextCarry on from a teammate

Delivery and control

  • Client portalDelivery under your brand
  • Team accessA connector per person
  • Data sourcesNative sources coming soon

Get started

  • How it works
  • Request a demo

Learn

  • DocsSet up and use SnowDots

Read

  • BlogNotes on client reporting
  • AboutWhy SnowDots exists

Latest post

  • 12 AgencyAnalytics alternatives in 2026, tested and compared

Get started

  • Request a demo
Request a demo

Product

  • Build in your AI tool
  • Collaborate
  • Review and publish
  • Context
  • Client portal
  • Team access
  • Data sources
  • How it works
  • Request a demo

Resources

  • Docs
  • Blog
  • About
  • Request a demo
Legal

Security

The controls that protect your data in SnowDots, and how to tell us about a problem.

Last updated 21 October 2026

This page describes the controls in SnowDots. We hold no security certification, such as SOC 2, and we do not claim one.

Access control

  • Each client is a hard boundary. Reports and their context records belong to one client, and access is granted per client or per space within it. A report that draws on several spaces opens only for people who can see all of them.
  • Connectors scoped per person. Each team member connects their AI tool through their own MCP connector, limited to the clients where they hold Contribute or higher. A person’s AI tool cannot reach another client’s work through SnowDots. An admin can revoke a connector at any time.
  • A permission ladder: View, Contribute, Approve, Admin. Client contacts stop at View, and a viewer has no connector access.
  • Access that ends by itself. Access can be given with an end date, for example for a consultant on a fixed term.
  • Ethical walls keep the teams on competing clients apart inside one agency.
  • Publishing is a separate step. A pushed report arrives as a draft only the team can see. Only an approver can publish it, and it can be taken off the portal or rolled back at any time.
  • Public links are off by default. A report opens without signing in only if someone turns its public link on, and turning it off stops the old address working.
  • Disabling a team member removes its grants, connector and sign-in at once. It can be undone for 30 days.

Data handling

  • SnowDots does not connect to your clients’ ad or analytics accounts and holds no logins or tokens for them, so it cannot read or change those accounts.
  • SnowDots stores the data your AI tool supplies. It does not check that data against the platform, so review reports before publishing.
  • Data is encrypted in transit. We encrypt stored data and access tokens at rest.
  • Each client’s timeline shows when team and contact access was given or removed.
  • We do not train AI models on your data.

Incidents

If we confirm an incident that affects your data, we will tell the affected agencies without undue delay and give them what they need to meet their own duties.

Report a vulnerability

If you find a security problem, email hello@snowdots.com with the subject “Security”. Please include enough detail to reproduce it and do not access data that is not yours. We will acknowledge your report and keep you updated. Our contact details are also published in security.txt.

Product

  • How it works
  • Build in your AI tool
  • Collaborate
  • Review and publish
  • Context
  • Client portal
  • Team access
  • Data sources
  • Request a demo

Legal

  • Privacy
  • Terms
  • Data deletion

Trust

  • Security
  • Subprocessors
  • Cookies

Company

  • About
  • Brand guidelines
  • Contact
  • hello@snowdots.com
© 2026 SnowDots. All rights reserved.TermsPrivacy

Cookies

SnowDots uses analytics cookies to see how people find and use this site. You can accept or decline them.