How to Hide Event Details When Sharing Your Calendar

Sharing a calendar should not mean sharing your life. Here is how to share availability with the details stripped out.

Jakub Beneš

Jakub Beneš

Founder, CalendarPipe · June 9, 2026 · 10 min read

To hide event details when sharing your calendar, share a stripped copy instead of the real calendar. Run your events through a rule that replaces every title with "Busy" and clears the location and the notes, write the result into a separate share-only calendar, and send that calendar's read-only link. Whoever you send it to subscribes in Apple Calendar, Google Calendar, or Outlook with no account and no login, and sees only the hours you're unavailable. Start and end times pass through untouched, which is the whole point: you hide the what, never the when.

Why I hesitate every time someone asks for my calendar

A client emails: "Can you send me your calendar so we can find a time?" A collaborator at another company wants to coordinate a launch. A friend planning a trip asks when you're around. Reasonable requests, all of them — and every time, I hesitate for a second.

Because sharing my calendar the normal way means sharing everything. The 1:1 with my therapist. The line that says "call recruiter." The dentist appointment with the address attached. The alternative is dragging the other person into my Google org or asking them to make an account somewhere just to see when I'm free. None of that is what they asked for. They asked for one thing: when can we meet.

If you've ever wanted to hide event details when sharing a calendar — to share your availability without showing the details behind it — that gap is exactly the problem. Here's how I close it: share calendar busy-only, with the titles, locations, and notes stripped before they ever leave my machine.

Sharing availability is not the same as sharing your life

