Robin Ads Automation Privacy Policy
Effective 14 October 2026.
Robin Ads operates Robin Ads Automation. Contact robin0070101@gmail.com for privacy questions or requests concerning the tool.
Data accessed and purposes
The OAuth setup reads your verified Google account email and account identifier to confirm the authorized identity. It obtains a Google Ads authorization grant and stores the credentials needed to refresh access. The current simulation deployment does not request Google Ads account inventory or perform Ads mutations.
When explicitly configured and permitted by Google's API access level, the planned Ads integration reads authorized account, campaign, ad group, ad, keyword, asset, bidding, and policy-status information to implement the account owner's Sheet-based instructions. Production integration is not currently active. These disclosures must be reviewed before activating additional data uses.
Configuration and operational outputs are stored in private Google Sheets. Google Cloud hosts the automation, credentials, logs, and checkpoint data. Operational logs and checkpoints record execution status and recovery information; credentials are not intentionally written to logs or public pages.
Storage and access
OAuth credentials are stored in Google Cloud Secret Manager. A restricted credential-check identity accesses the named credential secrets. The simulation runner has no permission to read those secrets. Google Cloud and Google Workspace process information to provide the hosting and storage services. Access to the private configuration and output workbooks is restricted to authorized identities.
Sharing and other uses
The tool's current implementation does not sell Google user data, use it for advertising targeting, or send it to an AI model. It uses Google services for authentication, hosting, and storage. Any change to these practices requires updated disclosures before activation.
Retention, revocation, and deletion
Credentials are retained while needed for the authorized integration. You can revoke authorization in your Google Account connections and contact the operator to request removal of stored credentials and associated configuration or operational data. Revocation does not automatically remove copies already stored in Sheets, checkpoints, or Cloud logs. Deletion and retention controls must be agreed with the operator; the service does not promise a fixed retention period or an automated deletion feature that has not been implemented.
Limited Use
Robin Ads Automation's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.