TreeLeads

Privacy policy.

What we collect, why we collect it, how long we keep it, and how to make us delete it.

Effective
September 17, 2026
Last updated
September 17, 2026

1. Who we are

TreeLeads is software for tree service companies. It runs the advertising, the booking pages, the call handling and the follow-up that turn a homeowner's search into a booked job, and it reports what each of those stages cost and produced.

This policy is issued by NEEDS FAIZAN — registered legal entity name — the company that signs contracts (Leeds Company or Scale and Automate LLC), operating as TreeLeads at treeleads.io. In this policy "we", "us" and "TreeLeads" mean that company.

OperatorHow to reach us
NEEDS FAIZAN — registered legal entity name — the company that signs contracts (Leeds Company or Scale and Automate LLC)Email support@treeleads.io
NEEDS FAIZAN — business mailing address — a commercial or registered-agent address, never a home addressPhone (469) 369-2430

For any privacy question, a data access request, or a deletion request, email support@treeleads.io. That mailbox is monitored and is the fastest route to a human.

2. Who this policy covers

This policy covers three different groups of people, and it is worth knowing which one you are, because the answers differ.

  • Site visitors — anyone reading treeleads.io. We collect the least from you: the request data your browser sends, and whatever you type into the booking form if you choose to use it.
  • Customers — tree service companies who buy the software or an engagement. We hold your business contact details, your account configuration, and the operational data the platform produces for you.
  • Your customers' contacts — the homeowners who call you or fill in a form on a page we run for you. We process their data on your instructions, as your service provider. You decide what happens to it; we carry it out.

It also covers the Google integrations — the Google Ads API, Google Analytics 4 and Google Tag Manager. Because Google holds developers to specific commitments about that data, it has a section of its own below.

3. What we collect, and why

One row per category of data. "Who receives it" names the sub-processors in section 7.

Data categoryWhy we collect itLegal basisRetentionWho receives it
Website request data — IP address, browser and device type, pages requested, referring page, timestamps. Collected automatically by our host.Serve the site, keep it available, block abuse and automated attacks.Legitimate interests — running and defending a website.30 days in host logs.Cloudflare
Booking request — name, company, phone, email, and the city or county you work. You type these into the form on our booking page.Call you back about the enquiry you submitted.Steps taken at your request before entering a contract; consent for any SMS.Life of the relationship, then 24 months.GoHighLevel
Customer account data — business contact details, billing contact, account configuration, support correspondence.Provide the service, bill for it, support it, and keep tax records.Performance of a contract; legal obligation for tax records.Life of the relationship, then 7 years for financial records only.GoHighLevel, our payment provider
Your customers' contact records — homeowner name, phone, email, service address, job notes and pipeline stage. Reaches us from your ads, your booking pages, your calls and your forms.Run your pipeline for you: route the lead, book the estimate, follow up, request the review.Performance of our contract with you. You are the controller; we act on your instructions.While you are a customer, then 90 days, unless you ask us to delete sooner.GoHighLevel, CallRail, Anthropic
Call recordings and transcripts — inbound calls to tracked numbers, and the AI summary written from them.Write the call into the contact record automatically, so a 4:40pm call is not lost.Performance of our contract with you; consent where your state or your caller's state requires it.24 months, or on request.CallRail, GoHighLevel, Anthropic
Google Ads account data — campaign, ad group, keyword, cost, click and conversion metrics from the Google Ads account you connect.Report what your advertising did, and change it when it is not working.Performance of a contract; your consent at the Google consent screen.12 months.Google
Google OAuth tokens — the credential that keeps your Google Ads connection alive.Maintain the authorised connection without asking you to sign in repeatedly.Your consent, given at the Google consent screen and revocable there.Until you disconnect or revoke; deleted within 30 days of either.Nobody — held encrypted at rest, never shared
Landing page analytics — Google Analytics 4 and Google Tag Manager on the advertising pages we operate for customers.Attribute a booked job back to the ad and keyword that caused it.Legitimate interests; consent where required in the visitor's jurisdiction.14 months (Google Analytics default).Google

We do not collect special category data — health, biometrics, race, religion, political opinion, union membership, sexual orientation — and we ask you not to type it into free-text fields.

4. Google User Data

This section describes exactly what TreeLeads does with data obtained through Google APIs. It applies whenever you connect a Google account to TreeLeads.

The APIs we use

