Sharing your schedule without oversharing

The reason a lot of people never solve the schedule-sharing problem is not that they cannot find a tool. It is that every tool they try shares everything, and there are things on a calendar they do not want to hand over.

This is a legitimate objection and it deserves a better answer than “just use a second calendar”.

What people actually want to keep

In roughly the order it comes up:

• Medical appointments. Therapy, a scan, a fertility clinic, a consultation you have not told anyone about.
• Job interviews. For obvious reasons, and especially from anyone who might mention it.
• A second job. Common among shift workers and frequently not something they want discussed.
• Anything to do with a relationship that is not yet public.
• The things you are doing on your day off that you would rather not justify.

None of these are dramatic. All of them are enough to stop somebody sharing a calendar with a parent.

Why “share a calendar” usually fails here

A shared calendar is all-or-nothing by default. The usual advice is to keep a second, private calendar and put sensitive things there — which works, right up until the evening you add something quickly and it lands on the wrong one.

The failure mode is that the safety depends on you remembering, every single time, at the moment you are least attentive. Systems that depend on perfect recall from a tired person fail.

What good looks like

Three properties, and it is worth checking any tool for all three:

Per-event, not per-calendar. The decision should be attached to the thing, at the moment you create it, with a sensible default.

Private means invisible, not hidden. There is a real difference between “your mother can see that you are busy 14:00–15:00 with no details” and “your mother cannot see anything at all”. Busy-with-no-details still discloses something — a weekly Tuesday afternoon commitment invites a question you did not want. Proper privacy means the time reads as free.

Enforced by the server, not the interface. This sounds technical and is not. If privacy is implemented by the app declining to display something, then anything else reading the same data — an export, a sync, a future version — may not decline. If the server refuses to send it, there is nothing to leak.

That last one is how Freeish does it: private events are not filtered out for display, they are never sent to anyone else at all.

The middle option people forget

You do not have to choose between full disclosure and nothing. A useful middle is sharing only your work shifts and nothing else.

For most of the people asking — a parent doing pick-ups, a partner planning, a friend trying to find a free evening — your work schedule is the entire question. They do not need to know about the dentist. Sharing shifts and keeping everything else private is both the most private option and, usually, completely sufficient.

Different people, different amounts

The other thing worth having: not everyone needs the same view.

Your partner may reasonably see more than your mother. A friend organising a birthday needs less than either. Tools that support groups — Freeish calls them circles — let one event go to some people and not others, which is closer to how sharing actually works in life.

The alternative, which many people end up at, is sharing the lowest common denominator with everybody, so the person who should see more sees less.

A practical setup

What works for most people:

1. Work shifts public. That is the information everyone actually wants.
2. Everything else private by default, so forgetting to change something errs safe.
3. A tighter circle for a partner, if the tool supports it, for things they should see and others should not.
4. Nothing shared with anyone who has not been explicitly invited — and no directory, so nobody can find you.

The point of getting this right is not paranoia. It is that a sharing arrangement you trust is one you will still be using in a year, and one you do not trust quietly becomes one you stop updating.