Europe · EN

Switzerland · CHF

Sign in Request your free first measurementRequest first measurementFirst measurement

Legal · Privacy

Privacy policy ECHO

Last updated: 17 November 2026

This policy describes the processing of personal data on echo-cockpit.com, in the ECHO GEO Tool and in the course of our work together.

Who is responsible

Pixels AG, Mühlemattstrasse 8, 6004 Lucerne, Switzerland, operates ECHO and echo-cockpit.com. For data protection matters, you can reach us at geo@echo-cockpit.com or on +41 41 539 17 59.

The Swiss Federal Act on Data Protection (FADP) applies, as does the EU General Data Protection Regulation (GDPR) where it is applicable.

We have not designated a representative in the EU under Article 27 GDPR. ECHO is aimed at businesses, does not process special categories of personal data on a large scale and processes personal data from the EU only occasionally and with low risk (Article 27(2)(a) GDPR). If you are in the EU, send your requests directly to geo@echo-cockpit.com.

Pixels AG is the controller for its own customer contacts, contract administration, invoicing and the security of operations across the service. We process personal data for the performance of a customer assignment on the client’s instructions and under the data processing agreement. This also covers the project accounts and project-related logs maintained on the client’s behalf. In agency projects, this may take place on behalf of an end customer. We coordinate requests concerning such data with the responsible client.

Website, contact and account

For operation, fault analysis and abuse prevention, we process the IP address, time, page path without URL parameters, response code, duration, data volume, browser identifier and, where applicable, the account ID. Security logs record, for example, sign-ins, failed attempts, role changes and data connections, together with account details, time and IP address.

For enquiries and first measurements, we need your company or brand, website and email address. Your name and message are optional. We also record the language, time, source and IP address. We use this information to answer your enquiry, carry out the measurement and prepare a quotation. The form cannot be submitted without the required fields. Alternatively, you can email us.

Through self sign-up at echo-cockpit.com/start, we use your details to create an account and a trial project. We send you a link to confirm. Until you use it, we measure nothing. After confirmation, we read your public website, suggest questions, check technical accessibility for AI crawlers and measure five questions once with the AI services (trial round). The legal basis is the trial contract under clause 5a of our terms and conditions. The data processing agreement you accept when signing up applies to the project data.

We check form submissions for abuse, for example based on the time taken to complete the form. We hold back suspicious submissions. If you receive no response, you can request a personal review by email.

Account data comprises name, email address, language, roles, password hash, sign-ins, notification settings and, where applicable, two-factor data and invitation or reset tokens. Authorised staff can open projects for support and operations. We log access in customer view. If you give feedback in the cockpit, we store it with your account and the time. Our support team receives an email notice with the category only, without your name, email address or text. We use feedback to respond to you and to improve ECHO.

For quotations, contracts and payment of invoices, we process company and contact details, billing address, services, prices, and invoice and payment information.

AI measurements and support functions

ECHO sends project questions with location and language context to the application programming interfaces (APIs) of the AI services, in some cases with web search. The measurement concerns these interfaces, not the consumer apps. We store and analyse answers, mentions, sources, links, search terms and result lists to show the visibility of companies.

For setup, question suggestions, translations, recommended actions, source classification, fact checking and briefings, one of the configured AI services receives, depending on the function, companies, brands, domains, competitors, website excerpts, facts, AI answers or project metrics. For question suggestions, we send up to 25 Search Console queries per run together with project context.

Questions, search queries, website texts and AI answers may contain personal data. We do not add contact details to measurement questions. Only enter information that you are entitled to use and disclose. The data comes from you, your connected services, public websites and AI and search answers.

The AI providers do not use our API requests to train their models. OpenAI and Anthropic generally retain inputs and outputs for abuse monitoring for up to 30 days. Under the paid tier of the Gemini API, Google retains them for a limited period for abuse monitoring. Perplexity does not state a fixed period.

Optional connections and exports

