Security and privacy
How Autessa Meetings protects calendars and bookings
Autessa Meetings shares only open times: colleagues, invitees and websites that embed a booking page never see your events. Calendars that cannot be read count as busy, public pages are protected by abuse limits, and every manage link is private to its booking.
Every booking sends a calendar invite to the address someone typed, so Meetings limits how many one person can make.
Data handling
What does Autessa Meetings see, store and share?
Calendars stay private
Meetings reads busy times from the calendars you tick and adds new meetings to your booking calendar. Only you see your calendars; colleagues and admins never see your events, who you meet or your busy times.
Open times only, in public
Booking pages and embeds show open times, never events, other attendees or which calendars are connected.
Embeds learn very little
The embed tells the host page its height and, after a booking, the link and the time. It never shares who booked, their email, answers or the reschedule link. Messages are accepted only from the embed’s own frames.
Email used for the meeting only
The booking form says it: the email is used only to send the invite and updates about the meeting.
Fail closed
If a calendar sign-in expires or a calendar cannot be read, that person shows as busy until they reconnect, so nobody is booked over a meeting Meetings cannot see.
A narrow data key
Meetings reads and writes its own tables through one narrow key that cannot delete anything, kept in a sealed secret that people never see. Admins can rotate it or turn it off from Setup.
Public pages
How are booking pages protected from abuse?
Every booking sends a calendar invite to the address someone typed, so Meetings limits how many bookings one person can make and catches bots.
| Protection | What it does |
|---|---|
| Upcoming meetings per person, per link | Caps future meetings one email can hold on one link. |
| Bookings per person, per day | Across every link in your company. |
| Bookings per hour, company-wide | A safety stop; past it people see “Try again shortly”. |
| Shortest time on the form | Faster submissions get a fake confirmation and nothing is booked. |
| Honeypot field | A hidden field only bots fill; they get a fake success. |
| Email code | Per link: confirm the email with a 6-digit code before booking. |
| Private manage links | Each reschedule or cancel link carries its own token. |
Permissions
Who can do what?
| Role | Can |
|---|---|
| Member | Their own profile, calendars, schedules and links. Sees every link and every person’s page, never anyone’s calendar. |
| Link owner | Edit and archive links they created. |
| Host | See, cancel and retry bookings on links they host; leave a shared link. |
| Meetings admin | Brand, abuse limits, admins and setup; edit any link or schedule; see every booking. |
| Company admin | Always a Meetings admin. |
| Invitee | Book, and reschedule or cancel their own booking from its private link. |
Embeds
Content Security Policy for embeds
If your website uses a Content Security Policy, allow the booking site in two directives. The calendar runs on the booking site inside its frame, so the host page cannot read or change it.
Autessa’s security program
Company-wide security practices, policies and reports are on the Autessa Trust Center.
FAQ
Security questions
Can my colleagues see my calendar events?
No. Only you see your calendars. Colleagues see your links and personal page, never your events or busy times.
What does a website that embeds a booking page learn?
Only its height and, after a booking, the link and the time. Never who booked, their email or answers.
What happens if my calendar disconnects?
You show as busy for that calendar until you reconnect, so nobody can book over a meeting Meetings cannot see.
100% customizable, code and all
Make Autessa Meetings fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours