Privacy policy

English edition: 8 November 2026

How VozAgenda processes personal data for its website, WhatsApp, voice reception and supported calendar integrations.

1. Who we are

The data controller is VozAgenda (sole-trader business activity), R. Joseph Bleck 53, 1495-724 Cruz Quebrada, Portugal. Privacy contact: geral@vozagenda.pt. Telephone / WhatsApp: +351 965 390 878.

2. Data we may collect

We may collect identification and contact details, such as name, telephone number and email; messages and interactions concerning appointment requests; availability and reception history; and technical metadata needed for security and operation.

When a business connects WhatsApp, we also collect its WhatsApp Business Platform account ID, telephone-number ID and Meta business ID, solely to route that business’s messages through the integration.

When a business connects Google Calendar or Microsoft Outlook Calendar, we collect the calendar data strictly necessary to schedule and manage appointments. Sections 8 and 9 describe permissions and storage.

3. How we use data

We use data to respond to enquiries and manage appointments; operate communication channels including WhatsApp and telephone; synchronize appointments and check availability through connected calendars; improve quality, security and reliability; comply with legal obligations and prevent fraud or abuse; and monitor service performance using aggregated, anonymous data.

4. Legal basis

Processing relies on consent where applicable, pre-contractual steps and performance of a contract, legitimate interests in operation and security, and compliance with legal obligations.

5. Analytics (Google Analytics)

The website uses Google Analytics 4 to understand visits, including pages viewed, time spent, traffic source, device/browser and approximate country or region. Cookie storage is subject to your choice in the consent notice. Under denied consent, the current consent-mode configuration may send cookieless measurement signals. You may reject analytics cookies; that storage choice is respected.

6. Advertising (Meta Pixel)

The website uses Meta Pixel for Facebook/Instagram campaign measurement and relevant advertising. It loads only after cookies are accepted; it does not run when you reject them. Once active, it may send visit events such as pages viewed and lead events. Form events explicitly sent by this website’s code do not include names, email addresses or message content.

7. Third-party integrations

WhatsApp uses Meta Platforms infrastructure. Optional calendar synchronization uses Google Calendar or Microsoft Outlook Calendar. Infrastructure providers, such as cloud hosting, email, logging and monitoring, may process data only as needed to provide the service.

8. Google Calendar

The business grants OAuth access for calendar.events, used to create and read events for appointments and availability checks, and calendar.calendarlist.readonly, used to list calendars so the business can select the one to use. We do not request calendar-sharing settings or access to Gmail, Drive, Contacts or other Google services.

Event data read to calculate availability is used in memory for the request and is not stored in our database. For a created appointment, we retain the Google event identifier, not its content, to support later changes or cancellation.

The business, rather than its end customers, grants authorization and can revoke it in VozAgenda settings or its Google account. Each business has at most one active calendar provider at a time, Google Calendar or Outlook Calendar.

9. Outlook Calendar (Microsoft)

For Outlook.com or Microsoft 365, the business grants the Microsoft Graph Calendars.ReadWrite permission to create, read, update and delete calendar events for appointments and availability checks. Personal Outlook.com/Hotmail and work Microsoft 365 accounts are supported. We do not request access to other people’s shared calendars or Microsoft email, files or contacts.

Availability event data is used in memory for the request, not stored in our database. We retain only the identifier of the event created for an appointment, to support later updates or cancellation.

The business can revoke authorization in VozAgenda settings or Microsoft account access settings. Each business has at most one active calendar provider at a time.

10. Google Limited Use

VozAgenda’s use and transfer of information received from Google APIs comply with the Google API Services User Data Policy, including Limited Use requirements.

Google Calendar data accessed through the integration is not transferred, sold or used to create, train or improve AI or machine-learning models, by VozAgenda or third parties. AI providers used for conversational intent and speech processing receive the customer conversation’s text/audio and business configuration, never Google Calendar content, under plans or settings that exclude our data from model training by default or explicit configuration.

11. Retention

Data is retained only as long as necessary for the stated purposes and legal, contractual or audit obligations. Calendar event identifiers associated with an appointment are retained while the appointment and calendar integration exist. Disconnecting the integration stops calendar access and deletes stored access tokens.

12. Sharing and transfers

We do not sell personal data. Essential processors, such as Meta for WhatsApp and Google or Microsoft for business-enabled calendar synchronization, may receive data under appropriate technical and contractual measures.

13. Security

We apply technical and organizational measures including access controls, audit logs and security practices appropriate to the service. Calendar access tokens are isolated per business, never shared between businesses, and used only within the minimum scopes described in sections 8 and 9.

14. Your rights

You may request access, correction, erasure, restriction, portability or objection, and withdraw consent where applicable. Contact geral@vozagenda.pt to exercise your rights. For deletion instructions, use the data-deletion page.

15. Changes to this policy

We may update this policy periodically. The latest version will always be available on this page.