Privacy policy

Data we collect

• Contact details you provide (name, email, company, phone).
• If you sign up or sign in with Google: your name, email address and Google account identifier, used only to create your account and sign you in. With this sign-in we do not obtain any other data from your Google account.
• Content of messages and requests sent via forms or email.
• Basic technical browsing data (IP address, browser, date and time).

Purposes

• Respond to inquiries and manage information or support requests.
• Administrative and commercial management of client and supplier relationships.
• Improve the site experience and service security.

Legal basis

• User consent when submitting forms or communications.
• Performance of a contract or pre-contractual measures.
• Legitimate interest in maintaining service quality and security.
• Compliance with legal obligations when applicable.

Retention

We keep data for as long as needed to fulfill the stated purposes and legal time limits. After that, it is blocked or deleted.

Recipients and transfers

We do not share data with third parties except where legally required or with processors acting under contract. We do not carry out international transfers outside the EEA unless appropriate safeguards apply.

Gmail connection

If you connect a Gmail account to Aizy's Mail channel, you grant us only permission to send email on your behalf (gmail.send) and access to your email address and Google account identifier. Aizy has no permission to read, modify or delete the content of your Gmail.

• Sending. We use this permission only to send, from your address, replies to the emails your bot receives: automatic replies, if you enable them, and those your team writes from Inbox.
• Forwarded email. Incoming email reaches us because you turn on automatic forwarding in Gmail to an Aizy address. We store the sender, subject and text in your bot's conversation, along with the technical identifiers needed to keep the thread together. We do not store attachments or images.
• Artificial intelligence. The text of those emails is sent to the AI providers we use to deliver the service (currently OpenAI and Google) to generate the reply or the internal summary. This data is not used to train generalized AI models.
• No sale or advertising. We do not sell this data or use it for advertising, and we share it only when necessary to provide the service, comply with the law or protect its security.
• Human access. People in your organization with Inbox access can read these conversations. Aizy staff access them only with your consent, for security reasons or where required by law.
• Security. Google access tokens are stored encrypted and do not appear in logs.
• Retention. Conversations are kept for the retention period configured in your environment and then deleted.
• Withdrawing permission. You can withdraw it at any time from your Google account permissions or by disconnecting Gmail in Channels → Mail. The latter revokes the permission at Google, deletes the tokens and disables your forwarding address. Remember to also remove the forwarding in Gmail.

Aizy's 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 Calendar connection

If you connect Google Calendar to an Aizy bot, you grant us permission to view your calendars (calendar.readonly) and to create and edit events (calendar.events). Aizy uses these permissions only as described below.

• Lookup. We list your calendars so you can choose which one the bot uses, and we check whether a time is free or busy. We do not look up the titles, descriptions or attendees of your events.
• Appointments. When someone books with your bot, we create the event in the chosen calendar and, if you allow rescheduling, we edit that same event. We do not edit or delete any other event.
• Appointment data. The title and description come from the Task you configure and may include data from the conversation, such as the name or phone number of the person booking. We store the title, description, date and event identifier in the conversation.
• Artificial intelligence. The times offered by the bot are part of the conversation and may be sent to the AI providers we use to deliver the service (currently OpenAI and Google). This data is not used to train generalized AI models.
• No sale or advertising. We do not sell this data or use it for advertising, and we share it only when necessary to provide the service, comply with the law or protect its security.
• Human access. People in your organization with access to those conversations can see these appointments. Aizy staff access them only with your consent, for security reasons or where required by law.
• Security. Google access tokens are stored encrypted and do not appear in logs.
• Retention. Appointment data is kept with the conversation for the retention period configured in your environment and then deleted. Events created remain in your calendar until you delete them.
• Withdrawing permission. When you disconnect Google Calendar in Integrations, we delete the tokens Aizy stores. To also withdraw the permission at Google, do so from your Google account permissions.

Aizy's 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.

Your rights

You can exercise your rights of access, rectification, erasure, objection, restriction, and portability by emailing hello@aizyagents.com. You may also lodge a complaint with the supervisory authority.

Withdrawal

In case of withdrawal, contact hello@aizyagents.com.

Policy changes

We may update this policy to reflect legal or service changes. The current version will be published on this page.

Data controller

• Controller name: Marc Brunés Ramos
• Trade name: Aizy Agents
• Contact email: hello@aizyagents.com