Privacy policy
Last updated November 15, 2026.
The short version. We help companies measure and improve their growth. We look at public websites, and, when a client connects them, the client's own tools. We act on our clients' behalf for their customers' data, we use it only to do the work they hired us for, never for another client, and never to train AI models. Deletion requests are handled within seven days.
Who we are
Tend is a product of Lee Flannery Consulting LLC, which runs it. Questions about privacy go to hello@tendgrowth.com.
Two kinds of data
Data about our clients. When your company works with us, we hold the email addresses of the people on your team who sign in, and a record of what they do in the app (for example, marking a finding fixed or sharing a report by link). We are responsible for this data.
Data about our clients' customers. When a client installs our site tag or connects a source such as Stripe, we process data about that client's own customers on the client's behalf. The client decides what is collected and why, we follow their instructions. If you are a customer of one of our clients, that company is responsible for your data and is the first place to ask about it. We will help them answer you.
What we collect and why
- Public web pages. We read public, logged-out pages of a client's website and related public sources to produce a report. We never read pages behind a login.
- Repository reads. If you install our read-only GitHub app on a repository, we keep which repository it is, the result of each read, short excerpts of up to 1,200 characters with their file and line range that back each finding, the ordered steps of your implementation sequence (a title and an acceptance test for each), and whether your progress card is switched on, and the delivery id and commit of each push GitHub tells us about. We keep no other repository files. This is deleted when you disconnect the repository or your account is closed.
- Sign-in details. Your email address, used to send you a sign-in link. There are no passwords. If we invite you, the invitation holds your email address. We delete the invitation 90 days after it is accepted, cancelled or expires.
- Read requests. When you ask for a free read of your website, we keep your email address and the website address so we can send the read and set up your account. We also note in one word how you reached us (for example a search engine or a forum), taken from the link you followed. We do not keep the address of the page you came from.
- Email updates. If you tick the box when you ask for a read, or switch it on in Your data, we keep that choice, the date and the wording you saw, and send occasional product news. Switch it off in Your data at any time, or use the unsubscribe link in any update.
- Saved links. If you sign in and save a tagged link from the link builder, we keep the link and its source, medium and campaign names, any naming templates you edit or add, the dates and goal of any campaign you save, the pages you add and the signup event you pick for each, under your sign-in, along with the values the link had before each edit. They are deleted when your account is closed.
- Link spellings. If you tell the links report that two spellings of a source or campaign are the same, or dismiss a suggestion to merge them, we keep that choice under your sign-in. It is deleted when your account is closed.
- People we talk to. If you have spoken with us about Tend as a prospect, a design partner, a research participant or a consulting client, we keep your name, work email, company, our notes from those conversations and any follow-ups we owe you, with a log of changes to that record. This is our own record of the relationship, not client data, and it is never shared or sold. Ask and we erase the contact details and notes, keeping only a count.
- Security log. We record sign-in attempts so we can spot misuse. The log holds a hashed form of your user id and IP address, not the address itself.
- Visits to this website. The pages at tendgrowth.com (the home page, this page, the terms and the site tag page) use Google Analytics to count visits and see which channels bring visitors, and PostHog to see how the pages are used, including a replay of your visit with anything you type hidden, but only after you accept each in the cookie notice; until then neither loads. Your choice is kept for a year in a cookie named "klaro" on this site, and you can change it from the notice. Once you accept, Google sets its own cookies and receives your IP address and browser details. The app does not load it.
- The read page. The read page, reached from the link in your email, counts views and how far the page is read, and with your consent records the session, with no account or identifier of you attached.
- Use of the app. We record which screens and features your team uses, under a hashed user id, to find what is confusing or broken. If you accept it in the cookie notice, the app also loads PostHog, an analytics service, which records how you use the app, including a replay of what was on screen, so we can see where the app is confusing or broken. PostHog receives the hashed id, your company's id and plan, and the session recording; it never receives your email, your sign-in or invitation fields, or the raw account id. We record your cookie choice (accepted, declined or withdrawn) under the hashed id, so we know what share of people the analytics service can see. You can decline or change your choice from the cookie notice, and the app works the same either way. The app loads no advertising scripts.
- Notes and error logs. We keep notes your team adds in the app (for example, why a finding was set aside, what you did about a recommended move, or a note you add to a test), our own notes on the work, and which operator asked for a scan (their user id, never an email). When something fails, we log the page, the error and the time, with email addresses and keys removed before the message is stored.
- Our own site tag. Where it is switched on, the home page and the app use the same site tag we give clients, to see how many visitors ask for a read and sign in. It sets first-party cookies whose names start with "_gp_" on tendgrowth.com and app.tendgrowth.com, and it sends no email address or other contact detail. For a browser that sends Global Privacy Control it sets no cookie and sends nothing.
- Site tag events. The tag keeps its identifiers in first-party cookies on the client's own site for 90 days. It sets no third-party cookies and does no fingerprinting. It sends nothing when someone only browses, except that a visit arriving from a tagged link (one with campaign tags in its address) is counted, with nothing that identifies the visitor. When a visitor buys or signs up, it sends one record of that conversion, named by the client's own event name (for example sign_up, lead or purchase). A visit arriving from a tagged link sends a page_view event. The record holds ad-click identifiers, hashed contact details, and the visitor's IP address and browser type, which every web request carries. The client uses it to see which channels bring customers, and the ad platform uses it to match the sale to an ad. It does nothing for a browser that sends Global Privacy Control. What the site tag collects.
- Connected sources. A client can connect Stripe, Google Analytics, Google Search Console, Google Ads or Meta, and install our site tag. Stripe is read through a read-only key, which is stored encrypted and never shown back. Google Analytics and Search Console are each read through a Google sign-in with the read-only scopes named below; we keep session and key-event counts by source, medium, campaign and date from Analytics, and your search queries and page figures from Search Console. For Google Ads and Meta the client gives us an account ID and we check that access has been granted. For Google Ads, that check uses Tend's own access to ask Google Ads whether the account ID is one it can reach. For both platforms we do not read ad numbers (spend, impressions, clicks). Ad numbers appear in Tend only when you type them in, as described next. You can disconnect Google Analytics or Search Console in Connections, which removes our access at Google.
- Ad platform numbers you type in. When you compare two ads, you enter each ad's impressions and clicks from the ad platform, with the platform, the source of the figure and the date it applies to. We store them with the date you entered them and show them back labelled as reported by you. Tend does not read them from the ad platform. Optional: if you connect Google Analytics, we also read session counts for the same window.
- After a paid plan ends. After a paid plan ends, Tend checks your public home page twice, at 30 and 60 days, to learn whether the business is still open. It never logs in.
- Customer records a client shares. Used to match results to real customers. When we send data to an ad platform on a client's behalf, we send contact details only in hashed form, along with the IP address and browser type from the conversion record, and only for people who bought or opted in.
- Customer quotes a client shares. If a client gives us reviews, support messages or sales notes, we remove the names the client lists, email addresses, phone numbers and handles before we keep the wording. Stripping does not catch every name, so a person who finds their words in a quote can ask the client or us to delete it. These quotes are not linked to any person.
Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Through your Google sign-in we read the following, and nothing else: with the read-only Analytics scope (analytics.readonly), session and key-event counts by source, medium, campaign and date for the property you choose; with the read-only Search Console scope (webmasters.readonly), the search queries and pages your site appeared for. Through that sign-in we never write to your Google account, and we read no Gmail, Drive or contacts. We do not use Google Analytics or Search Console data for advertising. We use it only to answer the checks and show results in your own account.
We do not buy data about people who have not transacted with or opted in to our client, and we do not build profiles of individuals from community or social posts.
Services we use
We use a small number of providers to run the service. Supabase (database and sign-in), Anthropic (AI models that draft and check reports), Google Cloud (hosting), Resend (sending team invitations), Google Analytics (visits to the pages at tendgrowth.com, not the app), PostHog (how the pages at tendgrowth.com and the app are used, including session recordings; data held in the United States), and, only when a client connects them, Stripe, Google and Meta. Each provider receives only what it needs for its part of the work.
How long we keep data
- A client's customer records: for the engagement and 90 days after it ends. When an account is closed, we delete its customer records (orders, leads, contact hashes and the people built from them) 90 days later, unless the client asks for an export first. Reports keep their figures but lose the links to those records, and we keep a log of the deletion that holds counts only.
- Customer quotes a client shares: for the engagement and 90 days after it ends. We delete one on request, and the client can ask us to remove a single quote or a whole import.
- Site tag events that never matched a customer: 90 days.
- Records of what we sent to an ad platform: kept with the account. When a person is deleted, the record keeps the fact that a send happened and loses the link to that person.
- Team sign-in details: while your company works with us. When someone is removed from the team or the account closes, we delete their sign-in, unless they belong to another account with us.
- Read requests: until the account closes or you ask us to delete them.
- App usage records, the security log and error logs: 90 days.
- Records of each email we queue for your team: 90 days. A record holds a one-way scrambled form of your email address, the kind of email, its subject line, a one-line summary of what it said, whether it was sent, and when it was first opened and when a link in it was first clicked. It never holds the address, the full email or which link. After 90 days, or sooner if you ask, we remove the scrambled address, the subject line and the summary, and keep the kind of email, whether it was sent, opened or clicked, and the dates.
- Session recordings held by PostHog: 30 days.
- Notes, the history of each finding and recommended move, shared link records and our log of changes to the account: kept as the account's history, including after the account closes.
- Public web observations: kept as a dated history, since they describe companies, not private individuals.
- Search Console figures (the search terms and pages your site appeared for) and Google Analytics figures (session and key-event counts by source, medium, campaign and date): kept with the account's history, including after the account closes, unless you ask us to delete them. They hold search terms and counts only, never who searched or who visited.
Your rights
You can ask to see, correct or delete personal data we hold about you. If you are a client's customer, you can ask the client or write to us, we act on a deletion within seven days across our store, and send deletion requests to the ad platforms where their tools allow. We log that a deletion happened, not what was deleted. So the same person is not added back when a client sends the same contact again, we keep a one-way scrambled form of the deleted identifier that cannot be turned back into the address, until the client's account is closed and its data deleted. Depending on where you live (for example California or the EU), you may have further rights, write to hello@tendgrowth.com and we will answer.
Changes
If we change this policy in a way that matters, we will tell clients before it takes effect.