The connections are optional. Without them, the corresponding additional data is not available.

  • Google Search Console: After you grant read-only access, we store the property, search queries, page metrics, the Google account email address and an encrypted token. We filter recognisable email addresses and phone numbers out of search queries. Other references to individuals may remain. AI question suggestions are described above. When you disconnect, we delete the connection data and attempt to revoke access at Google. You can also revoke access in your Google account. Project questions already adopted and the time-limited record of the authorisation remain.
  • Cloudflare: Using your API token, we read aggregate figures on AI crawlers visiting your website. We store the token, the website assignment and daily values. We do not retrieve visitor IP addresses or individual visit paths in doing so.
  • Microsoft Clarity: Using your key, we read metrics and the associated raw data on pages, channels and sources. We do not retrieve individual session recordings. URLs and small groups may nevertheless relate to individuals. ECHO does not embed a Clarity tracker on its own website as a result.
  • Bing/Copilot: You can upload a report exported from Bing Webmaster Tools. We store the information imported from it, such as search queries, page URLs and citations, as well as the file name and checksum. ECHO does not query Microsoft or Copilot itself for this import.
  • Dashboards and API: Authorised dashboards retrieve project measurement values using a revocable key, which we store as a hash. The export covers questions, companies, websites and results, but no account email addresses, visitor IP addresses or complete AI answer texts. Questions and URLs may relate to individuals. The dashboard operator is responsible for any further use. The Google connector runs as Apps Script at Google.
  • Google results through DataForSEO: For enabled measurements of Google search results, AI Overviews, AI Mode or Shopping results, we send the question, language, selected search location and device type to DataForSEO.

When you disconnect Cloudflare or Clarity, we delete the respective access key. Metrics already imported remain stored until the project data is deleted. You can delete Bing imports individually.

Consulting and comparisons

For the agreed consulting, we process contact and project details as well as the content of conversations in order to prepare, conduct and follow up on the sessions. We agree duration and focus according to your individual needs.

With prior notice and the consent of all participants, we may record a conversation in order to send you minutes and the key findings afterwards. Consent is voluntary. Without it, the consulting session takes place without a recording. We use the recording exclusively for this purpose. Where the GDPR applies, the recording is based on Article 6(1)(a). You can withdraw your consent at any time with effect for the future at geo@echo-cockpit.com.

For consulting calls, we use Google Meet in the Google Workspace of Pixels AG. A Google Meet recording and its transcript are stored in the Google Drive of the person organising the call. We delete them once the minutes have been completed and sent. We send you the final minutes by email. They remain stored in our mailbox until twelve months after the end of the contract.

In addition to the individual competitor comparison, the cockpit shows aggregate comparison values. For this, we combine measurement results of the participating projects into group values. ECHO determines the groups. A group value appears only once at least five independent companies contribute to it. Other customers receive no individual project questions, answer texts, project names or contact details. The comparison is part of the agreed service and of the data processing agreement. You can switch off participation for each project. The project’s contributions are then dropped at the next calculation, at the latest when the project data is deleted.

We use these values for public metrics or our own reports only under a separate agreement.

Emails and product news

Brevo sends account messages, invitations, password resets, reports and briefings. Our internal mailboxes receive support copies of some of these messages, but not of password resets.

We send ECHO product news with promotional content with your consent or under an applicable statutory exception for existing customers. Every such email contains a free unsubscribe option. Unsubscribing does not affect necessary account, security and contractual messages.

Brevo counts in aggregate how often ECHO emails are opened and links in them are clicked. Brevo does not attribute these counts to any person. For this purpose, the emails contain a tracking pixel, and all links lead to their destination via a Brevo server. Brevo thereby technically receives the usual connection data such as IP address and browser details. We do not analyse any of this on a personal level. The legal basis is our legitimate interest in reliable delivery. If you do not load images in emails, no open is counted.

We keep measurement data from the pilot phase in Google Analytics 4 as well as open and click data from Brevo from the time before this version for no longer than twelve months from its entry into force and delete them afterwards.

Cookies, fonts and spam protection

The cockpit uses no analytics or advertising trackers. We serve fonts ourselves.

On the website, we use the LinkedIn Insight Tag only if you consent in the cookie notice. We use it to measure whether visitors open ECHO after seeing a LinkedIn ad. We also build audiences for our ads. For this purpose, LinkedIn receives the IP address, browser and device information, the page visited, the referring page and the time, and sets its own cookies. If you are signed in to LinkedIn, LinkedIn can link this information to your account. We receive only aggregate reports without information about individual persons.

LinkedIn processes the data as an independent controller under its own privacy policy. LinkedIn removes direct identifiers within seven days and deletes the remaining data within 180 days. The cookies, such as “bcookie”, “li_sugr”, “UserMatchHistory” and “AnalyticsSyncHistory”, remain stored for between 24 hours and one year. You can withdraw your consent at any time via “Cookie settings” at the bottom of the page. Your browser stores your choice in the “echo_li_wahl” cookie for twelve months.

