Privacy · services to businesses · last updated: 12 November 2026
Privacy for services to businesses.
How I handle personal data in the commercial emails I send to small businesses across Portugal, and in the services I provide to them: replies to Google reviews, an allergen table and a menu in four languages, Anfitrião IA, and VSME Simples, the Google reviews waitlist, the QR menu waitlist, the TV screen waitlist and the group card waitlist. This notice follows the General Data Protection Regulation (GDPR, Regulation (EU) 2016/679), Law 58/2019 and Law 41/2004. If you only use the Day in Portugal guide, read the site privacy policy.
Who is responsible
Pedro Carvalho, self-employed, Portugal (the “controller”) · dayinportugal@gmail.com.
I have not appointed a data protection officer, because the law does not require one for this activity. For any question about your data, write to the email above.
For the review-reply service, the client business is the controller of the reviewers’ data. I process that data on the business’s behalf, as a processor (GDPR art. 28).
Commercial emails to businesses
- Who I write to. Only to companies (legal persons), at the company’s public contact email. I do not write to personal email addresses or to sole traders. Before I send commercial messages, I check the list of legal persons that have opted out, kept by the Directorate-General for the Consumer (Law 41/2004, art. 13-B), and I do not write to anyone on that list.
- What data. The company’s public contact email and the source where I found it (for example the company website, Google Maps or the RNAL, the national register of local lodgings). In sample review replies I use only public reviews from your profile, with the author’s first name as it appears on Google, or with no name.
- Why, and on what basis. I use the email only for the commercial proposal, on the basis of legitimate interest (GDPR art. 6(1)(f)).
- How many emails. At most one first email and a single follow-up.
- How long. The contact email and any exchange that gets no reply, or no interest, are deleted 6 months after the last contact. Samples (for example example replies) and anything you send me if we never sign a contract are deleted within 30 days.
- How to stop. Reply “REMOVER” and I will not write again. I record the request on an opt-out list, with only the email address and the date of the request, and I keep that list for as long as the activity continues. The record is what lets me honour your objection (Law 41/2004, art. 13-A, and GDPR art. 21; legal basis: legal obligation and legitimate interest, GDPR art. 6(1)(c) and (f)).
Review replies and access to the Google Business Profile
- Who decides. The client business is the controller. I process the data on its behalf, as a processor (GDPR art. 28), under a written agreement, and only on the client’s documented instructions (the agreement and the approvals).
- What data. The author’s public name or pseudonym and the text of the review, only to draft a reply and, after the client’s written approval, to publish it. Replies do not include personal data or details of bookings or accounts.
- Access to the profile. I access the Google Business Profile only with the owner’s written permission, and only as a Manager, never as the Owner, using the account dayinportugal@gmail.com with two-step verification turned on. I do not ask for or store passwords. The owner remains the Owner of the profile and can remove my access at any time. I do not change other profile information without written permission.
- When the service ends. I leave the profile within 2 working days (7 at most, as Google requires), return exclusive control to the client, and confirm by email.
- It is free. A Google Business Profile is free. What I charge for is the management service. I am not Google and I have no connection with Google, and I do not guarantee search positions, a number of reviews or a rating.
- Google’s own notice. Before you hire a third party to manage your profile, read Google’s notice “Working with a third party”. Google’s rules for third parties are in the Business Profile third-party policies.
- Artificial intelligence. Drafts are prepared with help from Grok Bot (the AI assistant used by the provider) and reviewed by me. Nothing is published without the client’s written approval.
- How long. I keep each client approval (for example the email “Aprovado”, meaning “Approved”) for up to 5 years after the agreement ends, only as proof of what was approved (legitimate interest, GDPR art. 6(1)(f)). When the agreement ends, I delete the remaining data and the drafts within 30 days and I do not keep copies, except what the law requires (invoices).
- If you wrote a review. To exercise your rights, contact the business you reviewed. That business is the controller. If you write to me, I will help the business answer your request.
Allergen table and a menu in four languages
- What data. The company and the establishment (legal name, company number (NIPC), registered office, and the name and address of the establishment), the name and role of the person who signs the declaration, and the contact email. Dishes, ingredients and allergens come from the owner, in writing. The signed declaration is mostly information about the company: the only personal data in it is the signatory’s (name, role and signature). Allergen information is about the dishes and is not anyone’s health data. I do not need data about the restaurant’s customers.
- Why. To format and translate the information the owner declared, and to keep the declaration the owner signed, confirming they reviewed and approved the final version. The restaurant is the operator responsible for allergen information (Regulation (EU) No 1169/2011, art. 8).
- Legal basis. For the signatory’s data: performance of the contract (GDPR art. 6(1)(b)) and a legitimate interest in having proof of what was declared and approved (art. 6(1)(f)). The restaurant remains the operator responsible for allergen information (Regulation (EU) No 1169/2011, art. 8).
- How long. The signed declaration and the approved versions are kept for up to 5 years after the contract ends, only as proof. That period matches the limitation period for proceedings over a serious economic offence (5 years, Decree-Law 9/2021, art. 36) and covers the period for non-contractual liability (3 years, Civil Code, art. 498). Working files are deleted within 30 days of final delivery.
- A person reviews it. I do not use machine translation without review: every delivery is read by a person.
Anfitrião IA
Anfitrião IA has free tools for local lodgings (a checklist and a house-guide generator) and the Kit AL.
- Visiting the site. Data: IP address, browser, page requested, date and time (technical logs of the site host). Purpose: to show the site and protect it from abuse. Legal basis: legitimate interest (GDPR art. 6(1)(f)). Retention: whatever the host keeps (usually days, or a few weeks).
- Checklist and house-guide generator. What you type and what you tick is used only to make the tool work. I do not receive this data: it stays in your browser (localStorage) until you delete it. You can delete it whenever you want.
- Kit AL pre-order. Data: email, municipality, listing link, number of properties, message. Purpose: to reply and prepare the proposal. Legal basis: pre-contractual steps at your request (art. 6(1)(b)). Retention: 12 months after the last contact, if you do not go ahead.
- Buying and delivering the Kit AL. Data: name, email, and the listing and property details you send me (for example house rules, check-in, and contacts you want in the guide). Purpose: to provide the service, support and corrections. Legal basis: performance of the contract (art. 6(1)(b)). Retention: up to 2 years after delivery, for corrections and complaints.
- Emails you send me. Data: email address and the content. Purpose: to reply. Legal basis: legitimate interest in replying (art. 6(1)(f)). Retention: until the matter is finished, and at most 12 months.
Do not send me guests’ personal data. The Kit AL does not need it. If I receive it by mistake, I delete it.
Artificial intelligence. To draft the Kit AL texts I use Grok Bot (the AI assistant used by the provider). I give it only the property information needed to write the texts (for example the description of the house and the rules) and never guest data. Where the tool allows it, I turn off the use of the data for training.
Assistant demos (dayinportugal.com/demos/). The demos run entirely in your browser. What you type into the demo assistant is not sent or stored by me or by anyone else. The page is served by GitHub Pages, which keeps the technical logs described above. The demos are not the official websites of the businesses named, and they are not connected to those businesses’ systems.
VSME Simples
This section covers the VSME Simples report-preparation service (the basic module of the voluntary EU sustainability reporting standard). It does not change the sections above.
- What data. I collect only aggregated company data, such as energy, water, waste and aggregated headcount. I do not ask for data that identifies an individual worker. In a very small company, even a total can identify someone (for example “1 woman” or “1 accident”). In that case the company aggregates the categories or omits the point, as the standard itself allows in order to protect a person’s privacy (Annex I, point 22(d)), and the report states the omission.
- Purpose. The aim is not to receive personal data. The files I receive are used only to prepare this report, and are not used to train artificial-intelligence models.
- If personal data still arrives. If a document nevertheless contains personal data, I process it only on behalf of the client company and according to its instructions, as a processor (GDPR art. 28), and only to prepare the report.
- How long. The files received are deleted 90 days after delivery of the final report. Only the invoice and the records the law requires the provider to keep are retained.
- Sharing. These files are not shared.
Waitlist: Google reviews offer
This section covers the waitlist for the Google reviews offer, which is still in development. It does not change the sections above, including the one on replies to Google reviews.
- What data. The business name and email address you send us by email or through the form on that page.
- Purpose. To manage your launch-price reservation and, only if you gave separate consent, to send you one email with the launch notice (and, if the launch is delayed, a delay notice). We do not send other campaigns.
- Legal basis. The steps you asked us to take before a possible contract (GDPR art. 6(1)(b)) and, for the launch email, your consent (art. 6(1)(a)), which you can withdraw at any time.
- How long. We keep the data until 14 days after the launch notice, or until 30 June 2027 if there is no launch, and then we delete it.
- Sharing. The request arrives by email, through Gmail (Google LLC), already listed under “Who receives the data”. We do not use any form tool other than your email programme.
- When the service is running: the business page, the QR code and the monthly count of QR reads process technical access data (for example, the date of a read). That count is emailed to the client business. We do not ask for data that identifies the end customer. Before delivery, these client pages will be hosted on a service whose terms allow commercial use (not GitHub Pages).
Free tool: Google review QR and A6 poster
The free tool at https://dayinportugal.com/qr-avaliacoes generates, only in your browser, the official Google “write a review” link and an A6 poster with a QR code. The business name and the Place ID are not sent to us. The page sets no tracking cookies of its own. If you use the waitlist form on that page, the section Waitlist: Google reviews offer applies.
Waitlist: QR menu offer
This section covers the waitlist for the QR menu offer, which is still in development. It does not change the sections above, including the one on the allergen table and a menu in four languages.
- What data. The restaurant name and email address you send us by email or through the form on that page.
- Purpose. To manage your launch-price reservation and, only if you gave separate consent, to send you one email with the launch notice (and, if the launch is delayed, a delay notice). We do not send other campaigns.
- Legal basis. The steps you asked us to take before a possible contract (GDPR art. 6(1)(b)) and, for the launch email, your consent (art. 6(1)(a)), which you can withdraw at any time.
- How long. We keep the data until 14 days after the launch notice, or until 30 June 2027 if there is no launch, and then we delete it.
- Sharing. The request arrives by email, through Gmail (Google LLC), already listed under “Who receives the data”. We do not use any form tool other than your email programme.
- When the service is running: the digital menu and the Google Sheet used to update prices and hide dishes process the restaurant’s menu data. Allergen information is provided and confirmed in writing by the restaurant, which remains responsible for it. The public menu page generates technical hosting logs. Before delivery, these client pages will be hosted on a service whose terms allow commercial use (not GitHub Pages).
Waitlist: TV screen offer
This section covers the waitlist for the TV screen offer, which is still in development. It does not change the sections above.
- What data. The business name and email address you send us by email or through the form on that page.
- Purpose. To manage your launch-price reservation and, only if you gave separate consent, to send you one email with the launch notice (and, if the launch is delayed, a delay notice). We do not send other campaigns.
- Legal basis. The steps you asked us to take before a possible contract (GDPR art. 6(1)(b)) and, for the launch email, your consent (art. 6(1)(a)), which you can withdraw at any time.
- How long. We keep the data until 14 days after the launch notice, or until 30 June 2027 if there is no launch, and then we delete it.
- Sharing. The request arrives by email, through Gmail (Google LLC), already listed under “Who receives the data”. We do not use any form tool other than your email programme.
- When the service is running: the full-screen TV page and the public Google Sheet used to update promotions process the business’s public content (menu, class timetable, promotions and slides). These are not intended to include personal data. The public page generates technical hosting logs. Before delivery, these client pages will be hosted on a service whose terms allow commercial use (not GitHub Pages).
Waitlist: group card offer
This section covers the waitlist for the group card offer, which is still in development. It does not change the sections above.
- What data. The company name and email address you send us by email or through the form on that page.
- Purpose. To manage your launch-price reservation and, only if you gave separate consent, to send you one email with the launch notice (and, if the launch is delayed, a delay notice). We do not send other campaigns.
- Legal basis. The steps you asked us to take before a possible contract (GDPR art. 6(1)(b)) and, for the launch email, your consent (art. 6(1)(a)), which you can withdraw at any time.
- How long. We keep the data until 14 days after the launch notice, or until 30 June 2027 if there is no launch, and then we delete it.
- Sharing. The request arrives by email, through Gmail (Google LLC), already listed under “Who receives the data”. We do not use any form tool other than your email programme.
- When the service is running: cards include colleagues’ names and messages, which are personal data. We process them only on behalf of the client company and according to its instructions, as a processor (GDPR art. 28), to provide the service. Cards are deleted 12 months after delivery unless the company asks us to keep them. The company keeps the PDF. Before delivery, the service will be hosted on a service whose terms allow commercial use (not GitHub Pages).
Invoicing (all services)
Name, tax number (NIF) and billing address, so I can issue the invoice-receipt and meet tax duties. Legal basis: legal obligation (GDPR art. 6(1)(c)). Retention: the following 10 calendar years (VAT Code, art. 52(1), applied by Article 118 of the personal income tax code).
Who receives the data
- GitHub, Inc. (site hosting, GitHub Pages): technical logs.
- Google LLC (Gmail): emails, pre-orders, approvals and declarations sent by email. For the review-reply service, also the Google Business Profile, where approved replies are published.
- Grok Bot (the AI assistant used by the provider): to prepare drafts, client data may be processed (texts, menus and public reviews), only as far as needed. Drafts are always reviewed by a person before they are delivered or published.
I do not sell data, and I do not share it for anyone else’s marketing.
Transfers outside the EU
GitHub and Google are in the United States. Transfers rely on the EU-US Data Privacy Framework (European Commission adequacy decision of 10 July 2023), where the company is certified, or on standard contractual clauses approved by the Commission (GDPR art. 46).
Using Grok Bot may mean a transfer of data outside the European Economic Area. In that case the transfer is made with the safeguards the GDPR provides, in particular standard contractual clauses approved by the European Commission (GDPR art. 46(2)(c)).
Your rights
You can ask for access, rectification, erasure, restriction, portability and you can object to processing based on legitimate interest (GDPR arts. 15 to 21). If you gave consent, you can withdraw it at any time. Write to dayinportugal@gmail.com. I reply within one month. You can also complain to the Comissão Nacional de Proteção de Dados (CNPD), the Portuguese data protection authority.
I do not make automated decisions that have legal effects on you, and I do not do profiling.
Cookies
This page is part of the Day in Portugal site. Cookies and local storage on the site are explained in the site privacy policy. On Anfitrião IA I do not use advertising or analytics cookies. I only use the browser’s local storage (localStorage) to keep the language you chose, the checklist ticks and the generator data, which is strictly necessary for the functions you asked for (Law 41/2004, art. 5(2)).
Changes
If this policy changes in a way that matters, I update the date above and, where I have your contact details and the change calls for it, I tell you by email.