Account and workspace data
Identity and setup details.
We store account names, email addresses, password hashes, and an optional GitHub account identifier for GitHub sign-in. Workspaces, sequences, steps, client names, client website or logo URLs, and endpoint names are stored so the shared deployment map can be displayed.
Deployment data
Status, timestamps, and failure details.
We store deployment and step statuses, start and terminal timestamps, durations, and a failure message when one is supplied. Private webhook credentials are used to receive these updates and should be treated as secrets.
Billing
Stripe processes payment details.
DeployState stores Stripe customer and subscription identifiers, subscription status, selected prices, and limited payment metadata such as payment type and last four digits. Card details are handled by Stripe, not entered into DeployState.
Attribution and retention
First-touch attribution stays deliberately small.
We store the first UTM source, medium, campaign, and content values seen in a browser session, along with the landing path, referrer host, and first-seen time when that session creates its first workspace. We do not store full referrer URLs or arbitrary query-string contents. The application has no automated deletion schedule or self-service account deletion tool. If you need to request deletion or have a privacy question, contact support.
Support
Request help through the project support channel.
Use the support page to open a support request. Do not include webhook URLs, private keys, or other credentials in a support request.
Open support options