Security at Ascend
Your company's data.
Clear boundaries.
Ascend connects to the services you choose. Here is what the app does with your access and the information it imports today.
Credentials and encryption
Stored provider credentials are encrypted with AES-256-GCM. The encryption key is a separate server secret, kept out of browser storage and public client configuration. The app binds encrypted credentials to their account and provider, and does not send them in workspace responses.
The deployed site uses HTTPS, with HTTP redirected to it. Connections to provider APIs use HTTPS as well.
Read access and write actions
Connections read data by default. Writing to a connected service is an explicit Pro action, such as editing a GitHub project or changing a connected billing plan. Destructive actions require confirmation before they are sent. Ascend records destructive actions in an audit log with the person, action, target, and time, without logging credentials.
Disconnecting and deletion
Disconnecting a source removes its saved credentials and imported history from the workspace immediately. Chat conversations and the destructive-action audit log remain. Disconnecting does not revoke access at the provider; use the provider's settings for that.
Automatic deletion of your credentials and data 30 days after cancellation is being built and is not live yet. Until then, disconnecting a source deletes its credentials and imported history immediately; email me@cfcosta.com to have your whole account deleted.
Internal access
Internal admin access is limited to account and service metadata, health, and Ascend's own billing information. It does not show customer credentials or imported business data. The admin audit records internal route paths and access outcomes. Destructive entries show the operation, account and workspace metadata, and broad target kinds, but no imported target names or details. Admins cannot impersonate a customer.
AI model providers
When you use chat, the selected model provider may receive the conversation, attachments, and tool results needed to answer. A gateway may also pass that context to its inference provider. The current recipient list and what each provider receives are published in the model provider list.
If you connect your own model key, Ascend stores it encrypted and uses it only for your requests. You can also use a model key configured by Ascend.
Report a vulnerability
If you find a security issue, email me@cfcosta.com. Include the affected area and steps to reproduce it if you can.