01Cookies and browser storage
Cookies are small values a website asks your browser to store and send with matching requests. Local storage stays on an origin until cleared; session storage normally lasts for a browser tab. These technologies can support authentication, your requested language, a shopping cart or optional tracking. Their legal treatment depends on purpose, not their name.
02Necessary and requested functions
We retain consent decisions so we can respect your choice. Authentication and security are necessary for the application. A language choice is stored when you explicitly request it; it is not a general permission for optional preference tracking. Storefront carts, checkout and webchat use service-specific storage. A business embedding Foljent must assess its own site and disclose its own integrations.
03Optional categories and tracking
When explicitly configured, the public marketing website offers optional PostHog measurement of public page visits, signup link clicks and recognized traffic sources. It sends only public route identifiers, language, recognized referrer/source labels and allowlisted campaign labels after analytics consent. Raw URLs, referrer paths and arbitrary query values are excluded. A random identifier lives only in page memory; no marketing analytics cookie, replay, automatic capture or cross-domain identity is used. Withdrawal stops future requests. Unconfigured categories remain off. Accept All enables only disclosed, available categories; it does not authorize future purposes. The application separately offers optional PostHog product analytics when configured. Its SDK uses memory-only persistence and does not initialize before an accepted application choice. Session replay and automatic capture are disabled. Change that choice in application account settings. Server-side operational and product event processing is distinct from browser storage; see the Privacy Policy.
04Inventory and third-party services
The inventory below describes storage found in the source implementation across the website, application, storefront and webchat. Not every item is set on every page. Google sign-in, Stripe checkout and connected Meta services have their own pages, storage and notices when you choose those services. The marketing layout also requests its brand font from Google Fonts, which receives the network request; it is not an analytics SDK. Provider-side cookies and infrastructure added at deployment must be assessed separately.
05Changing or withdrawing your choice
Open Cookie Preferences in the website footer at any time to change or reject optional categories. Choices apply immediately on this origin and remain independent of display language. The record includes a schema and purpose version, policy version, timestamp and source, with no added visitor identifier. Valid website choices are remembered for 180 days; a material purpose change requires a new choice. Website choices do not synchronize to the application, API or merchant subdomains. Application analytics preferences are managed separately.
06Browser controls
You can remove cookies or storage and use browser blocking controls. Removing the consent record makes the website ask again. Blocking required authentication or cart storage can affect those requested functions. Rejecting optional categories does not block public website access. Withdrawal stops future optional use; it does not undo earlier lawful processing. Contact info@foljent.com for questions.
07Contact
Service operator: Codexalab
Prishtina, Kosovo
Contact