Privacy Policy

Information we access

Google identity

Your verified Google email address is used for sign-in, access control, and identification of connected Google accounts.

Google Sheets

The application processes spreadsheet titles, identifiers, tab names, and cell values needed to select, create, read, and update project spreadsheets.

Google Drive metadata

When an administrator searches for a spreadsheet, Google Drive may return the file ID, name, modification time, web link, and each owner's display name and email address. Ads Automation limits discovery to Google Sheets files and does not search other Drive file types.

Google Ads

The application processes accessible customer account identifiers, names, and status, plus selected reporting fields such as dates, campaigns, ad groups, keywords, conversion actions, costs, impressions, clicks, and conversion metrics.

The Google Ads connection is used for reporting only. Ads Automation does not create or change campaigns, ads, bids, or budgets.

Meta Ads

Where an administrator connects Meta, the application processes authorized Meta account metadata and selected advertising reports for the same spreadsheet reporting purpose.

How we use information

Information is used to authenticate administrators, connect project spreadsheets, discover accessible advertising accounts, run scheduled or administrator-requested synchronizations, write reports, display dashboards, and record job status or diagnostic information.

Storage and security

Report rows are processed by the application server and written to the selected Google Sheet. The local application database stores operational information such as authorized email addresses, project and spreadsheet identifiers, account mappings, schedules, connection metadata, and job history.

Google refresh tokens are encrypted using AES-256-GCM. Short-lived Google access tokens are requested as needed and are not stored in the application database. Other controls include HTTPS, signed expiring sessions, HTTP-only cookies, OAuth state validation, same-origin checks, CSRF protection, and sign-in throttling.

Sharing

Ads Automation does not sell Google user data or use it for advertising. Information is disclosed only as needed to operate the service:

• With Google APIs to authenticate, retrieve reports, and read or update selected spreadsheets.
• With Meta APIs when an administrator enables Meta reporting.
• With authorized administrators and people who already have access to a selected Google Sheet.
• With LINE, only when the deployment enables failure alerts, to deliver the project and account name, refresh type and requested date range, attempt count, job ID, failure time, and a categorized error.
• When required to comply with applicable law or protect the security of the service.

Retention and deletion

Operational records remain in the live application database until removed by an administrator. Deleting a project removes its local mappings, jobs, events, and health records, but it does not delete the associated Google Sheet, workspace-wide Google connection, or information already written to Google Sheets.

Backups follow the deployment operator's configured retention policy. To request removal of your authorized-user record, Google connection, or other locally stored information, use the support contact below.

Your choices

You may revoke Ads Automation's access from your Google Account's third-party connections page. Revocation stops future Google API access, but it does not automatically delete existing local records or information already written to a spreadsheet.

Contact

For privacy questions, access requests, or deletion requests, contact: