Skip to content
Floating KeysDocs

Trust

Privacy, authority and availability

This page states plainly what Floating Keys can do today, what it is designed to do, and the limits of each. If something here disagrees with a marketing illustration, this page is the reference.

How authority works#

  • Agents are principals. An agent acting for you has its own grants. What it may do is the overlap of your access and its access, and any explicit deny wins.
  • Mentioning is not sharing. Referencing a file or resource in a thread keeps that resource’s existing access rules. It grants nothing.
  • Proposals need a person. Suggested access changes are explainable recommendations with a purpose and duration. They have no effect until an authorized person confirms them.
  • Checks happen at the moment of action. Sessions outlive grants, so permission is re-checked when an action runs, not only when a screen loads.

What stays private#

  • Project threads are private to their owner. Project membership is not conversation sharing.
  • Including conversation context in a run is opt-in and explained before you choose it.
  • Finding existing agent projects on your computer reads folder and timestamp information, not prompt or reply content.
  • A connected AI tool sees only the Projects and permissions you approved. Its activity record leaves out prompts, messages and replies.
  • The planned hosted audit trail records what happened without storing prompt, file or credential contents.

The waitlist#

The public waitlist stores your email address, consent and confirmation timestamps, and verification and delivery records, so we can send a confirmation, limit repeated sends and later send a beta invitation. Signup records are stored in Google Cloud Firestore in us-east1; confirmation email is delivered through Resend. Confirming your waitlist email does not create an account, a Project or an invitation, and nothing on the public site can run an agent.

Site analytics#

The home page and these documentation pages use PostHog to record page views and page exits. Each record includes the page path and referring page with query strings removed, how far you scrolled, basic browser and device details, and a random identifier stored in your browser. Like any web service, PostHog receives your IP address. We do not collect page titles, clicks, anything you type, your waitlist email, session recordings or heatmaps.

After you sign in, the workspace records the same page views and page exits, with Project, thread and run addresses replaced by placeholders, and links them to your account’s internal ID. It does not send your name, email address or anything you type.

Account sign-in#

Sign in uses Firebase Authentication to create or return to an account. Google shares your name, email and basic profile information. We request no access to your Google files, mail or calendar. Email sign-in uses an emailed link; opening it on another device requires you to confirm the same email address.

Phone sign-in is implemented with Twilio Verify and awaits service configuration. When enabled, Twilio receives your mobile number to send and verify a one-time code; the server issues a Firebase session only after verification succeeds. Verification records expire after ten minutes, with short-lived send counters used to limit abuse. Your chosen identity remains in Firebase until account deletion. Phone and email identities are not silently merged.

The local safety boundary#

Availability at a glance#

Status as of November 2026
CapabilityStatusNotes
Public site, docs and waitlistLiveEmail confirmation only
Account sign-inLiveGoogle and emailed links; phone awaits configuration. Does not grant beta access.
Hosted chatPartialInvited accounts; free models, usage receipts
Hosted Projects and filesPartialInvited accounts; private Projects, saved text files
Project file searchPartialInvited accounts; text files only, from Project Overview, with exact cited passages
Connect an AI tool (MCP server)PartialPublic discovery; account connection not verified end to end
Desktop app with local CoreLocalSingle user, Apple-silicon Mac; no public download
Projects, threads, explicit dispatchLocalHosted Projects do not start runs
Run approval and reviewLocalBound to exact task, source and policy
Codex governed runsLocalVerified locally
Claude Code governed runsPartialSigned-in execution under verification
CursorPartialHistory import only, best effort
Imported agent historyPartialRead-only context, not resume
Connector registry and KeysPlannedRead-only connector tests only
Hosted agents and schedulesPlannedAfter worker isolation and recovery gates
Team collaboration and open sign-upPlannedA later, separate decision

Order of the beta#

The hosted beta is planned in stages. Each stage has to pass its own checks before it is offered. This is the intended sequence; dates are not promised.

  1. Waitlist — live now.
  2. Invited chat and Projects — under way for a small group: sign in, chat, keep private Projects and files, and see the same confirmed state after reload.
  3. Governed connectors — a small set of reviewed services with Keys, revocation and receipts.
  4. Durable agents — multi-step agents on isolated workers that recover without duplicate outside actions.
  5. Broader product — more views, connectors and team features as each one is qualified.

Status reflects November 2026. Planned items are design targets, not commitments to a date.