This policy explains how KabData (“KabData”, “we”, “us”), the intended name of a company being incorporated in the Republic of Cyprus, uses cookies and similar storage technologies on the KabData website and platform.
Read this policy together with our Privacy Policy.
1. What these technologies are
A cookie is a small text file stored by a website in your browser. Cookies can support authentication, security and preferences. Similar technologies include local storage and session storage, which allow a browser to save information on a device.
“Session” storage is normally removed when the relevant browser session or tab ends. “Persistent” storage remains until its expiry or until you clear it. Actual duration can be affected by browser settings, device policies and account sign-out.
2. Our current approach
The reviewed KabData application does not load third-party advertising, behavioural analytics or social-media tracking scripts. It currently uses:
- strictly necessary authentication and security cookies; and
- first-party interface-preference cookies/local storage set to remember choices you request.
We provide information about these technologies even where consent is not required. We do not set a non-essential analytics or advertising technology before obtaining consent where applicable law requires it.
3. Cookie inventory
| Cookie | Provider | Purpose | Type | Default duration |
| -------------------------------------------- | -------- | ----------------------------------------------------------------------------------------------------- | ---------------------------------------------- | ------------------------------------------------------------------------ |
| kabdata-session or configured session name | KabData | Maintains your authenticated session, organisation context, security state and temporary requests | Strictly necessary, first party | Default idle lifetime 120 minutes; production configuration may differ |
| XSRF-TOKEN | KabData | Helps protect forms and authenticated requests against cross-site request forgery | Strictly necessary, first party | Normally aligned with the session |
| remember_web_* | KabData | Keeps you signed in after selecting “Remember me” | Requested authentication function, first party | Until the persistent login expires or is revoked |
| kd_auth (if present) | KabData | Tells the public website whether to display “Dashboard” instead of “Login”; it is not an access token | Requested navigation function, first party | Set by the platform and removed or replaced with the related login state |
| appearance | KabData | Remembers your selected light, dark or system theme for server rendering | User-requested preference, first party | 365 days |
| sidebar_state | KabData | Remembers whether you chose to expand or collapse the navigation sidebar | User-requested preference, first party | 7 days |
The authenticated session cookie is configured to be HTTP-only by default so page scripts cannot read it. Production must use HTTPS/Secure cookies and an appropriate SameSite setting. The appearance and sidebar_state values are not encrypted because they contain only the selected interface state.
4. Local and session storage inventory
| Storage key/category | Technology | Purpose | Typical duration |
| --------------------------------------------------------- | ------------- | --------------------------------------------------------------------------- | -------------------------------------------- |
| theme / appearance | Local storage | Applies your selected light, dark or system theme on later visits | Until changed or browser storage is cleared |
| Dashboard filter snapshots (key varies by dashboard/view) | Local storage | Restores selected app, date, campaign, publisher or other dashboard filters | Until replaced or browser storage is cleared |
| af-fraud-table-mode | Local storage | Remembers the selected fraud table view | Until changed or browser storage is cleared |
Local filter state may reveal business choices to another person who can access the same browser profile. Sign out and clear browser storage on shared devices.
5. Legal basis and consent
Authentication, session security, CSRF protection and a user-requested “Remember me” function are necessary to provide and secure the online service you request.
Theme, sidebar and dashboard-view storage is set when you select or use the relevant interface function and is used only to remember that choice. Depending on the jurisdiction, a user-interface customisation requested by the user may be exempt from cookie consent. We also rely, where applicable, on our legitimate interests in providing a usable business application, balanced against the minimal privacy impact of these preference values.
If we introduce a technology that is not strictly necessary or exempt—such as product analytics, advertising pixels, cross-site tracking or non-essential third-party embeds—we will:
- update this inventory;
- explain the provider, purpose, data and duration;
- prevent it from running before consent where required;
- provide equally prominent accept and reject choices; and
- make withdrawal as easy as consent.
6. Your controls
You can:
- use KabData settings to change the theme and relevant preferences;
- clear cookies, local storage and session storage through your browser;
- block cookies through browser or device settings; or
- use a private-browsing mode.
Blocking strictly necessary cookies will prevent login, security checks or other core functions. Clearing preference storage resets the interface to its default.
Because browsers differ and change frequently, consult your browser's help documentation for current instructions.
7. Third-Party Services
KabData can connect to AppsFlyer, Microsoft Teams, Slack, Telegram and public app-store services. Following a link to or signing in directly with one of those services may cause that service to use its own cookies on its own domain. Those cookies are controlled by that provider and governed by its policy, not this inventory.
KabData's optional AppsFlyer crawler stores a filtered, encrypted AppsFlyer browser session on the server for the customer's authorised account. That server-side integration credential is not a cookie placed in the KabData visitor's browser, but it is covered by the Privacy Policy, DPA and security controls.
8. Changes to this policy
We may update this policy when storage technologies, vendors or law change. We will update the date above and, where required, ask for consent before a new non-essential use.
9. Contact
Questions or requests may be sent to:
- Entity: KabData — Cyprus company under formation
- Current correspondence address: Cyprus, Cyprus
- Email: [email protected]