Effective Date: 06 August 2026
This Cookie Policy explains how Hue & Tints, operator of FSI Atlas, uses cookies and related browser technologies on its websites and platform. It forms part of the Privacy Policy and Terms and Conditions. References to cookies include HTTP cookies, local storage, session storage, pixels, tags, software development kits, browser identifiers, cached values, and comparable technologies that store information on or read information from a device.
Cookies are small records placed by a website or service provider in a browser or device. Session cookies normally expire when a browser session ends, while persistent cookies remain until their stated expiry or deletion. Local storage and session storage can retain account tokens, report state, consent status, preferences, project identifiers, temporary calculations, referral information, and other functionality without using a traditional cookie. Tags and pixels can transmit interaction and device information to analytics or service providers when a page loads or an event occurs.
The classification of a technology as necessary, functional, analytical, performance-related, promotional, or third-party describes its principal operational purpose and does not mean that the same identifier can never support an incidental security, attribution, debugging, aggregation, or compliance function. A single page request may involve several identifiers and service providers, and the technical name, host, expiry, payload, or classification may change when a provider, browser, deployment, subdomain, security architecture, or feature changes. The absence of a visible cookie does not establish that no data is processed, because equivalent state may be maintained in session storage, local storage, request headers, server logs, cache keys, pixels, or provider-side records.
First-party technologies are ordinarily set or read in the FSI Atlas domain context, whereas third-party technologies may be supplied by a separate provider or transmitted through an embedded script, frame, map, payment window, content-delivery service, or API. Browser treatment of these categories is not uniform. Blocking a third-party cookie may not block a server request, and clearing browser storage may not cancel a subscription, withdraw a report, reverse a payment, delete a server record, or erase provider-held data. Such actions must be addressed through the mechanism applicable to the relevant processing.
FSI Atlas uses necessary storage to operate authentication, account access, administrator preview, security, payment flow, load balancing, report generation, plan and feature entitlement, fraud prevention, error recovery, consent records, and user-requested functionality. This may include browser storage containing user or administrator tokens, current project identifiers, temporary report payloads, report settings, and the consent record named fsi_cookie_consent or an equivalent replacement. Blocking necessary storage may prevent sign-in, payments, reports, exports, account settings, or other core services from functioning and may require repeated authentication.
Preference storage may remember interface state, report options, selected plans, map or chart settings, dismissed notices, referral interaction, form progress, feature choices, and other convenience settings. The platform may use local storage entries such as cookieAccepted and may use a first-landing record such as fsi_landing to understand how a visit began and to retain that attribution for a limited period. Removing these records can reset preferences and affect report continuity but does not remove information already lawfully recorded on our servers.
Subject to applicable consent requirements, analytics and performance technologies help us understand page views, navigation, clicks, report sections viewed, device and browser characteristics, referral source, errors, latency, feature adoption, and aggregate usage. We use this information to diagnose failures, protect the service, evaluate offers, improve layouts and calculations, and prioritise product development. These technologies do not make platform outputs professionally reliable and do not change the report disclaimer.
Our pages may load Google Tag Manager, Microsoft Clarity, Google Analytics 4, Google Maps, Meta Pixel, payment gateways, cloud infrastructure, and other third-party scripts or embedded services where those services are configured for the relevant page or feature. Google Analytics 4, Meta Pixel, or other measurement technologies may be deployed or managed through Google Tag Manager.
Google Tag Manager can facilitate measurement, analytics, conversion, and advertising tags but does not by itself determine every purpose for which an individual tag processes information. Microsoft Clarity may record or reconstruct interaction patterns such as clicks, scrolling, navigation, device behaviour, and page-performance information for analytics and troubleshooting. Mapping, payment, AI, video, support, advertising, or other embedded providers may set or read their own cookies and identifiers.
These providers may receive information such as IP address, browser and device characteristics, page location, referral source, identifiers, interaction events, transaction or conversion status, and technical diagnostics according to the relevant configuration and provider terms. Third parties determine their own cookie names, purposes, retention periods, and independent processing practices under their respective policies. We do not control every third-party cookie or guarantee that an external provider will remain continuously available.
Some measurement, security, payment, report, and offer events may be created or correlated on our servers or transmitted directly between servers rather than originating from a browser cookie. Browser deletion therefore may prevent future association while leaving a previously generated transaction, audit, fraud, attribution, or aggregate event intact where retention remains lawful and necessary. A third-party provider may independently determine that it acts as a separate data controller or fiduciary for part of its service. Its policy, consent mechanism, opt-out process, and legal obligations apply to that independent processing, and FSI Atlas cannot alter or guarantee the provider's internal technology merely by updating this Policy.
We may use first-party or provider technologies to attribute referrals, validate promotional eligibility, prevent duplicate or self-referrals, measure campaigns, apply coupons, preserve landing information, and detect offer abuse. A cookie or referral identifier does not itself guarantee any discount, bounty, reward, milestone, credit, or plan benefit. All offers remain subject to the Terms and Conditions, account records, payment completion, technical verification, validity periods, management approval, and anti-fraud controls.
Retention varies by purpose. Some session records expire when the browser closes; authentication or preference records may remain until logout, expiry, replacement, or manual deletion; the current FSI Atlas landing and cookie-consent records may remain for approximately 180 days; and security, payment, fraud, or server-side records may be retained longer where necessary for contract, legal, audit, or dispute purposes. Third-party cookies follow provider-defined periods. We may alter retention when product design, security needs, or applicable law changes.
Where applicable law requires consent for non-essential storage, we seek it through a banner, setting, or comparable interface. Recording acceptance may itself require a necessary cookie or local-storage entry. Necessary technologies may operate because they are required to provide a service requested by the user, secure the platform, process a transaction, or meet legal obligations. Consent may be withdrawn by deleting relevant storage, changing browser controls, using any preference control we make available, or contacting us; withdrawal does not invalidate processing already lawfully completed and may not remove records that must be retained for security, contract, payment, or legal purposes.
We may record the time, version, domain, device or browser indication, consent category, and technical result associated with a preference in order to demonstrate and administer that preference. A consent record does not prove that the same individual controlled every subsequent session, and a missing record may arise from deletion, expiry, browser restrictions, private mode, domain separation, or device change. Withdrawal generally operates prospectively after it is received and technically implemented. It does not require reversal of aggregate analytics already produced, deletion of lawful security or payment logs, or cessation of a strictly necessary operation, and it may need to be repeated on another browser, device, profile, or domain that does not share the same storage.
Most browsers permit users to view, block, delete, or restrict cookies and site data, including third-party storage. Private browsing, tracking prevention, script blockers, DNS tools, or device settings may provide additional control. Instructions vary by browser and device. If cookies, JavaScript, local storage, session storage, maps, analytics scripts, or third-party resources are blocked, parts of FSI Atlas may fail, reports may not restore, preferences may be lost, payment or authentication may not complete, and beta or export features may become unavailable.
Clearing browser data does not automatically delete server-side account information, reports, projects, invoices, transaction records, security logs, audit records, or information retained for legal purposes. Requests relating to server-side personal data, account closure, report deletion, correction, or erasure are governed by the Privacy Policy and the account controls made available by FSI Atlas.
Deactivating or deleting an FSI Atlas account does not automatically remove downloaded reports, exported files, cached documents, autofill information, cookies, local-storage entries, session-storage entries, or other information already stored on the user's device or browser. When account deletion becomes final, FSI Atlas will invalidate active authentication sessions and server-controlled access tokens where technically applicable. Users should separately clear browser data and delete downloaded files from their devices where required.
An employer, client, administrator, network operator, security product, browser extension, or device-management policy may impose controls that differ from the user's stated preference or may inspect, block, rewrite, or retain traffic independently of FSI Atlas. Users of shared or managed devices should understand that account state, downloaded reports, autofill information, local storage, session storage, browser history, cached files, and saved credentials may be accessible to an authorised device administrator or a later user of the same device.
Users should avoid accessing confidential projects through shared or unsecured devices, should sign out after use, and should remove downloaded reports or browser-stored information where necessary. FSI Atlas is not responsible for controls, surveillance, retention, access, or disclosure performed independently by the owner, employer, administrator, security software, browser extension, or network operator controlling the relevant device or network.
Some browsers transmit "Do Not Track" or other preference signals, but there is not a single universally applicable technical standard for every signal and service used by the platform. We will respond to legally recognised signals where applicable and technically supported. Users should continue to use browser and platform controls appropriate to their requirements.
Cookie and browser-storage controls reduce some risks but cannot provide absolute security. A compromised device, browser extension, shared computer, stolen token, malicious script, software defect, server error, or third-party incident can expose or destroy stored information. You must protect your device and credentials, avoid shared sessions, log out when appropriate, and promptly export important reports. Browser storage and platform storage are not substitutes for independent PDF, PPT, spreadsheet, image, or document backups.
Expiration, deletion, corruption, or blocking of a token or state record may cause the service to treat a returning user as a new session, lose unsynchronised form progress, repeat a notice, fail to restore an in-browser draft, or require account verification. Recovery may not be technically possible where the relevant state existed only on the affected device. The Company may rotate, invalidate, or replace identifiers without notice when reasonably required for security, deployment, fraud prevention, consent administration, or compatibility, and no identifier creates a proprietary right, permanent access entitlement, or guarantee of report retention.
We may change this Cookie Policy, cookie names, providers, purposes, or retention periods to reflect legal, security, analytics, product, and operational requirements. The current version will be posted with its effective date. Questions or privacy requests may be sent to Hue & Tints, FSI Atlas, Pune, Maharashtra, India, at [email protected] or [email protected]. This Policy is governed by Indian law and, subject to non-waivable statutory rights and mandatory forums, courts of competent jurisdiction at Pune, Maharashtra shall have exclusive jurisdiction.