In the cockpit, we use the “session” cookie for sign-in and security. It expires after twelve hours without use and at the latest seven days after sign-in. “echo_geraet” recognises a browser that has already signed in for 90 days and protects against abusive sign-in attempts. “lang” stores your chosen language for one year.

If you close the language notice on the website, your browser stores this locally under “echo-hinweis-zu”. The entry remains in your browser until you delete it. You can delete cookies and local storage in your browser settings. If you block cookies required for sign-in, you cannot use the cockpit while signed in.

We protect the request form on the website and the self sign-up in the cockpit with Cloudflare Turnstile. When the form loads, Turnstile checks in the background whether a person is using it. For this, Cloudflare, Inc., United States, processes the IP address and browser and device characteristics. Turnstile does not set advertising cookies. The basis is our legitimate interest in protection against automated requests and sign-ups. We also check submissions using a signed timestamp and the website domain provided.

Service providers and countries

The following services receive data as required for their tasks, as do authorised staff and, where necessary, professional advisers or authorities.

  • Hetzner: Hosting of the app, database and backups with the data stored in them. Company and processing countries: Hetzner Online GmbH, Gunzenhausen, Germany. Servers for the website and cockpit in Nuremberg, Germany. Encrypted backups on a Hetzner Storage Box in Germany.
  • Brevo: Email delivery with recipient details and email content, aggregate counting of opens and clicks without attribution to a person. Company and processing countries: Brevo GmbH, Berlin, Germany, together with Brevo SAS, Paris, France. Storage in France and Belgium. Support access is also possible from the United States and India.
  • OpenAI API: AI measurements and, where applicable, support functions with the content described above. Company and processing countries: OpenAI Ireland Ltd., Dublin, Ireland. Processing mainly in the United States and in further countries according to the OpenAI sub-processor list.
  • Anthropic API: AI measurements and, where applicable, support functions. Company and processing countries: Anthropic Ireland, Limited, Ireland. Processing also in the United States and worldwide in data centres and for support according to the Anthropic sub-processor list.
  • Perplexity API: AI measurements and, where applicable, support functions. Company and processing countries: Perplexity AI, Inc., United States. Processing in the United States.
  • Google Gemini API: AI measurements with Google Search and, where applicable, support functions. Company and processing countries: Google Cloud EMEA Limited, Dublin, Ireland. We use the paid Gemini API. Google does not use the inputs and outputs there to improve its products. Processing in all countries where Google operates data centres, including the United States.
  • DataForSEO: Retrieval of Google results with question, language, search location and device type. Company and processing countries: DataForSEO OÜ, Tallinn, Estonia. Processing in the EU, the United Kingdom and the United States. DataForSEO also maintains a location in Ukraine. DataForSEO stores queries for up to 365 days.
  • Google Search Console: Authorised retrieval of website and search data via Google OAuth. Company and processing countries: Google Ireland Limited, Dublin, Ireland, for your Google account. The Search Console interface is provided by Google LLC, United States. Processing also in the United States.
  • Cloudflare: Spam protection of the forms with Turnstile and optional retrieval of crawler metrics from the customer account. Company and processing countries: Cloudflare, Inc., United States.
  • Microsoft Clarity: Optional retrieval of metrics from the customer account. Company and processing countries: Microsoft Ireland Operations Limited, Dublin, Ireland, and Microsoft Corporation, United States. Storage in the Microsoft cloud, including the United States.
  • Google Apps Script: Execution of the optional dashboard connector and retrieval of project measurement values. Company and processing countries: Google Ireland Limited, Dublin, Ireland, in the Google account of the person who sets up the connector, or Google Cloud EMEA Limited, Dublin, for Google Workspace. Processing also in the United States.
  • LinkedIn: Insight Tag on the website after your consent, for measurement and audiences for our ads. Company and processing countries: LinkedIn Ireland Unlimited Company, Dublin, Ireland, and LinkedIn Corporation, United States.
  • Communication, consulting, administration and operations: Customer correspondence, email copies, calls, invoices, accounting and, where applicable, support and development data. Company and processing countries: Google Workspace (Gmail, Meet, Drive) of Google Cloud EMEA Limited, Dublin, Ireland, with data centres also outside Europe. The mailbox geo@echo-cockpit.com is hosted by cyon AG, Basel, in Switzerland. We manage quotations, time tracking, invoices and accounting in pixelcockpit, software we operate ourselves on servers of Hetzner Online GmbH in Germany.

