This Privacy Policy explains how a3labs handles personal data in connection with A3Labs Calendar, our Google Calendar integration for A3Labs scheduling agents. It should be read together with the general a3labs Privacy Policy. For Google user data, the specific limits below take precedence over more general statements in either policy.
Last updated: 15 October 2026
a3labs provides AI agent design, implementation, and maintenance services for small businesses. For the purposes of this policy, “a3labs”, “we”, “us”, and “our” refer to the business operating this website.
If you have questions about this policy or want to exercise your privacy rights, contact us at privacy@a3labs.ai.
A3Labs Calendar connects your Google Calendar to A3Labs scheduling agents so they can check availability and create, update, or cancel appointments on your behalf.
The Google user data accessed includes your connected Google account email, calendar availability, and appointment details such as event identifiers, appointment times, attendees, notes, and meeting links.
Google Calendar access is authorized through Google. The permissions displayed during authorization describe the access you are being asked to grant. Review those permissions before connecting your account.
We use Google user data for the disclosed scheduling features: connecting your calendar, checking availability, and creating, updating, or cancelling appointments on your behalf.
The general policy’s references to marketing, analytics, and improving services do not authorize use of Google Calendar data for those broader purposes. The Google-specific purpose limits in this section take precedence over general statements elsewhere in this policy or the general a3labs Privacy Policy.
We do not sell Google user data or use it for advertising, marketing profiles, or training or improving AI or machine-learning models. Our use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including their Limited Use requirements.
We store your connected Google account email, calendar identifier, and an encrypted authorization credential called a refresh token. This allows A3Labs Calendar to perform authorized scheduling actions without asking you to sign in each time. Disconnecting Google Calendar through our app deletes the stored connection and refresh token. This does not automatically delete previously created Google Calendar events or historical appointment records.
Our storage policy is to keep only the records needed to manage appointments handled by A3Labs Calendar: the relevant workspace and calendar identifiers, event identifier, appointment times and time zone, attendee names and contact details, appointment status, and any notes or meeting link needed for that appointment. We do not keep a permanent copy of your full Google Calendar or retain unrelated calendar events. Availability results are used for the scheduling request rather than kept as a historical calendar record.
Active appointment records are retained while the appointment needs to be managed. Records of completed or cancelled appointments must be deleted or irreversibly anonymised within 90 days of completion or cancellation. Disconnecting a calendar does not itself delete these records or cancel future appointments; retained records remain subject to these limits and can be included in a deletion request.
For a verified deletion request or account closure, our policy is to delete the associated connection credentials and appointment records from active systems within 30 days. Deleted appointment data may remain in restricted backups for up to 90 additional days before those backups expire. Backup copies are not used for ordinary operations; if a backup is restored, deletions must be reapplied.
Operational and security logs must exclude authorization credentials and appointment notes, meeting links, and attendee contact details, and must be deleted within 30 days. Where specific information must be retained to meet a legal obligation or preserve evidence of a security incident or dispute, it is restricted to that purpose and deleted when that need ends.
Deleting our records does not delete events or invitations already held by Google Calendar or appointment attendees. You can manage those events in Google Calendar; copies held by other participants are subject to their own controls.
We use Microsoft Azure services in Europe for AI processing of scheduling requests. Data processed through these services is not used to train AI models. The scheduling-only purpose limits and data-minimisation rules below also apply to this processing.
Hosting and database providers process the connection and appointment records described above to run the service, store data, and maintain restricted backups. They act on our instructions under contractual confidentiality, security, deletion, and purpose restrictions. Refresh tokens remain encrypted in storage and must not appear in logs, AI requests, or messages to workspace users or attendees.
AI service providers may process the minimum information required to understand a scheduling request and prepare an appointment action: the scheduling instruction, candidate availability slots, appointment times and time zone, and relevant appointment details. Names, attendee contact details, notes, or meeting links may be included only when necessary for the requested scheduling action. We do not send authorization credentials, full calendar exports, or unrelated event details to AI services. AI processing requires user consent for the disclosed scheduling feature and provider terms that prohibit model training and independent use of the data. Our policy is to use no-retention processing where available and otherwise limit provider-held request data to no more than 30 days.
Authorized users in your workspace may see the appointment details needed to coordinate the bookings they are permitted to manage, such as the appointment time, status, attendees, relevant notes, and meeting link. This does not give them access to your authorization credentials or unrelated private calendar entries. Access must follow workspace permissions.
Google Calendar receives the information needed to perform your authorized calendar actions. Appointment attendees receive the event information included in invitations and updates, which may include the title, time, organizer, guest list, description, and meeting link, depending on the event’s Google Calendar settings. Information placed in an invitation should be suitable for its recipients.
Our staff may view identifiable Google user data only with your explicit permission for a specific support task, where necessary for security or to comply with law, or as otherwise permitted by Google’s Limited Use rules. We may disclose the minimum necessary data where required by law or for a legitimate security investigation. Any transfer as part of a business sale or merger requires prior explicit user consent for Google user data.
We may collect information you choose to provide, such as your name, email address, phone number, company name, role, website, meeting details, messages, and any other information you send to us.
We may also collect technical and usage information, such as IP address, browser type, device information, pages visited, referral source, approximate location, cookie identifiers, and interaction data.
When we work with clients, we may process business data needed to assess workflows, build agents, connect tools, provide support, and maintain the services we deliver.
Where EU or UK data protection law applies, we rely on one or more legal bases: consent, performance of a contract, steps taken before entering a contract, compliance with legal obligations, and our legitimate interests in running, securing, and improving our business.
We may use necessary cookies to run the website and, where enabled, optional cookies or similar technologies for analytics, preferences, and marketing. Where required, optional cookies are used only after consent.
You can change cookie settings in your browser. If a cookie banner is shown, you can also use it to manage your choices.
Some providers may process data in countries other than your own. Where required, we use appropriate safeguards such as contractual protections or other lawful transfer mechanisms.
We use reasonable technical and organisational measures to protect personal data. No online service can be guaranteed to be completely secure, but we work to reduce risk and limit access to people and providers who need it.
Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a copy of your personal data. You may also have the right to withdraw consent and lodge a complaint with a data protection authority.
To make a request, contact privacy@a3labs.ai. We may need to verify your identity before responding.
You can review and revoke A3Labs Calendar’s access in your Google Account’s third-party connections settings at https://myaccount.google.com/connections.
Revoking access through Google stops the app’s access to Google Calendar, but does not itself delete records stored in our database. Disconnecting through our app deletes the stored connection and refresh token; it does not automatically delete historical appointment records or events already created in Google Calendar.
Revoking access and requesting deletion are separate steps. To request deletion of personal data held by a3labs, email privacy@a3labs.ai with the subject “A3Labs Calendar data deletion” and identify the email address associated with your connection. Do not include passwords or access credentials. We may need to verify your identity before responding.
We may update this Privacy Policy from time to time. When we do, we will update the date shown at the top of this page.