Privacy Policy

Last updated: 7 September 2026

This policy covers the self-hosted automation running at eshnetwork.space (“the Service”). The Service is operated by a single private individual for their own personal use. It has no customers, no public sign-ups, and no users other than its operator.

1. Google user data the Service accesses

With the operator's explicit OAuth consent, the Service uses the Gmail API to access the operator's own Google account. Specifically it may:

• read message headers and body text of incoming mail;
• apply, create and remove Gmail labels;
• move messages out of the inbox (archive).

The Service does not send email, does not delete messages, and does not access contacts, Drive, or any other Google product beyond the scopes granted.

2. Why it accesses that data

The sole purpose is to automatically sort the operator's own inbox — assigning a category label to each incoming message and archiving low-priority categories such as marketing mail. There is no other use.

3. How the data is handled and stored

• Processing happens on hardware physically owned by the operator. No copy of any message is stored in a hosted database or transmitted to any analytics service.
• Execution logs retained by the automation engine may briefly contain message subjects and senders. These are held locally and pruned automatically.
• OAuth tokens are stored encrypted on the operator's own server.

4. Third parties

To categorise a message, its subject and a truncated portion of its body are sent to a third-party large-language-model API (Groq) for classification. That provider processes the text to return a category label. No other third party receives Google user data from the Service.

Google user data is never sold, rented, published, or used for advertising, profiling, or model training by the operator.

5. Retention and deletion

The Service keeps no permanent archive of message content. Local execution history is discarded on a rolling basis. The operator may revoke the Service's access at any time at myaccount.google.com/permissions, which immediately and permanently ends all access; stored tokens are then invalid.

6. Limited Use disclosure

The Service's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

7. Changes

Any change to this policy will be published on this page with a revised date above.

8. Contact

Questions: eshan.k.iyer@gmail.com