1. About this policy
This policy describes the privately provided Photo Automation Mac application, its Google account connections, its administration service and this information website. The provider is Gray. Contact graycreative@gray-creatives.com with privacy questions or requests.
2. What Google data is accessed
You authorize access directly with Google. A Gmail source requests gmail.readonly and drive.readonly; a Drive source requests drive.readonly. These permissions allow broad read access to the authorized account’s Gmail or Drive data. Selecting a mailbox or folder guides the app’s workflow; it does not narrow the Google permission itself.
- Gmail: the app reads the account email address, lists messages in the configured mailbox or label, retrieves complete message content, and parses attachments and eligible Drive attachment links. Processing can include message headers, sender, date, message identifiers, body content, attachment names and attachment bytes.
- Drive: the app reads the account email address, browses folders, reads folder and file identifiers, names, types, sizes and available checksums, and downloads supported file content from monitored folders and subfolders or eligible Gmail-linked Drive attachments. Some Google-native document types are not downloaded by this workflow.
This access supports the download automation you request, source identification, duplicate tracking, recovery, integrity checks and troubleshooting. The Google connection does not request permission to send email or change or delete Gmail messages or Drive files.
3. What stays on your Mac
Downloaded file contents and partial downloads are saved to local storage for the selected destination and recovery process. The app keeps a local database with source settings, account identities, mailbox and folder identifiers, sender/date metadata where applicable, filenames, job and download records, local destinations, checksums and activity history. Message bodies are processed to find attachments and links; the app does not implement a separate persistent archive of complete emails.
Google OAuth credential records, including access and refresh tokens and associated authorization information, are stored in macOS Keychain. The app can refresh access with Google while authorization remains valid. Its license credential and provider setup profile also use Keychain. For separately configured legacy connections, source credentials use the same secure store.
The download files and local database are not themselves stored in Keychain or encrypted by this app. Their protection depends on your Mac’s account permissions, disk protection and backups.
4. What reaches the provider’s server
When the provider connection and license are configured, the app automatically sends administration and operational reports over HTTPS. These can include:
- Device identifier and display name, operating system and version, processor architecture, application version, license validation and last-seen information.
- Source identifiers, source display names, connected account email addresses, source type and active, disabled, removed or disconnected state.
- Download totals, event and check times, successful-check and download times, retry timing, failure counts, automation and updater status, available disk space and storage-writability status.
- Structured diagnostics: error codes and categories, operation stage, limited technical status fields, and failure history. A failure record can include a filtered filename, source name and account address, occurrence count and resolution state. Filtering is not anonymization.
The server stores this information and makes it available in the provider’s Admin interface for license administration, monitoring and support. Source and diagnostic history may remain after a source is removed. Normal activity reporting sends counts and status rather than the full local activity database; failure reports can identify individual filenames.
The reviewed reporting paths do not upload Google access or refresh tokens, complete message bodies, downloaded file contents, or the local database. Routine technical diagnostics exclude raw provider responses and exception text. User-entered source and device labels can contain personal information; avoid putting secrets in them.
The server also uses an IP-derived hash for request rate limiting. Hosting and update-delivery services receive network requests; infrastructure logging and backup practices are described below.
6. Retention, disconnection and deletion
Downloaded files remain on your Mac until you delete them. Removing an email source or disconnecting a Drive source stops its monitoring and attempts to delete that source’s Keychain credentials. If credential cleanup fails, the app reports the problem and asks you to retry. Removal does not erase downloaded files, partial downloads, local history or server records.
You may also remove Photo Automation’s access from your Google Account connections. Local disconnection does not itself revoke the Google grant. Revocation stops future authorized access but does not delete information already stored.
The local activity list is limited to the most recent 10,000 entries. Local technical logs rotate by size. Other local source, job and diagnostic records have no general automatic expiry established in this build. The server includes an operator-run cleanup for selected operational records older than 90 days; this is not a blanket retention limit or proof that cleanup runs. Source metadata, failure diagnostics and other records are not all covered by that cleanup.
Server and Admin operational records may be retained while they are reasonably needed to operate, support and troubleshoot Photo Automation. There is no blanket automatic deletion period for all server records. If a user requests deletion, Gray will manually delete the relevant client, device and diagnostic information where reasonably possible, subject to information that must be retained for legitimate operational, security or backup purposes.
To request deletion of server or support data, contact graycreative@gray-creatives.com and identify the account or device concerned. Do not send passwords or tokens. Ask support for assistance with local app data. Copies in your own folders and backups need to be handled separately.
7. Website and policy changes
These static pages contain no analytics scripts, advertising trackers, forms or application cookies. The hosting provider may keep access and security logs. Opening an email link uses your mail application; visiting an external link is subject to that service’s practices.
The provider will keep this policy aligned with the service and notify affected users before introducing a new use of Google data, obtaining consent where required. The effective date above identifies the applicable version.