Skip to content
← Back to Locus

Privacy Policy

Last updated: 10 November 2026

At Locus ("we", "our", or "us"), we are committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use locusintel.io, Locus accounts and services, or connect Locus to ChatGPT or another AI assistant through our Model Context Protocol (MCP) service.

1. Information We Collect

We may collect personal information that you voluntarily provide when you:

  • Register on our Site
  • Subscribe to our newsletter
  • Fill out a contact form
  • Use our location intelligence services
  • Participate in surveys or promotions

2. How We Use Your Information

We may use the information we collect to:

  • Provide, operate, and maintain our services
  • Improve, personalise, and expand our services
  • Understand and analyse how you use our Site
  • Develop new products, services, features, and functionality
  • Communicate with you for customer service and support
  • Send you promotional emails about new features and updates

3. Data Security

We implement appropriate technical and organisational measures to protect your personal information. However, no method of transmission over the Internet or electronic storage is 100% secure, and we cannot guarantee absolute security.

4. Your Data Protection Rights

Under data protection law, you have rights including:

Access — You have the right to ask us for copies of your personal information.
Rectification — You have the right to ask us to rectify information you think is inaccurate.
Erasure — You have the right to ask us to erase your personal information in certain circumstances.
Data portability — You have the right to ask that we transfer the information you gave us to another organisation, or to you.

5. Cookies and Tracking

Essential cookies support sign-in, security and your saved privacy choice. Google Analytics loads only after you accept analytics, and the service remains available when you reject them. Advertising storage and personalisation remain disabled. Provider information is available from Google and Ahrefs.

Types of cookies we use

Essential — Necessary for the website to function. Cannot be switched off.
Google Analytics — With your permission, measures visits, traffic sources and approved interactions. We send public page paths and referring origins rather than private query strings or report links. Google Analytics uses first-party analytics cookies.
Ahrefs Web Analytics — Counts page visits across the site independently of your optional cookie choice. This cookieless measurement sends sanitized page labels and referring origins to Ahrefs, without private query strings, report tokens, personal titles or persistent browser storage. Dynamic private pages are grouped by route type.
Privacy choice — Your accept or reject choice is stored in this browser. Use the controls below to change it; withdrawing analytics also clears accessible Google Analytics cookies.

Your choices

Most browsers let you decline cookies. Visit aboutcookies.org to learn more, or opt out of Google Analytics. Rejecting optional analytics does not prevent you using Locus.

6. Data Sources and AI Processing

Demographic & Income Data — Sourced from the Office for National Statistics (ONS) 2021 Census data to provide insights about geographic areas.
Business & Competition Data — Sourced from Google Places API, including local business listings, categories, and publicly available information.
AI Assessment — AI features process your requests and the relevant location, business, report and research context using model providers, including OpenAI and, depending on the feature and configuration, DeepSeek or Google Gemini. User-entered text and business briefs can contain personal information. Do not include sensitive personal information or information you are not authorised to share. The MCP read service itself does not call a model or start new research; it returns permitted data to your connected assistant.

When you use the free competitor finder, your search text and selected location are sent to Google Maps Platform to find matching businesses. Google handles this data under its Privacy Policy. This tool does not save provider results or require an account. To enforce its allowances, we keep a keyed hash of the connection IP with short-lived counters, rather than storing the raw IP in those counters.

We make reasonable efforts to ensure accuracy but cannot guarantee the completeness of third-party data sources.

7. Account, Service and Technical Data

We collect account details such as your name, email, sign-in identifiers and authentication records; subscription, purchase and payment-status references; support correspondence and newsletter preferences. Payment processing is handled by Stripe. We use these records to provide access, fulfil purchases, deliver reports and emails, handle support and administer billing.

When you use research and monitoring features, we process the locations, addresses or coordinates, business types, search text, project names, candidate decisions, briefs, property details, links and documents you supply, together with saved analyses, comparisons, evidence and monitoring observations. These may identify individuals, sole traders or a sensitive business plan. We use them to perform the requested analysis, save your work and deliver monitoring and follow-up services.

Our infrastructure processes connection IP addresses, request times, device/browser information, request paths, status codes, errors and security or usage counters to operate the service, troubleshoot failures and prevent abuse. Optional website analytics follow the choices described above.

8. Data Exchanged Through the Locus MCP Connection

Connecting requires signing in to Locus and approving access scopes. We store an account-linked OAuth grant, client name and identifier, redirect URI, requested scopes, consent and revocation timestamps, and hashed authorisation/token values. These associate each read with the correct account and check its current plan, permissions and allowances. Locus does not receive your entire ChatGPT conversation simply because you connect it; it receives the tool calls and arguments your assistant sends.

