Privacy Policy

Last updated: [CONFIRM: publication date]

DRAFT FOR OWNER REVIEW — remove this box before publishing. Every highlighted [CONFIRM: …] item states something that has not been verified. Replace each with the accurate statement (or delete the sentence), then remove the highlight. See docs/CONFIRM-BEFORE-PUBLISHING.md.

1. Who operates the integration

This website describes “LSA Integration – Dashboards” (the “Integration”), a private Google Local Services Ads integration built on the Zapier Platform and operated by Ariel, an independent consultant ([CONFIRM: legal name and business entity, if any; and whether you act as a data controller, a processor/service provider for client companies, or both]). The Integration is not a public product and is not available for public registration. This website does not collect Google login credentials and does not offer account sign-up.

2. Information accessed

When an authorized Google account grants access, the Integration can use supported Google Ads and Local Services Ads API operations under the OAuth scope https://www.googleapis.com/auth/adwords. Depending on what Google's API returns and what the authorizing account is permitted to see, the Integration may access:

Local Services Ads lead records, which may include customer contact details (such as name, phone number, or email address) and other personal information the customer provided or Google recorded about the lead;
lead metadata, such as lead type, creation time, category, and status;
advertiser account identifiers needed to address API requests; and
lead feedback (positive or negative) that the operator submits through the Integration.

The Integration only accesses data for Google accounts that have explicitly authorized it.

3. Purpose of access

Data is accessed solely to provide the four functions of the Integration: searching recent LSA leads, submitting positive lead feedback, submitting negative lead feedback, and retrieving the advertiser ID. These support lead management, feedback workflows, and operational reporting for the authorizing business. Data is not used for advertising, profiling, or sale.

4. Processing through Zapier

The Integration runs on Zapier. When a Zap uses it, Zapier makes requests to Google's APIs on behalf of the authorized account, and the responses (which may contain lead information) pass through Zapier's systems and into whichever Zap steps the operator has configured. Zapier processes this information under its own terms and privacy policy. [CONFIRM: where retrieved lead data goes after Zapier — e.g. a spreadsheet, database, CRM, ServiceTitan, Slack, email, or Power BI — and name each destination here; if data is not stored anywhere beyond Zapier's own task history, say so.]

5. Third-party service providers

Information may be processed by the following third parties as part of normal operation:

Google LLC — provides the Google Ads and Local Services Ads APIs and the OAuth consent flow.
Zapier, Inc. — hosts the Integration and runs the workflows that call Google's APIs.
Cloudflare, Inc. — hosts this informational website only. The website does not receive lead data.
[CONFIRM: any other systems that receive lead data, e.g. ServiceTitan, Google Sheets, a CRM, a database]

This is not a promise that data is never shared with third parties: the providers above necessarily process data to make the Integration work.

6. OAuth authentication and token handling

Authorization uses Google's OAuth 2.0 flow, which takes place on Google's consent screen and within Zapier's connection process. This website does not request, receive, or store passwords, OAuth tokens, or refresh tokens. [CONFIRM: that OAuth access and refresh tokens are stored and managed entirely by Zapier, and that you do not copy them into any other system.]

7. Data storage and retention

This website does not use a database, does not set cookies, and does not run analytics. Retrieved lead data is requested from Google when a workflow runs. [CONFIRM: whether the Integration itself stores any lead data; how long Zapier task history retains it (check your Zapier plan's data-retention setting); and your retention period for any downstream copies, e.g. “deleted after __ days”.]

8. Security measures

This website is served over HTTPS. Data is transmitted to and from Google's APIs over encrypted connections. [CONFIRM: any additional measures you actually apply, e.g. two-factor authentication on Google and Zapier accounts, restricted Zapier workspace membership, encrypted storage in downstream systems. Do not list measures you do not use.] No method of transmission or storage is perfectly secure.

9. Access controls

Access to the Integration and any data it retrieves is limited to the integration administrator and personnel of the authorizing business who need it. [CONFIRM: exactly who has access — administrator only, or named client personnel — and how that access is granted and removed.]

Data obtained through Google APIs is not sold, and is not used or transferred for advertising, retargeting, or data-broker purposes. It is shared only with the service providers listed above as needed to operate the Integration, with the authorizing business, where required by law, or with the user's consent. [CONFIRM: you are willing to make this commitment; it mirrors Google's API Services User Data Policy requirements for sensitive scopes.]

The Integration's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. This statement describes our compliance commitment; it is not a claim of Google certification, verification, or approval.

11. Data deletion and access requests

To request access to, correction of, or deletion of information handled through the Integration, please email arielaleksander@gmail.com. Include the relevant business or Google account to help us verify authorization. Do not include passwords or sensitive account credentials. Where the authorizing business controls the underlying lead data, we may refer requests to that business.

12. Revoking Google access

An authorized user can revoke the Integration's access at any time at myaccount.google.com/permissions by selecting the Integration and choosing “Delete all connections” (or the equivalent option shown). The Zapier connection can also be disconnected from the Zapier account's connections page. After revocation, the Integration can no longer retrieve data from that Google account.

13. Contact

For privacy questions, data access requests, or deletion requests, contact arielaleksander@gmail.com. For general business inquiries, contact ariel@dashboards.com.

14. Updates to this policy

This policy may be updated as the Integration changes. The “Last updated” date above shows the latest revision. Material changes will be communicated to the authorizing business directly [CONFIRM: how you will notify them].