Last updated: August 16, 2026
Effective date: August 16, 2026

This Cookie Policy explains how Apexbase LLC uses cookies, local storage, session storage, service-worker caches, pixels, and similar technologies when you visit Pikbase websites or use the browser application. It should be read with the Privacy Policy and Terms of Service.

1. What these technologies are

A cookie is a small value stored by a website in a browser. First-party cookies are set by Pikbase; third-party cookies or similar technologies are controlled by the provider that sets them. Session technologies expire when a session ends, while persistent technologies remain until their expiry or deletion.

Browser storage, IndexedDB, cache storage, and service workers are not technically cookies, but this Policy covers them when they perform a similar function. Authentication tokens and API credentials are not consent data. They must be handled according to the security architecture of the application and are never placed in the cookie-preference record.

2. Categories

Essential

Essential technologies are required for a feature you request or for the security and operation of the Services. They may support authentication state, routing, language, accessibility, consent records, load balancing, fraud prevention, rate limiting, error handling, and security. They cannot be disabled through the consent control without preventing or materially impairing core functionality.

Functional

Functional technologies remember optional preferences such as display, language, or workflow settings. They are enabled only when you select the functional category, where applicable.

Analytics

Analytics technologies help us understand aggregate traffic, feature use, errors, and performance. They are enabled only after the analytics choice is granted. We will document the relevant provider and purpose before activating a provider that requires consent.

Marketing

Marketing technologies measure campaigns or support communications and advertising. They are enabled only after the marketing choice is granted. They are not required to use the core Services.

On first visit, the consent control offers an equal choice between accepting optional categories and using essential technologies only. Customize lets you choose categories individually. Essential technologies remain enabled. Closing the prompt does not create a positive consent record; the application continues with essential technologies only until you choose.

You can reopen Cookie settings to change or withdraw optional choices. Withdrawal applies going forward and does not undo processing that was lawful before withdrawal. Where a third-party provider already placed storage, you may also need to clear it through your browser or the provider’s controls.

You can block or delete cookies through browser settings. Blocking essential technologies may prevent sign-in, security checks, language routing, consent storage, or other core features. Do Not Track and Global Privacy Control signals will be handled where required and where the relevant product and jurisdiction support them.

4. Current technologies and providers

The Pikbase consent system stores the pikbase-cookie-consent record in local storage. It contains the policy version, decision, timestamp, and category choices and is used only to remember the visitor’s preference. Theme and interface preferences and AI-feature consent may also be stored locally. Service-worker and browser caches may retain application files to improve availability and performance. These records do not contain authentication credentials.

Authentication uses secure, HttpOnly cookies that browser scripts cannot read. Their names and expiration may vary by environment and session state. Identity flows may redirect to Google or another provider selected by the user; the provider may set its own essential technologies on its domain. Paddle may set essential fraud-prevention, checkout, and payment technologies when a user opens a paid checkout. Provider retention is governed by the provider’s notice and the transaction requirements.

Pikbase does not currently activate a first-party analytics or marketing script based on optional consent. If that changes, this section will identify the provider, technology, purpose, data, and retention before activation, and the script will not run until the required choice is granted.

5. Third-party technologies

If you enable an integration, embedded service, payment flow, identity provider, analytics provider, or other third-party feature, that provider may use its own cookies or similar technologies. Read its privacy notice and terms. Apexbase LLC does not control storage set directly by a third party.

6. Contact and updates

Questions about cookies or consent can be sent to info@apexbase.net. We may update this Policy when technologies, vendors, purposes, or legal requirements change. The current version is posted with its effective date.

Apexbase LLC
1209 Mountain Road PL NE Ste N
Albuquerque, NM 87110, United States
https://pikbase.com

Pikbase Cookie Policy