Privacy policy
Last updated: 6 November 2026
Who is responsible
Benjamin Libor
Grünberger Straße 17
10243 Berlin, Germany
Email: ibo@allsite.pro
What Echo stores and why
- Your account: your email address, your name and profile picture if you sign in with Google, and the time you signed up. We need these to let you sign in (Art. 6(1)(b) GDPR, performing our contract with you).
- Sign-in sessions: a session record with your IP address and browser name, so you stay signed in and we can spot misuse. Sessions expire after 7 days without use.
- What you set up and what Echo finds: your brand, website, competitors, prompts, the AI answers Echo collects, and the numbers calculated from them.
- Guests and file requests in Brand assets: when a workspace invites you as a guest, Echo stores your email address, the name the team gave you, the collections you may open, when you accepted and when you were last in, and which files you added. When you send files through a “Request files” link, Echo stores the files with your name, email address and the time; the person who asked for them gets one email per batch. The workspace that invited you or asked for the files decides what happens with them: it is responsible for them, and Echo processes them on its behalf (Art. 28 GDPR). They stay until the team deletes them (then 30 days in Recently deleted) or removes you; ask the team, or us, to delete them. To make files searchable, the text inside PDFs and documents is read in the team's browser and kept with the file until it's deleted. For images, Echo can ask OpenAI to suggest tags from a small preview (never for files still waiting for review).
- Usage and costs: how many prompts were run and their estimated cost, to enforce the limits of your plan.
- Abuse protection: for sign-in emails and runs, we count requests per email address, IP address or account for up to two days, to stop anyone flooding an inbox or the service (Art. 6(1)(f) GDPR, our legitimate interest in a secure service).
- Plan and billing: your workspace's plan, its status (trial, active, cancelled), the dates it renews or ends, and Stripe's customer and subscription IDs, so Echo applies the right limits (Art. 6(1)(b) GDPR). Echo never sees or stores your card number. Invoices are kept as long as tax law requires (Art. 6(1)(c) GDPR; in Germany currently up to 10 years).
- Websites Echo reads: to suggest actions and watch competitors, Echo reads public pages of your brand's website and of the competitors' websites you add (respecting their robots.txt), and keeps the page text when it changes for 12 months. These pages can contain names, for example in customer quotes; Echo doesn't look for personal data in them (Art. 6(1)(f) GDPR, our legitimate interest and yours in understanding a market from public sources).
- Competitors' ads: once a week Echo reads the ads your watched competitors run from the platforms' own public transparency libraries: Meta's Ad Library (through Meta's Ad Library API) and Google's Ads Transparency Center (through DataForSEO). Echo never scrapes these sites or signs in to them. It keeps each ad's texts, dates, countries, the advertiser's public page name and a link to the ad for 12 months after the ad stops; Google's preview pictures stay on Google's servers and load from there when you look at them. The advertisers are businesses; ads rarely name a person (Art. 6(1)(f) GDPR, understanding a market from public sources).
- Mentions (social listening): Echo looks for public posts that name your brand or the competitors you watch: forum and review pages your AI answers cite, Google's results for a weekly search per site (through DataForSEO), the Google Alerts feeds you add, Hacker News (through its public Algolia search), Stack Overflow (through the Stack Exchange API), YouTube (through Google's YouTube Data API) and news articles (through GDELT's free public news search, which receives only the brand and competitor names). Echo keeps only what those sources show publicly: the link, the title, a snippet, the date, a star rating and the author's public name where the site gives one. It never opens the pages itself, never builds profiles of the people who post and never posts for you. An AI model reads each snippet for who it names, its tone and whether it's a question. Mentions are deleted 12 months after Echo last saw them, unless an action or a reply points to them (Art. 6(1)(f) GDPR, understanding what the public says about a business).
- The free AI score (/score): the website you enter, your first and last name, your email address, the result and the time. We email you the result, and Echo's owner gets a copy to follow up about it (Art. 6(1)(b) GDPR for sending the result you asked for, Art. 6(1)(f) GDPR for the follow-up; you can object any time by email). To stop misuse, we count scans per IP address for an hour and per email address for a day. Anyone with the report's link can see the result, but never your name or email address. Scans are deleted after 24 months, or sooner if you ask.
- Free playbooks (/playbooks): when you ask for a playbook by email, we store your email address, which playbook, the page you asked from, your country (from your connection, to know which consent rules apply), whether you agreed to occasional emails from Echo about AI visibility, how you agreed (a box you ticked, or the line under the button) with its exact words, and the time. We email you the link to the PDF (Art. 6(1)(b) GDPR) and, only if you agreed, occasional emails about AI visibility (Art. 6(1)(a) GDPR, consent you can withdraw any time with the unsubscribe link in every such email). To stop misuse, we count requests per IP address for an hour and per email address for a day. A request is deleted after 24 months, or sooner if you ask. Whether the popup was closed is kept in your browser (local storage), never sent to us.
- The partner program (/partners): when you apply, your name, company, website, LinkedIn, country and what you write; once you're a partner, the websites and contacts you add as prospects, their AI score reports (shared with whoever you send the link to, with your company's name on them), which customers signed up through you and what they paid, and where to send your payouts. The account details for payouts are stored encrypted and only Echo's team reads them, to pay you. When someone opens a partner's link or report, a cookie keeps the partner's code for 90 days so their sign-up credits the partner (Art. 6(1)(b) GDPR, the partner agreement; Art. 6(1)(f) GDPR for the cookie). We keep payout records as long as tax law requires and the rest until you leave the program and ask us to delete it.
- Visits from AI crawlers: when a workspace connects its website to AI crawlers (a snippet or a log file), the website sends Echo only visits whose user agent names a known AI crawler or assistant (such as GPTBot, ClaudeBot or PerplexityBot). Echo stores the crawler's name, the page's path without its query string, the status code and the time; everything else is dropped before it's stored. No IP addresses, no cookies and nothing about the website's human visitors. echo-aeo.com records the same four facts about AI crawlers that visit it. The single visits are deleted after 90 days; the daily counts per crawler stay while the brand exists (Art. 6(1)(f) GDPR, the workspace's legitimate interest in knowing how AI assistants read its website).
- The Echo tag on a customer's website: when a workspace adds the Echo tag (a script) to its website, Echo processes data about that website's visitors on the workspace's behalf, as its processor (Art. 28 GDPR). For each page view, form sent or marked click the browser sends the page's address, the page it came from, the event's name and its browser details; Echo keeps the page's path, where the visit came from (such as "ChatGPT" or "Google"), UTM tags, the country (from Cloudflare, never the city), the kind of device and a visitor code. The code is made from a random key of the day, the website, the IP address and the browser; the key is deleted after two days, so the code can't be traced back to anyone, and the IP address itself is never stored. No cookies, nothing stored in the visitor's browser, never what people type into forms, and nothing is sent by browsers that ask not to be tracked (Do Not Track, Global Privacy Control). Single events are kept 90 days in Cloudflare Workers Analytics Engine; daily counts stay 25 months.
- Landing pages hosted by Echo: when a workspace publishes a landing page, Echo hosts it on echo-aeo.com or on a subdomain of the workspace's own domain, and processes data about the page's visitors on the workspace's behalf, as its processor (Art. 28 GDPR). Echo counts page views on its server while it answers the request, the same way as the Echo tag above: the page's path, where the visit came from, UTM tags, the country, the kind of device and a visitor code made from a random key of the day, the IP address and the browser. The IP address is used only for that daily code and is never stored. The page sets no cookies and stores nothing in the visitor's browser, and visits from browsers that ask not to be tracked aren't counted. Visits from AI crawlers are recorded as described under "Visits from AI crawlers". Sign-ups through a lead form on the page are handled as described under "Forms" below, with double opt-in, and counted for that page. The workspace decides what the page says and tells its visitors about it in its own privacy policy.
- Tests of landing pages and forms (conversion experiments): when a workspace tests versions of a landing page or a lead form Echo hosts, Echo picks the version a visitor sees from a code made from a random key of the day, the test, the IP address and the browser, so the visitor keeps it for that day. Echo stores that code (never the IP address) with the version and the day, to count visitors once a day per version, and adds each day's count up and deletes the codes the next day. A sign-up remembers which version it came from. No cookies are set; bots, AI crawlers and browsers that ask not to be tracked always get the original version and aren't counted.
- Tags and the cookie banner through the Echo tag: when a workspace enters the IDs of its own marketing tags (such as Google Analytics, Google Ads, the Meta pixel or the LinkedIn Insight Tag), the Echo tag shows the workspace's cookie banner and loads those tags in the visitor's browser only after the visitor agrees. The visitor's choice is kept in their own browser for six months; Echo doesn't receive or store it. What those tags then collect goes straight to their providers, under the workspace's own agreements with them.
- Conversions sent to ad platforms: only when a workspace switches it on, as its processor (Art. 28 GDPR). For a form sent or a marked click on the workspace's website, if the visitor agreed to marketing (or analytics for Google Analytics), Echo passes the event, the page, the visitor's IP address and browser details and the platforms' own browser IDs straight on to Meta, LinkedIn or Google Analytics while handling the request, and stores none of them. For confirmed form sign-ups and won deals from HubSpot or Attio, only when the workspace switched on hashed emails, Echo sends a one-way SHA-256 hash of the email address (never the address) with the deal's amount. Echo keeps a log of what it sent (the event's name, platform, time and whether it arrived, without any personal data) for 90 days, and for deals only the hash of the contact's email.
- Company visitors: only when a workspace switches it on for a brand (it's off by default), the Echo tag also loads the tracker of Snitcher (see below) on that brand's website, which finds out which company a visit comes from, for the workspace (Art. 28 GDPR; the workspace relies on its legitimate interest, Art. 6(1)(f) GDPR, and tells its visitors in its own privacy policy). Snitcher's tracker keeps an identifier in the visitor's browser only after the visitor agrees in the website's cookie banner. Echo reads back from Snitcher only the companies (name, website, industry, size, country and its LinkedIn page) with the visits' pages, source and times, never an IP address, and never identifies people: home, mobile and cloud connections show no company. Browsers that ask not to be tracked don't load the tracker. Company visits are kept 400 days.
- Emails we sent you: which weekly report or alert went out and when, so none is sent twice.
- Team invites: when a workspace owner invites someone, we store the invited email address, who sent the invite and when, and send one invite email (Art. 6(1)(f) GDPR, the owner's legitimate interest in working with colleagues). The invite is deleted when it's accepted or cancelled, and stops working after 7 days.
- Customer stories: when a workspace asks one of its customers to answer a few questions or to approve a customer story, Echo stores, for that workspace, the customer contact's name, role and email address, their answers (saved as they type), the logo and photo they upload (kept with the workspace's files), the items shown to them, their answer per item and channel, the wording they suggest instead, their comments, the name and role they typed, how long the approval lasts, any withdrawal and its reason, the time, their IP address and browser name, and a PDF record of the approval. Echo sends the questions, the approval email, up to two reminders for each, the record and a withdrawal confirmation on the workspace's behalf. The contact can withdraw an approval at any time with the link in the record. For this data the workspace is the controller and Echo processes it on the workspace's instructions (Art. 28 GDPR); the workspace relies on its own legal basis, usually its legitimate interest in documenting the customer's consent to be named (Art. 6(1)(f) GDPR). The record is kept until the workspace deletes the customer, so it can show what was approved, and until when. Contacts can ask the workspace, or us, for access or deletion.
- PR and events contacts: when a workspace uses PR and events, Echo stores, for that workspace, the business contact details it adds of journalists, podcast hosts, partners and community members: name, role, outlet or company, work email, website and profile links, the topics they cover and the workspace's notes, typed in or imported from a file, plus the pitches, briefs and invites the workspace writes to them and what happened (sent, replied, published). Echo never emails these people, never posts for the workspace, and never adds to, enriches, sells or uses the details for anything else: the workspace sends from its own mail. For this data the workspace is the controller and Echo processes it on the workspace's instructions (Art. 28 GDPR); the workspace relies on its own legal basis, usually its legitimate interest in contacting people professionally about their work (Art. 6(1)(f) GDPR), and informs them where the law asks it to. The details stay until the workspace deletes the contact (PR and events → Contacts) or the brand. Anyone listed can ask the workspace, or us, for access or deletion. For coverage links, Echo fetches the public page once when it's added and when someone checks it again.
- Audience research: when a workspace uses Settings → Brand → Audience, Echo reads data the workspace already keeps in Echo to find its buyers' segments, needs, objections and words: its prompts and AI answers, customers' answers to story questions, lead form answers (never the name, email or phone fields), replies to its email campaigns, community threads from PR and events, interview notes and call transcripts it pastes in or picks from Brand assets, and, when HubSpot or Attio is connected, contacts' job titles and companies and why deals were won or lost. Deal and contact notes from the CRM are read only when the workspace switches that on for the brand. Snippets of this text are sent to OpenAI (as for Echo's other analysis) to propose research items; each item stores short quotes from its sources so the team can check it. Nothing from this is sold, shared with other workspaces or used to train models. For this data the workspace is the controller and Echo processes it on its instructions (Art. 28 GDPR). Items, quotes and notes stay until the workspace deletes them or the brand; the team should avoid pasting notes with sensitive personal details.
- Email campaigns (leads): when a workspace uses email campaigns (Growth and Pro plans), Echo stores, for that workspace, the leads it adds: email address, name, company, website, role, notes and other columns it imports, where each lead came from and when they agreed to hear from the workspace. Echo also stores every mail it sent to a lead, the replies that come back to the sending address (forwarded to the workspace), and whether a lead unsubscribed, bounced or marked a mail as spam. For this data the workspace is the controller and Echo processes it only on the workspace's instructions (Art. 28 GDPR); the workspace needs the lead's consent or another legal basis for writing to them. The workspace can delete leads any time (More → Pipeline → Contacts). Addresses that unsubscribed, bounced or complained are kept, with only that fact, so they're never emailed again; they're deleted with the workspace. A lead can unsubscribe with the link in every mail, and can ask the workspace, or us, for access or deletion.
- Sources and industry benchmarks: to sort the websites AI answers cite (an editorial site, a forum, a review site …), Echo sends the cited pages' addresses and titles to OpenAI once and keeps only the kind of site and page, which every workspace shares because it describes a public page, not who cited it. To see whether a brand is already named on a page AI cites, Echo reads that public page now and then. When a brand picks its industry, its AI visibility and citation shares count toward that industry's benchmark: Echo shows only the middle value, and only once at least 10 brands from 5 different workspaces share the industry, so no company's own numbers can be seen or worked out. The workspace owner can keep the workspace out of every benchmark (Competitors → Against your industry); it then sees none either.
Google user data
This section covers the data Echo gets from Google when you sign in with Google or connect a Google account. Echo's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
- What Echo accesses: with "Sign in with Google", your name, email address and profile picture (scopes
openid,email,profile). If you connect Google for a brand, read-only access to Google Analytics (analytics.readonly: the property's visits by source, landing pages and key events) and Search Console (webmasters.readonly: clicks, impressions and positions by query and page). If you connect Google Tag Manager, access to your containers (tagmanager.edit.containers) to read tags and triggers and add the ones you ask for in a new workspace; Echo never publishes a container. - How Echo uses it: only to provide the features you see in Echo: signing you in, showing visits from AI assistants and search performance for your brand, before/after numbers on actions, your monthly AEO report, and setting up tags you ask for. Echo doesn't use Google user data for advertising, doesn't sell it, and doesn't use it to develop, improve or train generalised AI or machine learning models. People at Echo don't read it, except with your permission, for security reasons, to comply with the law, or when it's aggregated and anonymised for internal operations.
- Who it's shared with: Echo doesn't sell, rent or share Google user data with anyone, except: (1) Cloudflare, which hosts Echo and its database; (2) OpenAI, which receives weekly totals (never names or email addresses) only when it writes words for a feature you use: your monthly AEO report and answers from Echo's agent when you ask it about your traffic; under OpenAI's API terms this data isn't used to train their models; (3) members of your own workspace, who see the numbers in Echo; (4) tools you connect yourself and choose to share with: your own Claude or ChatGPT through Echo's connector, and the API keys and webhooks your workspace owner sets up. Each provider processes the data for us under a data processing agreement and only to run Echo. Echo may also disclose data if the law requires it, or as part of a merger or sale of the business, under the same protections.
- How Echo protects it: all traffic to and from Echo and Google is encrypted in transit (HTTPS/TLS). Google's access and refresh tokens are encrypted at rest with AES-256-GCM, with a key kept only in Cloudflare's secret store, and are never shown in the app, sent to the browser or written to logs. The database is encrypted at rest by Cloudflare. Every request is checked against the signed-in person's workspace, so nobody outside your workspace can read your data. Google Analytics and Search Console access is read-only.
- How long Echo keeps it and how to delete it: the weekly Analytics and Search Console numbers for 25 months. When you disconnect (Settings → Connections, or Website → Health → Tracking for Tag Manager), Echo revokes its access at Google and deletes the tokens and the imported numbers. You can also remove Echo's access any time at myaccount.google.com/permissions, delete your account in Settings → Account, or write to us to have everything deleted.
Cookies and local storage
Echo sets one cookie: the session cookie that keeps you signed in. It's strictly necessary, so we don't ask for consent. Your browser also remembers your light or dark theme and whether the sidebar is open (local storage, never sent to us). There is no analytics, advertising or tracking of any kind, with one exception: if you came to our website from one of our ads in ChatGPT, we ask whether we may measure the ad. Only if you allow it, OpenAI's pixel loads and sets three cookies (__oppref, the ad click, for 30 days, __obref, a random browser reference, for a year, and __oaiq_consent, your choice), we keep the ad click in a cookie of our own (echo_oppref, 30 days), and your browser remembers your choice (local storage). If you say no, nothing is loaded or set.
Emails
We send sign-in links, and, if you keep them switched on, a weekly report and drop alerts about your brand. You can turn these off in Settings → Notifications, or with the unsubscribe link in every email. The workspace owner also gets billing emails (a trial ending soon, a failed payment), which belong to the contract and can't be turned off.
Services we use
These providers process data for us under data processing agreements:
- Cloudflare (Cloudflare, Inc., USA) hosts the app and its database. Data may be processed outside the EU; Cloudflare is certified under the EU-US Data Privacy Framework and uses the EU Standard Contractual Clauses. When a workspace connects its own subdomain for landing pages, Cloudflare issues the certificate for it and serves the pages there; it receives the subdomain's name and the visitors' requests, as for any page Echo serves.
- Resend (Resend, Inc., USA) sends our emails. It receives your email address and the content of the email. Email campaigns go through a separate Resend account: it receives the lead's email address, the mail and the replies to it, and the workspace's sending domain.
- OpenAI (OpenAI, L.L.C., USA) answers the prompts and analyses the answers, websites and competitor changes. It receives your brand's name, website, description, competitors and prompts, and text from the websites Echo reads, but never your email address or name. Under OpenAI's API terms, this data isn't used to train their models. When you use the agent in the app, OpenAI also receives your messages, the files you attach, the Echo data the agent reads to answer, and your name and your workspace members' names (so you can assign work to them), never email addresses. OpenAI keeps these conversations for 30 days so a chat can continue, then deletes them. For email campaigns, OpenAI writes each mail from the lead's details (email address, name, company, website, role, notes), the campaign's goal and the earlier mails to that lead. For landing pages and Creative, OpenAI writes the copy and makes the images: it receives what you ask for (the prompt), the brand's voice, guidelines and facts, and the text of the page or design, and for a page imported from an address, that page's public text. Images are made without text, logos or real people, and are stored in the workspace's Brand assets.
- Your workspace's own OpenAI key, only if the workspace owner adds one (Settings → Usage): Echo stores the key encrypted and uses it for drafts, content briefs, the agent, email writing, customer stories and guideline checks. Those requests then go to OpenAI under your own OpenAI account and its terms, with the same data as above; Echo logs only their token counts and estimated cost. Removing the key deletes it at once.
- Claude or ChatGPT (Anthropic PBC or OpenAI, L.L.C., USA), only if you connect Echo to your own Claude or ChatGPT (Settings → Connections): when you ask it something, it reads through Echo's connector what you can see in the workspace you chose (brands, actions, AI visibility, prompts and answers, competitors, SEO, performance, campaigns, drafts, brand voice and guidelines, asset names and links, and your members' names), with email addresses hidden. That data then sits in your chat with that assistant, under your agreement with Anthropic or OpenAI, which Echo doesn't control. Changes it suggests are stored in Echo as proposals only you see until you apply them. Echo stores the app's name, which person and workspace it acts for, hashed access tokens and a log of each request (the tool's name and time, kept 90 days). Disconnect any time in Settings → Connections.
- Perplexity (Perplexity AI, Inc., USA) answers the prompts for Perplexity. It receives the prompts and the country they're asked from, nothing about you.
- Anthropic (Anthropic PBC, USA) answers the prompts for Claude through its API, with the same data as Perplexity. Under Anthropic's commercial terms, this data isn't used to train its models.
- xAI (X.AI LLC, USA) answers the prompts for Grok through its API. It receives the prompts, nothing about you.
- Google (Google Ireland Ltd.) answers the prompts for Gemini through the Gemini API, with the same data as Perplexity. On the paid Gemini API, Google doesn't use it to improve its products.
- DataForSEO (dataforseo.com) runs the prompts as Google searches, to read Google's AI Overviews. It receives the prompts and the country and language they're searched in, nothing about you. For SEO it also receives your brand's and competitors' website addresses and the keywords you track (checked on Google and Bing), and it crawls the public pages of your website for the monthly site audit (respecting robots.txt). For competitors' ads it receives the competitors' names and website addresses and your markets' countries, and returns their ads from Google's Ads Transparency Center. For Mentions it receives searches like site:reddit.com "your brand" and returns Google's public results. For Google reviews it receives your brand's and competitors' names and returns their public Google listings and newest reviews; Echo keeps the rating, the review's text and date and whether the business answered, never the reviewer's name, for 12 months.
- Brave Search (Brave Software, Inc., USA) answers searches in Brave's own index, so Echo can show whether your pages are found there and where your brand ranks for the keywords you track. It receives your website's address, page titles and those keywords, nothing about you or the people in your workspace. Echo keeps only whether a page was found and a position, never Brave's results.
- Bing Webmaster Tools (Microsoft Ireland Operations Ltd.), only if you connect it with your own API key: Echo sends it the addresses of your website's new and changed pages, so Bing (and the AI assistants that search with it) finds them sooner. Your key is stored encrypted.
- Stripe (Stripe Payments Europe, Ltd., Ireland) handles payments, invoices and VAT. When you choose a plan, Stripe receives your name, email address, billing address, VAT ID if you enter one, and your payment details, which go straight to Stripe. Stripe processes them for us and, for fraud prevention and its own legal duties, as a controller itself (see stripe.com/privacy). Data may be processed in the USA under the EU-US Data Privacy Framework and the EU Standard Contractual Clauses.
- OpenAI ads (OpenAI Ireland Ltd.), only if you came from one of our ads in ChatGPT and allowed measuring it: when you run the free AI score or create an account, OpenAI's pixel and our server tell OpenAI so, with the ad click, your IP address and browser, and your email address and account ID as SHA-256 hashes, so OpenAI can count which ads led to sign-ups (Art. 6(1)(a) GDPR, your consent; you can withdraw it by clearing this site's cookies and storage). Data may be processed in the USA under the EU Standard Contractual Clauses.
- Google (Google Ireland Ltd.) handles sign-in if you choose "Sign in with Google". Google tells us your name, email address and profile picture.
- Google Analytics and Search Console, only if you connect them for a brand (Settings → Connections): Echo reads, read-only, your property's weekly visits by source, landing pages and key events, and your site's search clicks, impressions and positions by query and page. Echo keeps these weekly numbers for 25 months and deletes them when you disconnect (which also removes Echo's access at Google).
- Google user data: Echo's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Echo uses Google Analytics, Search Console and Tag Manager data only to show you your own numbers and make the changes you ask for. It never sells this data, never uses it for advertising, never uses it to train AI models, and no person at Echo reads it unless you ask us to for support, for security or because the law requires it.
- HubSpot (HubSpot, Inc.), only if the workspace owner connects it: Echo sends your Outreach leads (name, email, company, website, campaign, status, consent) and replies to your HubSpot account, and reads contacts' email opt-outs, deals (name, amount, dates, stage) and where contacts first came from. HubSpot processes this for you as your CRM. With Company visitors, "Add to HubSpot" also creates the visiting company (name, website, LinkedIn page) with a note of its visits.
- Attio (Attio Ltd, UK), only if the workspace owner connects it: the same as HubSpot for your Outreach leads, replies and deals, and, with Company visitors, "Add to Attio" creates the visiting company with a note of its visits. Attio processes this for you as your CRM.
- Snitcher (Snitcher B.V., Netherlands), only for brands that switch on Company visitors: its tracker on that brand's website receives the visit (pages, referrer, browser and IP address) and finds the company behind the network. Snitcher processes it in the EU under its data processing agreement, in a workspace of its own for the brand; after a 14-day trial the workspace chooses and pays for Snitcher's plan directly. The footer of echo-aeo.com's public pages shows Snitcher's partner badge, loaded from app.snitcher.com, so your browser contacts Snitcher (your IP address and browser) when it shows the badge; no Snitcher tracker runs on echo-aeo.com.
- Google Tag Manager, only if you connect it for a brand (Website → Health → Tracking): Echo stores an access token (encrypted) that can edit your containers, reads your accounts, containers, tags and triggers, and adds tags and triggers in a new workspace when you ask. It never publishes: you do that in Tag Manager. Disconnect removes Echo's access at Google.
- Meta, LinkedIn and Google Analytics as recipients of your conversions, only if you switch them on (Website → Health → Tracking): see "Conversions sent to ad platforms" above. Your Meta Conversions API token and your Google Analytics Measurement Protocol secret are stored encrypted. These providers receive the data as your processors or as controllers under your own terms with them.
- LinkedIn (LinkedIn Ireland Unlimited Company), only if you connect it for a brand: Echo stores an access token (encrypted) to publish the posts you schedule, with their images or PDFs, and reads your name, profile picture, the company pages you administer and, for company-page posts, their statistics. Remove an account in More → Social any time.
- Hacker News search (Algolia, run for Y Combinator) and the Stack Exchange API (Stack Exchange, Inc.): Echo searches them for your brand's and competitors' names. Nothing about you or your visitors is sent.
- Meta's Ad Library API (Meta Platforms Ireland Ltd.): Echo asks it for your competitors' public ads by their names and Facebook page ids, with Echo's own access, not yours. Nothing about you or your visitors is sent.
- Meta (Meta Platforms Ireland Ltd.), only if you connect Meta ads for a brand: Echo stores an access token (encrypted) with read-only access to your ad accounts (
ads_read) and reads your name, the ad accounts you can see, and per campaign and day the spend, impressions, clicks and conversions. Echo keeps these daily numbers for 25 months and deletes them when you disconnect (which also removes Echo's access at Meta). Reading is all Echo does with this access. - Paid ads on Meta, only if someone in the workspace clicks "Allow Echo to create ads" for a brand: Echo then also holds the
ads_managementpermission and the Page permissions Meta requires for ads to run as your Facebook Page (listing your Pages and posting ads as them), and stores the wider token encrypted in the same way. With it Echo changes only the campaigns it created, and only on a person's click in Echo: it creates them paused, launches, pauses, resumes and ends them, changes their budgets and end dates, and uploads the images you picked from Brand assets together with the ads' text and links. On its own it only lowers spend: it pauses Echo's campaigns when the brand's monthly limit is reached, and when an ad costs far more than the others (only if you switch that on); if access is lost, it emails the workspace owners instead. Every hour it reads these campaigns' spend, results and review states, and keeps them, with a log of every change and who made it, while the brand exists. Campaigns you made elsewhere are only read, as above. The ads, the audiences you choose and your ad account's payment details stay with Meta under its own terms; Echo never sees or handles ad payments. - Google Ads (Google Ireland Ltd.), LinkedIn Ads (LinkedIn Ireland Unlimited Company), Microsoft Advertising (Microsoft Ireland Operations Ltd.), Reddit Ads (Reddit, Inc.) and X Ads (X Corp.), once each platform has approved Echo and only if you connect them for a brand: the same as Meta above. Echo reads spend and results per campaign, and creates and changes only the campaigns you build in Paid ads, on a person's click. Echo uses Reddit's ads API only for your own ad account; it never reads Reddit's posts or comments through it and never posts.
- ChatGPT ads (OpenAI), only if someone in the workspace pastes an Advertiser API key from OpenAI's Ads Manager for a brand: Echo stores the key encrypted, never shows it again, and deletes it when you disconnect (you can also delete it in Ads Manager). With it Echo reads the ad account's name, currency and time zone, its campaigns, and per campaign and day the spend, impressions, clicks and conversions, kept for 25 months like the other platforms. In Paid ads it creates and changes only the campaigns you build there, on a person's click, the same way as on Meta above, and uploads the images you picked from Brand assets with the ads' text and links. The ads and your ad account's payment details stay with OpenAI under its own terms.
- Forms: when someone signs up through a brand's form, Echo stores what they entered, the consent text they agreed to, the time, and a one-way hash of their IP address, and emails them a confirmation link. Only after they confirm do they become a lead the brand may email.
- Webhooks, the API, Zapier and n8n, only if the workspace owner sets them up (Settings → API and webhooks): Echo sends the events you pick (for example a form sign-up with the lead's name and email, a reply, an action) to the addresses you enter, and lets tools holding one of your API keys read and change the data that key allows. You choose these recipients; they process the data for you or under your own terms with them. Echo stores only a fingerprint of each API key, encrypts webhook secrets, and keeps the events and deliveries for 30 days. Playbooks email only leads who agreed to hear from you.
How long we keep data
We keep your data while you have an account. When you delete your account (Settings → Account → Delete account), we delete your account, the workspaces only you use (with their brands, prompts, answers and usage) and your memberships in other workspaces right away. A workspace other people use stays until its owner deletes it. The database's automatic point-in-time backups expire within 30 days.
Your rights
You have the right to access your data, to have it corrected or deleted, to restrict or object to its processing, and to receive it in a portable format. Most tables in Echo can be exported as CSV. For anything else, write to the email address above. You can also complain to a data protection authority, for example the Berliner Beauftragte für Datenschutz und Informationsfreiheit (Berlin Commissioner for Data Protection and Freedom of Information).
Data processing for customers
Where Echo processes personal data for a workspace (its leads, contacts, website visitors and the data from tools it connects), the workspace is the controller and Echo its processor under our data processing agreement (Art. 28 GDPR). How Echo protects data is on /security.
See also the imprint.