TermsOfUse.nl
Transparent product, privacy, and contact information for visitors reviewing whether the site is trustworthy.
Cookie Policy
Essential cookies, sign-in protection, and consent controls on TermsOfUse.nl.
This Cookie Policy explains the cookies and similar technologies that may be used to keep the site secure, preserve account sessions, support Google sign-in, and explain how optional technologies should be handled if they are added later.
Trust and readiness note
TermsOfUse.nl treats essential session, security, and authentication cookies differently from analytics, personalization, embedded media, or other optional technologies that may require consent.
- Essential cookies help the site work and protect requests
- Google sign-in may add authentication-related cookies during sign-in
- Optional technologies should wait for clear disclosure and consent controls
Essential cookies used by the app
The app may set a session cookie to keep an authenticated account session working and a CSRF cookie to help verify that important requests came from the visitor’s browser. CSRF means cross-site request forgery, a type of attack where another site tries to make a browser submit an unwanted request.
These cookies support login, sign-out, draft ownership, publication checks, and account security. Blocking them may stop account features or form actions from working correctly.
Google sign-in cookies
If Google sign-in is enabled, Google’s identity script may use cookies or tokens during the sign-in flow, including a CSRF token used to protect the login exchange. These technologies are connected to authentication rather than guide content.
Visitors who do not sign in can still read public pages such as the homepage, guides, FAQ, examples, disclaimer, privacy page, and cookie policy.
Analytics, embeds, and optional technologies
Optional technologies such as analytics scripts, personalization tools, retargeting pixels, or third-party embeds should not be treated as essential. If they are added later, the site should update this policy and add the required regional consent controls before serving them where consent is required.
Optional scripts should not be enabled silently. The live policy should describe the actual tools in use, and any consent banner should give visitors the choices required for their region.
Product controls should stay easy to recognize. Visitors should not have to guess whether something is a site control, generated output, account action, or optional third-party element.
Managing cookies
Visitors can usually remove or block cookies through their browser settings. Doing so may affect sign-in, saved drafts, publication controls, security checks, or any future preferences saved through a consent banner.
If a consent-management platform is added later, visitors should also be able to review or update non-essential cookie choices through that tool.