Who is responsible
Helios Intelligence Ltd operates ClearPath and is responsible for the personal information described here. Our registered details are below. Contact mic.con87+clearpath@gmail.com for a privacy question or request.
Information we use
- Your email address, profile name, sign-in information and project permissions.
- Building addresses, project answers and the names and contact details of clients, designers, contractors and other people entered by project members.
- Uploaded documents and their versions, extracted text and facts, page previews, draft documents, comments, findings, review decisions and exports.
- Invitations, information requests and delivery records; purchase references and payment status; security, technical and service-usage records.
You provide information when you use the service. Other project members may also add information about you or invite you to a project. Only upload material you are entitled to share. Avoid unrelated sensitive information. We need an account email to provide signed-in access and enough project information to run the relevant checks.
Why we use it
We use account and project information to provide the service you request: access, document handling, preparation checks, assistance, collaboration and exports. We rely on performance of our agreement with you for those account and service functions.
We rely on legitimate interests in operating a secure and useful service for access controls, abuse prevention, troubleshooting and project collaboration involving people named by other users. These interests do not remove those people's privacy rights. We use billing and related records to meet applicable legal obligations where these apply. We do not use your uploaded documents for advertising.
AI assistance and your decisions
ClearPath uses OpenAI's API to help identify documents, extract information and assist with questions and drafts. Relevant project information, document text or page images can be sent for that purpose. API data is not used to train OpenAI's models by default; this is not a promise of zero retention.
Rules and checks identify items needing attention. You can review sources, correct document types and record decisions. Findings and drafts are not a regulator's decision or a professional assessment. Your recorded reasons and account attribution can appear in project history and exported reports.
Who receives information
Access in the app follows project and workspace permissions. People you give access to can view information available to their role. Authorised service operation may also require access. If a member downloads or shares an export, that copy is outside the app's access controls.
We use Supabase for accounts, database and file storage; Vercel for the website; Railway for document processing; OpenAI for AI assistance; Resend for transactional email; and Stripe for the payment integration. Information needed for each function is processed by that provider. Our support mailbox is hosted by Google. Payment-card details belong in Stripe's payment form, never in a project document or support email.
Project database and file storage are configured in Supabase's London region. Other processing, provider support and backups may take place outside the UK. Location and retention depend on the service and its configuration; we do not claim that all processing stays in the UK. Contact us for information about the providers and transfer arrangements relevant to your project.
Retention and deletion
Project information is retained while the project remains in your account, including previous document versions and review history. Uploading a replacement does not delete its earlier version. Project owners can delete projects and authorised editors can remove documents.
Deletion removes the relevant live application records and attempts removal of stored files, previews and exports. Storage cleanup can need follow-up if a provider cannot complete it. A deletion audit can remain at workspace level. Deleting a project is not the same as deleting your account, and it does not immediately remove every provider log, backup or copy another member downloaded.
For other records, the relevant criteria are whether they are still needed to run your account, investigate a specific security or service issue, handle a complaint or dispute, or meet applicable legal record-keeping duties. Provider-held logs and backups follow the provider's applicable retention arrangements. We do not promise an automatic expiry period that the service does not implement. Contact us to request account deletion or help with remaining data.
Cookies, saved answers and optional measurement
Authentication cookies keep signed-in access working. Browser storage can keep your intake answers while you move from starting a project to signing in. The personal intake copy is replaced with a small completion reference after it is saved successfully. You can clear this site's browser storage; doing so may sign you out or remove an unfinished local draft.
Optional product measurement, when enabled, sends selected usage events to PostHog. The implementation excludes document contents, filenames and free-text answers, but can include an account identifier and technical request information. That information is not anonymous merely because names and email addresses are excluded.
Your rights and complaints
You can ask for access, correction, deletion, restriction or a portable copy of your personal information, subject to the applicable conditions. We may need to verify that the request is yours and distinguish your information from another person's project records.
You can object to processing based on our legitimate interests. Explain the processing you object to when you contact us. If we rely on consent for a particular activity, you can withdraw it without affecting earlier lawful processing.
Email mic.con87+clearpath@gmail.com. You can also complain to the Information Commissioner's Office. For practical account and upload help, see Support.