CustodyTap

Cookie Policy

CustodyTap uses as few cookies as it can. The website uses none. The application uses two, and both are strictly necessary — there are no analytics, advertising or third-party cookies anywhere.

Last updated 14 November 2026.

The website: no cookies

custodytap.com is made of static pages with no scripts and nothing loaded from other sites. It sets no cookies and uses no local storage. You can read every page here without anything being stored on your device.

The application: two strictly necessary cookies

When your organization's people sign in to CustodyTap, the application sets two cookies. Both are needed for it to work safely, so neither can be turned off while you use the service:

  • sessionid — keeps you signed in after you authenticate. It is marked HttpOnly (not readable by scripts), Secure (sent only over HTTPS) and SameSite=Lax, and it expires after about twelve hours.
  • csrftoken — protects the forms you submit against cross-site request forgery, so that another site cannot act as you. It is marked Secure and SameSite=Lax.

These are "strictly necessary" cookies. Under ePrivacy and GDPR-style rules, cookies that are essential to deliver a service the user has asked for do not require consent, which is why CustodyTap shows no cookie banner — there is nothing optional to accept or reject.

What we do not use

  • No analytics or measurement cookies (no Google Analytics, Plausible, Umami or similar).
  • No advertising, retargeting or social-media cookies or pixels.
  • No third-party cookies of any kind.

Controlling cookies

You can delete or block cookies in your browser settings. If you block the two cookies above, you will not be able to sign in to or use the CustodyTap application, because the service cannot keep you signed in or protect your submissions without them. Blocking cookies has no effect on this website, which sets none.

Changes

If we ever introduce a new cookie we will update this page first and, if the cookie is not strictly necessary, ask for your consent before setting it.

Contact

Questions about this policy: dbrown@enthropicdata.com.