Liya Design Outreach Cloud

Privacy, plainly.

How the private outreach runner handles Gmail data when sending Liya Kharitonova’s approved website-design emails.

Effective 26 August 2026 Private Liya-only workflow

01 / Scope

What this covers.

This policy covers the Gmail data used by Liya Design Outreach Cloud, a private automation that sends only Liya Kharitonova’s pre-written, approved website-design outreach. It is currently used only with liyakharitonova@gmail.com.

It does not describe unrelated portfolio projects, case studies, or services shown elsewhere on this website.

02 / Gmail data

Only what the runner needs.

The app requests two Gmail permissions only:

  • Gmail read access to confirm the connected sender, check Sent mail for prior outreach, and identify documented opt-outs and delivery failures.
  • Gmail send access to deliver an approved outreach draft only after the sender and eligibility checks pass.

For those checks, the runner may process the connected account address, relevant Sent-message metadata and content, recent messages from a prospective recipient that clearly request no contact, and recent mailer-daemon or postmaster messages that report a bounce.

It does not access Gmail contacts, Google Drive, Google Calendar, or any other Google service.

03 / Use

A narrow job.

Gmail data is used only to prevent duplicate or unwanted outreach, record a delivery result, and send an eligible approved message from Liya’s exact Gmail address. The runner never automatically replies to inbound email.

Google API data is not sold, used for advertising, or shared with data brokers. The app’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

04 / Storage

The minimum operational record.

The runner executes in Liya’s private GitHub Actions repository. Gmail message content used for an opt-out or bounce check is processed for that check and is not written to the repository or workflow output.

To prevent repeat contact and delivery errors, the private operational record may retain a business name, recipient email address, eligibility or delivery status, source queue, date and time, and Gmail message ID for a successful send. OAuth credentials are stored only as private GitHub Actions secrets and are never committed to the repository.

05 / Control

You can stop it.

Liya can stop this automation by revoking Google authorization, removing its private workflow credentials, or disabling the scheduled runner. If the app’s Gmail access or purpose changes, this policy will be updated before that new use begins.

If you receive an outreach email and want no further contact or want the related operational record removed, email liyakharitonova@gmail.com. Requests are handled by Liya Kharitonova.