Trust & security
How we protect
your project data.
Your documents are private. You choose who joins your project, and access follows their assigned role. Here we explain how files are stored, how our AI provider processes information, and how you keep track of changes.
Read our privacy notice for data handling and your rights, or contact support with a security or privacy question.
Sam uploaded the revised sheet
North point and scale added · linked to Site or block planOriginal upload retained
Available in version history for comparisonIllustrative project · current and earlier files remain distinguishable.
Private files and controlled project access
Document storage is private. Files are opened through temporary, expiring links after an access check. Database access rules restrict project records to authorised workspace and project members.
Access follows your role
Your project permissions determine who can view files, make changes and manage collaborators. Inviting someone to one project does not give them access to every other project.
Where files are stored
The project database and file storage are configured in Supabase’s London region. The website and document processing use other service providers, so processing locations can differ.
Authorised service processing also needs access to data. The providers and their purposes are explained below and in the privacy notice.
How AI uses your documents
ClearPath uses OpenAI’s API to identify document types, extract details and review supplied content. Relevant document text or images are sent to that service for the requested AI task.
Training policy
OpenAI states that API inputs and outputs are not used to train its models by default. ClearPath’s AI requests use the API rather than a public ChatGPT conversation.
Provider retention
OpenAI’s standard abuse-monitoring logs may contain request content and are normally retained for up to 30 days. Provider policies and exceptions apply; ClearPath does not promise zero retention.
The services behind ClearPath
Supabase hosts the database and files; Vercel runs the website; Railway runs document processing; OpenAI provides AI assistance; Stripe handles checkout; and Resend sends transactional email. Each processes the information needed for its part of the service.
Document contents are excluded from product analytics. Project access controls also keep another customer’s project documents outside your workspace.
A clear history of file changes
A revised upload becomes a new file version. Earlier versions remain available, and the project records who uploaded the file and which version is current. A drawing’s own revision, such as P3, is shown separately from the platform’s file version, such as v2.
Review findings refer to the document versions used in that check. After you change a file, run the checks again to review the updated content. Previous results are labelled when they no longer reflect the current application.
You choose the current files for submission separately from the full project library. Background material and earlier versions can stay with the team.
Control over collaborators and project data
Members with team-management permission can invite collaborators and remove their project access. Authorised editors can remove documents, and project owners can delete projects. Key actions are recorded in project history.
Deletion can require follow-up if a storage service cannot complete file cleanup. Provider logs and backups have their own retention periods. The privacy notice explains your rights and how to make a data request.
Requirements linked to published sources
Checklist items cite national requirements and guidance from Planning Portal and GOV.UK. Some applications also have reviewed local additions; other council requirements may still need checking. Higher-risk building control checks trace to the Building Safety Regulator’s published requirements and the relevant regulations.
Source dates and coverage limits are shown where available. A recorded local source is not a complete council check. Confirm any remaining local requirements with your planning authority.
Results you can check against the documents
AI-assisted findings show available source quotations, document references and the versions reviewed. If a page cannot be read or a comparison is incomplete, the result says so. Word extracts use text references rather than verified page numbers.
You and your professionals review the recommendations and decide what to change. Supported edits to unsigned Word documents need your approval before a new version is created; original files remain available. Starter drafts need your review and completion, then the completed document is uploaded for checking.
For higher-risk building work, checks cover document presence, structure and factual consistency. Your professionals remain responsible for the technical content and its adequacy. The fire and emergency file template provides headings for professional completion.
An independent preparation service
ClearPath is independent of government, Planning Portal, the Building Safety Regulator and local planning authorities. It helps your team prepare and review an application. You submit the chosen files through the relevant service, which assesses your application.
Start with the checklist for your project.
See what to gather, then bring your documents together and review what needs attention.
Free to start · No card required · England householder planning, lawful development certificates & higher-risk building control