Google APIWhat we accessWhyScope of access
Google Ads APICampaign, ad group, ad, keyword, budget, bidding, cost, impression, click and conversion data for the Google Ads accounts you explicitly connect. Where you have asked us to manage the account, we also create and change campaigns, ad groups, keywords, ads, budgets and bids.To report what your advertising cost and produced, and to change it when it is not performing. This is the core of the product.Read and, for managed accounts, write — limited to the Ads accounts you authorise.
Google Analytics 4Aggregated traffic and conversion measurement for the advertising pages we operate for you.To attribute a booked job back to the ad and keyword that produced it.Read only.
Google Tag ManagerThe tag container on the advertising pages we operate for you.To deploy and maintain conversion tracking on those pages without hand-editing page code.Container configuration only.

Where it is stored, how long, and who can see it

  • Where. Google Ads reporting data and OAuth tokens are stored on infrastructure we control, hosted in the United States. Tokens are encrypted at rest and are never written into a browser bundle, a log line, or a URL.
  • How long. Reporting data for 12 months. OAuth tokens until you disconnect or revoke access, and deleted within 30 days of either.
  • Who. Only the TreeLeads operator or operators who run your account, and only for the purposes above. No other customer can see your Google data. We run no process that pools one customer's Google Ads data with another's.

Limited Use

The Google API Services User Data Policy is the document that language refers to. Specifically, and without exception:

  • We do not sell Google user data. Not to anyone, in any form, for any price.
  • We do not transfer Google user data to any other app or third party, except as necessary to provide or improve the features you are using, to comply with applicable law, or as part of a merger or acquisition in which the receiving party remains bound by this policy.
  • We do not use Google user data to serve advertising, to build advertising audiences, or for any advertising purpose outside operating your own advertising account at your instruction.
  • We do not allow humans to read Google user data, except with your explicit consent for a specific purpose such as support you have asked for, where it is necessary for security purposes such as investigating abuse, to comply with applicable law, or where the data has been aggregated and anonymised.

Disconnecting

You can revoke our access at any time at Google Account permissions, or by emailing support@treeleads.io. Revoking stops all further access immediately. We delete the stored tokens within 30 days, and we will delete the reporting data we already hold on request. There is more detail, step by step, on our Google Ads integration page.

5. How we use what we collect

  • To run the service you bought: advertising, booking pages, call handling, follow-up and reporting.
  • To contact you about an enquiry you submitted, or about your account.
  • To keep the service working, secure and free of abuse.
  • To meet legal, tax and accounting obligations.
  • To improve the product — using operational and aggregated data, never by reading one customer's data to benefit a competitor of theirs.

We do not use your data, or your customers' data, to train general-purpose machine learning models. Where we use an AI provider to summarise a call, that provider processes the call on our instruction and does not use it to train its models.

6. Calls, SMS and consent

Phone and text are how this industry actually works, so it is worth being precise about consent.

  • What consent we collect. Where a form on our site or on a page we operate for a customer offers SMS, it carries a separate, unticked checkbox. Ticking it is consent to receive text messages at the number given. It is never required to submit the form and it is never bundled into the terms of service.
  • Message frequency. Message frequency varies with your enquiry — typically a handful of messages around a booking, and never a recurring marketing programme you did not ask for.
  • STOP and HELP. Reply STOP to any message to stop all further messages to that number. Reply HELP for help, or email support@treeleads.io. We honour STOP immediately and automatically.
  • Cost. Message and data rates may apply. Your carrier, not us, sets those rates.
  • Call recording. Calls to tracked numbers may be recorded and transcribed. Where the caller's state requires all-party consent, the call carries a recording announcement before the conversation begins.

Mobile information and consent to receive SMS are never sold, rented or shared with third parties or affiliates for their own marketing purposes. They are shared only with the sub-processors in section 7 that deliver the message on our behalf.

7. Sub-processors

These are the companies that process data on our behalf. Each receives only what its job requires.

Sub-processorWhat it does for usWhat it receives
Cloudflare, Inc.Hosts and delivers this website and the serverless function behind the booking form.Website request data: IP address, user agent, requested URL. Booking form fields in transit.
HighLevel Inc. (GoHighLevel / LeadConnector)The CRM behind the platform: contact records, pipelines, calendars, SMS and email delivery, and the booking calendar embedded on our booking page.Booking requests, customer account data, your customers' contact records, message content.
CallRail, Inc.Call tracking and recording on advertising numbers.Caller phone number, call time and duration, call recording and transcript, the ad or keyword that produced the call.
Google LLCGoogle Ads (ad delivery and the Ads API), Google Analytics 4 and Google Tag Manager on the advertising pages we operate.Advertising account data, aggregated measurement data from those pages, conversion events.
Anthropic, PBCThe AI model that summarises an inbound call and extracts the caller's details into the contact record.Call transcript text and the fields extracted from it. Not used to train models.
Our payment providerProcesses payment for the software and for engagements. Named on your order form or invoice.Billing contact and payment details. We never receive or store full card numbers.

