eDOC Mail Worker
Privacy policy
What the personal automation processes, why it needs access, and what remains under the owner’s control.
Last updated:
01 Who operates eDOC Mail Worker
eDOC Mail Worker is a personal email and document automation operated by its owner, for their own Google account. It is not a service offered to other account holders. This public website provides information about the automation and has no signup, document upload or Google authorization form.
For questions about this policy or a data deletion request, use the owner’s contact details below.
02 Google account access and its purpose
Access is granted through Google authorization. The automation uses these permissions for the following purposes:
The workflow does not delete source email, change inbox labels or make app-created files publicly accessible.
03 Information processed
The automation may process sender and recipient details, subject lines, receipt dates, message identifiers, relevant email text, attached eDOC packages and the documents they contain. It recursively extracts nested packages and uses document content to prepare a brief. Receipt dates are used in filenames.
Delivery preserves the original outer eDOC and extracted underlying documents. Processing records may include document text, generated briefs, document hashes, delivery status, error information and usage records needed to prevent duplicate work and reconcile delivery.
04 Service providers and AI processing
Google provides Gmail, Drive and the services used to run and store the automation. Relevant document content or excerpts, together with supporting email context, may be sent to the OpenAI API to generate or check a brief. This processing can include personal information contained in those documents or messages.
The automation requests that API responses are not stored as response objects (store: false). This is not a zero-retention guarantee. OpenAI states that API data is not used for model training unless the customer opts in, and that abuse-monitoring logs may ordinarily be retained for up to 30 days, with exceptions such as legal or safety requirements. Other service-specific retention can apply. See OpenAI’s API data controls.
eDOC Mail Worker does not sell Google account data, use it for advertising, or use it to train general-purpose AI models. It does not publish document content on this website. Google and OpenAI process information as service providers for the functions described here.
eDOC Mail Worker’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
05 Storage and retention
Source messages and delivered briefs remain in the owner’s Gmail account until the owner deletes them. Private Drive files, extracted content, cached briefs and operational records can remain in the automation’s private storage until the owner cleans them up; there is no automatic deletion deadline promised for these records.
Google, OpenAI and the website hosting provider may retain operational, security or backup records under their own policies. Revoking account access does not automatically delete data already processed or retained by those services.
06 Revocation and deletion
The owner can revoke the automation’s Google access through Google Account connections. Revocation stops future access under that authorization. It does not remove previously sent emails, existing Drive files or stored processing records. If more than one Google authorization is in use for the workflow, each relevant authorization must be revoked to stop all routes.
The owner can remove messages and app-created files through their Google account and clean up the automation’s stored records. Anyone with a question about information relating to them, or a request to delete it from this automation, can contact the owner. The owner will review the request and any relevant identity, retention or legal requirements.
07 Access and security
The automation uses Google authorization instead of collecting a mailbox password. Credentials and processing records are kept in private app storage. App-created Drive files are restricted to the owner, and the application’s delivery destination is fixed to the owner’s email address. This public website contains no mailbox content or application credentials.
08 Visiting this website
The website’s code uses no cookies, analytics, advertising trackers, external fonts or embedded third-party content. It does not collect information through forms. The hosting provider may process IP addresses, request times and other technical request information to deliver and protect the site.
Links to Google or OpenAI take you to services governed by their own privacy practices.
09 Policy changes
This page will be updated when the described processing changes. The date above identifies the latest version.
10 Contact the owner
For project questions, privacy enquiries or deletion requests, use this forwarding address:
pelt-suds-freckled at duck.com
To send an email, replace “ at ” with @ and remove the spaces.