AIOS Architects

Privacy policy

Effective 6 November 2026

This policy covers the AIOS Architects booking service at book.aiosarchitects.com. People use it to book calls with our team, and our team uses it to offer times when they are free. It explains what we collect, why, and what we never do with it.

If you book a call

We collect your name, email address, time zone, the time you choose, and anything you write in the notes. We use it only to create the meeting, send you the calendar invite, and let you reschedule or cancel. The invite goes to you and the people you are meeting.

If you host calls (our team)

Hosts connect a Google or Microsoft calendar so the service can find free times and add bookings.

• Free and busy times only. With Google we read free/busy information, which contains no event titles, descriptions, locations or attendees. With Microsoft we read only the start, end and busy status of events. When someone reschedules a booking, we also read the start, end and status of Google events in that time window (still no titles, descriptions, locations or attendee lists) so the meeting being moved does not block its own new time.
• Your list of calendars, so you can choose which ones count as busy and which one receives bookings.
• Booked meetings. We create, move and cancel the events that people book through this service, and no others.
• Your name and email address from your account, to identify you as a host.

Access tokens from Google and Microsoft are stored encrypted. We do not store the contents of your calendar.

Google user data

The use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, we use Google user data only to provide the booking features described here. We do not sell it, use it for advertising, use it to train AI or machine learning models, or let people read it, except with your consent, for security, or where the law requires.

Who processes the data

The service runs on Vercel (hosting) and Supabase (database, United States (Virginia) region). Google and Microsoft provide the calendars and video links. We share data with them only to run the service, and with no one else.

Cookies

Hosts get one sign-in cookie. Booking a call sets no cookies. There is no analytics or advertising tracking.

How long we keep it

Bookings are kept as a record of the meeting. A host's calendar connection, including its tokens, is deleted when the host disconnects it. You can ask us to delete your data at any time.

Your choices

You can remove this service's access to your calendar at any time from your Google account or Microsoft account. To see, correct or delete what we hold about you, email brad@automationarchitecture.ai.

Changes

If this policy changes, we will update it here and change the effective date above.