Information governance

Privacy & Security

Documented, risk-based information security with human oversight.

Scope
Website, enquiries, bookings, client engagements and the SharePoint client area
Policy owner
Justin Anderson
Version
1.4 · 27 October 2026
Contact
office@justinanderson.co.uk

1. Purpose and responsibility

This policy explains how we handle personal information and protect information entrusted to us through this website and our professional services. We are responsible for the personal information we collect for these purposes. Where a client engagement involves processing information on a client’s behalf, the respective responsibilities are set out in the agreed scope and any required data-processing agreement.

Our security objectives are to protect confidentiality, maintain the accuracy and integrity of information, and support its availability for authorised purposes. Controls are selected with regard to the information involved, the intended use and the associated risks. Responsibility for decisions, commitments and the authorised use of information remains with us.

This is a public privacy notice and security policy. It is not a statement of ISO/IEC 27001 certification.

2. Information we collect and why

Enquiries and brochure requests

We use contact details and information you provide to respond to enquiries and deliver requested material. Brochure requests record the email address, selected perspective, request time, brochure version and delivery status. A name or telephone number is not required to receive a brochure. Providing a telephone number does not itself request a call or consent to marketing.

Bookings and conversations

We use your name, email address, selected time, time zone and discussion notes to arrange and prepare for a conversation. A telephone number is required only for a WhatsApp call. We check work and personal calendar availability; the public booking page displays available times, not private event titles or details.

Booking records support confirmations, reminders, changes, cancellations and administration. A declined calendar invitation is flagged for review and does not automatically cancel a booking. Private management links permit booking changes and should be kept confidential. Advisory links may offer longer meetings; they do not grant access to documents or other people’s records.

Client-area files and collaboration

Once an engagement is agreed, JA may provide an invitation-only client site using Microsoft SharePoint. We process invited email addresses and account identifiers, files and document versions, authorship, permissions and service activity needed to deliver, administer and protect the shared service. Where enabled, comments and notifications also form part of the working record.

Microsoft handles sign-in and checks access to the site and its documents. Use the email address invited by JA. A link from our website does not itself grant access. Participants may be able to see each other’s names and contributions. Reading, editing, uploading, commenting and sharing depend on the role and permissions granted; these capabilities are not automatically available to every guest.

Material placed in a shared engagement area is visible to participants who have access to that area. Agree any restricted handling with JA before uploading. Do not upload material that you are not authorised to share. File-change notifications may be sent to the recipients configured for the engagement.

Professional and operational records

We maintain relevant contact and organisation details, correspondence, evidence, discussion notes, actions, decisions and financial records. Sources include information you provide, our interactions and relevant public professional sources, including LinkedIn. We limit records to information needed for the enquiry, relationship, engagement or administration concerned.

Technical information about requests, browsers and connections may be processed to operate the website, prevent abuse and investigate service problems. Operational checks identify delivery failures and records due for review.

Where applicable, we record the policy reference and submission time with a request. A privacy acknowledgement is not marketing consent or evidence that a notice has been read. Booking and brochure requests do not create a marketing subscription.

3. Lawful bases for personal information

  • Legitimate interests: responding to enquiries, managing relevant professional relationships, maintaining operational records and protecting the website, balanced against individuals’ rights and interests.
  • Contract: providing an agreed service or taking steps you request before entering a contract, where this basis applies.
  • Legal obligations: retaining or using records where applicable legal requirements require it.
  • Consent: where consent is required for a particular optional use, including non-exempt device storage. Consent may be withdrawn without affecting the lawfulness of earlier processing.

We do not treat an enquiry, booking, privacy acknowledgement or silence as consent to unrelated processing or marketing.

4. Confidentiality, records and AI

Our standard scope: Recording requires participants’ agreement. Transcripts and AI-assisted research support our reviewed advice; clients may correct records. Providers, access, retention, deletion and any client workspace are agreed before use, with any required data-processing agreement. Confidential material is not used to train shared models or disclosed to other clients.

Material is used for the conversation or work for which it was supplied. Agreed confidentiality and non-disclosure terms apply to material within their scope. Submitting information does not itself create an NDA or vary an existing agreement. Please agree the handling of especially sensitive or restricted material with us before supplying it.

