Questions worth a direct answer.

A placeholder occupying the same period of time, carrying a label you chose. No subject from the real meeting, no attendees, no notes, no location, no links, and no attachments.

Someone looking at that calendar learns that you are unavailable. They do not learn anything about why.

Not from the placeholder itself, because it carries no information from the original meeting. You set the label per calendar, and it is never derived from the real meeting’s subject, so whatever you pick, it cannot leak by accident.

Anyone with access to a calendar can of course see the shape of your week, exactly as they can today when you block time by hand.

No. Avenclave runs on your machine and works directly against your own calendar providers. There is no synchronization service, no copy of your schedule held by us, and no analytics or crash reporting sent anywhere.

Deliberately little, inside your own Windows user profile. The local store holds busy start and end times, a mapping row per placeholder, and opaque identifiers, with no subjects, attendees, bodies, locations, or attachments.

That is the point. The less Avenclave keeps, the less there is to lose, and the simpler the privacy story stays.

No. Avenclave does not request tenant-wide application access to an organization’s calendars. It uses each provider’s own sign-in and the access you already have, keeping each account in a session of its own, and it asks for no elevated permissions on your machine.

To be precise about the limit of that claim: your organization still controls its own calendar and how long your sign-in stays valid. Avenclave avoids needing an administrator to grant it access; it does not and cannot override the policies an administrator sets.

No. Avenclave keeps its own sessions, one per account, and does not touch your ordinary browsing or leave anything on screen. It works in the background and stays out of your workspace.

That is up to you. Avenclave makes a first pass shortly after your accounts are ready, then repeats on the cadence you pick: roughly every five minutes when you want changes reflected quickly, about once an hour when you would rather it stay quiet, or a balanced setting in between. You can also run a pass on demand.

It only looks a configurable number of days ahead. Beyond that window, nothing is planned until the window reaches it.

That is decided by your provider and by each organization’s policy, not by Avenclave. Some policies keep a session valid for a long time; others require a fresh sign-in as often as once a day.

We treat occasional interactive re-authentication as an accepted cost of not asking for tenant-wide administrative access, and we will not claim you can set Avenclave up once and never see a sign-in prompt again. What we can do is make it safe: writing stops until the session is genuinely restored, and it never resumes against a different account.

The placeholder is moved to match, or removed. Avenclave compares what your calendars currently say against what it previously recorded and plans the smallest correction.

Avenclave notices on a later pass and restores the placeholder to match your real availability, because the source meeting is still there. Placeholders are output, not input; editing one does not change what you are actually busy with.

It is specifically built not to. Avenclave records the identity of every placeholder it creates before it creates it, and will only modify or remove an item when it can find that exact identity, exactly once, in fresh calendar state.

If it finds nothing, finds two matches, or cannot see identities at all, it reports the situation as Inconclusive and changes nothing. A calendar item that merely looks like one of its placeholders is never treated as one.

Availability is reconciled in absolute time, so a meeting booked in one time zone occupies the correct hour on a calendar in another, and a recurring series stays anchored correctly when a daylight-saving transition moves underneath it, including between a region that observes it and one that does not.

Yes. Recurring series, individual exceptions to a series, and all-day and multi-day events are all reconciled.

If Avenclave ever meets a calendar entry it does not understand, it reports it as an unsupported shape rather than quietly treating it as free time. Being told about a gap is very different from not knowing one exists.

No. That is the honest cost of running locally with no service in the middle: when the machine is off, nothing is synchronizing. Avenclave picks up where it left off when it comes back, and it re-establishes the truth from your calendars rather than assuming its last view is still correct.

No. Avenclave is for one person holding several calendars. Team and organization-wide availability is a different product with a different privacy model, and it is not something we are building.