Last Updated: September 2026

1. Scope

This Cookie Policy explains how CodeConda LLC (“CodeConda,” “we,” “us,” or “our”) and authorized third parties use cookies and similar technologies across our websites, applications, and digital services (the “Services”). Technologies vary by Service, feature, route, domain, and user choice. This Policy covers technologies set by CodeConda and authorized third parties through the Services.

Consent and preference records are generally stored separately for each domain or subdomain, sometimes called an origin. A choice made on one Service, browser, device, domain, or subdomain may not apply to another. You may need to set preferences separately on each origin you use.

CodeConda operates multiple websites, applications, and digital services across separate domains and subdomains. The combined cookie and similar-technology inventory maintained through our consent tools may list technologies used across those Services even when a particular Service does not set every listed technology. Consent choices are stored per origin and do not automatically carry to another domain.

2. Cookies and Similar Technologies

Cookies are small text records stored by a browser. We may also use local or session storage, pixels, tags, beacons, scripts, software development kits, server-side events, and device or browser identifiers. These technologies can remember settings, maintain sessions, protect forms, measure use, diagnose errors, attribute referrals, or support permitted marketing.

Some technologies operate only on public pages, while others may be needed on sign-in, account, checkout, or authenticated routes. Consent tools may still appear or retain choices on authenticated routes. Blocking essential storage can prevent login, security, preferences, billing, or requested features from working.

3. Preference Center Categories

Essential

Required for core operation, security, authentication, network management, fraud prevention, consent records, checkout, and requested functionality. These technologies cannot ordinarily be disabled through the preference center because the relevant Service may not function without them.

Functional

Supports enhanced features and remembered choices, such as language, display, account preferences, integrations, or media. Disabling Functional technologies may reduce available functionality.

Analytics

Helps measure traffic, interactions, performance, errors, and feature use so we can understand and improve the Services. The consent implementation may recognize “Statistics” as an alias for “Analytics.” Analytics data can include personal information or online identifiers and is not necessarily anonymous.

Marketing

Supports promotion, campaign measurement, referral or affiliate attribution, advertising, and, where used, interest-based or cross-context advertising. Affiliate attribution records a referral or commission source and does not necessarily involve behavioral advertising.

The category labels above are intended to match the GetTerms preference center and the aliases recognized by our consent integration. A provider may support more than one purpose; we classify each deployed technology by its actual configured use on the applicable Service.

4. Representative Technologies and Providers

• Consent management: GetTerms may store consent status, category choices, timestamps, or related consent records.
• Authentication, infrastructure, and security: Supabase, Cloudflare, including Turnstile, hosting providers, and payment or account systems may use essential storage or identifiers.
• Analytics and diagnostics: DataFast, Sentry, or similar configured tools may process usage, device, IP, event, performance, or error information when allowed by the relevant preference and law.
• Payments and embedded features: Stripe, PayPal, connected platforms, media, mapping, or other feature providers may set or read technologies needed to deliver an integration or transaction.
• Affiliate and marketing: configured partners, such as Rewardful, ProfitWell, or Affonso, may use identifiers for attribution, program administration, frequency, measurement, or permitted promotion.

A representative name does not mean that provider or technology is active on every Service.

5. Available Inventory

The cookie preference center and scanner available from the relevant Service provide a combined inventory of cookies and similar technologies. Where detected and applicable, the inventory identifies the provider or technology, purpose, category, duration or persistence, first-party or third-party status, and applicable domain or Service. Scanner results can lag a deployment or include conditionally loaded technologies, so the inventory should be read together with this category-based Policy.

Open the inventory and controls using the “Cookie settings” link in the footer, account area, or consent banner of the relevant Service. If the preference center is unavailable, does not retain your choice, or appears inaccurate, including because of browser settings, storage restrictions, extensions, content blockers, private browsing, network tools, or other technical conditions, contact us through our support page.

6. Consent and Withdrawing Choices

Where consent is required, nonessential categories are intended to load only after the relevant choice. You can accept, reject, or adjust available categories through the preference center and withdraw consent later using “Cookie settings.” Withdrawal does not affect processing already carried out and may not remove data already received by a provider, but it applies to future use on that origin as technically supported.

Browser controls can delete or block cookies and site storage. Private browsing, clearing storage, changing browsers or devices, or using a different origin may reset choices. Some server-side events or technologies are not controlled by browser cookie settings alone. Where consent or an opt-out is required, we apply the relevant choice to those events and technologies within the legally required scope of our configured integrations.

7. Global Privacy Control, Sale, and Sharing

Where legally required, a recognized Global Privacy Control (“GPC”) or similar opt-out preference signal is processed as a request to opt out of sale or sharing to the extent we can associate the signal with the browser, device, or account that transmitted it. If we can reasonably link the signal to a logged-in account, we apply the opt-out to that account and related sale or sharing as required. GPC does not by itself authenticate you or automatically carry across unrelated browsers, devices, domains, subdomains, or accounts. You may also use the preference center to opt out of Marketing technologies associated with sale, sharing, or targeted advertising where those technologies are used.

Legacy “Do Not Track” signals are different from GPC and lack a uniform standard, so the Services may not respond to DNT. For more information about applicable privacy rights and request methods, see our Privacy Policy.

8. Changes and Contact

We may update this Policy and the available inventory as technologies, Services, or law change. We will update the “Last Updated” date and provide additional notice where legally required. For cookie questions or choices that cannot be completed through the preference center, contact CodeConda through our support page.