Calberry Privacy Notice
Version 1.1 · Version date: 18 November 2026
1. Who is responsible
SETTER AI LTD, Georgiou Karaiskaki, 11–13, CARISA SALONICA, Flat/Office 102, Pervolia, 7560, Larnaca, Cyprus, is responsible for our own website, account, contract, billing and business communication processing described here. Calberry is our product. Contact us at team@calberry.ai.
If you book an appointment with a Calberry customer, that appointment provider normally controls your lead and booking information. We process it on its instructions. Read section 7 and that provider's own privacy information. A customer acting for another controller must identify the applicable responsible party.
2. Purposes and legal grounds
Where the GDPR applies, our own processing relies on:
- Article 6(1)(b): taking requested steps before a contract with you and performing it, for example for a self-employed customer;
- Article 6(1)(f): our legitimate interests in a secure, reliable service, responding to business enquiries, working with customer representatives, and preventing abuse. A company's employee is not automatically personally a party to its contract;
- Article 6(1)(c): legal obligations, including applicable accounting and tax requirements;
- Article 6(1)(a): consent where sought for a specific purpose.
Rules governing storage of, or access to, information on your device apply separately. A GDPR legal ground does not replace consent required by applicable device-storage or communications law.
3. Website access and hosting
To deliver and protect the website, we and our hosting provider process necessary connection and request information, such as IP address, requested resource, timestamp, browser/device information and error or security details. The purpose is delivery, operation, troubleshooting and abuse prevention. Our legal ground is Article 6(1)(f) GDPR.
Vercel Inc. is planned for hosting our marketing website and separate documentation, but is not currently used for either. The hosting information here describes that planned use after approval. Vercel may process information internationally. Our website's Inter and DM Sans fonts are served from our own site; loading those fonts does not require a connection to Google Fonts.
4. Cookies and browser storage
The marketing website’s cookie settings store your external-media choice as calberry-consent in local browser storage. The entry contains a version number, the time of your choice and your external-media decision. The choice is respected for 180 days, after which you are asked again. You can change or withdraw it at any time using “Cookie settings” in the footer.
The Setter AI examples contain videos hosted by Wistia. Video files are loaded from the provider only after you consent to “External media”. This establishes a connection to Wistia and transmits technical information such as your IP address. Without consent, local still images remain visible. Withdrawing consent stops playback and removes the external video source. Further details are available in Wistia’s privacy policy.
The website stores an explicitly chosen language as calberry-lang in local browser storage so later visits can respect your selection. It remains until replaced or removed in your browser; there is no separate automatic expiry. Without a saved selection, the browser language may be used. This serves your requested preference; our GDPR ground is Article 6(1)(f), alongside applicable device-storage rules.
The application uses necessary login and security cookies. Our own cookies include __Host-app_login for the login context, __Host-app_session for short-lived access, and __Host-app_refresh for maintaining the authenticated session. Their planned lifetimes are 10 minutes, 15 minutes and seven days respectively; these values have not yet been confirmed as the actual production configuration; session renewal can replace the relevant cookie, and logout or revocation invalidates access. Clerk's authentication service may use additional necessary browser mechanisms under its applicable settings.
Dashboard preferences, such as appearance and navigation settings, may be stored locally until changed or cleared. Session storage can hold the selected workspace and an unfinished booking. Booking drafts can contain contact details and form answers and are removed after successful booking or otherwise when the tab session ends or its storage is cleared.
Customer-enabled tracking is separate from these functional mechanisms. Tracking state may be held in session storage only according to the applicable consent arrangement. You can manage browser storage through your browser; blocking necessary functions may prevent login or completion of a booking.
5. Contact and support
When you contact us, we process the information needed to handle the enquiry. The website form collects name, email, optional company, topic, message and form language. Required fields are marked. Without the information needed for a reply, we may be unable to deal with the request.
The form sends messages through Resend, operated by Plus Five Five, Inc., to our team mailbox. Google Workspace provides our email mailboxes, including stored enquiries and replies. These services receive the contact and message information necessary for their role. Processing may occur internationally according to their contracts and settings.
Our legal grounds are Article 6(1)(b) for a requested contract with you, otherwise Article 6(1)(f) for handling legitimate business enquiries and support. Sending an enquiry is not consent to a newsletter or general advertising.
6. Accounts and business administration
We process account names, email addresses, user/workspace identifiers, memberships, permissions, preferences, authentication/security information and relevant contract, plan and billing details to provide and administer accounts.
Clerk, Inc. provides identity verification and email-code authentication. Identity and session information can be processed outside the EU. Lead and booking contents are not provided to Clerk as part of the login process.
Railway Corporation provides application infrastructure, including the API, worker and database. Calberry stores lead and booking data in the EU in its own application storage. This does not mean that all authentication, payment, communication, provider-log, support or integration processing stays exclusively in the EU. Customer-directed copies in external tools follow those tools' arrangements.
Our grounds for our own account and business administration are Articles 6(1)(b), 6(1)(f) and, where required by law, 6(1)(c) GDPR.
7. Information processed for appointment providers
On our customers' instructions, Calberry can process:
- contact details, such as name, email, phone number and company;
- answers to the customer's form questions;
- appointment time, time zone, assigned host and booking status;
- message contents, delivery events and replies;
- enquiry attribution, such as campaign parameters, referring information and supplied click identifiers;
- recorded permissions, the notice/consent text and the relevant timestamp where permission is collected.
The appointment provider determines its purposes, questions, recipients, retention instructions and legal grounds. We act under the applicable Data Processing Agreement and do not use a booking alone as permission to advertise Calberry or Setter AI to that person's contact details.
If enabled, a customer's form may capture entered information before a booking is completed. The customer must give timely notice and establish a lawful basis. Capturing information does not by itself authorise marketing contact. Marketing follow-up of an incomplete enquiry requires the necessary separate, explicit and demonstrable permission.
For access, correction or erasure of this information, contact the appointment provider first. We assist the responsible customer and route requests where reasonably possible and lawful. This does not limit your rights against us for processing for which we are responsible.
8. Calendar, email, WhatsApp and integrations
Google Calendar and Meet
If an account user connects a Google calendar, Calberry processes the granted permissions, access/refresh tokens, selected calendar information and necessary availability/event data. The connection allows the required reading of calendars and creation, update and deletion of appointments, participants and, where applicable, Google Meet links.
Tokens are used to maintain the authorised connection. You can revoke Calberry's access in your Google account. Previously transferred calendar events do not automatically disappear merely because access is revoked.
Google data is used for the visible scheduling and calendar functions. Its use and transfer follow the Google API Services User Data Policy, including Limited Use requirements. We do not use it for personalised advertising or training general-purpose AI models. Customer-directed calendar processing follows the customer's instructions; its privacy information must explain the relevant purpose and legal ground.
Application emails and relevant system messages use Mailgun (Sinch) through its EU sending endpoint. Recipients, necessary appointment/message contents and delivery events are processed for sending and troubleshooting. Calendar invitations may be sent directly through the customer's Google calendar.
The EU endpoint does not imply that all provider account, support or technical information is exclusively processed in the EU. Organisational messages must stay within the permitted appointment purpose. Marketing additions require their own valid basis and any necessary communications permission.
Where the customer enables WhatsApp, ZERNIO SOFTWARE SL, Spain, and the applicable WhatsApp/Meta business infrastructure process necessary phone numbers, appointment/message contents, sender information, replies and delivery events. A shared Calberry sender number or the customer's connected number may be used. The customer must clearly identify the channel before collection and meet the applicable platform and legal requirements.
An organisational WhatsApp message is not blanket permission for general advertising. Provider processing for its own purposes must be distinguished from instructed message delivery. See Zernio's DPA, WhatsApp Business Data Processing Terms and WhatsApp's EEA Privacy Policy.
Customer-connected tools
A customer may direct information to its own CRM, webhook destinations or automation tools. It determines the recipients and purpose and must provide the necessary privacy information. Such copies are stored according to those tools' arrangements; Calberry's own EU storage statement is not a storage-location guarantee for them.
9. Subscriptions, payments and taxes
Stripe is planned for payment processing but is not currently used for Calberry. After approval of that planned use, Stripe would process necessary business/contact, billing and payment information, country, relevant tax details, plan, seats and transaction status for paid purchases. The checkout collects payment information through its payment facilities; we receive the information needed to administer the transaction.
Stripe can act as our processor for some services and as an independent controller for others, including legal compliance and fraud prevention. Involved entities depend on the applicable contract, location and product. Stripe explains its entities and roles.
Our grounds are Articles 6(1)(b), 6(1)(c) and 6(1)(f) GDPR for the contract, legal duties and legitimate business billing/security interests.
10. Analytics and customer tracking
Our marketing website does not include an enabled advertising or behavioural-analytics platform. Necessary hosting and service processing still occurs as described above.
Booking pages or embeds can make events such as form start and completed booking available for a customer's configured measurement. Their allowed event fields exclude direct contact details and form answers. Funnel, lead and booking identifiers can nevertheless be personal or pseudonymous; they are not automatically anonymous.
The customer is responsible for any configured analytics/advertising recipients and necessary permission controls. Permission for follow-up contact is not permission for tracking. The customer's own privacy information must identify its actual services.
11. Recipients and international transfers
Access is limited to people who need it for their tasks. Necessary technical, email, messaging and payment providers described above, appropriately bound advisers and legally entitled authorities may also receive information. Processors require suitable agreements; customer-data subprocessors require the applicable customer authorisation. A privacy notice does not replace these contracts.
International providers can process data outside the EEA or allow access from another country. Where GDPR transfer rules apply, a valid basis under Chapter V is required, such as an applicable adequacy decision or Standard Contractual Clauses with necessary supplementary measures. The EU-US Data Privacy Framework is used only where the receiving entity is validly certified and the transfer is covered. Equivalent requirements of other applicable laws are also considered.
The DPF-list check of 26 October 2026 found that Resend (Plus Five Five) and Mailgun Technologies, Inc. are not certified under the Swiss-US Data Privacy Framework. Transfers to those recipients governed by Swiss data protection law rely solely on the applicable Standard Contractual Clauses (SCCs), with the necessary Swiss adaptations; EU-US participation or the UK Extension does not replace that basis. Mailgun's actual contracting and receiving entity still needs to be confirmed.
Meta Platforms, Inc. and WhatsApp LLC do not have the UK Extension to the DPF. Transfers governed by UK data protection law are covered through the WhatsApp Business Data Transfer Addendum and its applicable UK transfer safeguards. Their EU-US or Swiss-US certification is not treated as UK certification. Coverage of the actual integration by the relevant contractual basis must be evidenced before that integration is approved.
You may ask team@calberry.ai for information about the relevant recipients, safeguards and an available copy of the applicable guarantees. Public provider terms do not, by themselves, establish that every type of information is EU-only.
12. Retention and deletion
Retention depends on the specific processing purpose, valid customer instructions, valid requests and legal preservation duties.
The implemented automated purge removes message contents from our delivery history 30 days after the first sending attempt or receipt. This does not cover all lead data, delivery metadata or independently retained provider copies. The actual production configuration and provider retention periods must be confirmed before publication.
Automated standard retention periods for leads without a booking, completed or cancelled bookings, delivery metadata, routine logs and closed contact/support enquiries have not yet been implemented and tested. Previously proposed fixed periods are planning values and are not stated here as existing service settings. Necessity for the specific purpose, valid instructions and legal duties still govern retention; this does not justify indefinite storage. Send erasure requests to team@calberry.ai; for customer-controlled information, also see section 7.
Paid-plan cancellation alone is not account deletion: the free account may remain. Full account/workspace erasure, the retrieval window after termination and backup expiry have not yet been implemented or evidenced. No retrieval or backup-erasure period is therefore described as already operational. Statutory access, return, switching and erasure rights remain unaffected; the necessary processes must be implemented and tested before the corresponding operation begins.
Necessary accounting/tax records are held for their applicable statutory periods, with purpose-restricted access. For transactions actually subject to OSS record requirements, those records are retained for ten years from the end of the transaction year. Other mandatory accounting or legal periods depend on the type of record and applicable law. Minimal opt-out/suppression information may be needed for as long as required to respect a person's choice; it is not a marketing database.
Connected providers can have their own necessary retention and statutory duties. We apply required deletion/return instructions through our contractual arrangements. Customer-controlled calendar or CRM copies are handled by the responsible customer and provider, not automatically erased by every local deletion in Calberry.
13. Your rights and complaints
Under the applicable conditions, GDPR rights include access, correction, erasure, restriction and portability.
Right to object: You may object to legitimate-interest processing on grounds relating to your situation. You may object to direct-marketing processing at any time without giving such a reason.
You may withdraw consent for the future without affecting the lawfulness of earlier processing. Other applicable privacy laws can provide additional rights. Contact team@calberry.ai; for customer-controlled appointment information, also see section 7. Any identity check is limited to what is reasonably needed.
You may complain to a competent supervisory authority, including in your place of habitual residence, work or alleged infringement. In Cyprus: Office of the Commissioner for Personal Data Protection, 15 Kypranoros Street, 1061 Nicosia, commissioner@dataprotection.gov.cy, official contact details.
14. Required information and automated decisions
Required information is identified in context. Without it, the relevant service may not be available. Optional information is distinguished.
Our own account and contract administration is not intended to make solely automated decisions with legal or similarly significant effects under Article 22 GDPR. Customer-configured selection or booking rules and any separately contracted Setter AI service must be assessed for their actual purposes; this notice does not replace the customer's required assessment or information.
15. Updates and languages
We update this notice when processing or legal requirements change. Publishing an update does not replace a required permission for a new purpose. Translations are provided for accessibility; no language-precedence statement removes your rights or the information requirements of applicable law.