PolicyWorkspacePlanning lab

Notice at collection

This page summarizes the categories of information collected from California users and the business purposes for that collection in the current product implementation.

CategoryExamplesBusiness purpose
IdentifiersBrowser-generated customer reference for free-access session state, auth session cookie identifiers, partner click IDs, export IDs, request identifiers.Maintain access features, partner attribution, export retrieval, and abuse controls.
Planning profile dataNames you enter for records, product category selections, locations, amounts, time horizons, assumptions, notes, and product-specific inputs.Generate planning records, assumptions, checklist outputs, and export content where supported.
Internet or network activityStructured lifecycle events, request metadata, rate-limit signals, and page/feature usage tied to the product workflow.Measure product usage, detect abuse, troubleshoot failures, and monitor service quality.
Partner and access activitySelected access label, legacy webhook status, partner click metadata, postback status, and routed-action details.Maintain free access state, reconcile partner handoffs, and measure conversion paths.
Account and collaboration dataWorkspace email, saved planning profiles, and invited team-member email addresses.Authenticate a workspace session, store reusable records, and coordinate team-oriented planning workflows.
  • • Planning drafts are browser-local by default.
  • • Saved scenarios can sync to backend storage for the current browser session reference and signed-in workspace history.
  • • Authenticated workspaces can store saved planning profiles, scenario history, invited member records, and sign-in code delivery records.
  • • Exports, explicit saved-scenario sync, partner routing, telemetry, free-access state, and workspace features use backend services.
  • • Backend app data can be pinned to a durable directory with `SMB_APP_DATA_DIR` or moved onto Firestore with `PERSISTENCE_BACKEND=firestore`; without a durable backend, storage defaults may reset with the environment.
  • • Current account and workspace records are lightweight product sessions, not a full enterprise identity stack.

This is a product implementation summary for planning and review. It is not legal advice and should be reviewed against the actual deployment, vendors, and retention settings in production.