Skip to content

privacy: what FTW Cloud sees and keeps when an assistant has access - #21

Merged
frahlg merged 2 commits into
mainfrom
privacy-assistants
Oct 17, 2026
Merged

frahlg merged 2 commits into
mainfrom
privacy-assistants

Conversation

@frahlg

@frahlg frahlg commented Oct 17, 2026 •

Copy link
Copy Markdown
Member

Problem

The privacy page says assistants come "later" and that we will update the page before they ship. FTW Cloud's MCP door and its keys part (ftwkeysd, AWS KMS) now run, and the offer key is pinned in srcfl/ftw#1680 and srcfl/ftw-app#80. The page has to say what changes before an owner can approve an assistant.

Change

The section "Assistants and support access, later" becomes "Assistants", in English and Swedish:

  • how an owner approves an assistant (Face ID in the app, or the box page with the house password), read by default, control as a separate choice, a length the owner picks up to a year, revocable;
  • that this connection is not end to end: FTW Cloud opens the box session for the assistant, keeps its key sealed by AWS KMS, reads questions and answers in memory while it passes them on, keeps none of them, and logs only a failed tool's name;
  • what FTW Cloud keeps per assistant (clients, agents and tokens in srcfl/ftw-cloud internal/oauth/store.go);
  • the data-free notices that reach owner phones even with the readable copy off;
  • that what an assistant reads goes to the company that runs it;
  • that Sourceful support access is not available yet.

The FTW Cloud section's storage paragraph points to the new section. The date moves to 17 October 2026.

When to merge

Merge when the first approval path reaches owners: a Core beta with the box page's Access UI and the pinned key, or a TestFlight build with srcfl/ftw-app#80. Until then the page would describe something owners cannot do.

The year comes with srcfl/ftw#1686, srcfl/ftw-cloud#27 and srcfl/ftw-app#82. Until they ship, the most an owner can pick is 30 days, so merge this with or after them.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 17, 2026 •

Copy link
Copy Markdown

Deploying ftw with  Cloudflare Pages  Cloudflare Pages

Latest commit: 3f68331
Status: ✅  Deploy successful!
Preview URL: https://0c9c0814.ftw-613.pages.dev
Branch Preview URL: https://privacy-assistants.ftw-613.pages.dev

View logs

Pairs with srcfl/ftw, srcfl/ftw-cloud and srcfl/ftw-app, which raise an
assistant's longest grant from 30 days to a year.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 17, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-17T08:13:42.382614Z 3f68331 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3f68331d18

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread privacy.html
<p>This connection is not end to end between you and your box. The assistant runs outside your home, so FTW Cloud opens the encrypted connection to your box for it. FTW Cloud makes a key for each assistant you approve and keeps it sealed by Amazon's key service (AWS KMS), which only that part of FTW Cloud may use. FTW Cloud reads the assistant's questions and your box's answers while it passes them on, holds them in memory only, and keeps none of them. When a request fails, it logs the tool's name, not what was read.</p>
<p>For each assistant, FTW Cloud keeps its name and web address as the assistant gives them, the public half of its key, which home it may reach, what it may do and until when, and hashes of its access tokens. Your box keeps a record of what each assistant read and did for 90 days.</p>
<p>Even with the readable copy off, FTW Cloud sends your phones a short notice through Apple's push service when an assistant gets access, asks for a change or is about to lose access. The notice names the assistant only if the readable copy is on.</p>
<p>What you let an assistant read goes to the company that runs it, such as Anthropic, OpenAI or Anysphere (Cursor), under that company's own privacy policy. Sourceful does not control what it does with it.</p>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Qualify the claim that energy data stays local

When an owner enables an assistant, this paragraph says home data is sent through readable FTW Cloud processing to an external provider, but the page lede and meta description still state categorically that energy data stays on the box and phone and describe the readable copy as the only exception. This makes the privacy summary and search snippet misleading for the newly documented assistant flow; add the assistant path as another explicit exception in both language versions and their metadata.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant