Cookie Policy

Effective date: 29 March 2026
Last updated: 29 March 2026

This Cookie Policy explains how EviWrite ("EviWrite", "we", "us", or "our") uses cookies and similar technologies in connection with the EviWrite website, public pages, restricted-access areas, verification surfaces, and related services.

The short version is simple: EviWrite does not use cookies on its public website as a general tracking or marketing mechanism. Cookie use is narrow and functional, and primarily relevant only where authorised institutions, licensees, or approved third parties access restricted service areas.

1. What cookies are

Cookies are small text files that may be stored on a device when a website is visited. Some cookies are necessary for a service to function. Others are used for preferences, analytics, advertising, or behavioural tracking.

Not every technical control is a cookie. A site may still apply security, rate limiting, logging, and abuse-prevention controls without setting browser cookies.

2. EviWrite’s general approach

EviWrite’s public site is designed to minimise unnecessary tracking surface.

As a general rule:

• public visitors do not need cookies to read public pages;
• EviWrite does not rely on marketing or advertising cookies for ordinary public access;
• EviWrite does not treat cookie deployment as a default website habit;
• any cookie use is intended to be narrow, justified, and tied to actual operational need.

3. Public website use

For ordinary access to public EviWrite content, cookies are generally not required.

That means browsing public pages, reading legal pages, viewing guidance, or accessing ordinary informational content should not depend on non-essential cookies set by EviWrite.

Where public-facing protections or infrastructure providers use technical challenge mechanisms outside EviWrite’s direct control, those may involve temporary cookies or similar identifiers imposed by that infrastructure rather than by EviWrite as a matter of site design.

4. Restricted-access and login use

Cookies may be used where authorised licensees, institutions, or approved third parties log in to restricted-access areas or operational workflows.

In those cases, cookies may be used for legitimate functional and security reasons such as:

• maintaining authenticated session state;
• protecting account security;
• preserving secure workflow continuity;
• preventing session tampering;
• enforcing access boundaries.

These cookies are not used because EviWrite wants to follow people around the web. They are used because authenticated systems require controlled session handling.

5. What EviWrite does not use cookies for

EviWrite does not use cookies on the public site for broad behavioural profiling or ad-tech style monitoring.

In particular, EviWrite does not position its public site around:

• advertising cookies;
• social-tracking cookies;
• cross-site marketing profiles;
• casual analytics bloat;
• unnecessary user profiling through cookie chains.

If that changes materially, this Policy would need to change as well.

6. Non-cookie technical controls

The absence of cookies does not mean the absence of technical controls.

EviWrite may still use non-cookie methods to protect its systems, verification surfaces, and public routes. These may include, for example:

• IP-based rate limiting;
• request fingerprinting or technical request characteristics;
• abuse-prevention and bot-detection signals;
• header, network, and connection analysis;
• service logs and security logs;
• challenge-response controls where necessary;
• anomaly detection and protective access controls.

These measures exist to protect the availability, integrity, and trustworthiness of EviWrite services. They are not the same thing as browser-cookie tracking, even if some users wrongly collapse all technical controls into the word “cookies”.

7. Verification and abuse prevention

Certain EviWrite public functions, including verification-related routes, may be more sensitive to abuse than ordinary static content.

For that reason, EviWrite may apply stronger technical controls to requests aimed at:

• verification surfaces;
• high-frequency request patterns;
• unusual access patterns;
• suspicious or automated traffic;
• repeated lookups likely to impair public service availability.

Those controls may rely on IP address and other technical characteristics rather than cookies.

8. Third-party infrastructure

Some services, network protections, or delivery layers used in connection with the public site may apply their own technical cookies, temporary challenge tokens, or equivalent mechanisms for traffic filtering, availability protection, or abuse prevention.

Where that occurs, those technologies may be controlled by the relevant infrastructure provider rather than by EviWrite as a marketing or profiling choice.

EviWrite does not treat the existence of third-party security challenge technology as a licence to expand into unnecessary tracking.

9. Cookie categories used by EviWrite

Where cookies are used by EviWrite itself, they are expected to fall into narrow categories such as:

Strictly necessary / functional

Used only where needed for restricted-access session handling, authentication continuity, or secure service operation.

Security-related

Used where needed to preserve session integrity, protect authorised access, or resist abuse in restricted environments.

EviWrite does not currently describe broad analytics, advertising, or preference-cookie categories as part of its public-site model.

10. Your choices

Because EviWrite’s public site is designed to function with minimal cookie dependence, many users will not need to take any cookie-specific action for ordinary browsing.

Where restricted-access services rely on functional or security cookies, disabling those cookies may prevent login or break session continuity.

Users can usually manage cookies through browser settings, including deleting existing cookies or blocking future cookies. Doing so may affect the operation of restricted-access features where session cookies are required.

11. No guarantee of cookie-free third-party environment

EviWrite can define its own site posture, but cannot guarantee that every network path, infrastructure layer, browser feature, or third-party protection mechanism will behave as though no cookie-like technology exists anywhere in the request chain.

What EviWrite can say is this: cookie use on its own public site is intended to be narrow, justified, and not marketing-driven.

12. Relationship to the Privacy Policy

This Policy should be read together with the EviWrite Privacy Policy. The Privacy Policy explains the broader handling of data, including operational logs, security-related processing, and limited information associated with authorised service use.

This Cookie Policy is about browser-side cookie and similar mechanisms. It is not a complete description of every technical signal EviWrite may process.

13. Changes to this Policy

EviWrite may update this Policy from time to time to reflect changes in site operation, authentication methods, security controls, infrastructure, or legal requirements.

14. Contact

For questions about this Cookie Policy, contact:

contact@eviwrite.com

Final point

EviWrite’s position is deliberately restrained: public reading should not require tracking furniture, and serious systems should not pretend that every security control is the same thing as a marketing cookie.