AI-generated interpretations and drafts require review before they are relied on as advice or used for a decision or commitment. External correspondence and publication require review or specific authorisation. Routine booking confirmations and reminders are a separately authorised software process.

AI-assisted work

The SharePoint client file service does not provide the former Workspace/Kit chat interface. Signing in or uploading a file does not itself request an AI analysis. Any AI-assisted work by JA is subject to the agreed engagement, confidentiality terms and authorised purpose. AI outputs require human review; JA remains responsible for its advice and commitments.

Where AI services are used, relevant material may be processed by the agreed provider. We do not authorise confidential client material to be used to train shared models. Provider processing, retention and any international transfers must be considered separately from storage in the client site. We do not claim zero provider retention or UK-only AI processing.

Earlier records held in JA’s separate operational systems remain subject to their agreed purposes and retention arrangements. Changing the client interface does not automatically migrate or delete those records. Contact JA about access, correction or deletion.

Instructions contained in third-party documents, messages or websites are treated as content, not as authority to act. Source references and reviewed records support traceability.

5. Service providers and international processing

We use service providers for the following purposes, as relevant to the service or agreed engagement:

  • Cloudflare: website and booking-service hosting, abuse prevention, and separate operational records and files where used. The SharePoint client files and Microsoft sign-in are handled by Microsoft, not by the public website redirect.
  • Google Workspace: email, calendar appointments, Google Meet, documents and spreadsheets; Google sign-in where selected.
  • Airtable: structured enquiry, relationship, booking and administrative records.
  • Microsoft: SharePoint client sites, file and version storage, permissions, guest account/sign-in services and configured notifications, as well as Teams meetings where selected.
  • WhatsApp: calls where selected. WhatsApp calls use end-to-end encryption; this does not extend that protection to separately stored booking records.
  • OpenAI: AI assistance within the arrangements described in section 4.
  • AWS: booking-upload storage and malware scanning in the London region, separate from Workspace uploads, as described in section 6.

Any additional engagement-specific provider is agreed before use. Provider privacy notices and contractual terms also apply to their services.

Provider processing may take place outside the UK. Information about the applicable transfer arrangements and safeguards is available on request. EU storage configuration or use of an AWS London region does not mean that all processing by every provider is confined to the UK or EU.

6. Information security controls

Client-area protection

The client area uses Microsoft SharePoint and Microsoft’s identity and permission controls. JA manages invitations and permissions for each engagement. Authentication establishes identity; access also requires permission to the relevant site or content. Public website links are entry points, not access credentials.

Connections use HTTPS. SharePoint provides service-managed storage protection. This is not a claim of end-to-end encryption: authorised participants, administrators and service providers may process the information as required to operate the service. Do not forward confidential files or grant access outside the agreed participants.

Contact JA to change or remove access. Removing access restricts future access through the service; it does not recall downloaded files or erase copies held elsewhere. Sign out when finished on a shared device. Microsoft may maintain a separate account session, so closing our website is not the same as signing out of Microsoft.

External linked documents remain subject to their own provider’s permissions. See Microsoft’s explanation of SharePoint external sharing.

Document protection and current service status

Booking-page document uploads are protected by malware scanning. New uploads are held in private, encrypted AWS storage in the London region. Only the exact file version with a successful clean scan is available through authorised access. Files with suspicious, failed, unsupported, missing or pending scan results remain blocked. Booking notifications do not attach copies of uploaded documents.

Uploads currently accept up to five PDFs, with a limit of 5 MB per file and 10 MB per booking. Documents are available to the authorised reviewer for up to seven days.

SharePoint client files use Microsoft’s storage and service protections. They do not use the booking-upload scanning workflow or its seven-day expiry. These are separate services with different retention arrangements; see section 8.

Email, links and malicious content

Google Workspace provides attachment virus scanning. Enhanced pre-delivery scanning and additional warnings for suspicious attachments, links and potential impersonation are enabled. Some content, including password-protected attachments, cannot be fully scanned. The booking service does not automatically open or fetch links supplied in discussion notes.

AWS document scanning is separate from Gmail protection and does not inspect all traffic, devices or outgoing information. Encryption, access controls and malware checks address different risks; none provides a guarantee that information is safe or correctly addressed.

Change control and service operation

