Coszu
Cookies & Browser Storage Policy
Essential browser storage, local Coszu data and optional advertising partner choices.
Effective / updated: October 13, 2026
1. Scope and the choices offered
Coszu at https://coszu.com uses cookies and browser storage for authentication, security, requested local features and preferences. Advertising technology is a separate optional purpose. TrafficStars is loaded only when a dedicated Coszu spot is configured, age acknowledgement is present and an affirmative advertising receipt is valid. Rejecting advertising does not prevent ordinary service use.
The age declaration is separate from privacy permission and is not independent age verification. Coszu currently has no active Google Analytics measurement ID and presents no optional Analytics category. This policy describes the current code; it is not an exhaustive list of cookies an independent advertiser may later set on its own website.
2. Essential authentication and CSRF
Authenticated actions use server-managed HttpOnly session cookies, together with CSRF and origin protections. These support sign-in, authorized account requests and protection against forged requests. Their server-managed lifetime depends on the authentication implementation; browser settings and sign-out can affect access. They are not optional advertising cookies.
Blocking essential storage may prevent account functions, payment checks, Feedback or Upload from working. These functions have their own authentication requirements; rejecting non-essential ads does not waive them. Never copy session credentials or CSRF values into a public report or support attachment.
3. Consent receipt and age preference
The product-namespaced localStorage key coszu_cookie_consent_v2 holds version 2, choiceId, savedAt, analytics and advertising. Coszu writes analytics=false. A missing, corrupt or wrong-version receipt does not authorize ads, and an older legacy privacy choice is not migrated into Coszu advertising permission. The same validity check is used by the choice interface and advertising runtime. A failed save also sets the current tab’s coszu_advertising_write_failed_v1 sessionStorage marker when possible; it blocks advertising through reload until a new choice saves successfully or the tab session is cleared.
The separate coszu_adult_acknowledgement_v1 key stores adult-2026-10-10 following an explicit entry action. Neither key contains verified identity or proof of actual age. There is no automatic time-based expiry in this implementation: preferences persist until changed, storage is cleared or a required version changes. Storage errors block advertising; without age storage, the entry prompt returns on reload.
4. Language, preferences and engagement
Coszu uses its own language preference, including coszu.locale and coszu_locale, and product-scoped preferences for supported interface features. Favorites, viewed items and similar local selections may persist to provide the feature you request. They are distinct from advertising permission and can be removed with local controls or site-data settings.
The support-engaged:coszu:v1 preference records interface engagement for ad scheduling. It does not authorize tracking or replace age/advertising checks. Even prior engagement cannot load the SDK before the required permission. Clearing it resets engagement scheduling independently from your privacy choice.
5. Conversation and Create data
Local conversation history, custom personas and Create reference images can be held in localStorage or browser databases. They are retained for local functionality until removed or evicted. Reference images in the current Create implementation remain on the device. AI reply requests still transmit the necessary text/context to the service; browser-local history does not mean all chat processing is offline.
Deleting local history does not by itself delete a server account or a separately transmitted support message. Export or back up local drafts only when you have rights to do so. Shared browser profiles can expose local information to other device users; use a separate profile for private activity.
6. Caches, IndexedDB and offline resources
Coszu can use IndexedDB, browser caches and PWA/service-worker storage to retain application resources and local feature data. A cached resource may persist after a tab closes and may be evicted by the browser. These facilities are not evidence of a cloud media upload or a verified consent archive.
Use browser site-data and service-worker controls to clear cached resources. Clearing all site data may sign you out, reset language and privacy preferences and remove drafts or conversation history. The age prompt and advertising choices will then be requested again as needed. Offline informational routes do not authorize advertising or exempt adult media from access controls.
7. Advertising partner technology when enabled
TrafficStars and Kadam are the advertising partners covered by the optional advertising permission. One optional advertising choice covers configured partners. The configured TrafficStars SDK can serve advertisements and involve IP addresses, cookies, device/browser identifiers and advertising interactions for delivery, personalization and measurement. Advertisers and their partners may place additional tracking on permitted ad content or external destinations. This processing is separate from Coszu’s own essential session storage.
Coszu does not embed the TrafficStars SDK or delegated Client Hints before permission, and no active Google Analytics integration is copied into this setup. A configured spot alone is insufficient: a valid advertising choice, adult acknowledgement, ordinary runtime eligibility and a visible placement are also required. Public legal/help routes block this advertising integration.
8. Accept, reject and customize
Accept advertising stores an explicit receipt permitting TrafficStars and Kadam advertising, with analytics remaining false. Reject non-essential stores an equally valid refusal and leaves the service usable. Customize choices shows essential storage as always required and an optional advertising partner checkbox initially off; Save choices records exactly the selected optional permission.
There is no permission inferred from scrolling, dismissing, continuing to browse, entering your age or accepting Terms. Consent is requested after age entry when no valid prior choice exists. The privacy interface remains directly accessible from this page and the permanent Privacy choices control even when a prior refusal or acceptance has been saved.
9. Changing or withdrawing permission
Use Manage privacy choices below or Privacy choices on the site to accept, reject or customize again. A same-tab choice is dispatched to the runtime and saved choices synchronize through browser storage events in other tabs. Removing or corrupting the receipt blocks new loads. Existing provider execution is terminated with a page reload when an SDK was already initialized, so withdrawal cannot leave registered SDK callbacks running in that document.
Reloading then starts from the saved choice and blocks the SDK when advertising is refused. If saving fails, the runtime re-reads persistent state and fails closed rather than assuming permission. The interface does not promise deletion of previously set third-party cookies, advertiser records or independent copies. Remove those with browser controls or appropriate requests to the provider.
10. Third-party policies and limits
Review TrafficStars’ and Kadam’s privacy information for their own disclosures and the policies of any advertiser you choose to visit. Provider cookie names, partners and retention can depend on the live spot, region and creative and are not fixed by Coszu’s local receipt. The operator must review the actual production deployment and provide any additional required vendor information before launch.
External links are voluntary navigation, not pre-consent network requests to the provider. Coszu cannot control storage on another origin or guarantee that a browser clears it when you withdraw here. Privacy requests concerning Coszu’s own processing should use Feedback; the public notice form and its operational limitations are explained in Privacy and DMCA.
11. Applicable consent standards and contact
Where GDPR/ePrivacy consent requirements apply, non-essential advertising tracking needs an informed, specific, freely given affirmative choice that can be withdrawn. The EDPB guidance linked below provides the underlying consent principles; the interface does not certify that all jurisdiction-specific obligations are satisfied. Self-declared adult status is a different issue from advertising consent.
For errors, include the browser, page and whether the issue arose before choice, after acceptance or after withdrawal. Do not include session tokens or private chat content in diagnostic reports. The Privacy Policy explains access, correction, erasure and complaint rights and the difference between local clearing and server-side deletion.
Kadam privacy policy · TrafficStars privacy information · TrafficStars terms, section 38 · EDPB consent guidance