Privacy Policy

The Fabric desktop application is a local-first tool. When you install it, all of your data — projects, agents, tasks, comments, settings, and work history — is stored in a SQLite database file on your own computer. Fabric does not operate a server that stores this data, and the App does not transmit it to us.

There is no sign-in, no account, and no user identifier associated with the App.

The following never leaves your computer unless you explicitly configure it to:

• Your project goals, workflow instructions, agent configurations, tasks, subtasks, comments, and worker activity history
• OAuth access and refresh tokens for services you connect (encrypted at rest using your operating system’s secure credential store, via Electron’s safeStorage API)
• Browser sessions created by agent browser automation, stored in ~/.orchestrator/browser-profiles/ on your machine
• Git clones, worktrees, and any files your agents produce

If you uninstall the App, or delete the database file at ~/Library/Application Support/Orchestrator/data.db (macOS), this data is gone.

The App performs network requests in four situations. In each, the data goes directly from your computer to the third party you chose — Fabric is not in the path and does not see the contents.

(a) Anthropic (Claude API).Agents in Fabric are powered by Anthropic’s Claude models. You supply your own Anthropic API key or Anthropic account credentials in the App. When an agent runs, the relevant task content, tool results, and conversation context are sent directly from your computer to Anthropic’s API to generate the agent’s response. Anthropic’s terms describe how they handle this data; we recommend you review them at https://www.anthropic.com/legal. Fabric receives nothing about these calls.

(b) Services you connect.When you connect one of these services through the App’s OAuth flow, the authorization redirect uses a loopback address on your own machine (http://localhost:19361/oauth/callback). The resulting access and refresh tokens are stored on your device. When an agent calls one of these services, the request goes directly from your computer to that provider’s API using your stored token. Fabric receives none of the data returned.

(c) Update checks. About once an hour and when the App launches, the App checks GitHub Releases to see if a newer version is available. This request is made directly to api.github.com. Fabric operates no update server and does not log or count these checks. GitHub may log the request as it would any API call.

(d) Browser automation targets. If an agent uses browser automation, your local Chromium instance loads the web pages that agent visits. Session data is stored in a local browser profile on your machine. Nothing about the browsing is sent to Fabric.

The App does not include any of the following:

• No analytics, product telemetry, or usage tracking
• No automatic crash reporting
• No user accounts, sign-in, or device fingerprinting
• No advertising or ad-identifier collection
• No background uploads of your data to any Fabric-operated service

Fabric’s use and transfer to any other app of information received from Google APIs adhere to the Google API Services User Data Policy, including the Limited Use requirements.

What we access. Only the Google Drive, Docs, and Sheets files that you explicitly select through the Google Picker, plus files that Fabric creates on your behalf inside a folder you have designated.

How it is used. Google user data is used solely on your own machine to provide and improve the user-facing features of the App.

What we do not do. We do not transfer your Google user data to any party other than as necessary for you to use the App.

Storage. Fabric does not store the content of your Google Drive files on any server.

Because the App stores your data locally, you control retention. To delete your data, delete the database file or uninstall the App. To revoke an integration, disconnect it from Project Settings; the stored tokens are removed from your machine immediately.

OAuth tokens are stored using your operating system’s secure credential store (Keychain on macOS) via Electron’s safeStorageAPI. All network requests to third-party services use TLS. Because the App runs on your computer, the overall security of the App’s data depends on the security of your device.

The Website is built with Next.js and hosted on Vercel. When you visit the Website, Vercel processes standard server request data (such as your IP address and user-agent) as needed to deliver the pages and protect the service.

We use Vercel Web Analytics to understand aggregate traffic patterns on the Website — pages visited, referrer, country-level location, and device type. Vercel Web Analytics is cookieless and does not use persistent identifiers to track you across sites.

If you join the waitlist, we receive the email address you submit. If you email support@fabriccalendar.com, we receive your email address and anything you send.

The desktop app has no Fabric subprocessors. The Website relies on the following:

Neither the App nor the Website is directed to children under 13 (or under 16 in the European Economic Area). We do not knowingly collect personal information from children. If you believe a child has provided personal information through the Website, contact us at support@fabriccalendar.com and we will delete it.

Fabric, LLC is based in Florida, United States. If you use the Website from outside the United States, you understand that Website information is transferred to and processed in the United States. The desktop App runs on your own device; we do not receive or transfer App data across borders.

We may update this Privacy Policy from time to time. If we make material changes, we will update the “Last updated” date above and give reasonable notice — for example, by announcing it on the Website or notifying newsletter subscribers. Your continued use of the App or Website after changes take effect constitutes acceptance.

Fabric, LLC
support@fabriccalendar.com
https://www.fabriccalendar.com