Frequently asked questions

Cadence is an open-source tracker for recurring behaviors. You define a Behavior and its Schedule, and Cadence creates each Occurrence on a today-first timeline. Completed means the user declared the occurrence completed. Not Completed means the user declared the occurrence not completed. Unresolved means the user has not made a decision.

Unresolved means the user has not made a decision. Prior-day Unresolved Occurrences collect in Needs decision until you decide them. Cadence never converts silence into failure.

Cadence keeps the Record focused on explicit Decisions. It shows Adherence over 7, 30, or 90 days without turning a streak or score into the goal.

Yes. An Occurrence scheduled for today, or one still in Needs decision, can carry elapsed time. Start, stop, and reset the timer. Reviews show totals and averages alongside Adherence.

Cadence preserves title and description revision history in JSON and BehaviorLog exports. The current app does not provide a full revision browser.

You can add an optional note and elapsed time to an Occurrence. Context does not decide whether the Occurrence is Completed or Not Completed.

Cadence shows Adherence across 7, 30, or 90 days. Adherence is the share of decided Occurrences marked Completed. Unresolved Occurrences remain separate from final calculations.

Cadence provides prepared prompts. You export the data and choose an external AI service. Cadence does not send behavior data to an AI provider.

No. Cadence tracking works without Calendar. The optional connector is currently available only to Google OAuth test users while the app remains in Testing mode.

After separate consent with the same Google identity used for Cadence sign-in, Google grants read-only access to your subscribed calendar list and events on calendars you can access. Cadence reads the list so you can choose calendars, then fetches events only from selected calendars for the days displayed in Timeline. Depending on Google permissions and event data, details can include titles, descriptions, times, locations, organizers, attendees, conference details, attachment links, and Google event links.

No. Cadence requests read-only Calendar access. It cannot create, change, or delete Google events, and it does not download attachments automatically.

Choose Disconnect Google Calendar in Settings. This removes the live server credential and requests global revocation of the Calendar grant. Web sign-out ends only that Cadence session and leaves the account-level Calendar connection active. Disconnecting a Cadence account on desktop clears that Mac's Calendar cache but does not revoke the global grant. An offline device may retain stale cached event details until it reconnects or its Cadence account is disconnected.

Cadence is single-player by design. There is no social feed or collaboration layer. Read the Privacy page for the current data practices and the Trust page for bounded operational evidence.

Yes. Export your history as JSONL, JSON, CSV, Markdown, BehaviorLog bundle. These files can be inspected without Cadence.

Only when you choose to include it. Exports omit timing data by default because exact session timestamps can reveal activity patterns.

BehaviorLog is the open portability standard used by Cadence. A bundle contains plain JSONL files, a manifest, schemas, and SHA-256 checksums. The standard lives at https://github.com/emixd12/BehaviorLog-Bundle.

Cadence is currently available without charge.