Privacy Policy

Data the application accesses

The application accesses only the Google data needed for its stated purpose:

• Google Drive source files and metadata, read-only;
• a private Google Sheets manifest, which the archive component creates and updates and the recipient component reads;
• Google Photos, to upload media and read or manage albums and media created by this application;
• Google Apps Script triggers and script-local operational state; and
• the account email address, for private operational notifications.

How the data is used

The archive component scans an owner-approved Google Drive folder tree, uploads supported media to an authorized archive account, and records selected app-created media in a private manifest. The recipient component uses that manifest as an allow-list, validates each corresponding source file, and uploads only current matching media to a second authorized Google Photos account.

File identifiers and modification timestamps are used to prevent duplicate processing and to detect source updates. The account email address is used only for private operational notifications.

People-based selection

An account owner may manually configure Google Photos to add selected people to an app-created album. Google Photos performs that grouping. This application does not perform facial recognition, store face templates, or send media to an external biometric service; it only reads the app-created album contents made available by Google Photos.

Storage and sharing

Processing runs within Google Apps Script and Google APIs. The application has no separate analytics, advertising, tracking, or third-party data service. Operational identifiers and timestamps are stored in private Apps Script properties. The owner-controlled private manifest contains source file identifiers, modification timestamps, paths, media types, app-created Google Photos identifiers, and detection timestamps. It is shared only with the second authorized account for the recipient sync. Data is not sold or shared with unrelated third parties.

The application's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Deletion and retention

The application is append-only: it does not delete Google Drive source files or existing Google Photos media. Account owners control the source files, uploaded photos, private manifest, script project, and retention of those items through their Google accounts.

Control and revocation

The account owner can stop the application's scheduled trigger and revoke its Google Account access at any time. Questions can be sent to the support address displayed on the application's Google OAuth consent screen.