Privacy and data use
LocalCMO separates public evidence, connected first-party data, and business outcomes. This policy explains how those boundaries begin on the website.
Last updated: November 4, 20261. Scope
This policy describes the LocalCMO marketing website and the information passed from this website to the LocalCMO application. Product workspaces, connected accounts, and paid services may present additional notices at the point of collection or authorization.
2. Store and location search
When you type a city, area, ZIP, store name, or address, the website sends the query from our server to Google Places APIs to return location and business suggestions. The website requires you to select a suggested location and a suggested business before continuing.
- Search text and selected Google place identifiers
- Selected store name and formatted address
- The region selected for the search
3. Information used for analysis
LocalCMO may begin with publicly observable information about the selected business and its market. Public evidence does not include private account performance unless you authorize a connection.
Connected data such as analytics, Google Business Profile management information, booking, CRM, POS, or publishing accounts requires explicit permission in the application. Access should be limited to the minimum necessary scope.
4. Website operations
We may process standard technical information needed to operate, secure, and improve the website, such as IP address, browser and device information, timestamps, requested pages, and error logs. On the production website, a notice in the corner of the page asks every visitor, in every region, about Microsoft Clarity session recording, Meta advertising and affiliate cookies. Outside the European Economic Area, the United Kingdom and Switzerland, Microsoft Clarity session recording, Meta advertising and affiliate cookies run from the first page view until the visitor rejects them in the same notice; inside those regions, and whenever we cannot determine the visitor's region, they wait for an accept. Google Analytics measures website usage from the first page view, including page views and browser and device information. Where it runs, Microsoft Clarity captures clicks and scrolling for heatmaps and session recordings only on five public website pages (/, /pricing, /about, /contact, and /products) and approved static application pages. Authentication, invitation, onboarding, and other sensitive flows are excluded. Our fixed-version Clarity client masks page content, removes URL query strings and fragments, replaces unrecognized paths, and reduces referring URLs to their origin before recording. These protections limit recording detail; they do not anonymize every technical signal. Google advertising storage, advertising user data, and personalization remain denied even when you separately accept Meta advertising. Meta Pixel is a separate optional advertising purpose: only after an explicit advertising acceptance, Meta receives selected public page visits, cookie identifiers (such as _fbp and _fbc when available), IP address, and browser/device signals for advertising measurement and personalization. This is advertising data sharing with Meta, not necessary storage or analytics-only processing. No advanced matching or custom personal-data payload is configured. On the website, the pixel is restricted to the home, pricing, about, contact, and products pages, and only with an empty referrer, a known safe first-party static referrer, or the bare origin of an advertising platform (such as facebook.com) with no path, query string or fragment of its own. Campaign parameters on our own page URL are limited to a fixed allowlist of advertising tags (utm_*, fbclid, gclid and similar); any other parameter keeps the pixel off. These are collection gates, not a claim that the Meta SDK sanitizes URLs. Advertising consent is independent of analytics and affiliate tracking and is stored for 180 days in its own necessary preference cookie shared across the website and app. Accept enables Microsoft Clarity recording, Meta advertising and affiliate cookies together; Reject turns all three off. Cookie preferences reopens the same choice. Use Cookie preferences to withdraw; withdrawal revokes Meta consent, clears accessible _fbp/_fbc cookies, and reloads or disposes the active document. If a choice cannot be saved, advertising stays off and a visible notice asks you to retry. Meta may process this advertising information under its own privacy policy at https://www.facebook.com/privacy/policy/. One analytics choice covers Google Analytics and Microsoft Clarity across our website and app. It is saved for 180 days in a necessary preference cookie shared by localcmo.ai, www.localcmo.ai, and app.localcmo.ai in this browser. You can reject analytics or withdraw consent using Cookie preferences at the bottom of any page or in the app; open pages synchronize this choice when active and when you return to them. Withdrawal stops analytics and removes GA4 and Clarity cookies accessible to each site. If the preference cookie expires or is removed, Microsoft Clarity returns to the default for your region: on outside the European Economic Area, the United Kingdom and Switzerland until you reject it again, and off inside those regions until you accept. Rejecting analytics does not affect website access. Google and Microsoft process analytics information. For more about Microsoft’s data practices, see the Microsoft Privacy Statement at https://privacy.microsoft.com/privacystatement. Affiliate tracking is a separate optional choice. Affonso uses referral cookies for up to 90 days and may process IP address, browser, and location information after permission. Before permission, Affonso consent mode maintains referral continuity through URL parameters without setting referral cookies. Cookie preferences lets you reject or withdraw affiliate tracking.
5. Sharing and service providers
Information may be processed by service providers that support hosting, security, communications, store search, analytics, billing, or other product operations. We do not describe public evidence as private customer data, and we do not authorize third parties to use connected business data outside the agreed service purpose.
6. Retention and security
Information should be retained only as long as needed for the stated purpose, contractual obligations, security, dispute resolution, and applicable law. No system is perfectly secure, but access controls, encryption, and data-minimization practices should be used in proportion to the information involved.
7. Your choices
You may choose not to continue from the store search, decline an account connection, revoke a supported connection, or request access, correction, or deletion where applicable. Use the support channel shown in your LocalCMO account for account-specific requests, or write to us directly.
8. Changes
We may update this policy as the website, application, connected systems, or legal requirements change. Material changes should be reflected by an updated date and, when appropriate, an in-product notice.
9. Contact
Write to us with any question about this policy or about the information we hold. You do not need a LocalCMO account to contact us.