Legal
Privacy Policy
Last updated: 20 November 2026
This translation is for reference only. If the two differ, the European Portuguese version prevails.
Translation under review. We have not reviewed this translation yet. For legal purposes, read the European Portuguese version.
Your right to object
You can object at any time, free of charge and without giving reasons, to our sending you marketing emails. Use the unsubscribe link at the end of any marketing email from us, or write to [email protected]. From then on we stop sending marketing emails to that address, for every check in which you left it.
You can also object to any processing we carry out on the basis of our legitimate interest, including the analysis of your business’s site and our sales prospecting (see businesses whose site we analyse).
1. Who we are
Notado (notado.pt) is a product of Voidstep, Lda., tax number (NIPC) 518857948, with its registered office at Rua Alto do Moinho de Vento, n.º 32, 3.º Dto., 2615-285 Alverca do Ribatejo, Portugal (“Notado”, “we”). We are the controller of the personal data described in this policy. For any question about privacy: [email protected].
When a business customer entrusts us with personal data in its projects (for example, the access logs of its website’s server), that customer is the controller of the data and we process it on the customer’s behalf, under the data processing annex of the Terms of Service.
We have not appointed a data protection officer. The law does not require one for our activity: we do not monitor people regularly and systematically on a large scale, and we do not process special categories of data.
2. What we use your data for, and on what basis
Free check. We collect the address of the site to analyse and the sector you choose. Your email is optional. When you leave your email in a check form, we use it to send you the report you asked for. Legal basis: steps taken at your request before entering into a contract (Article 6(1)(b) GDPR). Only once you type the email does a short box appear, which starts unticked: if you tick it, you also accept the emails about the check described under “Follow-ups to the check”, with an offer of our paid services. Without the box ticked, you receive the report and nothing else.
Origin of the visit. With each free check we keep where you came to the site from, on the first page you opened in that tab: the campaign tags in the address (utm), that page and the domain of the site you came from. Until you choose in the cookie notice, they stay only on the open page. If you accept analytics or advertising, they stay in the tab’s storage until you close it, and we also keep a cookie with the first and the last origin of your visits for 6 months. That cookie goes with the payments you make, so that we know which channels bring customers; of the ads, it keeps only whether the visit came from a click, without the click identifier. If you decline, the origin goes only with a check requested on that same page and with the payment for that check’s report, nothing stays in the browser and we delete the cookie. The ads’ click identifiers stay only in the browser and go with the check only if you have accepted advertising (see cookies, site analytics and advertising). Legal basis: our legitimate interest in knowing which campaigns bring checks and customers (Article 6(1)(f) GDPR), with the cookie subject to your consent (Article 5 of Law 41/2004).
Bot protection. When you open a page with the free check form, the pricing questions form, the demo booking form or a free tool, a bot protection service confirms that the request comes from a person, using the IP address and technical data from your browser, before we spend money measuring the site. On most visits you see nothing; a box to tick appears only when the service is in doubt. We do not accept addresses from temporary email services. Legal basis: our legitimate interest in stopping abuse (Article 6(1)(f) GDPR).
News by email. If you tick the news box on the free check report page, which starts unticked, we send you news about Notado by email. We keep the version of that box’s text and the date you ticked it. Whoever ticked it before 12 November 2026 ticked it in the check form. Legal basis: your consent (Article 6(1)(a) GDPR, and Article 13-A of Law 41/2004). You can withdraw it at any time, through the link at the end of each email or by email to [email protected].
Monthly newsletter. If you ask for the newsletter in a guide, in a study or on the guides page, we keep your email, the version of the text you saw and the date of the request, and we send you an email with a link to confirm. Only after you open that link and press the button do you start receiving one edition a month, with the month’s studies and guides. Each edition includes the link to unsubscribe. Without the confirmation, we send you nothing more. Legal basis: your consent (Article 6(1)(a) GDPR, and Article 13-A of Law 41/2004). You can withdraw it at any time, through the link in each edition or by email to [email protected].
Personalised ads with your email. If you tick the personalised ads box, a separate box on the free check report page that also starts unticked and has its own text version, we send your email to the advertising platforms where we advertise (see who receives the data) so that they show you Notado ads. Before it leaves, we turn the email into a code (a hash), and the platform calculates the same code from the emails of the accounts it already has, to find yours, if you have one. The code is still personal data: its purpose is to recognise you. Legal basis: your consent (Article 6(1)(a) GDPR). You can withdraw it at any time, through the link at the end of each email or by email to [email protected]: your email leaves the next list we send to the platforms.
Follow-ups to the check. If you confirm your address through the link in the report email, we send up to three more emails about that check, three, seven and fourteen days after the confirmation: what the AI engines answered, an offer of our paid services and a last email. We send them only in the 21 days after the check. Whoever confirmed between 22 October and 11 November 2026 accepted a text that spoke of an offer of the full report or of a call, and receives the emails of that text. Whoever confirmed before 22 October 2026 receives the two emails of the text they accepted, in the 14 days after the check: the problem that weighs most on their site and, three days after the check, an offer of our paid services (the full report or monthly monitoring). Legal basis: your consent (Article 6(1)(a) GDPR, and Article 13-A of Law 41/2004). You can withdraw it in any email, through the link at the end of the message.
Waiting list for the full report. The full report stopped being sold on its own on 11 November 2026. If you left your email on the waiting list, we use it only to tell you that purchases have opened. Legal basis: your consent, given in the box on the form (Article 6(1)(a) GDPR).
Purchase of the full report. We sold the full report on its own until 11 November 2026. From those who bought it, we asked for the email, to deliver the report, and the tax number (NIF), if they wanted the invoice to show it. Legal basis: performance of the contract (Article 6(1)(b) GDPR) and, for the invoice, a legal obligation (point (c) of the same paragraph).
If you bought the full report, we may send you suggestions from Notado about similar services by email, such as monthly monitoring. Legal basis: our legitimate interest in offering existing customers services similar to the ones they bought (Article 6(1)(f) GDPR), under Article 13-A(3) of Law 41/2004. You can object to these suggestions at any time, free of charge and without giving reasons: at payment, in a box that starts unticked, and in any email, through the link at the end of the message (Article 21 GDPR).
If you ordered the Arranque, we may send you, on the same basis and in the order’s emails, suggestions of our plans. You can refuse them on the order page, in a box that starts unticked, and in any of those emails, through the link at the end of the message.
Record of what you accepted. With your address, we keep the form where you left it in each check (the first one, or the purchase, if you bought the report), the version of the last text you accepted (the form box’s or, if you confirmed the follow-ups, the confirmation’s), the date of the confirmation, the version and date of each optional box you ticked (news and personalised ads, each with its own version) and the date on which you unsubscribed or refused. It is the proof that Article 7(1) GDPR asks of us and the list that Article 13-B(1) of Law 41/2004 requires us to keep.
Account on the platform. Name, email, password (stored irreversibly, so that nobody can read it) and the data of the projects you create (domain, questions, competitors, metrics). Legal basis: performance of a contract (Article 6(1)(b) GDPR). When you create an account, we keep the date on which you accepted the Terms of Service and the versions of the Terms and of this Policy in force on that day, and your answer to “How did you hear about us?” (“Como nos conheceu?”), so that we know which channels bring customers.
Signing in with your Google account. If you choose “Continue with Google” (“Continuar com o Google”), Google (Google Ireland Limited) sends us the name, the email and the identifier of your Google account, which we use only to create your account and to open it when you come back. We do not keep the profile photo that Google also sends. Legal basis: performance of a contract (Article 6(1)(b) GDPR). Here too we keep the date and the versions of the Terms and of this Policy that you accepted.
Teams. When a member of an organisation invites a colleague, we use the email they give only to send the invitation. The address stays in the sending queue until the email goes out and joins the organisation only when the colleague accepts the invitation. Legal basis: the legitimate interest of the organisation, and our own, in giving access to the team it chooses (Article 6(1)(f) GDPR).
Alerts. If the team gives another address to receive the alerts of a site, we keep that email, with the chosen frequency and the date it stopped receiving them, for as long as the site exists. Each alert includes a link to stop receiving them, with no account needed. Legal basis: the organisation’s legitimate interest in alerting whoever it chooses (Article 6(1)(f) GDPR).
Subscriptions, orders and billing. Billing details (name, tax number (NIF), address) when you subscribe to a plan or order a service. When you accept an order, we keep the email, the IP address and the date of acceptance, as proof of the contract. Legal basis: performance of a contract and legal obligations (invoicing and accounting). After the first payment, if you book the kick-off call, we keep the time with the organisation and who booked it, and we send the invitation and the reminder the day before to the account’s email. The invitation includes the video call link, created for that booking. We do not record the calls: the notes our team writes by hand about what we agreed stay in your organisation’s record, as text, with no content from any recording. Legal basis: performance of a contract.
How you heard about us. When you answer the question “How did you hear about us?” (“Como nos conheceu?”), in the demo request, at sign-up or in the initial setup, we keep the option you chose and, if you choose “Other” (“Outro”), the short text you write (up to 120 characters), with the organisation, next to the measured origin of the visit. It tells us which channels bring customers. Legal basis: our legitimate interest in understanding how people reach us (Article 6(1)(f) GDPR). The answer is optional and you can object to it at any time.
Team notes and internal access. Our team may write notes about your organisation in the customer record, for example after a call or a request by email. Only the team sees them; they stay for as long as the organisation exists and leave with it. We log the team’s access to the internal panel (who, when and which page), in a log that nobody can change without leaving a trace. Legal basis: performance of a contract and our legitimate interest in providing the service and protecting your data (Article 6(1)(b) and (f) GDPR).
Monitoring and business profile. To measure the visibility of your business, we send questions to the AI engines (see who receives the data), which may include the name and the city of the business. When you set up a project, we send OpenAI up to 3,000 characters of the visible text of your site’s home page, to propose the business profile. Legal basis: performance of a contract.
Recording of your browsing on the platform. Only if you agree, we record your browsing on the platform so that we can fix problems (see cookies, site analytics and advertising). Legal basis: consent (Article 6(1)(a) GDPR), asked for within the platform and which you can withdraw at any time in Account (“Conta”).
Integrations you connect. If you connect Google Search Console, Google Analytics, Bing Webmaster Tools or WordPress, or if you send us the access logs of your website’s server, we process that data on behalf of your company, under the data processing annex of the Terms of Service. From the access logs we keep only the visits of AI bots and, per day, how many visits came to each page from an AI answer, with no IP addresses, browsers or cookies.
Google Search Console. With your authorisation, and with read-only permission, we read the searches, the pages, the clicks and the impressions of your site over the last 28 days, to show them in your project. We keep these figures in temporary memory for 15 minutes and we do not send them to AI engines or to other third parties. You can withdraw access at any time, on the platform or in your Google account. The 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.
Google Analytics. With your authorisation, and with read-only permission, we read, for each day, how many sessions on your site came from an AI answer and on which page they started, to show them on the AI traffic screen (“Tráfego vindo da IA”). We keep only those counts, with no data about who visited the site, and we do not send them to AI engines or to other third parties. You can withdraw access at any time, on the platform or in your Google account. The 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.
Support. When you write to us at [email protected], through the questions form on the pricing page or through the support form on the platform, we use your name, your email and your message to reply to you. Legal basis: performance of the contract, if you are a customer, or our legitimate interest in replying to whoever contacts us (Article 6(1)(f) GDPR). When support triage is on, the name, the email and the message you send us go through OpenAI, to classify the request and prepare a draft reply that we review before sending. We ask OpenAI not to store the response. OpenAI does not use these requests to train models and may keep them for up to 30 days to detect abuse.
Demo request. When you ask for a demo through the booking form, we use your name and email, the name and the site of the business, what you represent, its size (addresses, locations or clients, in ranges), how you heard about us and the day and time you choose, to book and prepare the conversation, which includes measuring the site you give before it. We send the confirmation to the email you give, with the calendar invitation and the video call link, created for that booking. We do not record the call. If the request comes from a personal email, our team confirms it first. Legal basis: steps taken at your request before entering into a contract (Article 6(1)(b) GDPR). The request arrives in our mailbox and follows the triage described in the previous paragraph.
Security and running of the service. To protect the service, stop abuse and fix errors, we process the IP address, the browser and the time of each request, the email and the IP of failed sign-in attempts and the technical logs of the application. In the logs, the error reports and the internal alerts, we mask emails, IP addresses, keys and private links. Legal basis: our legitimate interest in keeping the service secure and running (Article 6(1)(f) GDPR).
Site analytics and ad measurement. Only with your consent, given separately for each, as the section on cookies, site analytics and advertising explains.
3. Businesses whose site we analyse
Anyone can request a check of any site, and we also analyse sites to measure the market. If the site we analyse is your business’s, this section tells you what we keep without your having given us the data directly (Article 14 GDPR).
- What data: the name of the business, the domain, the city, the result of the analysis, the link to the contact form and, in the cases described below, the general email published on the site. We also keep the answers of AI engines that cite the business.
- Where it comes from: the public content of the site itself (pages, robots.txt, sitemap) and the answers of AI engines. We do not collect data about the site’s visitors.
- What for: to deliver the check to whoever requested it; to measure, in aggregate, how ready the sites of businesses are for AI (the Notado Index) and which businesses the AI engines name; and to present our services to those businesses. We analyse the sites in our database again every week, to measure how they change. We send the name and the city of the business to the AI engines, in the measurement questions.
- Legal basis: our legitimate interest in these three purposes (Article 6(1)(f) GDPR). In most cases this is company data; it becomes personal data when the business is a natural person or the email contains a person’s name. We weighed that interest against your rights: we read only public content, when we publish the Index it shows only aggregate figures with no business names, and the check reports are private (only whoever has the link can open them, and they stay out of search engines).
- How we contact businesses: we may write to companies at the general address published on the site (for example, geral@ or info@), if the company is not on the opt-out list kept by the Directorate-General for Consumers (Direção-Geral do Consumidor). To natural persons, and to addresses with a person’s name, we send emails or call only with their consent; without it, we write only by letter. Each contact says where the data comes from and how to refuse.
- What we keep: of the contact details published on the site, only the general email (for example, geral@ or info@) of companies, of customers and of businesses to which we sent an offer by letter. We do not keep addresses with a person’s name, or phone numbers.
- For how long: we delete the general email we read on the site 12 months after the last email we sent to it, or 12 months after we stored it, if we never wrote to it. Analysing the site again does not restart the period.
- How to object: write to [email protected]. We delete the email we read on your site, stop storing it in later analyses and stop sending to that address.
- People named in the answers: an AI engine’s answer may name other businesses and people, for example a professional who works on their own account. We keep the answer as the engine gave it, and the customer who follows that question sees those names in their account. Legal basis: our legitimate interest in showing the customer what the engines answer (Article 6(1)(f) GDPR). If your name appears in an answer and you want us to remove it, write to [email protected].
4. Required data and automated decisions
To create an account we need your name, your email and a password, or your Google account. To deliver the paid report we need your email; the tax number (NIF) is optional and serves only for the invoice. The free check works without an email: without it, we do not send you the report by email. We require nothing else.
We do not take decisions about people based solely on automated means, including profiling, that produce legal effects concerning them or affect them in a similar way (Article 22 GDPR). The scores of the check and of the monitoring assess sites and the answers of AI engines, and support triage only classifies messages that a person reads and answers.
5. Who receives the data
These providers process data on our behalf, each one only for the function stated. For each one we state where the data stays and, outside the European Economic Area, the safeguard for the transfer.
- Hosting: a hosting service keeps the server, the database and the backups, in a data centre in Helsinki, Finland (EU).
- Network and site protection: a DNS and attack protection service. Requests to notado.pt go through its servers, including the IP address of whoever visits. The company has its head office in the United States and servers in several countries; the transfer relies on the adequacy decision for the EU-US Data Privacy Framework, which it has joined.
- Bot protection: a bot protection service receives, in the free check form, in the pricing questions form and in the demo booking form, the IP address and technical data from the browser, to confirm that the request comes from a person. It is the same company as the network and site protection, with the same transfer safeguard.
- Reading sites: when the page of a project’s site only shows its text after loading in a browser, a remote browser service opens that public page so that we can propose the business profile. It receives only the public address of the page, with no data from your account. It is the same company as the network and site protection, with the same transfer safeguard.
- Sending emails: an email sending service delivers the emails of the platform (reports, notices, invitations and billing). Its servers are in the United States and keep the content and sending data of each email for 45 days. The transfer relies on the European Commission’s standard contractual clauses, included in the service’s terms. We do not record whether you open our emails or which links you click.
- Receiving emails: a service in France (EU) receives the emails sent to notado.pt addresses and keeps them in our general mailbox, with the same service. A copy goes to the company’s mailbox, hosted by a service in Portugal. Internal email notices (payments received, plan requests and operations notices), which may carry the payer’s email, tax number and billing address, also go to a team mailbox at an email service with its head office in the United States, and the transfer relies on the adequacy decision for the EU-US Data Privacy Framework, which the company has joined.
- Video calls and calendar: a calendar and video call service creates the event and the link of the demo and of the kick-off call. It receives the name, the email, the booked time and the title of the event. The servers may be outside the European Economic Area, and the transfer relies on the EU-US Data Privacy Framework, which the company has joined, and on the European Commission’s standard contractual clauses.
- Invoicing: an invoicing program in Portugal issues the invoices, with the billing details you give.
- Error reports: an error tracking service keeps the application’s error reports in the European Union (Germany). We mask emails, IP addresses, keys and private links before sending. The company has its head office in the United States: any access from there relies on the adequacy decision for the EU-US Data Privacy Framework, which it has joined.
- Visit counting: a statistics service that uses no cookies receives the page viewed and the funnel step, with no IP address stored and no data that identifies you (see cookies, site analytics and advertising).
- Site analytics: an analytics service, with servers in the European Union (Frankfurt), counts the visits to the site, the platform and the report, and records browsing (see cookies, site analytics and advertising). The company has its head office in the United States: any access from there relies on the adequacy decision for the EU-US Data Privacy Framework, which it has joined.
- Internal alerts: a team messaging service receives alerts about application errors, operations notices and sales. We mask emails, IP addresses, keys and private links before sending. The alerts stay on servers in the United States, and the transfer relies on the adequacy decision for the EU-US Data Privacy Framework, which the company has joined.
- AI engines consulted: OpenAI, Anthropic and Perplexity, and Google and Microsoft through search data providers. They receive the monitoring questions, which may include the name and the city of your business, and the text of the answers. The text of the answers goes only to OpenAI, which reads the tone with a fixed model, without web search. OpenAI also receives the public text of your site’s home page during the setup of a project, to propose the business profile, and, when support triage is on, the support messages. Outside support triage, the data of your account does not go to the engines.
- OpenAI (OpenAI Ireland Ltd, with servers in the United States): does not use the requests to train models and keeps them, with the answers, for up to 30 days. The transfer relies on the standard contractual clauses of the data processing agreement that OpenAI’s contract includes.
- Perplexity (Perplexity AI, Inc., United States): the transfer relies on the standard contractual clauses of the data processing agreement that the terms of Perplexity’s API include.
- Search data providers: they put the questions to Google Search (AI Overviews and AI Mode), to Google’s Gemini, to the ChatGPT app and to Bing’s Copilot, and return the answers to us. They receive only the monitoring questions; outside the European Economic Area, the transfers rely on the European Commission’s standard contractual clauses.
Our payment service provider, with its head office in the Netherlands, processes the payments and handles the payment data as a controller, under its own privacy policy. Card or bank account details stay only with the provider. With each plan payment, the provider also receives the name of the organisation, the email of whoever subscribed and, if you gave them, the billing name and the tax number, which we use to issue the invoice.
Advertising platforms. Only if you accept advertising in the cookie notice, the platforms where we advertise receive from your browser the visit, the check request and the payment for the report, with the amount, to measure our ads and to show you personalised ads from us. Only if you tick the personalised ads box, they also receive your email turned into a code (see what we use your data for). They are Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland), for Google ads, and Meta Platforms Ireland Limited (Merrion Road, Dublin 4, Ireland), for Facebook and Instagram ads.
With Meta, in collecting these data and sending them, we are joint controllers (Article 26 GDPR). In essence, the agreement between us shares out the responsibilities as follows: it falls to us to ask for your consent, to inform you in this policy and to send data only with that consent; it falls to Meta to protect the data it receives and to answer requests about your rights regarding what it keeps. Google processes the data it receives as an independent controller, under its data protection terms for ads. You can exercise your rights with us or with each platform. Once they receive the data, each platform processes it as a controller, under its own policy: Google’s privacy policy and Meta’s privacy policy, and Meta’s joint controller addendum. Both may transfer data to the United States, under the adequacy decision for the EU-US Data Privacy Framework, which they have joined.
When you sign in with your Google account, and in Google Search Console and Google Analytics, Google Ireland Limited processes the data of your Google account as a controller, under its own privacy policy, and sends us the data stated under what we use your data for.
If we add or replace a provider, we update this list before we send it any data. If you ask us, by email to [email protected], we tell you who each provider is and send you a copy of the safeguards for transfers outside the European Economic Area.
7. How long we keep data
| Data | Period |
|---|---|
| Unconfirmed email left in a check form or on the waiting list | We delete the contact details you leave in a free check and never confirm 12 months after we receive them. |
| Email confirmed for the follow-ups, and customers of the report | We keep the contact for up to 24 months after the last contact: the date we received it, the confirmation, the last email we sent you or, if you are a customer, the purchase. |
| News and personalised ads boxes ticked | The version of the text and the date of each box stay with your email, for the period of the email stated above. The code of your email leaves the next list we send to the advertising platforms after you withdraw your consent. |
| Newsletter request not yet confirmed | If you do not open the confirmation link, we delete the request 30 days later. |
| Confirmed newsletter | For as long as you receive it. When you unsubscribe, we keep the address marked as unsubscribed, so that we do not write to you again without a new request. You can ask for deletion at any time. |
| Origin of the visit kept with the check | Stays with the check, with no name or email. |
| Refusal of marketing emails | The address stays marked as a refusal until the end of the period above. After that, or after we delete your data, only a code calculated from the address (a hash) remains, kept for as long as we send marketing emails. |
| Email and tax number (NIF) of a payment you did not complete | If you start paying for a report and do not complete the payment, we delete the email and the tax number (NIF) you gave 7 days after the payment lapses. |
| Email and tax number (NIF) of a paid report | We delete the tax number (NIF) as soon as we issue the invoice; the invoice keeps it for the period that tax law requires. The email stays with the check, for the delivery, the guarantee and support, and we delete it 24 months after the payment, or earlier, if you ask for deletion or delete the account. |
| Result of the analysis of a site | We keep it for as long as we keep the series of market measurements, because it describes the site. We delete the full answer of each AI engine after 90 days; what we measured in it remains. |
| Exploration of a brand | We delete the text and the full answer of each AI engine after 90 days, or 30 days after you cancel the plan, if that comes first; the record of the question, the engine and the sources remains. |
| Code of the full answer | When we delete the full answer of an AI engine, we keep a code calculated from it (a hash), without the text, to prove what we measured. It stays for as long as the measurement exists. |
| General email read on the site of a business | 12 months after the last email we sent to it, or after we stored it, if we never wrote to it. |
| Account and projects | For as long as the account exists. When you delete it, we delete what the section on deleting the account describes. |
| Account with an email never confirmed | We delete an account 30 days after its creation when its email was never confirmed and the account has no projects or payments. If you change the email of the account, the account remains while you confirm the new address. |
| Demo requests | We delete them 24 months after the last message exchanged about the request, like the emails in our mailbox, or earlier, at your request. We keep the booked time without the name or the email, so that we do not offer it to someone else. |
| Demo and kick-off calls | We do not record them. The booked time and the link follow the period of the demo request or of the organisation. The notes of the team leave with the organisation. |
| Answer to “How did you hear about us?” | Stays with the organisation, or with the demo request, and leaves with them. |
| Notes of the team and log of access to the internal panel | The notes, for as long as the organisation exists. The access log, for the period of the platform’s audit log, which nobody can change. |
| Support messages | We delete the messages you send to support, and the drafts of our replies, 24 months after your last message. The emails that reach our mailbox follow the same period. |
| Acceptance of an order (email, IP and date) | For as long as it serves as proof of the contract. |
| Approval of a text published on a healthcare site | After you delete the account, we keep for 5 years the published text, the professional who approved it, the reference and the date of the approval, and the name and email of the account that recorded it. |
| Invoices | 10 years, in our invoicing program (legal obligation). |
| Password reset requests | Password reset requests expire after 60 minutes, and we delete them by the following day. |
| Session (IP and browser) | The session ends after 2 hours without activity, and an automatic clean-up deletes the row with the IP and the browser afterwards. |
| Failed sign-in attempts and request limits | We delete the technical records of failed sign-in attempts, with the email and the IP, two days later at most. |
| Logs of the application and of the web server | 14 days. We mask emails, IP addresses, keys and private links in the application logs before writing the log. |
| Log of operations on the account and the payments | 90 days. It keeps the identifiers of each operation, with no name or email. |
| Queued tasks that failed | 14 days. |
| Visits of AI bots in the logs you send us | When you send us the access logs of your server, we keep the details of each visit of an AI bot, with the IP masked, for 30 days. If you connect the site with the collection script we give you, the script sends only the requests of AI bots and the visits that come from AI answers, with no IP address, and the country comes from the field that the platform of your site provides. We keep the details of the requests for 30 days. After that, only the daily totals remain, while the plan is active. |
| Text of the answers of AI engines, after you cancel the plan | We keep the text of the answers and the full answer of each engine while the plan is active and delete them 30 days after you cancel. You can ask us to delete them straight away, before then. |
| File with your data, prepared at your request | We delete from our servers the file with your data that we prepare at your request 30 days later. |
| Database backups | Less than 30 days. Data deleted from the platform also leaves the backups when the last backup that contains it expires. |
| Emails sent, in the email sending service | 45 days. |
| Error reports | 30 days. |
| Internal alerts | 90 days. |
| Site analytics | Events: 1 year on the free plan or 7 years on a paid plan. Browsing recordings: 30 days. |
Sales log: 400 days. For each sale, it keeps the amount, the payment reference, the plan and the billing period or the type of service and the instalment, and the internal numbers of the user, the organisation, the check, the order or the waiting list contact, with no name, email or tax number (NIF). Plan requests, waiting list sign-ups and new accounts stay in the log in the same way. It lets us prove each sale and answer a payment dispute.
8. Deleting the account and unsubscribing from emails
You can delete the account at any time, on the account page. When you delete the account, we first cancel the monthly subscription with the payment service provider and withdraw the access to Google Search Console and Google Analytics that you gave us. We then delete the account, the organisations in which you are the only member and everything in them. If you had confirmed the email of the account, we also delete everything tied to the same email outside the account: the contact details from free checks, the email and the tax number (NIF) given in payments, the support messages and the contact read on the site of your business. In later analyses of the site of your business, we stop storing that email.
Deleting the account does not cancel the instalments of a quoted preparation still to be paid: we keep charging them on the agreed dates, by the same means of payment. For this reason, the order and its payments do not leave with the account.
In a shared organisation, the organisation continues with the other members; if you were the only owner, ownership passes to the longest-standing member. We withdraw the access to Google Search Console and Google Analytics that you connected with your Google account.
We keep only what the law requires us to keep or what serves as proof: the invoices stay in our invoicing program for 10 years, and the record of the acceptance of an order (email, IP and date) stays for as long as it serves as proof of the contract. When the account published on a healthcare site a text approved by a professional, we keep for 5 years the proof of that approval: the text, the professional, the reference and the date of the approval, and the name and email of the account that recorded it. The Health Regulatory Authority (Entidade Reguladora da Saúde) supervises healthcare advertising, and this proof lets us answer a complaint or an inspection about that text (Article 17(3)(e) GDPR). The payment service provider keeps its own records of the payment, as an independent controller.
Deletion is immediate. The backups delete themselves after 30 days, so deleted data leaves every backup within 30 days. The emails we sent you stay with our email sending provider for 45 days.
When you unsubscribe in one of our emails, we stop sending you marketing emails for every check with that address, including the news, and the code of your email stops going to the advertising platforms. We keep the address as a refusal, so that we do not write to you again. After we delete your data, only a code calculated from the address (a hash) remains, which does not keep the email in readable form and serves only to recognise it if it appears again. If you later request a new check and confirm the address for the follow-up emails, that confirmation, the most recent one, applies and we send them again; the code of your email stays out of the advertising platforms.
9. Your rights
You have the right to access your data, to rectify it, to erase it, to restrict its processing, to object to its processing and to receive the data in a format you can take to another service (portability). You can withdraw a consent at any time, without affecting what we did before.
To ask for a copy of your data, or for its deletion, write to [email protected] from the address concerned, even if you have no account. We reply within one month with a file containing everything linked to that email, or with the confirmation of the deletion. If the request comes from another address, we may ask you to confirm it from the address concerned. You exercise the other rights in the same way, within the same period.
You also have the right to lodge a complaint with the Portuguese supervisory authority, the CNPD (Comissão Nacional de Proteção de Dados, cnpd.pt).
10. Security
We encrypt every connection to the site (HTTPS). We store passwords irreversibly, and the integration keys stay encrypted in the database. The private links of the reports use long codes, and we sign the links to unsubscribe, to confirm and to accept an invitation. Access to the server takes a key and nothing else, and the backups are daily, with a restore test every month.
11. Changes
If we change this policy in a significant way, we let you know by email (if we have your contact details) and update the date at the top of the policy.