Privacy policy

Who we are

Ternly is an AI visibility tool for SaaS products and apps. This policy covers this website, ternly.io, and the Ternly app at app.ternly.io. “We” and “us” mean the people who run Ternly. Questions about this policy or your data go to aiden@ternly.io.

What we collect

When you sign in. You sign in with your Google account. Google tells us your email address and an account ID, and nothing else from your account; Google handles the sign-in, so we never see your password. Your email address is how Ternly knows which workspaces are yours.

What you add to a workspace. The sites and apps you track, their competitors, the keywords and questions you follow, your settings, and the email addresses of people you invite. We also keep what Ternly finds for you: copies of the public pages it crawls on your site and your competitors’ (their HTML and screenshots), audit findings, AI answers, rankings, backlinks and content briefs.

Accounts you connect. Connecting is optional. If you connect Google, you choose what to grant: read-only access to Search Console and Google Analytics, and if you want them, read-only BigQuery (for Crashlytics) and Google Sheets, limited to the spreadsheets Ternly creates for your exports. If you add the Slack app, a webhook, or keys for App Store Connect, Bing Webmaster Tools, RevenueCat, Apple Search Ads, AppsFlyer, Adjust, Mixpanel or Amplitude, Ternly uses them to read your numbers or post your alerts. What it reads through them, such as search queries, clicks, traffic, installs and revenue, is stored for your workspace. Tokens and keys are stored encrypted, and the app never shows them again, even to you. For exactly what Ternly reads from Google and what it does with it, see How Ternly uses Google user data.

Billing. Paid plans are sold by Lemon Squeezy, our merchant of record. Lemon Squeezy collects your payment details and billing address under its own privacy policy, and we never see your card. We get the subscription’s email address, plan and status.

How you use the site and app. We use PostHog to see how people use Ternly, so we can make it better. It records the pages you visit and what you click, how fast pages load, any errors you run into, your browser and device, the page that sent you, and your approximate location, worked out from your IP address. It may also record session replays, which show how you moved through a page, with anything you type hidden; in the app, replays hide the text on the page too. In the app, PostHog links what you do to your email address. It sees which pages and features you use, but not what’s on them, so the data from your sites and connected accounts never goes to PostHog.

Logs. Our hosting providers record requests (IP address, browser, time and the address asked for) so we can run the service, keep it secure and fix problems.

Cookies and browser storage

The website and the app use PostHog, which keeps a random ID in a cookie and in your browser’s local storage so it can tell a returning visitor from a new one. We don’t use advertising trackers. The website also remembers whether you picked the light or dark theme. In the app, cookies from Google’s sign-in keep you signed in, local storage remembers the workspace you last opened, and a link you pasted on the homepage is kept until you add it as a site.

You can block PostHog with your browser’s tracking protection or a content blocker. Ternly works the same without it.

How we use it

• To run Ternly: sign you in, do the crawls, checks and AI questions you ask for, and show you the results.
• To apply your plan’s limits and handle billing.
• To keep the service secure and working, and to fix it when it isn’t.
• To understand which parts of Ternly people use, and where they get stuck, so we can improve it.
• To contact you about your account or about changes that affect you.

We don’t sell your information, we don’t show ads, and we don’t use your data to train AI models.

Who else handles it

Ternly runs on these services. Each one gets only what its part needs.

• Google Cloud hosts the app, its database and its files, in the United States. Its Vertex AI service gives Gemini’s answers and makes text embeddings.
• Cloudflare serves this website and runs our domain names.
• Anthropic (Claude), OpenAI (ChatGPT) and Perplexity receive the questions Ternly asks about your product’s category, and for features like content briefs, the page text and search queries the feature works from.
• DataForSEO runs rank checks and keyword volumes, and asks ChatGPT and Gemini your questions the way people see them. It receives your keywords and questions.
• Lemon Squeezy handles payments and subscriptions.
• PostHog records how the website and app are used, in the United States.
• The services you connect, and Slack or your webhooks, which receive the alerts and digests you set up.

We share information otherwise only when the law requires it, to protect people or the service from harm, or with your permission. If Ternly were ever sold or merged, this policy would still apply to the data you gave us.

How Ternly uses Google user data

This section covers the data the Ternly app (app.ternly.io) gets from Google: when you sign in with Google, when you connect a Google account to a workspace, and when you give Ternly’s service account access to a Search Console property, a Google Analytics property or a Google Play app. Connecting Google is optional; you choose which of the permissions below to grant.

What Ternly accesses.