Here's the distinction that matters: there's availability (the times you're free or busy) and there's content (what those blocks actually are). When someone asks for your calendar, they want availability. They almost never want content.

The trouble is that most sharing tools treat those as a package deal. You hand over a calendar, and it carries the titles, the locations, the notes, the guest lists — all of it. So you either overshare or you don't share at all, and you fall back to the "how's Tuesday at 2?" email tennis that calendar sharing was supposed to kill.

What you actually want is private calendar sharing: expose the when, hide the what. Busy from 10 to 11, free after 3 — and not a word about why.

Native free/busy sharing exists — but the built-ins are clumsy

To be fair, the big calendar apps know this problem exists. Google's sharing menu includes a "See only free/busy (hide details)" permission, and Outlook lets you share a calendar with availability-only access. In theory, that's exactly the thing.

In practice it tends to disappoint, for a few reasons I keep running into:

  • It often only works inside your organization. Free/busy lookups are smooth when everyone's on the same Google Workspace or Microsoft 365 tenant. The moment the other person is at a different company — or on a personal Gmail, or has no account at all — it gets awkward fast, or stops working entirely. Sharing calendars between two Microsoft 365 tenants, for example, runs on organization relationships an administrator has to configure, which is not something you arrange on a Tuesday afternoon to answer one email.
  • It's coarse and all-or-nothing. You usually share a whole calendar at one privacy level. You can't easily say "expose these events as busy, drop those entirely, and never reveal locations."
  • It leaks more than you'd expect. Depending on settings, "private" events still show their time, declined events show up, and titles sometimes sneak through to people you never meant to show them to.

Apple draws the same line: on iCloud, a privately shared calendar requires the recipient to have an Apple Account, and the only way around that is publishing the whole calendar publicly. So the native tools either ask too much of the other person (be in my org, make an account) or give you too little control over what slips out. I wanted something that worked for anyone, anywhere, and let me decide exactly what crossed the line.

Here's the whole menu, laid out as honestly as I can:

MethodWhat the other side seesAccount or login neededWorks outside your org
Sharing your real calendarTitles, locations, notesUsuallyRarely
Native free/busy sharingBusy times, no detailUsuallyUsually not
Emailing "how about Tuesday?"Whatever you typeNoYes, one slot at a time
A screenshot of your weekWhatever was on screenNoYes, stale the moment you send it
Stripped feed link (Pro)"Busy" blocks onlyNoYes
Email invitations (Pro)Only the events you sendNoYes

The bottom two rows are the ones I use. The rest I've tried, and every one of them cost me either privacy or an email thread.

How to share availability without showing details — the CalendarPipe way

CalendarPipe runs on sync rules. A sync rule connects a source calendar to a target calendar and runs a small gate function on every event — a tiny piece of logic in a secure sandbox that decides, per event, whether it passes through and how it should look on the other side.

For hiding details, the gate is the important part. A gate can clear or replace the title (turn "Therapy" into "Busy"), strip the location and description, set the event to private, and mark it as busy. The one thing it deliberately cannot touch is the time: start, end, and duration always come through untouched. That's the point — you're hiding the what, never the when. The busy blocks line up exactly with reality, so nobody books over you.

Here's how I set it up to share with someone outside my world:

  1. Sync my real calendar into a hosted calendar. A hosted calendar is one that lives inside CalendarPipe rather than in Google or Outlook. I create a sync rule with my real calendar as the source and a fresh hosted calendar as the target.
  2. Put a privacy gate in the middle. The gate strips every event down to a private busy block — title replaced with "Busy", location and notes gone. I can describe that in plain English and let the AI generator write it, click it together in the visual builder, or start from a template. Took me about two minutes.
  3. Share the hosted calendar's feed link. Every hosted calendar has a public, read-only ICS feed link — something like https://www.calendarpipe.com/feed/<token> (there's a webcal:// version too). I send that link to whoever asked.

On their end, there's nothing to install and no account to create. They paste the link into whatever they already use — Apple Calendar, Google Calendar, Outlook, Thunderbird — and my availability shows up alongside their own, read-only, refreshing on its own. They see clean busy blocks at the right times and learn nothing else. (If they prefer, hosted calendars also speak CalDAV.)

One timing detail worth setting expectations on, because it catches people out: there are two clocks, not one. CalendarPipe refreshes the stripped copy from your real calendar every 15 minutes on the free plan and every 5 on Pro. Then the other person's calendar app re-polls the feed on its own schedule, which is typically somewhere between every 15 and 60 minutes, and the feed itself is cached for an hour. So a meeting you book at 9:00 usually shows up on their side within the hour, not within the second. For "when are you free next week," that's plenty. For "are you free right now," send a message.

I'll be straight with you about the line here, because I'd rather you find out from me than from a paywall: hosted calendars are a Pro feature. On the free plan you can build the privacy gate and sync between your own connected calendars all you like — that part costs nothing. What needs Pro is the outward-facing share link that lets someone with no account subscribe to a stripped-down version of your calendar. Pro is $4/month, or $40 a year ($3.33/month), with a 14-day trial — and it also gets you unlimited connections and rules instead of the free plan's two and one, a 5-minute sync interval instead of 15, AI rule generation, and the API. Most tools in this space start at $10 and up.

The other Pro option: send invitations instead

A shared feed is the right tool when someone wants an ongoing view of your availability. But sometimes you don't want them subscribing to anything — you just want a single meeting on their calendar without the back-and-forth.

For that there's invitation delivery (also Pro): synced events go out as standard email invitations the recipient can Accept or Decline. No signup, no OAuth, and because it's plain email it sails through corporate firewalls that block calendar subscriptions — the same privacy gate applies, so you control what each invitation reveals. I dig into that path in calendar sync when your company blocks third-party apps.

Who this is for

Private calendar sharing clicks for anyone who regularly coordinates with people outside their own org:

  • Freelancers and consultants sharing availability with clients who shouldn't see the other clients.
  • Cross-company projects where two teams need to find time but live in different calendar systems.
  • Founders and anyone wearing several hats, juggling personal and work in one calendar that no single audience should see in full.
  • Just coordinating with friends or family without exporting your whole life to do it.

If everyone you schedule with is already inside your company's calendar system, the native free/busy might be enough. The minute you're reaching across that boundary, the stripped-feed approach is what holds up.

Staying in control

The part I care about most is that you decide what's exposed, down to the event. The gate is explicit: it does exactly what you wrote and nothing more. There's no fine print where a title leaks through because of some default you didn't know about.

And it's reversible. Stop sharing whenever you want by deleting the hosted calendar or rotating its feed link — the moment you do, the link goes dead and the subscription on the other end shows nothing. No "please remove me from your calendar share" email needed.

This is the outward-facing half of a pattern I use constantly. There's also the inward version: personal → work, privately, where the goal is getting your own commitments onto your work calendar as anonymous busy blocks. Same gate, pointed the other way. If you want the full menu of what a gate can do, the docs lay it out.

If you've been quietly oversharing your calendar because the alternative was too fiddly, this is the fix I built for myself: share when you're free, keep the rest to yourself, and never make anyone create an account to find a meeting time. Build the gate for free, then flip on a share link when you need it — start with CalendarPipe.

— Jakub

Frequently asked questions

How do I share my calendar so people only see that I'm busy?

Share a stripped copy rather than the calendar itself. Sync your real calendar into a separate share-only calendar through a rule that replaces each title with "Busy" and clears the location and notes, then send the read-only link to that copy. The recipient sees your busy blocks at the correct hours and learns nothing about what those blocks actually are.

Can I share free/busy without giving access to my Google account?

Yes. You share a generated calendar link rather than your Google account — the recipient never signs in, never joins your organization, and never sees anything beyond the busy blocks you chose to expose. The link is read-only, so they cannot write to your calendar either.

Does the person I share my calendar with need an account?

No. The recipient pastes the feed link into Apple Calendar, Google Calendar, Outlook, Thunderbird, or any other app that subscribes to calendar feeds. There is nothing to install and no CalendarPipe account to create on their side.

How often does a shared calendar link update?

A shared calendar link updates on two schedules. CalendarPipe refreshes the stripped copy from your real calendar every 15 minutes on the free plan and every 5 minutes on Pro, and the recipient calendar app then re-polls the feed on its own schedule — usually every 15 to 60 minutes, with the feed cached for an hour. In practice a new meeting shows up on their side within about an hour.

Can I stop sharing my calendar after I have sent the link?

Yes. Delete the shared calendar or regenerate its feed token and the old link stops working immediately — the subscription on the other end simply shows nothing from then on. You never have to ask the recipient to remove anything.

Set this up in CalendarPipe

Connect Google, Outlook, or Apple Calendar and build a pipe that filters and transforms your events exactly how you want — in a couple of minutes.

Get started free