Public access lane
Review the open-source posture, managed-services options, and live public engagement views before requesting a signed-in workspace.
Privacy practices
OpenPlan is operated by Nat Ford Planning for agencies, RTPAs, counties, tribes, and consulting teams. This page describes what data the platform collects, how it is stored, who can see it, and how AI-assisted features are governed during supervised early access.
Data handling
Planning records, engagement inputs, modeling runs, and grant artifacts are isolated to the workspace they belong to. Row-level access controls enforce this at the database layer — not just in the UI.
Data uploaded by one agency or consulting team is not used to train shared models, seed other workspaces, or inform deliverables for another client. Workspace data stays within the workspace.
We ask for the data the planning work requires and nothing more. Sensitive engagement inputs, respondent identifiers, and confidential planning context are treated as confidential by default.
AI-assisted content
AI-assisted drafting is used inside OpenPlan for analysis, summarization, report scaffolding, and data cleanup. The platform labels AI-drafted content where it appears so reviewers can tell it apart from hand-authored work.
Screening-grade outputs from the behavioral modeling runtime and other internal prototype modules are never presented as planning-grade conclusions. Final client-critical analysis must be reviewed by qualified staff.
We do not sell or share workspace data with third-party model providers beyond what is strictly required to deliver the requested analysis. Where third-party inference is used, the integration is disclosed on the surface that invokes it.
Storage posture
Workspaces are backed by Supabase (Postgres + PostGIS). Authentication, storage, and row-level security are enforced by the database. Access is scoped to workspace members invited by the owner.
Planning deliverables, aerial imagery, model inputs, and generated packets are stored inside the workspace's own storage buckets. Owners can export their workspace data at any time for archival or handoff.
Production deployments run on Vercel. Runtime logs, error telemetry, and access records are retained for operational support and are not shared externally.
User rights
Workspace owners may request export of their data, deletion of specific records, or full workspace teardown. Requests are handled through the operator support channel once a workspace is active.
Engagement participants and survey respondents retain the rights granted by the agency or consulting team administering the engagement. OpenPlan does not independently monetize respondent data.
Where a planning deliverable must be preserved for regulatory or audit purposes, records may be retained in line with the agency's own retention rules — not OpenPlan's default lifecycle.
Operator
Privacy questions, export requests, and deletion requests can be directed to the operator via the sign-in surface's support channel once a workspace is active. During supervised early access, privacy posture is reviewed alongside terms and legal notices and may be updated as the platform matures.