Plain language, no surprises.
Earl reads the email thread you're viewing in Gmail (subject, message text, sender, labels) only when you click the Earl draft button. It's sent to your own Earl backend solely to generate a reply draft. He reads; he does not delete.
Email content is sent only to the Earl backend operated by
your own organisation (the App URL you configure), which uses Google's Gemini API to produce the
draft. Drafts are written into your Gmail as normal drafts. Your settings (app URL + personal API
key) are stored locally in Chrome's storage.sync. No inbox content is stored by the
extension itself.
Drafts Earl writes follow a plain house style and are always reviewable before they leave your outbox.
Questions: heyearl.app@gmail.com