MERITLIVES / Legal information
An explanation of the browser storage, administrative sessions and external media supported by this website, with clear review requirements for future tracking.
Cookies are small values stored by a browser and sent with relevant requests. Browser session storage is different: it stores values for a page?s tab session without automatically attaching them to every request. Embedded media and remote assets can also disclose technical request information without relying on a first-party cookie.
This inventory reflects the inspected application source, not a completed scan of a production hosting or CDN setup. It does not claim that every visit sets cookies or that privacy-enhanced video is free of third-party processing.
The Laravel administration area uses session authentication and CSRF protection. These technologies support authenticated access and protection of administrative actions. Ordinary corporate-site browsing does not have a public reader-login workflow in the inspected frontend.
The session-cookie name and domain are runtime-configurable, so no unverified production name is listed here. The code?s session lifetime default is 120 minutes, with expiry-on-close disabled by default; both can be overridden. That default is not a verified production duration. Secure cookies default on in production; HttpOnly and SameSite=Lax are also defaults, not confirmation of deployed settings.
REVIEW REQUIRED: Inventory actual cookies, purposes, names, providers, domains and durations in staging and production, including CSRF, hosting/CDN security and any persistent authentication features. Confirm which technologies are strictly necessary under applicable rules.
Two service pages use first-party session-storage flags to remember that an enquiry prompt has been shown, reducing repeated prompts within a tab session:
ml-web-development-enquiry-shown ? Web Development enquiry prompt.ml-business-automation-enquiry-shown ? Business Automation enquiry prompt.These flags hold a simple shown/not-shown value rather than enquiry contents. Their scope is browser tab-session storage; browser restore behaviour can affect when a session ends. They are not configured as persistent advertising identifiers.
REVIEW REQUIRED: Assess whether these functional flags require consent for the intended audience. The current site has no consent preference interface controlling them; this page does not introduce one.
Watch supports YouTube?s privacy-enhanced embed domain, youtube-nocookie.com, and YouTube thumbnails. Loading or playing embedded media can connect your browser to the provider, exposing technical information such as IP address and browser details. Depending on page behaviour, media connections may occur as content loads; do not assume that every connection waits for a separate consent choice.
Other service pages support configured video and caption sources. Provider storage, cookies and durations depend on the actual media configuration and provider behaviour, which have not been exhaustively verified.
REVIEW REQUIRED: Audit external media requests and storage, confirm the provider notices and any consent requirement, and agree a suitable consent-gated media approach before production where required. No existing Watch playback behaviour has been changed by these pages.
No Google Analytics, Google Tag Manager or other visitor analytics SDK was found in the inspected application source. Server security rate limiting is not evidence of an active visitor analytics integration. Hosting and CDN analytics settings remain unverified.
REVIEW REQUIRED: If analytics is introduced, first approve the purpose, provider, data fields, retention, transfer arrangements and applicable lawful basis. Update the inventory and notice, and prevent optional scripts or network requests until the required consent is present.
No AdSense script, publisher identifier, ad unit or advertising consent platform was found in the inspected application source. These pages do not activate advertising, profiling or tracking, and no ad placements are included on legal pages.
Any future advertising proposal is limited to separately approved News and Blog routes. It is not an active service or a statement that consent has already been obtained.
REVIEW REQUIRED: Approve the advertising model and providers, assess the applicable consent and platform requirements, and validate consent enforcement before activation. Legal, contact, enquiry and other non-approved routes should remain outside advertising placement.
Browser settings let you inspect, block or clear cookies and site data, including session storage. Blocking essential session technologies can prevent administrator login or other protected actions. Clearing functional storage can allow enquiry prompts to appear again.
Third-party providers may offer their own account or privacy controls. Those controls are separate from this website. No working ?cookie settings? button or consent banner is claimed here, because no consent-management interface is currently implemented.
For questions about site technologies or a privacy request, use the contact form. Read the Privacy Policy for the current review status and contact procedure.
A proposed future consent interface would offer clear choices for optional analytics, functional technologies and advertising, with essential security functions explained separately. Accepting, rejecting and later changing optional choices should be accessible, and optional providers should stay inactive until the relevant choice permits them.
Consent preferences would need a versioned record, a clear withdrawal route and integration tests covering initial load, navigation and revocation. Any necessary preference-storage duration must be approved and disclosed before implementation. No such platform or preference record is enabled by this policy page.
REVIEW REQUIRED: Select and assess a consent-management platform, confirm regional requirements and provider compatibility, and test in staging. Provider certification alone must not be treated as proof of full legal compliance.
This draft should be revisited when media providers, hosting, browser storage, analytics or advertising change. Verified cookie inventories should reflect the deployed website rather than framework assumptions.
REVIEW REQUIRED: Complete the deployment inventory, obtain company and qualified privacy/legal approval, assign an effective date and maintain a change history before production release.