> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_15/session_02_security_and_privacy_vault.md).

# Session 02: Security And Privacy Vault

**Session ID**: `phase15-session02-security-and-privacy-vault` **Package**: public-website **Status**: Not Started **Estimated Tasks**: \~18-24 **Estimated Duration**: 2-4 hours

***

## Objective

Build `/security` with precise local-first lifecycle, consent, redaction, analytics, optional integration, and no-overclaim boundaries.

***

## Scope

### In Scope (MVP)

* Create or complete `src/pages/security.astro`.
* Build trust manifesto section.
* Explain local-only data lifecycle.
* Explain what stays on the machine by default:
  * Prompts.
  * File paths.
  * Terminal output.
  * Local event snapshots.
  * Credentials.
* Explain optional integration boundaries:
  * Optional War Room.
  * Optional outbound adapters.
  * Optional future hosted services.
* Add redaction and consent guardrails.
* Detail passive Settings status and strict telemetry blocks.
* Add analytics posture:
  * Absent by default.
  * Future analytics must use existing Umami guardrail posture if approved.
  * Never collect prompts, local paths, replay data, demo payloads, terminal output, credentials, or user-provided code.
* Add security FAQ.
* Link to product, how-it-works, demo, and docs.

### Out of Scope

* Legal privacy policy page.
* Security certification claims.
* Full threat model documentation.
* Trusted unified erasure claim.
* Hosted identity claim.
* Production-hosted validation claim.

***

## Prerequisites

* [ ] Phase 14 product/how-it-works pages completed or link destinations planned.
* [ ] Copy guardrails from current security posture reviewed.

***

## Deliverables

1. `src/pages/security.astro`.
2. Security boundary component or sections.
3. Security FAQ data/content.
4. Metadata and structured data if appropriate.
5. Conservative copy reviewed against known no-claim boundaries.

***

## Claim Boundaries

Allowed first-release claims:

* Core workflow is local-first by default.
* No hosted account required for the core workflow.
* Analytics are absent by default.
* External demo and docs links are explicit.
* Optional integrations are boundary-aware and should be described as optional.

Do not claim:

* Hosted identity, SSO, org membership, public collaboration safety, or production auditability.
* Full trusted unified erasure.
* Formal mobile/WCAG certification.
* Production-hosted app validation.
* Broad media readiness.
* Remote execution, real file/git/terminal/Docker executors, or inbound command support.

***

## Task Expansion Guidance

When expanded with `plansession`, keep the checklist to 18-24 tasks covering:

* Security route.
* Trust manifesto.
* Local lifecycle section.
* Data-stays-local list.
* Optional boundary section.
* Redaction/consent copy.
* Analytics posture.
* Security FAQ.
* Cross-links.
* Metadata.
* Accessibility review.
* Copy no-claim review.
* Build/typecheck.

***

## Success Criteria

* [ ] `/security` renders with complete first-release security content.
* [ ] Local-first, optional integration, analytics, and data-handling claims are precise.
* [ ] Known no-claim areas are not converted into product promises.
* [ ] Page links to related product and setup context.
* [ ] No tracker, analytics, or form code is introduced.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_15/session_02_security_and_privacy_vault.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.