Skip to content

PRIVACY.md

Latest commit

 

History

History
37 lines (25 loc) · 1.41 KB

PRIVACY.md

File metadata and controls

37 lines (25 loc) · 1.41 KB

Privacy and Accuracy

Who Read Me is a power-user analytics tool. The owner is responsible for lawful and ethical use in their jurisdiction.

Data Collected

Tracking events may include:

  • Message ID and recipient ID.
  • Event type.
  • Timestamp.
  • User agent.
  • Referrer when available.
  • Coarse location metadata provided by Cloudflare.
  • Bot or scanner hints.

The extension should not upload full received email bodies for tracker detection. Local deterministic rules run first.

Owner emails, sender emails, recipient emails, Cloudflare account identifiers, and local machine paths must not be committed to the repository. Keep deployment-specific identity data in Cloudflare configuration, Worker secrets, D1, or local ignored files.

Accuracy Limits

Open tracking does not prove that a human read an email. Common distortions include:

  • Gmail image proxying.
  • Apple Mail Privacy Protection.
  • Corporate mail scanners.
  • Security bots and link prefetchers.
  • Remote image blocking.
  • Forwarded emails.
  • Individualized tracked sends, which may create one Gmail sent message per recipient.

Dashboard labels should use careful language such as "open event" and "likely read" where appropriate.

Retention

Retention is configurable in dashboard settings. The current implementation stores the configured value and uses it as product policy; a scheduled retention Workflow should delete older rows in a later deployment pass.