Security, privacy and permissions
How Autessa Analytics keeps your analytics data safe
Autessa Analytics never puts an analytics key in the browser: every PostHog read runs through a server-side Autessa script tool with bound values, access follows Autessa sharing, campaign edits run as the person making them, and app replays mask all text and inputs.
Controls
What is protected, and how?
| Area | How it works |
|---|---|
| PostHog key | Held only in a server-side Autessa script tool. The dashboard never contains a PostHog key, and the browser never receives one. |
| Query safety | Every value that comes from the page or the link (dates, sources, searches, ids) is bound through a named placeholder, never pasted into the query text. |
| Who can open it | Autessa Analytics is an Autessa app. Only people it is shared with can open it, and they also need access to the PostHog query tool. |
| Read or edit | Campaign, post and survey data are Autessa tables. Reads and writes run as the person using the app, so read-only teammates can see campaigns but not change them. |
| Session replays | Recordings of the signed-in app mask all text and inputs. Recordings open in your PostHog project, under your PostHog permissions. |
| Link scanners | Email security scanner visits are left out of reports, not deleted; raw events stay in PostHog. |
| Deleting campaigns | Posts are deleted before their campaign, so a failure never leaves orphaned posts. Tracked visits stay in PostHog. |
| Errors | Failed queries show a plain message with a retry, never partial or stale numbers from another range. |
Where the data lives
Events stay in your PostHog project
Autessa Analytics reads events, people and recordings from PostHog; it does not copy them into another store. What your site and app collect, and how consent is handled, is set where they send events to PostHog.
What Autessa stores
Campaigns, posts and survey answers
These are Autessa tables, governed by the same sharing and permissions as the rest of your Autessa account.
Trust Center
Security documentation for Autessa
Autessa’s security program, policies and reports are published in the Autessa Trust Center.
FAQ
Security questions
Is my PostHog key safe in Autessa Analytics?
Yes. The key lives in a server-side Autessa script tool. The dashboard sends only the query and its values, and never holds the key.
Who can see the analytics?
Only people the app and its query tool are shared with. Sharing can be read-only, so teammates can view reports without changing campaigns.
Is personal information shown?
Identified people appear by name and email, as recorded in your PostHog project. App session recordings mask all text and inputs.
Where can I read about Autessa’s security program?
See the Autessa Trust Center at trust.autessa.com for security documentation and reports.
100% customizable, code and all
Make Autessa Analytics fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours