LEGAL & TRUST
Cookie and Tracking Technologies Policy
Necessary technologies support requested functions and security. Optional technologies must be disclosed and appropriately controlled. KRAVIA does not use cross-site behavioural advertising profiles. The actual technology inventory, not a list of hypothetical vendors, identifies what a site uses.
1
Technologies covered
This Policy addresses cookies, local and session storage, similar device identifiers, pixels, SDKs and other technologies that store or access information or measure interactions. The same privacy principles apply regardless of the technology's label. Server-side collection is not exempt from data-protection duties merely because it does not use a browser cookie.
2
Categories and purposes
Strictly necessary technologies enable functions such as a requested login session, access protection, fraud prevention and saving privacy choices. Their scope and lifetime must be proportionate. A tool is not classified as necessary simply because it is useful to a marketing or analytics team.
Optional preference, analytics or personalization technologies may help remember a chosen experience or understand service performance. They are not automatically required for public browsing. KRAVIA's company baseline is to keep optional tracking off until the relevant affirmative choice; a narrower legal exemption does not silently change this selected baseline. Advertising profiles across unrelated sites are not part of KRAVIA's permitted model.
3
Choice before activation
Where an optional technology is offered, the consent interface provides clear Accept, Reject and Manage Preferences choices with reasonably balanced prominence. It must not use preselected optional consent, misleading button emphasis or repeated prompts designed to wear users down. Rejecting optional technologies must not block public legal policies or unnecessary parts of the site.
The choice takes effect before relevant scripts, requests, pixels or storage operations occur. Hiding a banner while optional tracking already runs is not consent management. Essential technical requests may continue for the function the user requests, with accurate disclosure.
4
Inventory and provider disclosure
For each actual technology the public inventory identifies its name or identifier, provider, first- or third-party status where relevant, purpose, category, duration or expiration criteria, and the applicable site or product. Technologies with multiple purposes are not concealed under a single inaccurate category.
The inventory must be generated or maintained from the actual implementation and reviewed after provider or feature changes. An unverified inventory is not evidence that there are no cookies. A new tracker must not be introduced merely because this Policy contains a general category that could describe it.
5
Changing or withdrawing choices
Use the site's privacy or cookie-preferences control to revise optional choices. We stop future consent-dependent activity and remove or expire relevant controlled identifiers where appropriate. A record of the choice may be retained to honor it. Browser controls may also block or remove storage, although removing necessary session information can sign you out or affect a requested function.
Previously disclosed information held independently by a third party follows applicable law and that party's responsibilities; consent withdrawal is not a claim that KRAVIA can erase every external record instantaneously. Privacy requests can also be submitted to privacy@kraviaprivatelimited.com.
6
Browser privacy signals
Recognized legally applicable signals, including Global Privacy Control where relevant, are honored for their supported legal effect. They do not automatically mean “delete my account” or “reject all necessary security processing.” We do not demand identity verification merely to honor an applicable opt-out signal. Older generic Do Not Track settings are not represented as having the same effect as every recognized statutory signal.
Our no-sale and no-behavioural-advertising commitments apply regardless of whether a signal is enabled. Signal support and visible explanations must match actual implementation.
7
Consent records and expiry
We keep proportionate evidence of choices, relevant notice or configuration version, timestamp and subsequent changes. We avoid recording unnecessary identifying information solely for consent evidence. Material changes or expiry may require a fresh choice, but do not justify treating silence or a previously rejected category as consent.