Tool inputs include geographic identifiers, data family, source and entity identifiers, project identifiers, report or artifact identifiers, expected report versions, page limits and pagination cursors. Discovery and profile tools accept no arguments. Inputs are used to locate and filter existing permitted records, enforce ownership and scope, and return the requested page or version.

Tool outputs sent to ChatGPT or your chosen MCP client include a stable opaque account ID; available capabilities, plan/scope restrictions and data definitions; and permitted demographic, local supply, property, traffic, planning, market and Pulse records. Records include field values, geographic/entity identifiers, source URLs, attribution, units, vintage, retrieval/expiry dates and uncertainty. They may contain public business or property information that relates to individuals.

With the appropriate scope, project tools return project names, business types, target geographies, status and candidate IDs, priorities, decisions and saved-report references. Saved-report tools return owned analysis titles/search text, location, business type/niche, decision status, dates and version references. Tenant comparison tools return separately consented saved comparisons and frozen evidence, which can include your business brief. They also return availability/restriction explanations. Private notes, credentials and unreviewed raw provider payloads are withheld. Legacy report bodies without reviewed external-AI rights and expiry are not returned.

Only reads are exposed by the current MCP tools: they do not acquire new data, execute research, send enquiries, make purchases or change budgets. Authentication records and rate-limit counters are still updated to operate these reads. Returned information becomes available to your assistant provider and may appear in its conversation history; that provider controls its subsequent storage and use under its own terms and privacy settings.

9. Recipients and International Processing

We share the relevant tool outputs with OpenAI when you use Locus in ChatGPT, or with the operator of another MCP client you connect. This is necessary to answer your requested tool call. We do not send your Locus password or OAuth token secrets in tool outputs.

Providers supporting the wider Locus service include DigitalOcean for hosting and database infrastructure; model providers described above for AI processing; Google Maps Platform and Mapbox for location search and maps; Apify and Firecrawl for requested public-web/business research; Stripe for payments; Resend for service and marketing email; Sentry for error monitoring; and Google Analytics and Ahrefs for consented website analytics. Relevant queries, locations, content, contact details or technical records are disclosed only as needed for that provider function. Not every tool call invokes these providers: the MCP read tools retrieve retained records.

Authorised operators may access records to provide support, maintain security and operate Locus. Information may also be disclosed where required by law, to protect rights or prevent fraud, or as part of a business transfer subject to applicable protections. Processing by our providers and your chosen assistant may take place outside your country. Applicable contractual and other legal safeguards are used where required for international transfers.

10. Retention and Deletion

Account, project, saved-analysis, brief and report records are retained to support your account and saved work until you delete them where controls are available or request deletion. Disconnecting an assistant does not delete these Locus records. Support, billing and security records may be retained as needed to resolve requests, meet legal/accounting duties, investigate abuse or establish legal claims. We assess retention according to the purpose, sensitivity and applicable obligations rather than promise a single period for all records.

OAuth authorisation codes are valid for five minutes, access tokens for fifteen minutes and refresh access for up to thirty days. Revocation blocks further authorised reads. These are access-validity periods, not automatic database deletion deadlines: expired or revoked grant metadata and hashed token records can remain until removed as part of account deletion or operational maintenance. Read-limit counters expire for enforcement after two minutes; expiry does not itself promise immediate physical deletion of the database row.

Retained evidence has source-specific reuse/expiry dates; expired or revoked evidence is withheld from MCP reads, and reading it does not renew its original expiry. Saved comparisons can retain frozen references subject to their access and consent controls. Infrastructure logs, diagnostic records and backups follow the relevant operational/provider lifecycle; deletion from active records may not immediately remove backup copies. Where retention is required, access is limited to that purpose. Copies already returned to ChatGPT or another client are subject to that provider’s retention and deletion controls.

11. Your Controls and Privacy Requests

You can decline the MCP connection, choose the scopes offered at authorisation, and revoke a connection on the Data connections page. Tenant comparisons require separate permission for external-AI access. Removing or revoking access prevents future reads; it cannot recall information already returned. Disconnect Locus in ChatGPT or your other client as well, and use that provider’s controls to manage its conversation history and data.

Use the contact page linked below to request access, correction, export or deletion of your personal data, or to ask about retention and recipients. Identify your Locus account and the records concerned; do not send passwords or tokens. We may verify your identity before acting. Depending on applicable law, you may also request restriction, object to processing or withdraw consent without affecting prior lawful processing. You may complain to your local data protection authority, including the UK Information Commissioner’s Office.

You can change optional analytics using the controls above and unsubscribe from marketing using the email unsubscribe link. Service and security messages may still be needed to administer your account. We process data to provide requested services, meet legal duties, protect and improve service reliability, and, where required, with consent for optional analytics, marketing and separately approved external-AI sharing.

Manage Data connections

12. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated "Last updated" date.

13. Contact Us

Questions about this Privacy Policy? Contact us