Updated 12 November 2026.
Information used to provide the service
Blakeport Base handles account sign-in and passwords. Kincharter uses the verified account identity and necessary session information. Depending on the features used, it keeps assessment answers, saved progress, planning work and notes, named people and roles, uploaded documents and extracted information, signed versions, sharing records, saved scenarios and retained AI-generated work.
Payment references, necessary technical activity and security records support billing and operation. Browser preferences may remember choices such as currency. This page does not introduce advertising or tracking tools.
Customer enquiries
If you use the contact form, we receive your name, email address, enquiry category and the message you choose to send. We use these details to handle the enquiry and reply, through our email delivery service and support mailbox. They are not sent to AI or automatically added to marketing lists or the customer CRM. This form does not accept attachments; please do not include passwords, card details or private family plans.
The application does not save a contact-message record in its database. The delivery service and receiving mailbox process the email; their retention and deletion arrangements still need to be confirmed. A necessary security cookie protects form submissions, and limited rate-control information helps prevent spam.
Private work, access and sharing
Private family content is protected by encryption and workspace permissions. Authorised users can read the information their role permits. Reports downloaded by a customer are readable files; protecting the downloaded copy also depends on the recipient's device and file controls.
Public search pages must not contain customer answers, results, plans, documents, private identifiers or access links. Permission to use a feature does not make its information public.
AI assistance
Selected information passes through a local identity-masking boundary before external AI processing, with protected transmission and local handling of the answer. Masking reduces identifying detail but does not guarantee irreversible anonymity. The provider can read the masked message it receives. Provider retention, training use and processing locations must be disclosed for the actual services enabled.
Service providers and the customer CRM
Hosting, payments, transactional communications and any enabled AI or CRM connection involve service providers. The provider information must identify their roles and applicable processing locations and safeguards.
The approved Kincharter CRM scope is limited to basic contact information, an authorised answers-or-four-area-summary profile, completion indicators and minimum agreed service-use information. Private plan contents, planning notes and uploaded documents are excluded. This describes the permitted scope, not a claim that every optional connection is enabled.
Retention, deletion and requests
Planning records, derived copies, operational records and backups need their own retention and deletion treatment. Exact periods and any backup exceptions are awaiting confirmation here; backup deletion timing remains to be confirmed.
Use the contact form and choose “Privacy request” to ask about access, correction, deletion or other applicable data rights. Any necessary identity checks can be arranged separately. Ending a subscription and deleting account or plan information are separate actions.
Operator and processing details
The legal operator/controller, privacy contact, purpose-specific lawful bases, current provider and transfer details, retention periods and request-handling process are being confirmed.