Cookie Policy

This Cookie Policy explains how Novapro Lab LLC ("Novapro Lab," "we," "us," or "our") uses cookies, local storage, session storage, and similar technologies on websites and applications for GreatSales AI™ (the "Services"). This Cookie Policy should be read with our Privacy Policy.

1. What are cookies and similar technologies?

Cookies are small text files stored on your device by your browser. Local storage and session storage are browser mechanisms that store data locally on your device. Session storage typically clears when you close the browser tab; local storage persists until cleared. Pixels, tags, and scripts may be used by us or service providers to collect usage information. We collectively refer to these as "Technologies" in this policy.

2. How we use Technologies

We use Technologies to:

• Enable authentication and security
• Remember preferences (language, currency, UI settings)
• Store draft onboarding and profile data locally during setup
• Operate and improve the Services

3. Consent and cookie management

3.1 Our consent approach

GreatSales AI™ is accessed by visitors worldwide. Novapro Lab LLC applies a privacy-protective default:

• Essential technologies may operate without optional consent where legally permitted, because they are necessary for core operation, security, authentication, language and preference storage, and remembering your consent choice.
• Analytics, marketing, advertising, remarketing, campaign measurement, profiling, and other non-essential technologies remain disabled until you provide the required consent.
• We do not load optional scripts first and attempt to disable them afterward.
• We do not rely solely on your location to apply a lower consent standard.

When implemented, a first-visit consent banner and Privacy Preferences modal will allow you to Accept all, Reject non-essential, or Manage preferences with equal ease. Closing a banner notice, if shown, does not constitute consent to optional technologies. Detailed implementation requirements are in our internal Consent Management Specification (file 18). This policy describes your choices and our practices.

3.2 Manage your preferences

You may change or withdraw optional consent at any time by selecting Manage privacy preferences on this page, on our Privacy Policy, or in the site footer. Withdrawing optional consent:

• Prevents future loading of optional technologies you previously allowed
• Removes or expires optional first-party cookies and storage where technically possible
• Does not automatically erase personal information lawfully processed before withdrawal (see Privacy Policy)
• Does not require account cancellation or block access to basic public content

3.3 Technology categories

We do not display preference categories for technologies we do not use.

3.4 Current implementation status

As of the audit date for this draft:

• No cookie consent banner or consent-management system is yet implemented in the GreatSales AI web application.
• Strictly necessary authentication Technologies (Clerk session cookies) are required for logged-in functionality.
• Preference storage in localStorage is used for language, currency, UI settings, and operational drafts.
• No analytics or marketing trackers are verified in the current codebase.

Do not implement optional technologies until owner approval, inventory update, and attorney review of this policy.

3.5 Browser settings and signals

You can also control cookies through browser settings. Blocking strictly necessary cookies may prevent login and core functionality. Clearing local storage may reset language preferences, drafts, and locally saved profile data. Do Not Track: We do not respond to legacy Do Not Track signals. Do not conflate DNT with GPC.

4. Technology inventory

The following table is based on a code audit of the repository as of August 1, 2026. Clerk cookie names and durations should be verified against Clerk's current documentation and your Clerk dashboard before publication.

4.1 Technologies not found in current code

The following were not found in the repository audit and must not be listed until implemented:

• Google Analytics / GA4 / gtag
• Google Tag Manager
• Meta Pixel
• Hotjar, Mixpanel, Segment, Amplitude, PostHog, Plausible
• Stripe.js / PayPal cookies (no live integration)
• Marketing or advertising cookies

5. Third-party Technologies

5.1 Clerk

We use Clerk for authentication. Clerk sets session Technologies necessary for login and account security. Clerk's privacy practices are described at https://clerk.com/legal/privacy.

5.2 Google Maps (conditional)

If configured, we load Google Maps JavaScript API for address autocomplete. Google's practices are governed by Google's privacy policy.

5.3 Payment processors (when enabled)

6. Consent record retention

When the consent system is implemented, we retain consent records only as long as reasonably necessary to demonstrate your choice, enforce preferences, and comply with law. We do not store raw IP addresses solely for consent evidence unless legal review establishes that doing so is necessary and proportionate. When we materially change purposes, providers, or categories, we will update this Cookie Policy and may request a new consent decision.

7. Do Not Track and Global Privacy Control

Do Not Track (DNT): Some browsers offer DNT signals. There is no uniform industry standard for responding to DNT. We do not currently respond to DNT signals. Global Privacy Control (GPC): GPC is a browser signal that may communicate an opt-out of sale/sharing or targeted advertising under certain U.S. state laws. It is not the same as EU/UK opt-in cookie consent.

8. Updates to this Cookie Policy

We may update this Cookie Policy when we add or change Technologies. We will update the "Last updated" date and provide additional notice where required.