Security · Autessa Visibility
Security, data handling and permissions
Autessa Visibility stores your provider keys as sealed Secrets that nobody can read back, sends engines only the prompts you track, runs browser workflows that never log in, pay or post, and logs every run with the task sent and the raw reply. Compliance documentation is in the Autessa Trust Center.
Data handling
What Visibility stores, and how
| Data | How it is handled |
|---|---|
| Brands, prompts, workflows, events | Stored in your Autessa company’s workspace. Deleting a brand removes its prompts, check history and timeline events after a clear confirmation. |
| Check results | The answer text, cited URLs, organic results, notes, sentiment and who paid, per run. Deleted prompts and workflows keep their past runs, labeled as deleted. |
| Provider keys | Sealed Secrets: write-only, never shown again, never given to the AI, sent only to the provider. |
| What is sent to engines | Only the prompt text you track. Prompts should be unbranded questions, not customer data. |
| Browser workflows | Run in a server-side browser, follow only your steps, never enter passwords, pay or post. |
| AI features | Sentiment scoring, setup from your website, themes, briefings and the Advisor run as Autessa AI tasks, with numbers computed by the app first. |
Permissions
Who can do what?
| Role | Can |
|---|---|
| Your team (people the app is shared with) | Use every screen: brands, prompts, checks, workflows, alerts, briefings, the Advisor and API keys. |
| Company admin | Decide who the app is shared with, and manage the company’s Secrets, billing and usage limits. |
Access is managed through Autessa sharing, the same way as every other app in your workspace.
Audit
Every run has a receipt
The run log keeps every check and workflow, scheduled or on demand, with who requested it, when, the engine, who paid, the task sent to the agent and its raw reply.
Autessa Trust Center
Policies, security documentation and compliance reports for the Autessa platform.
FAQ
Security questions
How are my provider API keys stored?
As sealed Autessa Secrets. A key is checked with the provider, then stored so that nobody can read it back; the AI never sees it, and it is only ever sent to the provider it belongs to.
Does the browser agent log in to sites?
No. Workflows never enter passwords, pay or post on your behalf, and sites that block automated browsers are reported as Blocked rather than bypassed.
Who can see our results?
The people you share the app with in your Autessa company. Everyone it is shared with sees the same brands, prompts and results.
Where can I find Autessa’s compliance documents?
At the Autessa Trust Center, trust.autessa.com.
100% customizable, code and all
Make Autessa Visibility 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