Lanello GBP Privacy Policy

1. Data we access and collect

Access depends on enabled features, the permissions granted to the connected Google account, and the client properties or folders selected by staff.

• Google Business Profile: account and location identifiers, names, business details, and available performance measures such as views, calls and website interactions.
• Google Search Console: property URLs, access levels, search queries, clicks, impressions, click-through rates and average positions.
• Google Analytics: account, property and web-stream identifiers and names, website URLs, measurement IDs, and reports such as sessions, engaged sessions, conversions, channels and page performance.
• Google Ads and Local Services Ads: customer and campaign identifiers, campaign information, reporting dates, currency, impressions, clicks, advertising cost and conversion measures.
• Site verification and onboarding: domains, verification methods and tokens, verification results, and property or stream information needed to configure a client website.
• Google Drive content workflows: selected client-folder identifiers, image names, file metadata, image contents and thumbnails. The separately configured Drive connection can create workflow folders and move used files into an archive folder.
• Connection and operational information: OAuth tokens, granted permissions, connection times, the staff member who connected an account, client-to-property mappings, and API operation/status logs. We also process staff sign-in information and client information supplied through the app and its connected business tools.

2. How we use Google data

We use Google data to provide the app's client dashboards, scheduled synchronization, performance comparisons, reports and recaps; to diagnose integration errors; and, where enabled and authorized, to onboard client websites and manage client content.

Analytics read access supports reporting. Analytics edit access supports creating properties and web streams during onboarding. Search Console and Site Verification write permissions support adding and verifying website properties. The Ads integration reads reporting data; it does not use its Google permission to change advertising budgets, bids or campaigns. Drive workflows use configured client folders for image processing, content generation and archiving.

We do not sell Google API data, use it for unrelated advertising or profiling, or use it to train generalized artificial-intelligence or machine-learning models. Google API data is used to provide the client-service features described here.

3. Sharing and processing

• Lanello staff: authorized team members use client data to operate the service, review results and provide support.
• Client reporting: staff can share relevant results through client reports, recaps and report links or embeds. Anyone who receives an active share link may be able to view its report. Staff control the sharing of these outputs.
• Service providers: hosting, storage, authentication and operational providers process information needed to run the app. Connected publishing and messaging services, including GoHighLevel where configured, receive the content or report information required for the requested workflow.
• AI-assisted features: where enabled, selected client images and reporting inputs may be sent to Anthropic's API to generate content or report text. This processing supports the requested feature; it is not a separate use of Google data for model training.
• Legal and security needs: we may disclose information where necessary to comply with applicable law or to investigate abuse, protect users and secure the service, subject to the Google-data limits in this policy.

We limit transfers of Google API data to the purposes permitted by the Google API Services User Data Policy. We do not authorize recipients to use that data for unrelated purposes.

4. Storage and security

Reporting results, property mappings, content metadata and operational records are stored in the app's database. Images, thumbnails and generated assets may be stored on the application server. The shared Google reporting refresh token is encrypted before it is stored in the database. Separately configured integration credentials are held in server configuration and are not published in client reports.

The service uses HTTPS, staff authentication and access controls. Operational records and backups may contain copies of stored data. Processing may take place outside your country. No system can guarantee absolute security.

5. Retention and deletion

We retain reporting history, content and operational records as needed to provide the client service, maintain records, resolve disputes and meet applicable obligations. Disconnecting Google stops new access through that connection and clears the app's stored reporting refresh token; it does not automatically delete previously synchronized reports, generated content or backups.

To request deletion of stored Google data, contact info@lanello.io and identify the relevant client or Google property. Do not send passwords or tokens. We verify your authority, identify the affected records and arrange deletion or explain any applicable legal retention requirement. Backup copies may remain until they are removed through backup retention. A deletion request to Lanello does not delete the original data in your Google account or copies already shared with a recipient.

6. Your controls

Authorized staff can select or unlink reporting properties and disconnect the shared Google reporting connection in the app's Settings. Disconnecting a shared agency connection affects the clients that use it. Google account owners can revoke access through Google Account connections. A separately configured Drive connection must also be revoked or disabled separately. Contact us for access, correction, deletion or other privacy requests relating to data processed by the app.

7. Google API Services User Data Policy

Lanello GBP's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

8. Contact and updates

Lanello LLC · 30 N Gould St, Suite R, Sheridan, WY 82801, United States.
Email: info@lanello.io. We publish changes to this policy on this page and update the date above. Material changes to how the app uses Google data will be disclosed before the changed use begins, with consent requested where required.

9. Text messages

Clients of Lanello can say yes to text messages from us on their onboarding form. If you do, this is what we keep:

• Your mobile number: the phone number on your onboarding form.
• Your yes or no: if you said yes to texts, the day and time you said it, and which number it was for.
• The texts: the texts we send you and the texts you send us.

We keep these to text you about your account: answers from your account manager, reminders for calls and meetings, and notes about your setup and your results. We also keep them to show that you said yes, and so your team at Lanello can read what was said.

We do not share or sell your mobile number or your consent to receive text messages with third parties or affiliates for marketing or promotional purposes.

For your mobile number and your yes to texts, this part is what counts, even where our company privacy policy says something wider.

You can stop at any time. Reply STOP to one of our texts and we send you no more. The rules for our texts are in our texting terms.