Terms

What the service does

exceptwhen lets an account author schedule source text, compile it, publish feed configuration, and serve calendar output from active feed tokens. The service can also show explanations for generated events.

Generated schedules reflect the source facts and rules stored on the account. The service shows explanations for generated events and diagnostics when a schedule cannot be published.

Signup and access

Customer signup opens only when the deployment is configured for it. When signup is closed, direct signup and checkout requests return a stated refusal instead of creating an account or starting payment.

A free account may author one schedule and hold one feed token, with no time limit. Downloading the calendar as a file needs the one-time purchase. Serving a subscribable feed URL needs the ongoing subscription. An operator can also grant comped access.

Billing states

The store distinguishes free, one-time paid, subscription active, subscription past due, subscription canceled, admin comped, and unknown billing states. Unknown billing state is not treated as paid access.

A feed URL on an account that has never held the ongoing subscription does not serve its events, whether the account is free or has bought the one-time download; it answers with a notice saying the calendar is not published. Past-due and canceled accounts keep serving the events already published, alongside a notice, and a canceled subscription can remain active until its stored current period end.

Once a subscription is past due or canceled, the account keeps what it has and can still sign in, open its schedules and preview the dates they produce. It cannot edit, mint feed tokens, change feed settings, publish, serve a feed, or export until access is restored. A cancellation that has not yet reached its paid-through date is still treated as paid, and none of these refusals apply to it.

Published feeds

Feed URLs are credentials and should be protected like credentials. Anyone with an active feed URL can read that published feed without signing in.

A feed URL answers differently depending on why it is not publishing, and the two cases are not the same. On an account that has never held the ongoing subscription the URL serves no events and carries a notice saying the schedule is not published to that address. On an account whose subscription is past due or canceled, the URL returns the events already published and adds a notice saying the schedule has stopped updating; it is not an active serving feed. Both responses are served with `Cache-Control: no-store` so a restored account can start updating again. A calendar app still controls when it fetches and what it has already cached.

Open legal terms

This page describes current product behavior. It does not set a retention period, liability limit, governing law, dispute process, tax commitment, service-level commitment, or support commitment. Those are owner decisions that are not encoded in the repository.