Privacy Policy

Treble adheres to the GDPR and uses it as its guide when handling all User and Contact data. See Treble's GDPR policy for more information.

Access

Treble will not access, disclose, view or process the Company's and the Users' data stored on the Platform, except as provided in this Agreement, as authorized or instructed by the Company in writing, as needed to meet its obligations under this Agreement, or as required by applicable law. Treble may access anonymized or aggregated data derived from the Company's and the Users' data stored on the Platform as part of research into how the Platform is used.

Communications laws

The Company is fully responsible for ensuring that its use of the Platform complies with the laws of its jurisdiction, including, among others, laws on automated communications and on recording communications. The Company agrees not to hold Treble liable for any violation of law that occurs because of the Company's use of the Platform.

Communication restrictions

The Platform is an automated assistant that, as configured and instructed by the Company, holds conversations with Contacts on the channels the Company has connected (WhatsApp, Instagram, Messenger and web chat). Acting on the Company's behalf and according to that configuration, the Platform may reply to a Contact without human involvement, send them files, catalog cards and links, process the content the Contact sends (including transcribing voice notes and describing images), schedule, reschedule or cancel meetings with them — which makes the connected calendar provider send the matching invitation, update or cancellation to the email address the Contact gave — resume an earlier conversation when the Contact stops replying, after the waiting time the Company configures, and hand the conversation over to a human User. The Company may also use the Platform to start the contact, sending approved message templates to the lists or segments of Contacts it uploads, without a prior message from the Contact, and it is responsible for having a legal basis to do so. The Company is responsible for the content and lawfulness of these automated communications under the "Acceptable use" and "Communications laws" sections of this Agreement.

Except for the verification codes the Platform sends, from its own email infrastructure, to the address a Contact gives in the web chat to confirm their identity, Treble, as the provider, will only access and communicate directly with the Company, the Users or other employees of the Company. Treble staff do not contact, on their own initiative, the Contacts the Company has uploaded to the Platform, nor use their data for their own purposes; their access to Contact data is limited to what "Access" above describes.

Data collection

Treble uses cookies, sessions and other technologies to track use of the Platform. All Platform usage data is tracked and stored in accordance with Treble's GDPR policy. Treble may use anonymized or aggregated data for legitimate business purposes, such as evaluating, analyzing or understanding use of the Platform.

Cookies and similar technologies

We use cookies the Platform needs to work: sign-in, security, error reporting, theme and language. We also use optional cookies: analytics — Amplitude, to understand how the product is used, including session recordings; and marketing — Meta Pixel, from Meta Platforms, and the LinkedIn Insight Tag, from LinkedIn, to measure our ads. In the United States and the Spanish-speaking countries of Latin America, optional cookies are on from the first visit; you can block them in your browser settings. For any question or request about your data, write to us at support@ciarem.ai. Everywhere else we only turn them on with the visitor's consent, which can be changed at any time from "Cookie settings", at the foot of our site or in the account menu.

Privacy policy

Treble stores data about the Users of the Platform. Treble agrees to use best practices to store this data securely and to use it only to provide the Platform's service. Treble agrees to delete or anonymize any personally identifiable information at the Company's request and in accordance with Treble's GDPR policy.

This section describes how Ciarem accesses, uses, stores and shares Google user data. It applies only when a User voluntarily connects a Google Calendar account from the Platform's Settings → Calendars; if no account is connected, Ciarem accesses no Google data. Ciarem's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Permissions we request and why

• openid, email, profile — identify the connected account. We store the account identifier, the email address and the display name to show which calendar is connected and to avoid duplicate connections.
• .../auth/calendar.freebusy — read only the busy and free intervals of the primary calendar, within the date window being arranged with the Contact. This permission gives no access to event titles, descriptions, guests or locations, and Ciarem neither reads nor stores that information.
• .../auth/calendar.events — create, reschedule and cancel only the events Ciarem creates when it schedules a meeting with a Contact. Ciarem does not list or read the calendar's existing events.

Invitations sent on the User's behalf

By connecting a calendar, the User authorizes Ciarem to create, reschedule and cancel events in that calendar, and Google to send on their behalf, from their account, the matching invitations, updates and cancellations to the people the Company schedules with. The guest's email address is given by the Contact during the conversation.

Use with artificial intelligence

Ciarem does not use Google user data to train, retrain or fine-tune artificial intelligence or machine learning models, generalized or otherwise, whether its own or third parties'.

To propose times, the AI assistant does receive, at inference time, data derived from the calendar: a list of available start times, computed from the busy intervals and the working hours set in the Platform; the connection's configured time zone; and, when a meeting is confirmed, the email address of the connected account. The content of calendar events — titles, descriptions, guests or locations — is never sent to a model, because Ciarem has no access to it. This happens only to handle the conversation in progress and does not enable model training.

Storage, disclosure and deletion

Google access and refresh tokens are stored encrypted at rest (Fernet: AES-128 in CBC mode with HMAC-SHA-256) and are decrypted only to call Google APIs on the User's behalf. Google user data is not sold, rented, or used for advertising or profiling, and is not shared with third parties except the cloud infrastructure and AI model providers that run the Platform as subprocessors, or when applicable law requires it.

The User can disconnect the calendar at any time from Settings → Calendars. On disconnect, Ciarem deletes the connection with its tokens and asks Google to revoke the granted permission; the User can also revoke access directly from their Google Account's permissions page. After disconnecting, the history of meetings scheduled by the Platform (title, date, duration, guest email and event identifier) is kept as part of the Company's data; it can be deleted at the Company's request under this section.

This section describes how Ciarem accesses, uses, stores and shares Microsoft user data. It applies only when a User voluntarily connects a Microsoft account — personal, or work or school — from the Platform's Settings → Calendars; if no account is connected, Ciarem accesses no Microsoft data. Ciarem accesses that data only through Microsoft Graph and with the delegated permissions the User grants on Microsoft's consent screen.

