Forwarding a calendar invite, or posting an event file, hands over more than the time and place. An .ics file carries every invitee address, the organiser, the dial-in number and passcode, the join link, and often the name and version of the software that made it. CALSCRUB shows you exactly what is in there, lets you take out what you choose, and gives you back a file that still opens as a normal calendar entry.
Drop an .ics file here, or click to choose one
Nothing is uploaded. The file is read inside this tab.
CALSCRUB reads and rewrites the file you give it, in your browser. It cannot reach the copy already sitting in someone else's calendar, in the original email, or on the server that sent it: once an invite has gone out, this cleans the copy you are about to share, not the ones already delivered. Properties the calendar format requires are replaced rather than deleted, so removing the UID gives you a fresh random one instead of a broken file, and the same goes for the producing software and the timestamp. Everything else you untick is removed outright.
Questions people ask
What does a calendar invite actually reveal?
More than the time and the place. An .ics file lists every invitee's email address and the organiser's, along with the dial-in number, the meeting passcode and the join link sitting in the description, the software that produced it, and a unique identifier that often contains an internal hostname. Forwarding one hands all of that over.
Is it safe to post a meeting invite publicly?
Not without editing it first. The join link and passcode let anyone into the meeting, and the attendee list is a ready-made map of who works with whom. Both have caused real intrusions into public-body meetings. Strip the attendees and the join details before the file leaves your hands.
Can properties be removed without breaking the file?
Some, not all. The calendar format requires a few properties to be present, so a cleaner has to replace those rather than delete them: removing the unique identifier means generating a fresh random one, and the same goes for the producing software and the timestamp. Everything else can simply go.