Privacy Policy

Who and what this covers

Workflow Ownership is a validation-stage technology service. Avery is its disclosed AI General Manager app. Avery is currently limited to the company-owned mailbox specifically authorized through Google's OAuth consent process. The public website does not accept account credentials, payments, or confidential customer records.

Google data Avery accesses

When activated by the mailbox owner, Avery may access Gmail history identifiers, message and thread identifiers, sender and recipient headers, subject, date, the newest text message, attachment presence, and a bounded summary of the same thread. Attachment contents are not sent to the AI model and require human review.

How Google data is used

The data is used only to detect a new company email, verify that it belongs to an authorized conversation, understand the sender's request, preserve the correct Gmail thread, generate a relevant response, create a review draft, send a narrowly authorized reply, prevent duplicate actions, and maintain compact operational state.

AI processing and sharing

For a candidate response, Avery sends OpenAI only the newest bounded text message, sender, subject, compact thread summary, and verified company facts needed to prepare the reply. Requests use the OpenAI API with storage disabled. OpenAI processes that data as a service provider under its applicable API data controls. Avery does not send attachments to the model.

Google user data is not sold, used for advertising, used to determine creditworthiness, or shared with unrelated third parties. It is disclosed only when required by law or necessary to protect the service, its users, or the public.

Storage and retention

Raw Gmail message bodies are processed transiently and are not written to the durable company learning record. The runtime retains only compact per-thread summaries, Gmail history cursors, idempotency identifiers, response counts, and outcome codes and dates needed to operate safely and avoid duplicate replies. Production activation requires a persistent store and a documented deletion route; until those are deployed and separately approved, live processing remains disabled.

Security and control

OAuth credentials are stored outside source control. Access is limited to the single approved mailbox and the minimum configured Gmail scope. Deterministic gates block unknown threads, attachments, protected topics, prompt-injection indicators, low-confidence decisions, and a fourth autonomous reply. The mailbox owner can stop access by revoking Avery's Google OAuth grant; disabling Gmail watch and the push service stops event processing without deleting existing email.

Your choices

The authorized mailbox owner may request access, correction, or deletion of Avery's retained operational state, or may revoke Google access at any time. Send requests to vaughn.workflowaudit@gmail.com.

Google API Services User Data Policy

Avery's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Changes

This policy will be updated before Avery's data use, service providers, retention practices, or audience materially changes. The effective date at the top identifies the current version.