Storage, retention, and deletion
Stuff stores account details and the content needed for the product: files, versions, descriptions, metadata, comments, memberships, sharing settings, and agent-connection permissions. Operational services also process information needed to run and protect the service. See the Privacy policy.
Where data is processed
| Provider | Purpose |
|---|---|
| Supabase | Authentication and databases |
| Cloudflare | File storage |
| Railway | Hosting and processing |
| Resend | Email delivery |
Small text originals are stored in the database; other originals use private object storage. The product applies access checks to file reads regardless of storage location. Do not treat a storage implementation detail as a different sharing model.
Data travels over HTTPS. Stored data uses providers' storage protections. This is not a claim of end-to-end encryption, a particular data-residency commitment, or a compliance certification.
Versions and Trash
Replacing a file saves a new version; it does not erase the previous one. Restore creates another version so the change is visible in history. Keep your own backup of important material.
Trashed items are normally eligible for permanent cleanup after 30 days. Permanent deletion and an account-deletion request have different consequences from hiding a file in Trash. Some operational records and backup copies may remain for legal or security reasons and backup rotation. We do not promise that all backup copies disappear immediately; deleted backups are not used as active product data.
Delete data or your account
Follow the current deletion instructions. You can request deletion from the mobile app or email ash@elegancelabs.com from your Stuff account email. Use file links or names when requesting deletion of selected data. Do not attach sensitive documents or include sign-in codes.
Requests are reviewed manually to verify identity and resolve shared-space ownership. Account deletion covers the associated Stuff account and data, subject to the policy's exceptions; it does not delete separate accounts in other Elegance Labs products. Copies owned or retained by other people and connected assistants require separate handling.
Report a problem
For unexpected access or a potentially exposed credential, revoke the affected connection and contact support. Include the approximate time, the action, and relevant Stuff links. Do not send the credential itself. Report suspected vulnerabilities privately rather than placing details in a public space.
Content scanning and viewer isolation help reduce risk; they do not guarantee that every harmful file or instruction will be detected. Review what an agent is doing and use a narrowly scoped connection.