Source traceability
Public research identifies sources or labels original editorial frameworks. Fictional examples and historical interface previews are disclosed where they appear.
Trust / Evidence, access & privacy
Trust begins with
showing the work
Readers should be able to see where a claim comes from and where its limits lie. Here we explain our editorial standards, how this website handles information, and what we agree before private research begins.
Data minimisation
The contact form emails the details you provide to EchoFrame through its configured email service. Include only what we need to understand your request.
Reader control
Saved article identifiers stay in this browser. You can remove them using the save control or by clearing the site data on your device.
Clear service boundaries
External platforms, calendar booking, email, and font delivery involve other services. Their access and data-handling arrangements are separate.
Current public website
What happens
to your information
This website is a research publication and enquiry interface. It is not a private document room or a protected field-report intake channel.
Read the full privacy noticeEnquiry form
Your details are sent to EchoFrame when you click Send. The form reports whether the email service accepted the request.
Saved reading list
Article identifiers in local browser storage; no reading-list account.
Analytics & marketing
No advertising trackers, analytics scripts, or newsletter database in this build.
External requests
Google Fonts serves typography. The host and configured email service process the requests needed to deliver pages and messages. Calendar and platform links open separately.
Before a private engagement
Agree the handling
before sharing the material
The following are scoping requirements, not claims of deployed certifications or platform controls.
Access and permitted use
Agree who can access the output, whether redistribution is allowed, and which source licences constrain publication.
Sensitive material
Agree a suitable exchange channel and source-protection arrangements before sending confidential or identifying information.
Retention and deletion
Document the retention period, storage arrangements, responsibilities, and process for correction or deletion requests.
Platform assurance must be specific
This public site does not assert AES-256 deployment, AWS hosting, multi-factor authentication, SOC 2 certification, or end-to-end encryption for EchoFrame platforms. Any assurance statement should identify the actual service, control, evidence, and scope of review.
Editorial accountability
Show uncertainty
Make corrections possible
Keep evidence quality distinct from outcome likelihood. Record competing accounts and explain what would change the assessment.
A conversation with context
Discuss the research
Agree the boundaries
Tell us your sector, the decision you face, and what you would need to see in a first briefing.
See how we can help you