Data
How we measure and protect data.
What a measurement shows, what it does not prove, and what we do with each business’s data.
Measurement
What we measure.
- Real questions. We ask the AI engines the questions a customer would ask, in European Portuguese, and read the answers.
- Repeated. In the full report, each question runs 3 times on each engine: the same question does not always get the same answer.
- Three states. Named, not named or not measured yet. A question that failed stays not measured yet, counted apart from absences.
- Dated. Every number comes with the measurement date and the method version.
Limits
What a measurement does not prove.
- It does not guarantee tomorrow’s answer: engines change models and sources.
- The questions measured are a sample, not all the ones your customers ask.
- We ask programmatically, without a customer’s account. The phone app may answer differently.
- A before and after comparison does not prove the fix caused the change.
Fixes
Fixes with your approval.
- No fix goes onto your site without your approval.
- If a fix causes a technical error on the site, it is rolled back automatically, and we let you know by email.
- A drop in visibility does not roll anything back on its own: the decision is yours.
- We compare the 14 days before and after each fix. The result is one of four: positive signal, no detectable effect, insufficient evidence or negative signal.
Publishing
What we publish.
- The method, with its version and change log.
- Our own dated measurements, of sectors outside healthcare. They show the companies the engines named in their answers.
What we do not publish.
- Public rankings with the names of healthcare providers.
- The report of a check. It only opens with its link and stays out of search engines.
- A check’s data in a public list with the business name, without the owner’s consent.
Minimum
We keep what is needed.
- From a business’s site we read only the public content. We collect no data about the people who visit that site.
- Of the contacts published on a site, we keep only the general email, such as geral@ or info@, of companies, customers and businesses we sent an offer to by letter. We delete it 12 months after the last email we sent to it, and analysing the site again does not change that period. We do not keep addresses with a person’s name or the phone number; anyone who objects no longer has this data kept.
- In logs and internal alerts, emails, IP addresses and private links are masked.
Where
Where the data lives.
- Server and backups. In a data centre in Finland, in the European Union.
- AI engines measured. They receive the measurement questions, which may include the business’s name and city.
- Network and site protection. Requests to this site pass through an attack protection service, which receives the visitor’s IP address. The company is based in the United States, under the EU-US adequacy decision.
- Analytics for our site. A service in the European Union counts visits and, only if you accept, records browsing, with all text masked.
- Search data provider. It receives only the measurement questions, to put them to the search engines.
- Error reports. In a service in the European Union, with emails and IP addresses masked. The company is based in the United States, under the EU-US adequacy decision.
- Internal alerts. In a messaging service with servers in the United States, under the EU-US adequacy decision, with emails and IP addresses masked.
- Platform emails. A sending service with servers in the United States, under the European Commission’s standard contractual clauses.
- Payments. A payment institution in the Netherlands. Card details do not pass through us.
The full list, with the safeguard for each transfer, is in the privacy policy. To object, or to ask for a copy of your data, write to [email protected]. How we protect the server, and what to do if you find a flaw, is in security and data.