Skip to main content
Autopilot connects the way an analytics tool does: read-only, nothing installed in your database, and disconnected in a minute. It keeps only what it needs to measure your funnel and run your campaigns.

Read-only

The Autopilot user can read tables and follow the change feed. It can’t write, delete, or alter anything.

Nothing installed

No triggers, tables, functions, or schemas are added to your database. Your app and your schema stay exactly as they are.

Encrypted in transit and at rest

SSL with certificate verification in transit. Credentials double encrypted and data encrypted at rest.

Yours to revoke

Remove the connection in your dashboard, then drop the database user. Nothing else to uninstall.

​
What Autopilot reads

During onboarding we agree on the tables that matter for your funnel: typically users or accounts, signups, the key actions that define activation in your product, and subscriptions or payments. Autopilot uses those tables, and only those, the same way an analytics platform syncs the tables you select. It reads them in two ways:
  • Once at setup, to learn the current state of your users. Large tables are read in small batches in the background.
  • Continuously afterwards, through your database’s built-in change feed, so your funnel and your campaigns reflect what users are doing right now.

​
What Autopilot keeps

  • An up-to-date copy of the fields it uses, maintained from the change feed. This is what lets Autopilot measure your funnel over time, evaluate workflow conditions, and render previews without repeatedly querying your database.
  • Delivery and engagement data for the emails it sends: deliveries, opens, clicks, and unsubscribes.
  • Your brand and site context, learned from your website URL.
All of it is stored encrypted, isolated to your organization, and used only to run Autopilot for you.

​
What Autopilot never does

  • Write to, delete from, or alter your tables
  • Install triggers, tables, functions, or schemas in your database
  • Change your application code or your schema
  • Run heavy or long-running queries against your database
  • Share your data with anyone else, or use it to train models

​
How this compares

​
Security and compliance

Autopilot runs on the same infrastructure and controls as the rest of Dreamlit: SSL/TLS-encrypted database connections, credentials double encrypted at rest, organization-level isolation, intrusion detection, and 24/7 monitoring. See Security for the full list, and our privacy policy for how data is handled.

​
Revoking access

Remove the connection in your Dreamlit dashboard first, or ask us to. Then drop the Autopilot user in your database:
There’s nothing else to uninstall. See Removing access for why the order matters.
Last validated: 2026-09-08