Where data is processed outside Switzerland or the EEA, we use the transfer mechanism that applies to the respective recipient. For Brevo (support from the United States), Cloudflare, Google, Microsoft and LinkedIn, this is the Swiss-U.S. Data Privacy Framework under which the respective US company is certified. For OpenAI, Anthropic, Perplexity and DataForSEO as well as for support access from India, it is the standard contractual clauses of the European Commission recognised by Switzerland, with the adaptations required by the FADP.

You can request the applicable safeguards at geo@echo-cockpit.com, with any necessary redactions.

How long we keep data

The following periods apply. We keep required statutory records or evidence relating to an incident or legal dispute separately and with restricted access until the reason no longer applies.

  • Technical access and operating logs: 30 days at most. If an assignment ends earlier, assignment-related data follows the return and deletion rules of the data processing agreement.
  • Security and audit log: Twelve months at most from the entry. If an assignment ends earlier, assignment-related data follows the return and deletion rules of the data processing agreement.
  • Closed enquiries without a contract: Twelve months after handling is completed.
  • Form submissions held back as spam: 30 days after receipt.
  • Account and project data, including measurements, answers, briefings and imported metrics: During the contract and any applicable contractual or statutory retrieval period for switching providers and export. You receive an export on request within 30 days. Before the contract ends, we let you know by email that we will delete the data afterwards. At the latest 30 days after the end of the contract, we delete the active data and confirm the deletion to you by email. After that, the data is no longer available, not even to us. Removed team memberships and hidden questions do not by themselves trigger a complete deletion of all earlier data.
  • Self sign-ups without confirmation: We delete the account, trial project and sign-up 30 days after sign-up if you do not use the confirmation link.
  • Trial projects without a subscription: The trial ends 30 days after confirmation. Seven days before, we remind you by email and tell you the deletion date. When the trial ends, you receive another notice. 30 days later, we delete the trial project and project data and your account, unless it belongs to another project, and confirm the deletion to you by email.
  • Feedback in the cockpit: We delete the text twelve months after receipt, or earlier with your account. After that, we only evaluate ratings without text without any link to an account or project.
  • Temporary storage for Bing bulk imports: One hour at most. The imported project data remains subject to the project period stated above.
  • Record of former Google authorisations: As long as Google limits the number of accounts for unverified applications, we store for each authorisation only a hash of the Google account email address, the project code and the time. We delete the record after verification by Google, at the latest 24 months after the last authorisation.
  • Consulting recordings, any working transcripts and minutes: We delete the recording and any working transcript once the minutes have been completed and sent. The final minutes remain stored as an email in the customer correspondence until twelve months after the end of the contract.
  • Consent records and unsubscribe suppression list: Consent records until three years after withdrawal or the end of the account. The suppression list contains only the email address and the date of unsubscribing. We use it solely to avoid sending further marketing emails. We keep it for as long as we send product news.
  • Business records subject to statutory retention: Accounting books and accounting vouchers generally for ten years after the end of the financial year concerned.
  • Backups: Daily backups for 14 days, weekly backups for 56 days at most.

Display limits of a plan are not deletion periods. Deleted data may remain in protected backups until it is overwritten. We do not use these backups in ongoing operations. After a restore, we reapply any deletions that are due. Provider periods for API requests are stated above.

Your rights

Subject to the conditions of the applicable law, you can request access, correction and deletion as well as the release or transfer of your data. Where the GDPR applies, you can also request restriction of processing and withdraw consent at any time with effect for the future. Withdrawal does not affect the lawfulness of earlier processing.

Objection: You can object, on grounds relating to your particular situation, to processing based on legitimate interests under Article 6(1)(f) GDPR. We then assess whether continuing the processing is legally permitted. You can object at any time, without giving reasons, to the use of your data for direct marketing. This also applies to any related profiling.

Write to geo@echo-cockpit.com. We ask only for the proof of identity that is necessary. We generally respond to access requests within 30 days under the FADP and within one month under the GDPR. We inform you in good time of any permitted extension.

You can contact the Federal Data Protection and Information Commissioner (FDPIC). Where the GDPR applies, you can lodge a complaint with a competent data protection supervisory authority, in particular in the place of your habitual residence, your place of work or the place of the alleged infringement.

We do not make decisions based solely on automated processing that have legal effects or similarly significant effects. A person reviews form submissions that have been held back.

We protect data through appropriate technical and organisational measures, including encryption in transit, password hashes, encrypted connection tokens and role-based access. If our processing changes, we update this policy and also inform you where required.