Public site
No client evidence, no names, no personal case details, no advertising pixels, and no behavioural tracking. Public pages are search-ready so education and source links can be found.
Privacy First
Privacy-first. Not a tracking platform.
Privacy-first does not mean pretending a useful service handles no data. This page explains why data is used, how that use stays limited, and how removal routes stay clear.
No public intake
The public website is not a place to send reports, evidence, allegations, health details, family evidence, financial details, or case material.
Stripe boundary
Payment data belongs with Stripe for payment, fraud prevention, refunds, compliance, and accounting. Sensitive personal material is kept out of payment metadata.
Position
The opposite of social media is possible
Necessary data only
This service is designed to use only what is needed to provide the requested service, protect access, meet payment/legal duties, and honour retention or deletion choices. The ICO describes data minimisation as keeping personal data adequate, relevant, and limited to what is necessary for the purpose.
No attention economy
No feeds, no followers, no likes, no public profiles, no engagement scoring, no ad retargeting, no social tracking pixels, no Cloudflare visitor analytics beacon, and no resale of behavioural data. The service is designed to help, not to keep people scrolling.
Be honest about operational data
Security, access, payment, retention, and debugging may require limited operational records. Those records are not for private evidence content and are not for behavioural profiling.
Clear regulatory boundary
The public pages are static education and signposting pages. There are no comments, public profiles, feeds, public user uploads, public search, or user-to-user messaging.
Regulatory posture
Stay an information hub, not a social platform
Public side remains static
Public pages provide education, source lists, and help signposting. They do not collect client data and do not allow the public to post material.
No public accounts or posting
Visitors cannot create public profiles, post material, comment, message other visitors, or search for other people's information.
Sensitive evidence is not collected here
This public website does not ask visitors to send private evidence, health details, allegations, family documents, recordings, photos, or financial details.
Interactive features would change the service
Comments, uploads, chat, forums, public profiles, public search, feeds, recommendations, or user-to-user sharing would change the risk profile and would need a new privacy and safety explanation before use.
Rules
What public visitors can expect
No public exposure or payment mixing
Names, messages, recordings, photos, notes, and personal evidence are not published on public pages or placed in Stripe descriptions or payment metadata.
No public identity trail
Public pages do not publish private names, personal contact details, social profiles, dashboard screenshots, or personal source files.
No visitor profiling
The public website does not use advertising pixels, behavioural analytics, heatmaps, session replay, social embeds, Cloudflare Web Analytics, RUM/Browser Insights automatic injection, or Zaraz.
No public evidence route
The public website is for information and signposting only. It is not a route to send documents, media, timelines, allegations, or private records.
Public sources remain checkable
Public source links remain listed so visitors can check official guidance, research, statistics, law, and support routes.
New public features would change the boundary
Forms, uploads, accounts, chat, comments, public search, user-to-user posting, and case reporting would change what this website is. If those features ever appear, the privacy and safety boundary should be explained before use.
Security Notes
What this privacy model relies on
Stripe handles payment data for payment purposes
Stripe's data processing terms describe Stripe acting as a processor for platform services and as a controller for some payment, fraud prevention, compliance, billing, and financial-risk purposes. Card and payment processing stays inside Stripe, and sensitive personal facts are kept out of payment text.
Logs are for safety, not surveillance
Operational logs can help with safety, reliability, and debugging. They are not for behavioural profiling, advertising, or storing visitor evidence.
Cloudflare is infrastructure, not visitor analytics
Cloudflare may provide DNS, hosting, redirects, and security while optional visitor analytics stay off. Live public pages do not include Cloudflare Web Analytics, RUM beacons, Zaraz, advertising pixels, or third-party analytics tools.
Backups are not a visitor evidence route
Website backups are for public site files and operational code, not visitor evidence, allegations, or private records.
Review Links
Related pages
Evidence basics
How to preserve originals, separate interpretation, and keep records calm.
EvidenceBibliography
Every public source link remains checkable from the source register.
BibliographyTerms and data boundary
The public-facing rule that this site is not a public intake, upload, reporting, account, or tracking system.
Terms and Data Boundary