outerlayer sync uploads, see What leaves your machine.
Where events go
Events go to PostHog in the United States. PostHog is a subprocessor. The Privacy Policy on outerlayer.ai lists it. Events come from two places:- The dashboard in your browser. It starts PostHog only after you sign in.
- OuterLayer servers. They send three events when an organization reaches a setup milestone.
How PostHog identifies you
PostHog knows a person by user id. It never receives your email or name. Dashboard sessions are never recorded. Session recording is off in code, so a PostHog project setting cannot turn it on. PostHog also groups events by organization. The group has the organization id and the organization name.Events from the dashboard
The properties have these values:
page_pathis the path with each dynamic segment replaced by its name, such as/orgs/[orgName]/factories. The organization and factory names are not sent.tenant_idis the organization id.stepis one ofapp,repo,traceorteammate.doneandtotalare the number of finished steps and the number of steps.surfaceissetup-panelorbanner.providerisgithub.whatissetuporagent-prompt. The copied text is not sent.
$current_url, $pathname and $referrer. Those values contain organization and factory names. The only page location an event carries is page_path on $pageview.
Events from OuterLayer servers
app_id is the factory id. The first two events belong to the person who acted, by user id. org_api_key_created belongs to the organization, not to a person.
What is never sent
- Your email address or name.
- Session content, such as prompts, transcripts, tool output, code and file paths.
- API keys and other secrets.
- Text you type, and the text of anything you copy.
- Organization or factory names in page views.
Browser storage
PostHog keeps its state in memory for the page you are on. It writes no cookie and no local storage, so the dashboard shows no consent banner for analytics. The dashboard stores these items in your browser:- Sign-in cookies, which you need to stay signed in.
- Your color theme, in local storage.
- Two local storage keys per factory for the getting-started checklist:
agentmark:onboarding-checklist-dismissed:<factory id>andagentmark:onboarding-checklist-collapsed:<factory id>. - A short-lived session storage entry that stops the dashboard from reloading in a loop after a new version ships.