Integration privacy notices | Atendy

1. Google Workspace API data and Limited Use

When a customer connects Google Calendar, Atendy requests only permissions necessary for the activated function. The https://www.googleapis.com/auth/calendar.events scope reads events in the queried range to compute availability using start/end times, not titles, descriptions or attendees, and creates, changes or cancels agent-managed events. Other calendars and account settings are not accessed. openid and email show which Google account is connected.

Queried availability may be provided to Google Gemini solely to generate the agent’s answer during that conversation. Atendy follows the Google API Services User Data Policy and Google Workspace API User Data and Developer Policy, including Limited Use.

We do not use, transfer or sell raw, aggregated, anonymised or derived Workspace data to create, train or improve AI/ML models, including foundational or generalised models, ours or third parties’. Data are used only to provide or improve user-facing functions of the activated integration. Transfers are limited to what is necessary for those functions, security, legal obligations or customer consent. Human reading is limited to customer consent, security, legal compliance or aggregated anonymised internal operations.

Atendy’s use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

The refresh token and minimal account data remain while the connection is active. Disconnect in the agent editor (Tools → integration → Disconnect) to immediately remove the token and connection data. Access can also be revoked at https://myaccount.google.com/permissions. Request full deletion at info@atendy.es. Deleting the Atendy account removes its connections.

2. Shopify data

Installing Atendy Connector authorises Atendy through OAuth with read_orders and read_products only. These allow order/catalogue queries, not creation, alteration or deletion in Shopify.

The agent queries in real time for order status or product information, and necessary responses may be provided to the voice model for that conversation. Atendy keeps no separate replica of the store’s catalogue or orders. The technical domain and tokens needed for the connection are stored encrypted. Data used in calls may remain in transcripts and tool logs under this policy’s retention and controls.

Disconnect in the editor or uninstall in Shopify to remove tokens and minimal connection data. Mandatory privacy webhooks handle Shopify access/deletion/redaction requests. Assistance: info@atendy.es.

3. WhatsApp data

When customers connect their WhatsApp Business account, Atendy accesses Meta’s Cloud API only for necessary enabled functions and expressly connected accounts. whatsapp_business_messaging permits sending from the customer’s number, receiving replies and tracking delivery. whatsapp_business_management permits listing numbers and creating, querying and managing templates and approval status.

Account data include business-account ID, phone numbers, display name, templates, quality indicators and sending limits. Recipient data include phone/WhatsApp ID, profile name where provided, sent/received content and sent/delivered/read/failed status.

Data are used solely for activated messaging, sending configured messages on the customer’s behalf and displaying status and replies to that customer. Customers see only their own account. We do not sell or use these data for advertising or to create, train or improve our or others’ AI models, whether raw, aggregated or derived.

The customer is controller for recipient data; Telvia is processor under the DPA. Meta processes for the business account holder under the WhatsApp Business Data Processing Terms. Meta’s Cloud API documentation states a maximum 30-day message retention.

If the customer activates messaging through Atendy’s own number, Telvia sends as the customer’s messenger, identifying the business and its contact number. Meta then provides that messaging infrastructure to Telvia. Template text may be checked with AI to detect prohibited or misleading use. This does not authorise model training or remove the customer’s duty to ensure lawful content and recipients.

Customers must obtain the recipient consent required by WhatsApp policy and applicable law and honour opt-outs. Customer connection tokens/account data remain while active; disconnecting removes the token immediately, or access can be revoked in Meta business settings. Messages/status follow conversation retention in section 10 of the Privacy Policy. Contact info@atendy.es for full deletion; account deletion removes connections.

4. Claude connector

The optional connector allows customers to connect their own Claude account to Atendy. The owner chooses read-only access or permission to create/edit agents. On customer request Claude can access their agents’ configuration, numbers, call lists/details (summaries, transcripts, KPIs and tool use, potentially personal data) and minute balance, and with edit permission create agents or alter settings. Internal costs, API keys and telephony credentials are never shared. The connector cannot delete agents, change phone numbers, place calls or access payments.

Data go to Anthropic at the customer’s express request through their own Claude account, under their Anthropic terms/privacy arrangements. The customer decides whether to activate it. Atendy does not use these data for AI training.

We retain necessary connection/account/authoriser IDs, use dates, permission and authorisation data. Before an agent change we save a configuration copy for undo, retained for 30 days and deleted with the agent. Disconnect from the panel. Connector documentation is available in Spanish at /docs/conector-claude.