Data retention
What expires, what is retained, and how to request deletion
Different records serve different purposes. The limits below distinguish automatic expiry from operator-managed retention; cancelling a subscription, signing out, deleting a live record, and deleting a backup are different actions.
| Record | Current handling |
|---|---|
| Consumer workflow execution | The default active window is one hour. Configured active windows are bounded from 15 minutes to 24 hours. Encrypted workflow records default to deletion seven days after active expiry, with configured retention bounded to 30 days. |
| Saved projects, inputs, and artifacts | These support your requested workspace and its configured retention rules. They do not all share one universal automatic deletion deadline. Use the authenticated request process for records not covered by a direct deletion control. |
| Provider credentials and connections | Credentials remain encrypted for the authorized connection. Removing a connection does not itself cancel an external provider subscription or revoke that provider's key; revoke it with the provider if needed. |
| Broker execution and security evidence | Usage, cost, credential-version, and signed receipt records support billing, disputes, security, and audit integrity. The broker does not currently have a universal automatic age-based purge. Retention is managed for these purposes under the ASL Privacy Policy and any applicable organization agreement. |
| Accounts, organization membership, and billing | Records support account administration and payment obligations. Eligible account and connection records can be handled through the authenticated deletion workflow. Accounting and transaction records are retained for required tax, accounting, fraud, and dispute purposes; the shared ASL policy describes the payment-record schedule. |
| Logs and support tickets | The shared ASL Privacy Policy describes web-log and support-record handling. Do not put confidential task content or credentials into support messages unnecessarily. |
| Encrypted backups and deployment recovery | The routine local backup policy keeps one completed local snapshot per required component. Remote storage and separately retained deployment recovery copies are distinct. Deleting live data does not immediately erase every historical encrypted backup or third-party copy. |
Deletion, preservation, and restoration
Ask through the Privacy and AI Reporting Center or Support and keep the request reference. We verify identity and authority before deleting protected records. A legal hold, valid preservation requirement, documented dispute, security investigation, or applicable organization schedule may require restricted retention. Provider-held copies follow the selected provider's policy and contractual controls.
Backups protect recovery from loss. Any restoration must account for previously completed deletion requests; a restore receipt is not evidence that every requested record has already been erased. We do not promise immediate erasure of all backups or automatic whole-workspace deletion where that capability is not implemented.
Subscription cancellation is separate
Use Billing to manage the Stripe subscription and verify the displayed cancellation status. A privacy request alone does not cancel billing. Cancellation does not refund amounts already paid, except where required by applicable law. See Refunds and cancellation.
Access, correction, deletion, and AI-content reports
Use the AI Hub Privacy and AI Reporting Center, or Security in the native app, to submit an authenticated request and receive a status reference. Content reports are also available beside Studio results. Request details are encrypted; prompts and outputs are not attached automatically. A submitted or in-review receipt is not completed deletion, subscription cancellation, or completed moderation. If account access prevents a request, contact Support. Identity verification protects your information; rights, response timelines, and appeals follow the ASL Privacy Policy and applicable law.
Shared ASL policies and contact
This notice supplements the published ASL Privacy Policy and ASL Master Terms. Those documents describe ASL LLC, applicable rights, request procedures, and governing terms. Mandatory legal rights and an applicable organization agreement are not removed by this notice.
Contact ASL LLC, operating as Auto Secure Login, Colorado, United States, at contact@autosecurelogin.com or Auto Secure Login Support. Never include passwords, private keys, recovery codes, API keys, card numbers, or unnecessary personal content.