From a privacy perspective when using third-party booking sites that need an iCal for calendar availability, this is huge! We are unnecessarily exposing all the details of our guest (their name, email, and phone number) and hoping those sites do not siphone that PII and do something with it. I would much rather be safe than sorry.
Some options for implementation:
Two iCals: all reservation details or just availability.
Any number of iCals each with their own ACLs where any iCal can be revoked at any time (this is the more optimal but requires more product and engineering effort).
Log in to comment and vote
Comments1
Magenta Andromeda
May 2, 2025
From a privacy perspective when using third-party booking sites that need an iCal for calendar availability, this is huge! We are unnecessarily exposing all the details of our guest (their name, email, and phone number) and hoping those sites do not siphone that PII and do something with it. I would much rather be safe than sorry.
Some options for implementation:
Two iCals: all reservation details or just availability.
Any number of iCals each with their own ACLs where any iCal can be revoked at any time (this is the more optimal but requires more product and engineering effort).