Demo requests
We collect your company name, role, first name, work email and phone number so we can arrange and follow up your demo.
Lawful basis: steps prior to a contract and our legitimate interest in responding to business enquiries.This policy is in two parts. Part A covers the landscapebase.co.uk website, including demo requests, analytics and advertising. Part B covers the LandscapeBase application, including any Google account you choose to connect. Section 01 and sections 11 to 13 apply to both.
Last updated: 27 September 2026LandscapeBase is a product of ALPHARD GLOBAL LIMITED, company number 16519400.
Registered office: Flat 71 Warehouse Court, No 1 Street, London SE18 6FB.Alphard Global Limited is the data controller for the website and for your account with us. For the business records you keep inside the application, including personal data about your own customers, you are the controller and we act as your processor (see Part B). If you have a privacy question or want to exercise your rights, email hello@landscapebase.co.uk.
What we collect when you visit the site, request a demo, or reach us through one of our adverts on Facebook or Instagram.
We collect your company name, role, first name, work email and phone number so we can arrange and follow up your demo.
Lawful basis: steps prior to a contract and our legitimate interest in responding to business enquiries.If you submit a lead form on Facebook or Instagram, the details you enter on Meta's form reach us in the same way and we use them for the same purpose: arranging and following up your demo.
We use PostHog, hosted in the EU at eu.i.posthog.com, to understand how the site is used, including pages viewed and form interactions.
Lawful basis: our legitimate interest in understanding and improving the site.Only when you accept through the cookie banner, we use the Meta Pixel to measure whether our ads work. If you decline, no Meta cookie is set and the site still works fully.
Lawful basis: consent. You can withdraw consent at any time by clearing your cookies.We store which campaign or advert brought you here, including UTM parameters, in your browser's local storage and alongside your enquiry.
We use a small number of service providers to run the site and handle enquiries:
We never sell personal data. Where a provider transfers data outside the UK, the transfer relies on that provider's standard safeguards, such as standard contractual clauses or an adequacy arrangement.
We keep enquiry data while it is relevant to a live conversation and delete it on request.
Analytics data follows PostHog's default retention settings.
Campaign attribution stays in your browser's local storage until you clear it.
We keep this list short. Meta advertising cookies are optional.
| Name | Type | What it does | When it is used |
|---|---|---|---|
lb_consent | Local storage | Stores whether you accepted or declined Meta advertising cookies. | After you answer the cookie banner. |
lb_attribution | Local storage | Stores the campaign or advert that brought you to the site. | When campaign information is present in the page address. |
| PostHog analytics identifiers | Analytics storage | Helps us understand pages viewed and form interactions. | When you use the site. |
_fbp and other Meta Pixel cookies | Advertising cookie | Helps measure whether our Meta ads work. | Only after you accept. |
This list covers the website. The application sets the cookies needed to keep you signed in, provided by Clerk, our authentication provider, and records product analytics as described in Part B.
What we process when your business uses LandscapeBase, including data from accounts you connect such as Google.
When you use LandscapeBase as a customer, we process the account details you give us (name, work email, phone number and business details) and the business records you create or bring into the product: leads, customers, quotations and costings, jobs, appointments, documents and messages.
Lawful basis: performance of our contract with you.
For your account details we are the controller. For business records about your own customers and contacts, you are the controller and we are your processor: we process that data only on your instructions, keep it confidential, and help you respond to requests from the people it concerns.
We record product analytics in PostHog, hosted in the EU, to see which features are used. We do not send the content of your customers' messages to analytics. Lawful basis: our legitimate interest in improving the product.
Connecting a Google account is optional. If you choose to connect one, LandscapeBase uses Google APIs to access a limited set of your Google data. This only happens after you grant permission on Google's own consent screen, and you can withdraw that permission at any time.
| Google data | Scope requested | Why we need it |
|---|---|---|
| Your Gmail messages, including message bodies | gmail.readonly | To identify lead enquiry emails arriving in your inbox, extract the customer's name, contact details, address, job type and requirements into a LandscapeBase lead record, and match later replies to the correct lead so your timeline stays complete. |
| Sending email as you | gmail.send | Suggested replies are drafted, reviewed and edited inside LandscapeBase, not saved as drafts in your Gmail mailbox. For these replies, Gmail is used only to send the message from your own address when you choose to send it. |
| Your Google Calendar events | calendar.events | To create, update and cancel the site visits and quotation appointments you book from inside LandscapeBase, and to read existing events so we do not double-book you. |
| Your name and email address | openid, userinfo.email, userinfo.profile | To identify which Google account is connected and show it in your LandscapeBase settings. |
We request the narrowest scopes that make these features work. We do not access any other Google data, and we do not access Google data belonging to anyone who has not connected their own account.
LandscapeBase's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.
In plain terms, this means:
Nobody else receives your Google data.
We store Gmail message bodies alongside the lead records extracted from them to provide the connected email features and keep your lead timeline complete. We keep Gmail and Calendar data for as long as it is needed to provide these features and maintain the associated business records.
You can, at any time:
Disconnecting your Google account does not currently delete Gmail messages already stored in LandscapeBase. Disconnecting alone should not be treated as a deletion request. To request deletion of stored Google data, email hello@landscapebase.co.uk. Deletion requests are handled separately from disconnecting your account.
LandscapeBase uses AI models to read enquiry emails, draft suggested replies, and help produce costings and quotations.
We do not use your Google user data, including Gmail message content and Google Calendar event data, to develop, improve or train generalised or non-personalised artificial intelligence or machine learning models.
AI processing happens only at the moment you use a feature, only on the specific data needed for that request, and only to return a result to you. Requests are sent through OpenRouter, an API gateway, to models from Anthropic and OpenAI. Under their API terms, these providers do not use data submitted through the API to train their models, and we do not permit them to.
You remain in control. Suggested replies are drafted, reviewed and edited inside LandscapeBase. They are not written to your Gmail mailbox as drafts. For these replies, Gmail is used only to send the message when you choose to send it. Nothing is sent to a customer until you send it.
| Provider | What they receive | Purpose |
|---|---|---|
| Render (United States, Oregon) | The application database and files, including your business records, stored Gmail message bodies and extracted lead data | Hosting and running the LandscapeBase application |
| Clerk (United States) | Your name, email address and sign-in details | Authentication and account management |
| OpenRouter, Anthropic and OpenAI (United States) | The content needed for the AI feature you are using, for example an enquiry email and your business details | Classifying enquiries, drafting replies and producing documents, as described in section 08 |
| PostHog (EU) | Product usage events, not message content | Product analytics |
| Google Workspace | Emails you send to our support address | Our own email and support |
| Stripe | Payment details, where you pay us by card | Payment processing. We never see or store your full card number |
Where you connect a third-party account such as Google, Microsoft or WhatsApp, that provider processes your data under its own privacy policy as an independent controller.
Several of these providers are in the United States. Where a provider processes personal data outside the UK, the transfer relies on the UK International Data Transfer Addendum to the EU standard contractual clauses, or on the UK-US data bridge where the provider is certified. We never sell personal data.
Customer account and business records are kept for the life of your account and deleted within 30 days of account closure, unless we are required to keep them for legal or accounting reasons. Copies in short-term backups are removed on the normal backup cycle.
Google account data is covered separately in section 07.
You can ask us to:
Email hello@landscapebase.co.uk to exercise any of these rights. We respond within one month.
If you are a customer of a business that uses LandscapeBase, for example you asked a landscaping firm for a quote, please contact that business first. We will help them respond.
You also have the right to complain to the Information Commissioner's Office at ico.org.uk.
If we change how we handle your data, we will update this page and change the "Last updated" date at the top. If the change is significant, we will tell you by email before it takes effect.