Permissions we request and why

• openid, email, profile, User.Read — identify the connected account. We store the account identifier, the email address and the display name to show which calendar is connected and to avoid duplicate connections. Ciarem does not request the mailbox settings permission (MailboxSettings.Read) and therefore does not read the account's time zone: the connection is created without a time zone and the User sets it in Settings → Calendars.
• Calendars.ReadWrite — check availability and manage the meetings Ciarem schedules. Microsoft Graph has no permission equivalent to Google's free/busy-only one, so this is the narrowest permission Microsoft offers for both operations and, on its own, grants read and write access to the calendar. Ciarem limits its use to two operations: reading busy and free intervals through Graph's availability API (getSchedule), within the date window being arranged with the Contact, keeping only each interval's start, end and busy status; and creating, rescheduling and cancelling only the events Ciarem creates when it schedules a meeting with a Contact, identified by the event identifier Ciarem recorded when creating them. Ciarem does not list or read the calendar's existing events, and does not read, store or send to third parties their titles, descriptions, guests or locations.
• offline_access — renew access without asking for the User's consent again. Microsoft rotates the refresh token on every renewal; Ciarem stores only the current token.

Invitations sent on the User's behalf

By connecting a calendar, the User authorizes Ciarem to create, reschedule and cancel events in that calendar, and Microsoft to send on their behalf, from their account, the matching invitations, updates and cancellations to the people the Company schedules with. The guest's email address is given by the Contact during the conversation.

Use with artificial intelligence

Ciarem does not use Microsoft user data to train, retrain or fine-tune artificial intelligence or machine learning models, generalized or otherwise, whether its own or third parties'.

The AI assistant receives, at inference time, only the same derived data described for Google in the previous section: a list of available start times, computed from the busy intervals and the working hours set in the Platform; the connection's configured time zone; and, when a meeting is confirmed, the email address of the connected account. The content of calendar events — titles, descriptions, guests or locations — which Ciarem does not read, is never sent to a model. This happens only to handle the conversation in progress and does not enable model training.

Storage, disclosure and deletion

Microsoft access and refresh tokens are stored encrypted at rest (Fernet: AES-128 in CBC mode with HMAC-SHA-256) and are decrypted only to call Microsoft Graph on the User's behalf. Microsoft user data is not sold, rented, or used for advertising or profiling, and is not shared with third parties except the cloud infrastructure and AI model providers that run the Platform as subprocessors, or when applicable law requires it.

The User can disconnect the calendar at any time from Settings → Calendars. On disconnect, Ciarem deletes the connection with its tokens. Unlike Google, Microsoft offers no revocation mechanism an application can call, so the granted consent stays recorded in the Microsoft account until it expires or until the User withdraws it — which we recommend — from the apps portal of their work or school account or from the app permissions page of their personal Microsoft account. After disconnecting, the history of meetings scheduled by the Platform (title, date, duration, guest email and event identifier) is kept as part of the Company's data; it can be deleted at the Company's request under this section.

This section describes how Ciarem handles a Shopify store's data. It applies only when the store owner installs the Ciarem app from Shopify and links it to a workspace on the Platform; if no store is linked, Ciarem accesses no Shopify data. For the data of the store's customers, the Company is the controller and Treble.ai, INC., which operates Ciarem, acts as processor, following its instructions.

Permissions we request and why

• read_products, read_inventory — copy the store's products, variants, prices, images and stock into a catalog on the Platform and keep it in sync, so the AI assistant can answer questions about products.
• read_orders, read_customers — when a Contact asks about an order, look that order and its shipping status up in Shopify from the Contact's phone or email. Orders are read at that moment and are not saved in the Platform's database; the technical record of the AI assistant's reply may contain the order it looked up, and it is deleted after 90 days or when the Contact is deleted. These permissions are also used to send, from Shopify Flow, the WhatsApp templates the Company sets up (for example, an order confirmation) to the right customer.

What we store

We store the synced catalog, the store's access token (encrypted at rest), the link between a Shopify customer and the Contact who was sent a message, and the record of each send made from Shopify Flow, which includes the order data used in the template. Messages exchanged with the customer stay in the conversation, like any other conversation on the Platform.

Use with artificial intelligence

To reply to a Contact, the AI assistant receives at inference time the catalog data and, if the Contact asks about an order, that order's data. Ciarem does not use Shopify data to train, retrain or fine-tune artificial intelligence models, whether its own or third parties'. Shopify data is not sold, rented or used for advertising, and is not shared with third parties except the cloud infrastructure, AI model and observability (technical records) providers that run the Platform as subprocessors, or when applicable law requires it.

Customer requests and deletion

When the store requests a customer's data through Shopify, the Platform prepares the export of that customer's Contacts for the Company. When the store requests their deletion, the Platform deletes those Contacts with their conversations and that customer's send records. When the app is uninstalled, the store is unlinked, or Shopify asks us to delete the store's data, Ciarem deletes the access token, the synced catalog with its images, the links between Shopify customers and Contacts, and the records of sends from Shopify Flow.

Ciarem is operated by Treble.ai, INC. For any question or request about personal data, including access, correction or deletion requests, write to us at support@ciarem.ai.

We keep the Company's data while its account is active. If the Company never subscribed to a plan, we close its workspace and delete its data 30 days after the trial ends. If it subscribed to a plan and lost access, we close the workspace and delete its data 90 days later, and never without first emailing its administrators; billing records are kept with personal data removed, where the law requires it. If the account is deleted, its data is erased 30 days later, or 90 if it subscribed to a plan. The Company can ask for any data to be deleted sooner by writing to the address above.