What this service does with your data
The A2A Calendar POC is a proof of concept. It gives your Google account a small software agent that finds a meeting time with another person's agent and books it in both Google Calendars. This page states, from the running code, what the service reads, what it stores, for how long, who else processes it, and how you delete it.
1. Who operates the service and how to reach them
The service is operated by Innoestate Holdings, a French simplified joint-stock company (SAS) registered in Montpellier under SIREN 949 308 803, registered office: Bureau 3, 6 B boulevard Berthelot, 34000 Montpellier, France, represented by its president, Mathieu Colla. Innoestate Holdings is the data controller for the processing described here. Questions and requests about your data: mathieu@aithos.fr. You can also lodge a complaint with the French supervisory authority, the CNIL (cnil.fr).
2. Signing in with Google
Signing in uses Google's OpenID Connect flow with the openid, email and profile scopes. The service keeps:
- a random account identifier it generates for you (this identifier is also your agent's public identifier);
- your verified Google e-mail address;
- your Google display name, refreshed at every sign-in, used only as the title of the meetings your agent books ("Host name / Guest name");
- a SHA-256 hash of your Google subject identifier, used to find your account again. The identifier itself is not stored.
Your browser receives one session cookie (__Host-calendar-session): a random value valid for 12 hours, marked Secure, HttpOnly and SameSite. There are no analytics or advertising cookies and no third-party scripts.
3. Connecting Google Calendar
Connecting your calendar is a separate, explicit consent. The service asks for three Google Calendar scopes and uses each for one purpose:
| Scope | Used for | What is read or written |
|---|---|---|
calendar.freebusy | Finding a time that is free for both people | Busy intervals of your primary calendar inside a window of at most 30 days. The service turns them into free weekday slots between 09:00 and 18:00 and keeps nothing else. |
calendar.calendarlist.readonly | Interpreting times in your time zone | The time zone of your primary calendar. No other calendar-list data is used. |
calendar.events.owned | Learning your meeting habits and creating the meeting | See "Meeting history" and "The meeting your agent creates" below. |
The refresh token Google issues is encrypted with a customer-managed AWS KMS key before it is stored, bound to your account identifier, and decrypted only to obtain a short-lived access token for one operation. Access tokens are never stored. The connected e-mail address is stored with the encrypted token. Google may show the app as unverified until Google has completed its review.
Meeting history
When your agent arranges a meeting with a given person, it reads events of your primary calendar from nine months in the past to three months ahead, keeps only events you organised or accepted, and retains for each of them: the title (first 120 characters), the description (first 180 characters), the start and end times, whether you organised it, whether that person attended, and the identifier of a recurring series. At most 60 of these observations are sent, once per person per day, to an AI model that returns only a preferred weekday, a preferred hour, a duration and whether lunchtime is acceptable. The model's instructions treat calendar text as data, never as instructions, and forbid it from returning descriptions or identities. Up to 20 of the observations are cached for 24 hours as "previous meetings with this person" and shown to you on your account page. The model runs on Amazon Bedrock in the AWS Paris region (eu-west-3) through an EU inference profile; it is only used within a fixed monthly budget, otherwise deterministic defaults apply.
The meeting your agent creates
When a time is agreed, the host's agent creates one event on the host's primary calendar with: the title "Host name / Guest name", the start and end time, the guest's Google e-mail address as attendee, and a private property a2aBookingId that lets the service recognise the event later. Google sends the usual invitation e-mails to both people. The guest's agent then accepts the invitation on the guest's behalf. Both people therefore see each other's Google e-mail address on the meeting. The service never deletes or moves events, never creates calendars, and never changes sharing settings.
4. What other people and the public can see
- The public catalog and agent cards (
/.well-known/ai-catalog.json,/agents/…/agent-card.json) list every published agent so that other agents can find it. They contain your agent's identifier, its signed description ("Calendar agent" followed by the first eight characters of the identifier) and its public verification key. They do not contain your name or e-mail address. - Your agent's link (
/book/…) lets any signed-in person ask your agent for a meeting; only share it with people you want to meet. - The live log page (
/logs) shows technical events of the last 24 hours: agent identifiers, verification steps and error codes. Names, e-mail addresses, tokens, request bodies and calendar times are excluded by an allow-list and tested to stay out. - The other person sees the agreed time, the meeting title with your display name, and your e-mail address on the invitation.
5. Public booking pages (no Google account)
Separately from Google sign-in, anyone can register a public Google appointment-schedule link. The service then stores that public URL and reads the offered slots from the page when asked. If someone books an appointment through such an agent, the attendee's first name, last name and e-mail address are sent to Anakin (api.anakin.io), a browser-automation provider that submits Google's booking form; the service itself keeps only a hash of the attendee's e-mail address in its booking record.
6. How long data is kept
| Data | Kept |
|---|---|
| Account (identifier, e-mail, display name), agent, its card and key | Until you delete your account |
| Encrypted Google refresh token and connected e-mail | Until you disconnect Google Calendar or delete your account |
| Browser session | 12 hours, or until you sign out |
| Sign-in attempt (state and PKCE values) | 10 minutes, used once |
| Cached meeting analysis (preferences and up to 20 previous meetings) | 24 hours |
| Meeting proposal awaiting confirmation | 15 minutes |
| Single-use authorisation between agents | 90 seconds |
| Booking record (identifiers, the slot, a hash of the attendee e-mail) | 30 days after the meeting |
| Autonomous booking task record | 30 days after it completes |
| Rate-limit counters (hashed address or account identifier) | At most 24 hours |
| Public log feed | 24 hours |
| Technical server logs (AWS CloudWatch; identifiers and codes, no personal data by design) | 14 days |
| Database backups (point-in-time recovery) | Deleted or expired rows remain recoverable for up to 35 days |
7. Where data is processed
The service runs on Amazon Web Services in the Paris region (eu-west-3): AWS Lambda, Amazon DynamoDB, AWS KMS, Amazon SQS, Amazon Bedrock and Amazon CloudWatch. The website's static pages are delivered through Amazon CloudFront. Google APIs process the sign-in, calendar reads and the meeting creation under Google's own terms. Anakin processes public booking-page submissions as described in section 5.
8. Deleting your data
On your account page, "Delete my account and agent" revokes the Google Calendar permission with Google, deletes the encrypted token, your agent with its card and key (which removes it from the public catalog), your display name, your account and your session. The action is immediate and cannot be undone; signing in again creates a new, unrelated agent. What remains afterwards: the meetings already created in the Google Calendars of the people involved (they belong to those people and can be deleted in Google Calendar), booking and task records until their 30-day expiry, the 24-hour public log feed, technical logs for 14 days and backups for up to 35 days. You can also revoke the permission yourself at any time from your Google account's "Third-party apps & services" page. Write to mathieu@aithos.fr for anything you cannot do from the page.
9. Google API Services User Data Policy
The A2A Calendar POC'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. In particular, Google Calendar data is used only to provide the features described on this page, is not used for advertising, is not sold, and is transferred to a third party only as described here (Amazon Bedrock for the meeting-habit analysis, with human access limited to what security, legal compliance or your own consent require).
10. Your rights
Under the General Data Protection Regulation you can ask for access to your data, its rectification or erasure (the account page does this directly, section 8), a restriction of processing, its portability, and you can object to a processing. The legal basis for the processing is your consent when you connect Google Calendar (withdrawable at any time by disconnecting it or deleting your account) and the operation of the service you asked for. Write to mathieu@aithos.fr.
11. Changes
Changes to this policy are published on this page with a new effective date. The service's source code is public at github.com/Math1987/aithos-calendar; the statements above can be checked against it.