Privacy policy

What the connection accesses

With an adult’s Google authorization, Project Little Orbit reads the account’s calendar list so that the adult can choose calendars and verify their available access. It reads selected calendars’ event titles, descriptions, locations, dates, times, time zones, cancellations and recurrence information, along with identifiers and version information needed to synchronize them.

Project Little Orbit also checks event metadata, including whether an event has attendees or belongs to a recurring series, to determine whether an ordinary board edit is supported. OAuth access and refresh tokens are stored to maintain the authorized connection.

Google’s event permission covers the account’s calendars. Selecting sources in Project Little Orbit limits the board’s use; it does not narrow Google’s account-level grant. This Calendar connection does not request Drive, Photos, Gmail or Google profile permissions.

Why Project Little Orbit uses it

Selected events provide the household’s shared year and day views, Today and tomorrow plans, and relevant family schedule views. Adults choose which household people are associated with each selected calendar.

Where an adult enables board edits and the source has verified Google write access, Project Little Orbit can send supported one-off event creations and edits to that explicitly selected calendar. Recurring and invited events remain view-only on the board in this prototype. Changes are not copied automatically across different calendars, and the integration does not send invitations.

Project Little Orbit follows the Google API Services User Data Policy, including its Limited Use requirements. Google user data is used for these household Calendar functions, not for advertising, sale, data brokerage or training AI models.

Where data is stored and who can see it

Imported events, source choices, local annotations and queued changes are stored on the household-controlled Project Little Orbit server. Credentials are stored separately in owner-only local configuration and grant files. These file protections do not imply that the database, disk or recovery archives are encrypted.

Selected calendar details are visible to household members and other people who have access to the board according to its local privacy settings. Household maintainers with server or recovery-copy access can also access stored data. Treat physical and local-network access as part of the household’s privacy choices.

Household-approved private recovery copies can include Calendar records and reusable connection credentials. Their storage and retention are controlled by the household; a local backup does not authorize a public or cloud copy.

What leaves the board

The Calendar integration communicates with Google to authorize and renew the connection, retrieve selected data and submit deliberate supported changes. It does not upload Calendar contents or credentials to this public information site, to an advertising service or to an AI service.

Cloudflare hosts these public pages and may process ordinary request information, such as an IP address and HTTP headers, to deliver and protect them. See Cloudflare’s privacy policy. These pages contain no analytics scripts, advertising, sign-in forms or Calendar integration code.

Retention, disconnect and deletion

Project Little Orbit keeps imported records, annotations and queued drafts locally for household use, offline access and recovery until the household deliberately removes them. No automatic Calendar-history retention period is promised by this prototype.

Use Settings → Calendar connections → Disconnect on your local board to disable that account’s selected sources and request Google grant revocation. Successful revocation removes its local grant file. If Google revocation fails, sources stay disabled and Project Little Orbit asks you to retry or revoke access at Google. You can also remove Project Little Orbit’s access through your Google Account’s third-party connections settings.

Disconnect does not automatically erase imported events, queued drafts or earlier recovery copies. To request deletion of local data or backup copies, contact your household’s Project Little Orbit maintainer. Local cleanup does not itself delete the original events held by Google.

Adult-managed access and policy changes

Google connection and calendar selection are adult-managed household setup steps. Household members can use the board without signing in to their own Google accounts; children are not asked to grant Google account access.

Material changes to the data accessed or its use will be described here and in the relevant setup flow before new access is requested. An additional Google integration, such as Drive photo access, requires its own disclosure and authorization.

Questions or data requests

Contact the adult who maintains your household’s Project Little Orbit. The Google consent screen also displays the project’s user-support email. Do not send passwords, authorization codes, tokens or client secrets in a support message.