Privacy Notice

Scope

This notice applies to faebuild.com, the beta access request form, Fae's desktop app, and the Fae Browser Bridge Chrome extension. Fae is in beta, and product privacy details may change as the beta program changes.

Beta Access Requests

The beta request form sends the submitted email address, selected workflow track, and optional workflow note to Fae. That information is used to reply, evaluate fit, manage the beta program, and route feedback.

The website is hosted with GitHub Pages, and form submissions are processed through FormSubmit before routing to Fae email. Fae does not sell beta submissions or use them for advertising.

Product Privacy Posture

Fae is designed around local-first work: local models, local project state, local artifacts, local settings, and local memory where possible. Optional account, managed model, browser, GitHub, MCP, cloud provider, and support workflows may involve external services when the user configures or uses those surfaces.

Local Profile and Insights surfaces are product UI, not a promise that every action avoids external processing. The exact provider or integration used for a task depends on model choice, settings, and enabled capabilities.

Fae Browser Bridge

Fae Browser Bridge is the Chrome extension that connects the Fae desktop app running on your computer to Chrome tabs you explicitly allow Fae to use. Pairing requires a matching verification number and approval in Fae, and the extension shows its connection, control, pause, and Deep control state.

Information the extension processes

For a browser task you request, the extension may process the URL and title of scoped tabs; visible page text and structure; element and accessibility information; screenshots; console messages and network-request metadata during Deep control; download status; and browser actions requested through Fae. Chrome may categorize scoped URLs and titles as web history, but the extension does not read your general Chrome history.

If you explicitly approve a cookie diagnostic, the extension processes cookie names, domains, paths, expiration times, and security flags for the scoped page. Cookie values are discarded inside the extension and are not sent to Fae. The extension does not read Chrome's saved-password store and refuses automated input into fields that appear to contain passwords, MFA codes, tokens, API keys, or recovery codes.

How information is used

This information is used only to connect to the local Fae app, show connection and control state, enforce the sites and tabs you approved, perform browser actions you requested, diagnose the connection, and provide safety controls such as Stop, pairing approval, protected-action approval, and Deep control expiry.

The extension communicates with Fae through an authenticated WebSocket on the loopback interface of your computer. Page content needed for a task may then be sent by Fae to the model provider you selected, according to Fae's Browser access and model privacy settings. A local model can keep that model processing on your computer. External model providers process data under their own terms and the configuration you selected in Fae.

Fae does not sell extension data, use it for advertising, build advertising profiles, or use it for lending or credit decisions. Humans do not read browser content unless you deliberately provide it for support, it is needed to investigate abuse or a security incident, or disclosure is required by law.

Storage, retention, and deletion

Chrome's local extension storage holds the installation identity, local Fae endpoint, pairing credential, connection and pause state, site allow/block lists, action-cursor preference, bounded diagnostics, and Deep control lifecycle state. The raw pairing credential remains in extension storage; the Fae app stores only a hash. You can reset pairing, clear extension data, remove site access, forget the paired browser in Fae, delete relevant Fae conversations or data, or uninstall the extension.

Security and user control

The bridge accepts only local loopback endpoints. Fae scopes actions to approved tabs and sites, visibly groups tabs it opens, applies separate approval gates to protected actions such as downloads, provides an immediate Stop control, and time-boxes Deep control while Chrome displays a debugger notice.

Chrome Web Store Limited Use

The use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Accounts, Managed Beta, and Providers

Closed beta builds may use account sign-in for entitlement and may show managed model balances or capacity state in Profile. Selected testers may receive Fae/admin-granted managed beta access. Public managed checkout is not represented as open by this site.

Bring-your-own-key cloud providers, Fae-managed models, browser tools, GitHub, MCP servers, FormSubmit, and other integrations are governed by their own terms and privacy practices. Configure them only when they are appropriate for your project.

Diagnostics and Support

Diagnostics are intended to be explicit, privacy-bounded support exports. Do not send secrets, credentials, private keys, regulated data, browser cookies, raw databases, or confidential project material unless you have verified the exact support workflow and intentionally choose to share it.

Your Choices

To delete or correct a beta request, stop beta follow-up, or ask a privacy question, email early@faebuild.com.