Legal 03
Cookie and Tracking Technologies Policy
Contents (15 sections)
- 3.1 About browser technologies
- 3.2 Essential storage
- 3.3 Preferences and functionality
- 3.4 Analytics
- 3.5 Advertising and marketing
- 3.6 Your controls
- 3.7 Third-party embedded content
- 3.8 Publication inventory
- 3.9 Contact
- 3.10 Cookie classification and live inventory
- 3.11 Banner and preference centre
- 3.12 Blocking before selection
- 3.13 Consent history and withdrawal
- 3.14 Embedded providers and device technologies
- 3.15 Auditing changes
3.1 About browser technologies
Dear visitor, INRGIFT uses or may use cookies, local storage, session storage and related browser technologies to make the site function and remember selected settings. A cookie may be essential to retain an authenticated session, enforce security, remember a language or save your cookie choice. Other technologies may be optional and should never be described as deployed until their actual identifiers and recipients have been confirmed.
3.2 Essential storage
Strictly necessary mechanisms support authentication, fraud prevention, session continuity, request security, load management and consent-preference records. Turning these off in your browser may prevent sign-in or other necessary functionality. We should minimise duration and avoid keeping sensitive market research or credentials in unprotected browser storage.
3.3 Preferences and functionality
Where offered, optional functional storage may remember user-selected display density, preferred language, chart settings or saved interface preferences. Such settings should be controlled through an understandable user interface, with clear distinction between preferences needed for a requested feature and nonessential cross-site tracking.
3.4 Analytics
If analytics are activated, their purpose should be stated accurately: for example, understanding aggregate page performance or debugging navigation failures. Where applicable law requires consent, analytics scripts, pixels or identifiers must remain inactive until the user opts in. The consent banner should not preselect optional categories or treat silence as an affirmative choice.
3.5 Advertising and marketing
Advertising measurement, retargeting and similar promotional tracking, if ever deployed, require a separate assessment and any required consent. The mere existence of promotional email features does not mean advertising cookies are active. No category should be listed as operational without a verified vendor, lawful purpose and storage inventory.
3.6 Your controls
A Cookie Preferences link should be available from public pages so you may review and withdraw optional choices. Withdrawing consent should prevent future optional tracking where required; some already-collected data may remain where lawful. Browser settings can remove local records, though doing so may sign you out or reset preferences.
3.7 Third-party embedded content
Embedded charts, login providers, external links or support tools may set their own storage where enabled. Each integration must be reviewed for technical behavior, disclosure, consent needs and the limits of our control. A destination you visit through an external link applies its own policies once you leave INRGIFT.
3.8 Publication inventory
Before publishing this Policy as a claim about the deployed website, maintain a register of actual cookie or storage names, purpose, provider, classification, expiration, domain, security attributes, consent dependency and third-country disclosures. Do not invent names or retention periods. Significant changes should trigger review of the banner and relevant notices.
3.9 Contact
Questions about privacy or cookie controls can be sent to support@inrgift.com with the subject Cookie Preferences. This Policy is read together with the Privacy Policy.
3.10 Cookie classification and live inventory
Classify each technology based on what it actually does, not the name a vendor uses. Essential session or anti-abuse storage may be needed to provide a requested service; functional preferences can be essential or optional depending on context; analytics and advertising require separate assessment. Maintain a live register of cookie name, domain, vendor, first/third party status, expiry, purpose, region, basis and whether consent is needed. Do not publish fictional cookie names or cookie lifetimes.
3.11 Banner and preference centre
On first eligible visit display a concise notice offering a genuine choice. Acceptance of optional categories must not be pre-ticked, inferred from scrolling or hidden behind confusing navigation. Offer a practically comparable way to reject nonessential tracking, and provide a persistent link to reopen preferences. The design should work with screen readers, mobile keyboards, and languages actually offered by the service.
3.12 Blocking before selection
Optional pixels, analytics SDKs, advertising tags, fingerprinting scripts and third-party storage access must not run before the applicable consent or other lawful permission is satisfied. Blocking only the visible banner while scripts execute in the background is insufficient. Validate both network requests and client storage before and after each preference state.
3.13 Consent history and withdrawal
Record a minimal technical consent receipt that identifies the notice version, purpose choices and time without retaining excess browser-identifying data. Withdrawal must affect future nonessential processing and third-party integrations as technically required. Previous lawfully collected records may be retained only where an applicable basis permits; changing settings does not automatically erase unrelated purchase or security records.
3.14 Embedded providers and device technologies
Charts, video, single sign-on and support widgets may load their own resources. Assess whether they set storage or track across sites; apply consent gating or a lawful exception as relevant. External destinations publish their own notices and are not automatically governed by INRGIFT preferences after a user leaves the site.
3.15 Auditing changes
A tag-management update, new campaign tool, analytics migration or new social widget can change privacy behavior without changing visible design. Re-run a cookie scan after every relevant release and update both the legal inventory and consent interface. Where consent is not required for a strictly necessary technology, explain the necessity plainly instead of pretending that all cookies are optional.