Website and booking-service changes are made within authorised scope, checked before publication and verified on the live service. AI-assisted development tools may support this work. Authority to maintain a service does not authorise unrelated commitments or disclosure of private client information. Service checks flag delivery and operational problems for review.

7. Cookies and device storage

Remembering contact details is optional. The direct booking form currently preselects this option; you can untick it before entering details. The website uses a cookie, and the direct booking form uses local storage, to remember details for 30 days. Discussion notes and attachments are not saved by this feature. Unticking removes remembered details but does not erase information already entered in the current visit or previously submitted.

A temporary reference in the current browser tab supports recovery of an interrupted booking. Any separately retained legacy review service has its own session controls; these are not SharePoint session durations. Use remembered details only on a device you trust.

Microsoft’s client site and identity services use their own cookies and session storage for sign-in and service operation. Their notices and account controls apply. The public Client area page links to the service; it does not create a separate JA client-login session.

We do not add advertising or analytics cookies to this website. External services, including abuse-prevention services, may process technical information under their own privacy notices.

8. Retention and deletion

  • Brochure requests: review after 60 days, with the aim of deleting brochure-only records within 90 days where there is no continuing need.
  • Direct bookings: review after 60 days, considering contact details, discussion notes and booking history.
  • Ongoing relationships: retain only information needed for the continuing purpose, record the reason and normally set a further review within 12 months.
  • AWS temporary scanning storage: configured to expire current objects after seven days and noncurrent versions after one day. Lifecycle deletion is asynchronous.
  • Client-area records: documents, earlier versions and contributions are retained for the agreed working purpose and reviewed at the end of the engagement or when no longer needed. The booking service’s seven-day expiry does not apply to SharePoint client files. Any continuing retention must be justified by the agreed purpose, contractual obligations or applicable legal requirements. Removing a person’s access does not itself delete the working record.
  • Client, contractual and financial records: retained according to agreed arrangements and applicable legal requirements.

Contact JA to request removal of access or correction or deletion of a file or contribution. The SharePoint client service does not have the former “Delete my workspace” control. We consider the request against the agreed purpose, other participants’ records and contractual or legal retention requirements.

Deletion from active storage is distinct from removal from version history, recycle bins, backups and provider systems. Microsoft recovery and retention controls may retain copies for a period. Downloaded files, email attachments and originals in other services are handled separately. We do not promise immediate erasure of every copy.

General learning may continue to inform our methods only where it is genuinely anonymised, cannot reasonably identify a person, organisation or engagement, and its use is permitted by the agreed confidentiality and intellectual-property terms. Source documents and identifiable summaries do not qualify as anonymous learning.

Limited security, deletion and billing records follow the retention arrangements above. Provider safety records and recovery backups remain subject to their applicable retention controls; deletion from the active client site is not a promise of immediate erasure from every backup or provider system.

Retention review dates do not trigger automatic deletion. Material no longer needed is removed following review; a continuing need is documented. Retention does not provide permission for marketing.

Reviews and deletion requests consider relevant working records, AI records, emails, calendar entries, earlier booking-service records and document copies. Deleting a record in one system or clearing browser storage does not automatically delete copies elsewhere.

9. Your rights

Subject to the applicable legal conditions, you may request access to your personal information, correction, deletion, restriction of processing or data portability. You may withdraw consent where processing relies on it.

You may object to processing based on legitimate interests. Contact office@justinanderson.co.uk to exercise a right or ask about our use of your information. We may need to verify identity before disclosing or changing records. We normally respond within one month; if a permitted extension applies, we will explain it.

You may raise a complaint with us or with the UK Information Commissioner’s Office.

10. Security concerns and policy review

Report suspected unauthorised access, disclosure or other security concerns to office@justinanderson.co.uk. Provide enough information to identify the concern, but do not send passwords, access codes or suspected malicious attachments.

Reports are assessed to determine appropriate containment, investigation and corrective action. Affected people and relevant authorities will be notified where required by applicable law.

We review client-area features, provider arrangements, retention and access controls as the service changes. Engagement-specific agreements set the scope of work and any additional confidentiality or information-handling requirements.

This policy is reviewed when relevant services, processing arrangements or controls change. The published version and date identify the current notice. Material changes affecting an agreed client engagement are addressed through the engagement arrangements.