Voreliqo Agent Privacy Policy

Effective date: October 5, 2026

This policy explains how Voreliqo Agent, the internal operations tool of the Voreliqo online store (voreliqo.com), uses data it receives from Google APIs. The tool is used only by the store owner for the store's own Gmail mailbox. More about the tool: Voreliqo Agent.

1. Google data we access

Permission (scope): https://www.googleapis.com/auth/gmail.readonly only.
Mailbox: only the store's own email address. The sign-in is rejected and nothing is saved if a different account is used.
What is read: the list of inbox messages from the last few days (up to 50 per check), and for each message its metadata: sender, subject, reply-to, message ID, mailing-list and automatic-mail headers, and the short preview text (snippet) that Gmail provides. Messages from our supplier's domains (cjdropshipping.com / cjdropshipping.cn) from the last 60 days are read the same way.
Not read: full message bodies and attachments.

2. How we use it

To classify recent messages into categories and count them, so customer questions are not missed.
To prepare suggested replies from fixed templates for messages that are clearly from this store's customers. Replies are never sent by the tool; the owner reviews and sends them personally from Gmail.
To flag supplier messages that mention product images or permissions, so the owner can read them in Gmail.

We do not use Google user data for advertising, we do not sell it, and we do not use it to train artificial-intelligence or machine-learning models.

3. What is stored and where

Sign-in credential: the Google refresh token is stored in Windows Credential Manager on the store owner's computer and as an encrypted secret in the owner's private GitHub repository, which runs the tool's scheduled jobs. It is never written to code, logs or reports.
Processing: message metadata and snippets are processed in memory during each check.
Saved records (no message text, no addresses):
- Gmail thread IDs that already received a suggested reply (to avoid duplicates), in the owner's private GitHub repository;
- for supplier messages: message ID, date, sender domain, and whether the message mentions images, in the owner's private GitHub repository;
- counts per category, in run logs on the owner's computer and in the owner's private GitHub repository;
- suggested replies containing only the Gmail message ID, the category and the template text, on the owner's computer. Copies created during scheduled cloud jobs are discarded when the job ends.

4. Who can access it

Only the store owner, through their computer and their private GitHub repository.
Service providers that process data on the owner's behalf: Google (Gmail API), GitHub (private repository and scheduled jobs) and, when the owner operates the tool with the Claude Code assistant, Anthropic, which may process the saved records listed above during that session to provide the assistant's response.
No other person or company receives Google user data.

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

5. Retention and deletion

Saved records are kept until the store owner deletes them; they are not deleted automatically.
Access can be revoked at any time at myaccount.google.com/permissions; the tool then can no longer read the mailbox.
To delete data, the owner removes the saved records listed in section 3, deletes the GitHub secret and the Windows Credential Manager entry, and revokes access as above. Deletion requests can be sent to the contact address below.

6. Security

All requests to Google use HTTPS.
The code refuses any Gmail request other than the three read-only requests listed above.
Credentials are never printed in logs or reports.