Skip to content
Company Logo Protektant
Cookies on Protektant
We use necessary cookies to make the site work and optional cookies to improve your experience. By clicking Accept all, you agree to our use of cookies as described in our Cookie Policy.

Cookie Policy

Cookie Policy

Protektant Cookie Policy

Effective date: February 15, 2026
Last updated: February 15, 2026

Provider: Traditional Knowledge Inc. (“TKI”, “we”, “us”)
Service: The Protektant platform, including the Sovereign Data Treasury, and associated web and mobile applications, dashboards, and APIs.

This Cookie Policy explains how we use cookies and similar technologies when you visit or use Protektant.

It should be read together with our Privacy Policy and Terms of Service.

1) Quick summary

1.1 We use strictly necessary cookies to operate the Service, keep you signed in, prevent fraud, and protect the platform.

1.2 Optional cookies (for example, analytics) are used only if enabled and, where required, only with your consent.

1.3 You can manage cookie preferences through our cookie banner (where available) and through your browser settings.

2) What cookies and similar technologies are

2.1 Cookies are small text files stored on your device by your browser when you visit a website.

2.2 Similar technologies include:

  • (a) local storage or session storage (browser-based storage)
  • (b) pixels, SDKs, and tags (typically used for measurement or service functionality)
  • (c) device identifiers used in mobile apps
  • (d) server-side identifiers and request tokens (used for security and session management)

In this policy, “cookies” includes these technologies unless otherwise stated.

3) Why we use cookies

We use cookies and similar technologies for the following purposes:

3.1 Strictly necessary operations

  • (a) authentication and login workflows
  • (b) session management for the web application
  • (c) security controls such as CSRF protection and abuse prevention
  • (d) load balancing and platform reliability
  • (e) remembering essential settings required to deliver the Service

3.2 Preferences and functionality (where enabled)

  • (a) remembering certain user preferences such as language and interface settings
  • (b) remembering your cookie choices
  • (c) improving usability and accessibility features

3.3 Security and fraud prevention

  • (a) detecting and preventing suspicious activity
  • (b) protecting accounts and sessions
  • (c) supporting investigations of security incidents
  • (d) maintaining audit-grade integrity for platform operations

3.4 Analytics and performance (optional)

If enabled, we may use analytics to understand how the Service is used and to improve performance, reliability, and user experience. Where required by law, we will request your consent before setting analytics cookies.

3.5 Advertising

Protektant does not need targeted advertising cookies to operate. If we introduce advertising or marketing cookies in the future, we will update this policy and, where required, request your consent before using them.

4) Cookie categories we use

4.1 Strictly necessary cookies

These cookies are required for the Service to function and cannot be switched off in our systems. You can block them in your browser, but parts of the Service will not work.

Typical examples include:

  • (a) session cookies used to keep you signed in while you navigate the Service
  • (b) security cookies used for CSRF protection and request integrity

4.2 Functional and preference cookies

These cookies allow us to remember choices you make and provide enhanced functionality. If you disable these cookies, some features may not work as intended.

Typical examples include:

  • (a) language and display preference cookies
  • (b) cookie preference storage

4.3 Security and fraud prevention cookies

These cookies support platform security, fraud prevention, and abuse detection.

Typical examples include:

  • (a) cookies used to detect automated misuse
  • (b) cookies used by payment or identity providers for fraud prevention and account safety

4.4 Analytics cookies (optional)

These cookies help us measure and improve performance and understand feature usage. Where required, they are set only after consent.

5) Cookies and identifiers you may see

Cookie names can vary by environment and configuration. The list below describes common cookie types you may encounter on Protektant.

5.1 First-party cookies set by Protektant

(a) Session cookie (example: “JSESSIONID”)

Purpose: maintain a secure session during your visit.

Typical duration: session (expires when you close your browser) or a short configured period.

(b) CSRF or request integrity cookie (name varies by framework)

Purpose: protect against cross-site request forgery and ensure request integrity.

Typical duration: session or short configured period.

(c) Cookie preference cookie (name varies)

Purpose: remember your cookie choices.

Typical duration: typically months, depending on configuration.

(d) Essential UI preference cookies (names vary)

Purpose: remember non-sensitive preferences such as language or basic UI choices.

Typical duration: varies.

5.2 Pre-login notice cookie (UX-only)

We may set a short-lived cookie to remember that you viewed a pre-login notices page before being redirected to our identity provider.

Purpose: user experience only.

Important: this cookie is not evidence of acceptance of any agreement. Binding acceptance is captured separately through the onboarding and acceptance workflow.

5.3 Cookies set by our identity provider (single sign-on)

If you sign in using our identity provider (for example, hosted under a related Protektant domain), authentication and session cookies may be set by that system to complete sign-in and maintain the login session.

Purpose: authentication, session continuity, and account security.

Typical duration: session or configured short duration.

5.4 Cookies set by third-party services we use

Some service providers may set cookies or similar identifiers to provide their services. Examples may include:

  • (a) payment processors and fraud-prevention tools used during checkout or billing management
  • (b) security services that protect against abuse
  • (c) support or communications tools (if integrated)

These third parties act under their own policies, and we require appropriate contractual protections where applicable.

6) How you can control cookies

6.1 Cookie banner and preference center (if available)

Where provided, you can:

  • (a) accept or decline optional cookie categories
  • (b) change your choices later through a “Cookie Preferences” link or in-product settings

Strictly necessary cookies are always active because they are required to operate the Service.

6.2 Browser controls

You can control cookies through your browser settings, including:

  • (a) blocking all cookies
  • (b) blocking third-party cookies
  • (c) deleting existing cookies
  • (d) setting rules per site

Browser settings vary by browser and device.

If you block strictly necessary cookies, the Service may not function correctly.

6.3 Mobile app controls

If you use the mobile application, some identifiers may be stored within the app environment. You can typically control tracking permissions through your device settings. Some functionality may require essential identifiers to operate.

7) Do Not Track and similar signals

Some browsers send “Do Not Track” signals. There is no uniform industry standard for responding to these signals. Where required by law, we will honor applicable opt-out mechanisms. You can also manage optional cookies through our preference controls where available.

8) International users

8.1 Canada

We operate from Canada and apply Canadian privacy requirements, including meaningful consent principles where applicable.

8.2 Other jurisdictions (including the EU/UK)

If you are in a jurisdiction that requires opt-in consent for non-essential cookies, we will request consent before placing those cookies. Strictly necessary cookies remain active to deliver the Service.

9) Changes to this Cookie Policy

We may update this Cookie Policy from time to time to reflect changes in technology, legal requirements, or how we operate the Service. When we make material changes, we will provide notice in-product and or by other appropriate means. The “Last updated” date at the top reflects the latest version.

10) Contact us

For questions about cookies, privacy, or this policy, contact:
privacy@protektant.com

For security issues:
security@protektant.com

For legal notices:
legal@protektant.com