Your hours. Clear boundaries.
This page describes the pilot implementation. Paid subscriptions are not available, and manual planning does not require an account.
Current manual mode: team setup and activity counts stay in your browser. Optional connected mode requires separate service activation, explicit authorization and server storage. Do not enter confidential calendar details into pilot feedback.
Manual planning and device storage
Names, time zones, availability windows, date exceptions and manual pins are saved in browser local storage. The planner calculates schedules in a browser worker. It does not transmit these inputs to a calendar provider in manual mode. Download team JSON to back up or move your setup. Starting a new team keeps a recoverable previous setup on this device.
Local activity and pilot feedback
Successful summary copies and calendar/schedule downloads increment counters on this device. There is no central analytics endpoint in this release. The pilot feedback control downloads a report containing your answers, member count and local activity counts. It does not include teammate names, email addresses, calendar events or availability windows automatically. You decide whether and with whom to share that report.
Optional connected workspaces
When the connection service is activated, Google sign-in identifies the account that owns a workspace. Saving a team to a connected workspace transmits its setup to FairOverlap’s server. Member connection links allow each person to authorize their own Google account. Organizers can see connection status and availability blocks for scheduling; they do not receive OAuth tokens or event titles from this integration.
The first Google Calendar integration requests free/busy access, which returns occupied intervals. This initial integration checks only the connected Google account’s primary calendar. Calendar tokens are encrypted before storage. Disconnecting removes the stored calendar credential. The service does not request permission to create or delete calendar events. Direct event publishing and Microsoft calendar integration are not part of this release.
Calendar checks and limitations
Calendar checks are snapshots, not guaranteed reservations. A later calendar change may conflict with a generated plan. Missing, disconnected or failed calendar data is shown explicitly; it must not be presented as confirmed availability. Work-life preferences still come from each member’s declared windows.
Exports and deletion
ICS exports contain tentative events and do not send invitations. Files and copied summaries can contain team names and local meeting times; review them before sharing. Clear this site’s browser storage to remove manual setup, its previous-team backup and local counters. Connected workspaces offer a delete control; deleting a workspace removes its member connections and saved setup. Disconnect/revoke access in your Google account if you no longer want FairOverlap access.
Hosting and operational data
Cloudflare hosts the site and processes normal network request information. Connected-mode server errors use generic responses and do not intentionally log calendar tokens. No advertising or third-party tracking scripts are included.
Operator contact details will be published before connected mode is activated.
Before a public connected-calendar launch
The operator’s business identity, contact email and applicable terms must be added before opening a public connected-calendar service. Google OAuth verification and retention settings must also be reviewed. Until then, connected mode is restricted to an explicitly configured pilot allowlist. This notice describes behavior; it does not create a paid service agreement.