We will update this table before adding a sub-processor that handles personal data. If you are a customer and a new sub-processor is unacceptable to you, tell us and we will work out an alternative or end the engagement without penalty.

Beyond this list, we disclose personal information only where the law requires it — a lawful court order, subpoena or regulatory demand — or to establish or defend a legal claim. We do not hand over customer data on an informal request.

8. Retention and deletion

Retention periods are in the table in section 3. When a period ends, the data is deleted or irreversibly anonymised.

You can ask us to delete sooner. Email support@treeleads.io with the word Deletion in the subject line and tell us which data you mean. We acknowledge within 10 days and complete the deletion within 30 days, unless a law requires us to keep a specific record — in which case we will tell you which record and which law.

Step-by-step instructions, including what to send and what happens to backups, are on the data deletion page.

9. Security

Stated honestly. Everything below is verifiable in the code that builds this site, or is a control we actually operate.

  • This website is static, pre-rendered HTML. It has no database, no user login and no session. There is nothing on it to breach.
  • It has exactly one write path — the booking form — which posts to a same-origin serverless function. That function accepts an allow-list of five fields, truncates each to 200 characters, and fails closed if its credentials are missing rather than passing the request on.
  • The CRM credential and account identifier are held as server-side environment variables. They are never included in the browser bundle and are never read from the request body, so a crafted request cannot redirect a write into another account.
  • All traffic is served over HTTPS, enforced by the host. Data is encrypted in transit; OAuth tokens are encrypted at rest.
  • Access to the CRM, the ad accounts and the Google connection is limited to the operator or operators who run your account.
  • We do not hold SOC 2, ISO 27001 or any comparable certification, and we do not claim to. We are a small company and we would rather tell you that than imply an audit we have not had.

No system is perfectly secure. If you believe you have found a vulnerability, email support@treeleads.io and we will respond.

10. Cookies and analytics

treeleads.io loads no analytics scripts, no advertising tags and no third-party trackers of its own. That is a design decision and you can verify it by viewing the page source.

  • Our host may set a strictly necessary security cookie to distinguish humans from automated traffic. It carries no advertising identifier.
  • The booking calendar on our booking page is embedded from our CRM provider and may set its own cookies when you interact with it. If you would rather not load it, call (469) 369-2430 or email support@treeleads.io instead.
  • Advertising pages we operate for customers are different: those carry Google Analytics 4 and Google Tag Manager, because measuring an ad is the job. Those pages carry their own notice.

You can block or delete cookies in your browser settings, and opt out of Google Analytics with Google's opt-out browser add-on.

11. California privacy rights (CCPA / CPRA)

If you are a California resident you have the right to know what personal information we collect and why, to access a copy, to correct it, to delete it, and to limit the use of sensitive personal information. You also have the right not to be discriminated against for exercising any of them.

The categories we collect, the purposes and the recipients are in the table in section 3. To exercise any right, email support@treeleads.io. We will verify your request — usually by confirming control of the email address or phone number already on file — and respond within 45 days, extendable once where the law allows. An authorised agent may act for you with written permission.

12. UK and European rights (UK GDPR / GDPR)

Where the UK GDPR or the EU GDPR applies to our processing, you have the rights to access, rectification, erasure, restriction, portability, and objection, and the right to withdraw consent at any time without affecting processing already carried out.

Our legal bases are named per category in section 3. Where we rely on legitimate interests, the interest is operating and defending a business service, and we have weighed it against your rights.

To exercise a right, email support@treeleads.io. We respond within one month. Where we process your data as a processor on a customer's instruction, we will route your request to that customer and tell you we have.

We are based in the United States, so data you send us is transferred there. Where a transfer is subject to the GDPR we rely on the Standard Contractual Clauses with our sub-processors. You have the right to complain to your supervisory authority — in the UK, the Information Commissioner's Office.

13. Children

This service is sold to businesses and is not directed to children. We do not knowingly collect personal information from anyone under 13, or under 16 where local law sets that age. If you believe a child has given us personal information, email support@treeleads.io and we will delete it.

14. Changes to this policy

When this policy changes we update the "last updated" date at the top of the page and publish the new version here. For a material change — a new category of data, a new purpose, a new sub-processor handling personal data, or anything that narrows your rights — we will email active customers at least 14 days before it takes effect.

Questions about any of this go to support@treeleads.io, or (469) 369-2430.