Privacy, cost, and other questions

Does my computer need to stay on?

No. After installation and activation, the trigger runs on Google Apps Script. Your computer is needed for CLI management, not scheduled classification.

Does email leave Google?

Yes. The worker sends sender, subject, a bounded body snippet, recipient and direction context, and sometimes a short previous-message snippet to TypeSafe for classification. This is not an on-device model.

Where are credentials stored?

The CLI keeps Google credentials and tokens in a private local installation directory. The TypeSafe key is stored in your GAS Script Properties. Processing receipts also live in your script project.

What does it cost?

Jev-Mail is MIT-licensed open-source software. TypeSafe API usage is billed according to your plan, and Google Apps Script usage is subject to your account quotas. There is no Jev-Mail subscription.

Which AI providers can I use with Jev-Mail?

Jev-Mail supports TypeSafe directly, OpenRouter (~typesafe/jev-latest), Cloudflare Workers AI / AI Gateway, and Vercel AI Gateway. You can also specify any custom OpenAI-compatible decision proxy in your jev-mail.yaml.

Is classification always correct?

No. Review provides a fallback, and label-only mode lets you inspect behavior before enabling archiving. Live Google and Jev integration has been tested, but the small development fixture set is not a general accuracy benchmark.

Can it remember my corrections?

Not in the current version. Personal memory and automatic learning from manual label changes are not implemented. You can change classification rules through the CLI or YAML.

Do I need my own Google project?

Yes. The current installation uses your own Cloud project and Desktop OAuth client. The setup skill helps an agent guide the process; it does not remove Google's consent requirements.

Where can I ask for help?

Open a GitHub issue. Include the error code and relevant configuration details, but remove credentials and personal email content.