DBL / EDITORIAL PROTOCOL

Every arrow needs an evidence label.

What we use

We read public EroLove AI Privacy, Terms, About and Pricing documents, then distinguish statements the documents actually make from consequences a reader might infer. For general privacy and security context, we use official regulator or security-project guidance. A current document review is enough for a useful guide; a hands-on claim needs genuine observed evidence.

What we do not claim

A policy does not prove actual encryption implementation, processor behavior, deletion completion or legal compliance. We do not invent vulnerabilities, breaches, account tests, legal violations or responses to requests we have not sent. A broad or ambiguous clause can justify a question, not a verdict of misconduct.

Release control

Five initial notes are reviewed against the 5 November 2026 documents. Five more are approved for roughly weekly publication after the formal domain launch is verified and its schedule anchored. Until each date, the article path returns 404 with noindex and no-store, and is omitted from Blog, RSS, sitemap and llms.txt. Changeable primary-source claims should be checked again near release and corrected if they have changed.

Corrections

Material errors should be corrected with an honest updated date and explanation. The initial review was documentary and did not require an account login or invented first-person observations.