How Eprox handles data

This page explains the data used to provide Eprox Email Agent. It matches the product behavior in the repo: email brief and triage, upcoming event reminders, reply suggestions, user-approved sending, and Gmail access only after permission.

Public access

Available without login

Reviewers can inspect the policy before connecting a mailbox.

User control

User-reviewed actions

Drafts and reminders are suggested for review; sends require approval.

Support

arthuryuziyi@gmail.com

Information we collect

Account data such as your app user ID, sign-in method, and session metadata.
Connected mailbox data such as provider account ID, account email, token metadata, and mailbox sync state.
Email data used by the product, including sender, subject, snippets, timestamps, thread references, event context, and assistant-generated analysis used for triage, reminders, or drafting.
User settings and preferences related to mail behavior, event reminders, AI settings, and sandbox decisions.

How we use information

To sign you in and keep your session active.
To connect a Gmail mailbox only after user permission.
To generate email briefs, upcoming event reminders, draft suggestions, and other user-reviewed actions.
To operate, secure, and improve the service.

Storage and security

Sensitive token material is encrypted at rest.
Operational logs and cached processing data may be retained as needed for reliability and troubleshooting.
The product does not claim zero retention; it retains data needed to run the service and support account deletion.

Your choices

You can choose whether to connect a mailbox, review upcoming event reminders, and approve any suggested send action.
You can request account deletion through the app when that flow is available.
If you contact support, we may use your message to resolve the issue and improve the service.

Contact

Questions about privacy or data handling can be sent to arthuryuziyi@gmail.com.