Data & access

Privacy policy

Effective October 28, 2026

Conflx Founder Desk is a private planning application operated by Conflx. This policy explains its Google Calendar connection, private records and optional connections to AI assistants.

This public website contains application information and policies. It does not display private founder records or provide a public sign-in to the desk.

What the application accesses

With the account owner's consent, the application requests Google's calendar.events.owned permission. That permission covers reading, creating, editing and deleting events on calendars the account owns. The current sync code restricts requests to one configured calendar and its explicitly linked, published milestones.

For those events, full event responses can contain titles, dates, descriptions, event identifiers, version information, recurrence and attendee details. The application checks these fields to recognize the linked milestone and detect changes that require review. It does not use this access to browse unrelated calendars or build profiles of attendees.

How Google data is used

Google event data is used to reconcile selected milestone dates with the private timeline, detect conflicts and report whether synchronization succeeded. The date worker changes only all-day date boundaries after checking the latest event version. It does not send invitations, add guests or meeting links, delete events, or automatically publish proposed work.

Conflx Founder Desk does not sell Google user data, use it for advertising, or use Google Workspace API data to develop, improve or train generalized or non-personalized AI or machine-learning models. Its use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.

Where records and credentials are stored

The private desk stores planning records, selected calendar and event identifiers, agreed date baselines, source evidence and change history on the owner's computer. Source records and their history are backed up to a private GitHub repository. Full event responses are used in memory; sync status and comparison snapshots retain the fields needed for validation rather than copying unrelated notes or attendee identities into status reports.

Google OAuth client credentials and refresh tokens are stored in Windows Credential Manager on the owner's computer. Access tokens are used in memory. Credential values are not written to the source repository, application status reports or this public website. Google requests use HTTPS.

Connected assistants and service providers

The owner may authorize ChatGPT/OpenAI or Claude/Anthropic to read desk records and request changes through an authenticated connector. When used, those providers receive the records returned to that assistant, which may include synchronized dates. The Google date worker contacts Google directly; it does not send full Google event responses to an AI model for reconciliation.

OpenAI's private tunnel and the ngrok relay can carry connector traffic. Ngrok terminates HTTPS and can process the traffic it relays to Claude. GitHub stores the private source backup. Each service processes data under its applicable terms and the owner's account settings. Connected assistants should be configured consistently with the Google Limited Use requirements.

This public information site is hosted using OpenAI Sites and Cloudflare infrastructure. Hosting providers may process ordinary request information, such as IP addresses and request times, to deliver and protect the website. These pages add no advertising, analytics scripts or data-entry forms.

Retention and deletion

Private timeline records and change history remain until the owner removes them. Previous versions may remain in repository history and backups; editing or removing a current record does not automatically erase those copies. Google Calendar retains its own events under the account owner's settings.

Revoking the application's Google access stops future authorized syncing. It does not delete Google events, local records or backups. The owner can separately remove saved connection credentials from the operating-system credential store and manage local and backup retention. Contact support for questions about data access or deletion.

Your choices

The account owner chooses which milestones are published, can disconnect assistants, and can revoke Conflx Founder Desk's access in Google Account connections. Changes outside the supported date-sync scope require deliberate review.

Changes and contact

This page will be updated when the application's data practices change. Its effective date identifies the current policy.

For privacy or access questions, contact support@conflx.app. Do not include passwords, tokens, client secrets or other credentials.