• Google sign-in: your email address and Google account ID. Ternly asks for nothing else from your Google account and never sees your password.
• Search Console (read-only): the properties your account can see, and for the sites you add, the search queries people found them with, the pages those searches led to, clicks, impressions and average position by day, and each page’s index status from URL Inspection.
• Google Analytics (read-only): the GA4 properties your account can see, and for the properties you pick, sessions, engaged sessions, users, new and active users and key events, by day, landing page, channel and platform.
• BigQuery (read-only, only if you connect it for Crashlytics): the Crashlytics export in the Firebase project you name, from which Ternly counts crashes and ANRs by app version.
• Google Sheets and Drive (only if you turn on Sheets exports): access to the spreadsheets Ternly creates for you, and nothing else in your Drive. Ternly writes your site’s data to them and doesn’t read your other files.
• Google Play Console (only if you invite Ternly’s service account): your app’s store listing, reviews, and store listing visitors and acquisitions from Play Console’s reports.

How Ternly uses it. Only to provide the features you use and show you the results: search and traffic reports, the combined web and app views, alerts and weekly digests, keyword research, content briefs, Sheets exports, and answers to the MCP clients you connect, and to keep those features working and fix them when they break. Your Google sign-in is used to sign you in and to know which workspaces are yours.

Who it’s shared with. Only these, and only to provide those features:

• Google Cloud, which hosts Ternly’s database and files in the United States.
• Anthropic (Claude), when you ask for a content brief: the brief’s research includes how your site already does in Search Console for that keyword (the pages, clicks, impressions and position). When Ternly groups your keyword list, keywords you imported from Search Console are also sent to Claude to label their search intent.
• Vertex AI (Google), or OpenAI if it’s set up as the embedding provider, which turns keywords, including any imported from Search Console, into embeddings for clustering and search.
• Places you choose: your own Google Sheets, the Slack channel or webhooks you set up (alerts and weekly digests include Search Console clicks), and MCP clients you connect, such as Claude Code.

These AI providers process it only to do that work for Ternly, and their terms for API use don’t let them use it to train their models. Ternly never sends Google user data to PostHog or any other analytics service: app recordings in PostHog hide the text on every page. We don’t share it with anyone else except when the law requires it, to protect people or the service from harm, or with your permission.

How it’s protected. It travels over HTTPS. Google Cloud encrypts the database and files at rest, and the database only accepts encrypted connections. The tokens Google gives Ternly are encrypted again (AES-256-GCM) with a key kept in Google Secret Manager, and the app never shows them, even to you. Only signed-in members of your workspace can see its Google data, and only the people who run Ternly can reach the systems it’s stored on.

How long it’s kept. Data read from Google is kept for as long as the site or workspace it belongs to exists, so your reports can show history. Ternly keeps its access token until you disconnect Google. Database backups roll off within 7 days.

How to delete it. Disconnect Google in the app (Workspace → Connections): Ternly deletes its token and revokes it with Google, so it can’t read anything more. You can also remove Ternly’s access at myaccount.google.com/permissions. Data already read stays with its site until you delete the site or the workspace, which deletes it, or until you ask us. Email aiden@ternly.io to have all of it deleted, and we’ll do it within 30 days.

Limited Use. Ternly’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

• We use Google user data only to provide or improve the user-facing features described above.
• We transfer it to others only as described above to provide those features, to comply with the law, for security, or as part of a merger, acquisition or sale of Ternly, with notice to you.
• We don’t use it for advertising, including targeted, personalised, retargeted or interest-based advertising; we don’t sell it to data brokers or information resellers; and we don’t use it to decide credit-worthiness or for lending.
• No person reads it unless you ask us to (for example, for support), it’s needed for security or to comply with the law, or it has been aggregated and anonymised for running the service.
• Ternly does not use data obtained through Google Workspace APIs (Google Sheets and Drive), or any other Google API, to develop, improve or train generalised or non-personalised AI or machine learning models.

Where it’s kept, and for how long

Your data is stored on Google Cloud in the United States, and we keep it for as long as your workspace exists. Deleting a site in the app removes everything Ternly found for it, and an owner deleting a workspace removes its sites, results and connections. Database backups roll off within 7 days. Saved copies of crawled pages aren’t removed automatically yet; email us and we’ll delete them. PostHog deletes session replays after 30 days. To have your account and everything tied to it deleted, including the analytics linked to it, email us and we’ll do it within 30 days.

Security

Everything travels over HTTPS. Google Cloud encrypts the database and files at rest, the database only accepts encrypted connections, and the tokens and keys you connect are encrypted again with a key kept in Google Secret Manager. Only signed-in members of a workspace can see what’s in it.

Your choices and rights

You can see and change most of your data in the app, disconnect any account, and delete sites and workspaces. You can also email us to get a copy of your data, to correct or delete it, or to object to how we use it, and we’ll answer within 30 days. Depending on where you live, for example the EU, the UK or California, the law gives you these rights, and you can complain to your data protection authority.

Children

Ternly is a tool for businesses and isn’t meant for anyone under 16.

Changes to this policy

When we change this policy we’ll update the date at the top. For significant changes, we’ll tell workspace owners in the app or by email before they take effect.

Contact

Write to aiden@ternly.io with any question about your data or this policy.