A plain-language reference for compliance officers evaluating Atlas Signalis, and for managers answering a question from an advisor’s firm.
Atlas Signalis records what an advisor did on a manager’s page — pages opened, videos watched, documents downloaded. It does not record who they are, where they are, or anything they type.
Every engagement event stores exactly these fields, and nothing else:
| Field | Example | Why it exists |
|---|---|---|
event_type | video_complete | What happened |
strategy | Small Cap Value | Which strategy it happened on |
advisor_token | an opaque id, e.g. t7Kq2 | Which personal link was used |
session | an opaque id | To count return visits |
path | /m/marrowstone | Which page |
manager_slug | marrowstone | Which manager owns the page |
| timestamp | — | When |
That last point is the one compliance teams care about most, so it is worth stating flatly: no data collected on a manager’s Atlas Signalis page is ever shared with, sold to, or transmitted to any advertising network, data broker, or third-party analytics provider. There is no such integration to disable, because there is none to begin with.
Atlas Signalis does not identify anyone. This distinction matters, so here is the mechanism in full:
Atlas Signalis never resolves an anonymous visitor into a person. It has no identity graph, no data-broker enrichment, and no way to learn who someone is. It only reports what happened on a link the manager sent to a person the manager already knew.
Nothing is hidden. On every personal link, the top of the page states plainly:
“[Firm] can see how you engage with this page — pages opened, videos watched, documents downloaded. Nothing you type is recorded, and Atlas Signalis does not sell or share it.”
With a link to this page, so the advisor can read exactly what that means.
Some advisors’ firms prohibit their activity being measured. A manager can mark any advisor do not track:
Atlas Signalis measures what an advisor did. It never predicts, infers, or scores intent. The Signalis Engagement Score™ is a sum of things that actually happened — a video finished, a fact sheet downloaded, a conversation requested. It is not a judgment about a person, and it is not a prediction that they will buy.
The manager decides who receives a link and why. They are the controller of that relationship. Atlas Signalis is a processor acting on their instructions, and does not use engagement data for its own purposes. A Data Processing Addendum is available at Atlas Signalis DPA, including the current sub-processor list.
Atlas Signalis is not a broker-dealer, investment adviser, or solicitor. Fees are flat and are never tied to sales, assets raised, or AUM.
The authoritative and current list is Annex C of the DPA.
Everything above produces a record, and the record is one screen and one file. A manager can export it and hand it to their compliance officer, or to anyone reviewing the firm, without asking Atlas Signalis for anything.
The activity log is written by the database, not by the application. A change made directly in the database is logged exactly like one made in the interface.
Software that logs its own actions is only logging what it chose to admit to.
One person. Not everyone with a login.
A manager’s Atlas Signalis page is a marketing document, so exactly one designated person at the firm can change it. Everyone else on the account — wholesalers, regional directors, anyone with a seat — gets the full Command Center: their own advisor links, their own book, and who to call next. They cannot touch the page.
Two things sit outside the editor’s reach entirely, because they are the two a compliance officer will not let a marketing person near:
This is the control that sits underneath the approval workflow. A reviewer never has to check whether marketing touched the legend, because they cannot have.
Atlas Signalis does not archive. Archiving is Smarsh’s and Global Relay’s business, and building a worse version of it would help nobody.
Instead, every message Atlas Signalis sends on a manager’s behalf is blind-copied to their own archive — the reviewer sets the ingest address. So the answer to “does it feed our archive?” is yes, and the answer to “does it create a gap in our records?” is no.
And there is only one such message. Managers send their outreach from their own inbox, so their existing archiving already captures it. Atlas Signalis does not sit in the middle of a communication it has no business being in the middle of.
A firm can require that every change to the page is approved before an advisor sees it. When that is switched on:
And we do not launder self-approval. If the person who edited the page is also the person who approved it — which is simply the truth at a small firm — the record says self-approved, and the page history prints it.
A one-person firm is allowed to be a one-person firm. It is not allowed to look like two.
Atlas Signalis does not draft, suggest, or tailor the messages a manager sends.
Copy that an SEC-registered adviser sends to people who allocate client money is that adviser’s communication, subject to their own supervision and review policy. It is not written by their software vendor, and it is never shaped by engagement data.
Atlas Signalis hosts your marketing, measures it, and can prove what it said. It does not write it.
Managers send links from their own inbox, so their existing archiving captures every message. Atlas Signalis creates no gap in their communications record.
A manager’s Atlas Signalis page is an advertisement. Under SEC Rule 204-2 an adviser must be able to produce a copy of every advertisement it circulated. So Atlas Signalis keeps one.
The question a compliance officer actually asks is not “do you keep history?” — anyone can claim that. It is “how would I know if someone quietly rewrote it?”
You would know, because the seals would stop matching — and you would find out by checking the maths yourself, not by asking us.
Version records are not subject to the 24-month engagement purge below. They are advertisement records and are kept accordingly.
Engagement events are deleted after 24 months. Not archived, not anonymised — deleted. The purge runs automatically inside the database, on a schedule, and does not depend on anyone remembering to do it.
Every purge writes an audit row: when it ran, the cutoff date, and how many events were removed. So the answer to “can you show me the retention policy actually ran?” is a table, not a promise.
A manager’s own records — the advisor’s name, their contact details, the manager’s private notes — are the manager’s, and Atlas Signalis keeps them for as long as the account is open. What expires at 24 months is the engagement history: the page views, video plays and downloads.
If an advisor, or their firm, asks for their data to be erased, the manager can do it themselves — immediately, without contacting Atlas Signalis. One button in the advisor’s brief removes:
It is permanent and it cannot be undone. Atlas Signalis writes an audit row proving the deletion happened — the manager, the date, and the number of events removed — but that row contains nothing that identifies the person. Only the opaque token, which no longer refers to anyone.
Which is the point: we can prove we deleted them without keeping them.
Atlas Signalis stores one item in an advisor’s browser: the link token, so the page still recognises their personal link if they return to it later. It expires. There are no advertising cookies and no cross-site tracking of any kind.
If an advisor’s compliance officer has a question about what this page describes, they can write to hunter@atlassignalis.com and get an answer from a person.
See also: Privacy Policy · Terms of Use · Data Processing Addendum · Disclosures.
This page describes how Atlas Signalis works today. If the behaviour changes, this page changes with it.