Source: https://asterly.co/data-deletion

The boring bits

# Data deletion & contact

You can delete a hosted guide, but there is no verified self-service account deletion or full personal-data export. Email a request for help. The contact mailbox still needs to be confirmed before launch.

Last updated: 25 October 2026

Draft · not yet reviewed by a lawyer

On this page

1.  [Send a request](https://asterly.co/data-deletion#section-1)
2.  [What you can remove now](https://asterly.co/data-deletion#section-2)
3.  [What happens next](https://asterly.co/data-deletion#section-3)

## Send a request

Contact [hello@asterly.co](mailto:hello@asterly.co) with “Privacy request”, “Delete my data”, “Export my data” or “Security incident” in the subject. Include the account email, workspace or guide URL, the request and whether you are the account holder, a recorded person or an authorised agent. Never send a password, recorder token or a copy of sensitive records.

**Mailbox status:** hello@asterly.co is the published contact in code; Yash must confirm that it exists, receives external mail and is monitored. privacy@asterly.co is a proposed alias and is not verified as available. No form on this page stores a request and this preview does not itself complete deletion.

[Open a privacy request email](mailto:hello@asterly.co?subject=Privacy%20request)

## What you can remove now

The hosted guide editor offers guide deletion and unpublishing; the server deletes the guide record and attempts to delete associated screenshots. In the extension you can discard a capture draft and disconnect your account. Signing out ends the current session. Clearing extension/browser storage removes corresponding local data, but does not remove cloud copies. Account/workspace deletion and a complete export need operator help.

Markdown/PDF downloads cover a guide, not every account record. We have not verified an account-wide export, backup purge or a retry process for failed image deletion. Public downloads, search copies and caches may remain; published asset responses allow caching for up to a year.

## What happens next

The proposed procedure is to acknowledge the request, verify only the identity/authority needed, identify the relevant controller, locate the data and explain the action or any legal exception. Requests about a customer workspace may be forwarded to its controller for instructions. See [Privacy Policy](https://asterly.co/privacy) for applicable rights and response periods.

Proposed targets are deletion from active systems within 30 days of a verified request and backup expiry within 90 days. They are not automated or guaranteed yet. Provider retention and legal holds must be explained separately. We should give you a completion record and identify any copies we cannot control. If a grievance is unresolved, you may use the supervisory authority or other complaint route available under applicable law.

## All the boring bits

-   [Privacy Policy](https://asterly.co/privacy)
-   [Terms of Service](https://asterly.co/terms)
-   [Cookie Policy](https://asterly.co/cookies)
-   [AI Use & Data](https://asterly.co/ai-data)
-   [Subprocessors](https://asterly.co/subprocessors)
-   [Security](https://asterly.co/security)
-   [Acceptable Use](https://asterly.co/acceptable-use)
-   [Data deletion & contact](https://asterly.co/data-deletion)
-   [DPA template (draft)](https://asterly.co/dpa)