Review the documents and the customer journey together
A website can have polished terms and a visible cookie banner while still leaving important questions about what happens during a visit. Yudey helps organise a review of the selected website documents and tracking arrangements. We begin with the site's purpose, audience and functions, so the work reflects an enquiry website, online shop or subscription service rather than an unrelated template.
The proposal states which pages, journeys, technologies and documents are included. A document review and a technical browser audit are different activities. We identify whether the engagement uses information supplied by your team, includes agreed inspection or needs a separate technical assessment. This distinction prevents a wording change from being presented as evidence that every script on the site behaves correctly.
Clarify what the website terms cover
The agreed review can examine permitted use, account responsibilities, customer information and the relationship between website terms and sales terms. A visitor reading information is not necessarily entering the same contract as a customer placing an order. We identify unclear distinctions and conflicts between the materials included in the scope. The governing law and relevant customer locations also need to be established.
For online sales, customer information and the order process deserve their own attention. Government guidance explains the starting requirements for distance selling. [2] We can identify where product, delivery, cancellation or subscription information needs further review, without assuming that a general website terms page supplies every required detail. More complex consumer or regulated services may need a specialist expanded scope.
Build a useful inventory of tracking activity
The review asks what technologies the site uses, why they are used and which organisations receive information. Analytics, advertising tags, embedded video, chat tools and other services can behave differently. We request the relevant inventory and configuration evidence rather than relying only on the names displayed in a banner. If the business does not know what is deployed, that is an action to address first.
Current ICO guidance covers storage and access technologies beyond traditional cookies and explains consent and applicable exceptions. [1] The assessment needs to consider purpose and the conditions of any exception, not simply whether a supplier calls a tool analytics. We do not assume that every statistical tool is exempt or that every technology can be handled with the same category label.
Review the information and choices presented
The agreed work can consider whether the descriptions explain the purposes in a way the intended audience can understand. We identify inconsistent category names, unsupported claims and missing details that need confirmation. Where consent is required, the proposed choice mechanism and handling of changes should be assessed against the actual implementation. Where an exception is considered, its conditions and any required information or objection mechanism need attention.
A privacy notice, a cookie notice and a contractual acceptance checkbox serve different purposes. We help identify where the website has combined them confusingly. The review does not treat acceptance of general terms as a universal permission for advertising tracking or all future uses of personal information. Any proposed change should be connected to the relevant activity and supported by appropriate professional analysis.
Give developers precise implementation questions
The handover can distinguish content changes from technical tasks, such as checking when a technology starts, how a preference is stored and what happens after a person changes their choice. We identify the evidence needed to confirm those behaviours. If technical testing is outside scope, that limit is recorded explicitly rather than replaced with an assumption that a banner plugin handles everything.
We can also flag the need for reassessment when new tools or journeys are added. A one-off review cannot monitor future marketing tags or configuration changes. Your team should know who owns the inventory and approval process after handover. Ongoing monitoring, developer changes and repeat testing require a separate agreement if you want those activities included in continuing support.
Agree the review before sharing access
The deliverables can include comments on the selected terms, a tracking assessment questions list and a prioritised implementation brief. We state the information supplied, limitations and unresolved issues. The work is not an ICO approval or a guarantee of full website compliance. Accessibility, cybersecurity, advertising claims and other areas are separately scoped when they are relevant to the request.
Fees depend on the site functions, document set, technology range and level of technical involvement. The GBP quote identifies applicable VAT and any additional testing. Start with the website address, audience, sales functions and main tracking tools. We will clarify the scope before requesting protected configuration information; do not send passwords or customer records through the initial enquiry form.
Official information behind this service
Sources checked on 7 September 2026. Use the linked guidance for subsequent changes.