Effective date: 12 August 2026. This policy must be kept aligned with the technologies actually active on the live website. A cookie scan and consent-banner review are required before publication.
1. What Are Cookies?
Cookies are small text files that a website or connected service may place on a browser or device. They can help a website operate, remember preferences, understand usage or support communications and marketing.
Similar technologies may include local storage, pixels, tags, scripts, software development kits or other methods that store or access device information. In this policy, “cookies” includes these technologies where appropriate.
2. Who This Policy Covers
This Cookie Policy applies to www.aiaccountingindia.com. It should be read with our Privacy Policy, which explains how personal information may be handled more broadly.
Questions may be sent to admin@aiaccountingindia.com.
3. Why We May Use Cookies
Depending on the live website configuration and your choices, cookies may be used to:
- Load pages, route traffic and maintain website functionality.
- Protect forms and the website against spam, abuse or security threats.
- Remember cookie or interface preferences.
- Understand website performance and aggregated visitor behaviour.
- Enable communication tools, embedded content or enhanced features.
- Measure campaigns or support marketing where enabled and permitted.
4. Cookie Categories
| Category | Typical purpose | Consent approach |
|---|
| Strictly Necessary | Core operation, security, network management, form protection and remembering cookie choices. | May operate without optional consent where legally exempt; still disclosed. |
| Functional | Optional preferences, chat, media, language or enhanced website features. | Enabled only according to the applicable consent requirement. |
| Analytics | Measure visits, navigation, performance and aggregated website usage. | Should remain disabled until valid consent where required. |
| Marketing | Campaign measurement, advertising, retargeting or cross-site activity. | Should remain disabled until valid consent where required. |
The presence of a category in this policy does not mean that every category is currently active. The live consent panel and audited cookie inventory should identify the technologies actually used.
5. First-Party and Third-Party Cookies
First-party cookies are set through this website’s domain. Third-party cookies or similar technologies may be set by external services integrated into the website, such as analytics, embedded media, chat, spam protection or other tools.
Third parties control their own technologies and processing practices. Their retention periods and uses may change, so their notices should be reviewed alongside the live cookie inventory.
6. Your Consent Choices
Where consent is required, non-essential cookies should not be activated before you make a choice. The consent interface should offer clear options to accept, reject or manage optional categories without using pre-selected boxes or misleading design.
You can change or withdraw an optional consent choice through the website’s cookie-settings control when available. Withdrawal does not affect processing that occurred before the preference changed.
Elementor implementation:
Connect this area to the cookie plugin’s “Revisit Consent,” “Cookie Settings” or equivalent button. Do not publish a decorative button that fails to reopen the live preference panel.
7. Browser Controls
Most browsers let you view, block or delete cookies and may provide controls for cross-site tracking. Blocking all cookies can affect essential features or saved preferences. Browser instructions differ by provider and version, so consult the current help documentation for your browser.
8. Cookie Duration
Session cookies generally expire when the browser session ends. Persistent cookies remain for a defined period or until deleted. Duration should be proportionate to the stated purpose and reflected accurately in the live cookie inventory.
Consent-preference cookies may remain long enough to remember your choice. Consent should be refreshed when purposes materially change and otherwise at an interval appropriate to applicable law and guidance.
9. Current Cookie Inventory
The definitive inventory should be generated from a scan of the published website after all production plugins, scripts and integrations are configured. For each active technology, the inventory should identify:
- Cookie or technology name.
- Provider and whether it is first-party or third-party.
- Purpose and category.
- Duration or expiry.
- Whether it is activated before or after consent.
Do not invent this table. Use the consent plugin’s verified scan result and rescan after adding analytics, chat, video embeds, advertising tags, forms, security tools or other integrations.
10. Updates to This Policy
We may update this policy when technologies, providers, purposes or legal requirements change. The revised version will be posted on this page with an updated effective date.
11. Contact
For questions about cookies or website privacy, contact:
Implementation review required: Run a production-site cookie scan, classify every detected technology, block non-essential categories until the applicable choice, configure a working preference-revisit control and obtain jurisdiction-appropriate legal review.