“Delete everything” has several clocks
EroLove AI’s Privacy Policy opens with an easy-to-read promise that a user can delete everything at any time. Later, its retention section gives the operational timing: after account deletion, personal data is deleted within 30 days except limited billing, tax, fraud-prevention or legal records; encrypted backups are deleted on a rolling basis within 30 days. The policy also describes selected generated images that may have been published without account linkage and remain public after a chat or account is deleted. Those are separate paths, not one instant erasure event.
This is not evidence that the provider has failed a deletion request. We have not created an account, asked for deletion or inspected storage. The criticism is about how quickly a broad headline can outrun the detail a user needs. If a person is leaving an intimate service, the practical question is not merely “Can I click delete?” It is “Which data class disappears from which system, on which schedule, with which stated exception?”
Map the policy’s timelines
| Data class | What the checked Privacy Policy says | Reader’s follow-up question |
|---|---|---|
| Active account and chat | Kept while the account is active. | Can a particular chat or memory be removed before closing the account? |
| Unsaved guest account | Deleted after a period of inactivity. | What is the precise inactivity period, and how is it counted? |
| Personal data after account deletion | Deleted within 30 days, subject to limited exceptions. | Will the provider confirm completion and identify exceptions? |
| Encrypted backups | Deleted on a rolling basis within 30 days. | Does the clock begin at backup creation or at the account request? |
| Billing, tax, fraud and legal records | Limited records may remain. | Which fields, legal basis and retention period apply? |
| Selected public character images | Published copies are not tied to the account and stay published after deletion. | Was any image from my chat selected, and is there a separate report route? |
The policy does not publish a technical deletion runbook. For example, it does not tell a user exactly when a particular backup snapshot expires or how deletion propagates to each AI processor. A reasonable request can ask for those details without assuming noncompliance. The published “within 30 days” is a maximum described in the policy, not a measured completion time from our desk.
Keep a clean exit record
Before deleting, export information you legitimately need through the in-app controls described in the Privacy Policy. Record the request date, account identifier, confirmation screen and any case reference. Avoid sending intimate content again in an email just to prove ownership unless the provider specifically requires a secure route. After the stated window, ask whether active data, backups and processor copies have been handled and what limited records remain. If the response is incomplete, frame the follow-up around the exact missing data class.
Do not confuse an export file with an erasure receipt. Export concerns access to a copy of data; deletion concerns the provider’s stored data and exceptions. Likewise, the absence of an image from an export does not tell you whether a selected character image was published, because the policy explicitly places that publication path outside the account export.
The honest conclusion
EroLove AI’s wording gives a route to deletion and a 30-day operational window. A user should plan around that window instead of assuming immediate disappearance, and should notice the backup, record-retention and public-image exceptions. We have no basis to say the provider exceeds its deadline. We do have enough basis to reject the simpler marketing inference that a delete click proves every copy has already gone.
Evidence boundary
Document titles checked 2026-11-05: EroLove Privacy Policy, updated 2026-10-23 and checked 2026-11-05. Vendor document names are given without a vendor link. Public policies describe intentions and obligations; they do not independently verify implementation or compliance.