Cookies Policy

This Cookie Policy explains how AhuraSense AI Pvt Ltd ("AhuraSense", "Company", "we", "us", or "our") uses cookies, pixels, local storage, software development kits, tags, device identifiers, session identifiers, and similar technologies on our websites, portals, dashboards, APIs, documentation, billing interfaces, support systems, and related online services.

This policy applies when you visit or use our public website, customer dashboard, developer portal, API documentation, billing pages, authentication pages, support pages, product pages, and related online interfaces.

This Cookie Policy should be read together with our Privacy Policy, Terms of Service, and, where applicable, our Data Processing Agreement.

Cookies are small text files placed on your browser or device when you visit a website. They help websites remember information about your visit, such as login status, language preferences, device details, security settings, and user preferences.

Similar technologies may include:

• Local storage: browser-based storage used to remember settings or session data.
• Session storage: temporary storage that may expire when you close your browser.
• Pixels and tags: small code snippets used to understand page usage, conversion events, and marketing performance.
• Device identifiers: technical identifiers used for fraud prevention, authentication, analytics, and security.
• SDKs and scripts: code provided by AhuraSense or third parties to support analytics, support chat, payments, authentication, monitoring, and product functionality.

In this Cookie Policy, we refer to all of these technologies collectively as "cookies."

We use cookies to operate, secure, improve, personalize, and measure our services. Because AhuraSense provides cloud infrastructure and AI compute services, some cookies and similar technologies are important for account security, billing accuracy, abuse prevention, dashboard functionality, API access management, and operational monitoring.

3.1 Strictly Necessary Cookies

These cookies are required for our website, dashboard, and platform to function. Without them, core features may not work. Examples include cookies used for:

• Account login and session management.
• Authentication and multi-factor authentication.
• API dashboard access.
• Load balancing.
• Security controls and CSRF protection.
• Fraud prevention.
• Billing session continuity.
• Remembering cookie consent choices.
• Maintaining dashboard state during resource provisioning.

These cookies cannot usually be disabled through our cookie preference tool because they are necessary to provide the service.

3.2 Security and Abuse Prevention Cookies

We may use cookies and similar technologies to detect, prevent, and investigate:

• Unauthorized login attempts and credential stuffing.
• Suspicious API activity and bot activity.
• Payment fraud and denial-of-service patterns.
• Abuse of compute, GPU, domain, or deployment services.
• Attempts to bypass rate limits or account restrictions.

These technologies help protect AhuraSense, our customers, infrastructure suppliers, network partners, and other users.

3.3 Functional Cookies

Functional cookies allow us to remember your choices and improve your user experience, including language preferences, dashboard layout, region or product preference, recently viewed resources, theme preferences, form progress, support widget preferences, and documentation display settings.

Disabling functional cookies may make the platform less convenient, but core services may still remain available.

3.4 Analytics and Performance Cookies

Analytics cookies help us understand how visitors and customers use our websites and platform interfaces — including page visits, feature usage, documentation usage, dashboard performance, error rates, conversion funnels, referral sources, latency, and product adoption patterns.

3.5 Product Usage and Operational Telemetry

Because AhuraSense provides infrastructure services, we may collect platform usage and operational telemetry that may be linked to accounts, projects, resources, API keys, workloads, or billing profiles. This may include API request metadata, dashboard actions, resource creation and deletion events, billing events, authentication events, error logs, service health signals, security alerts, and quota and rate-limit events.

3.6 Marketing and Advertising Cookies

Where permitted by law and your consent choices, we may use marketing cookies to understand interest in our services and measure advertising effectiveness — including campaign performance, referral sources, and aggregated audience insights.

We do not use marketing cookies to access your Customer Data, workloads, model weights, datasets, prompts, outputs, containers, databases, or object storage contents.

The exact cookies may change over time depending on product updates, security requirements, analytics tools, payment providers, support systems, and marketing systems. Typical cookie categories include:

Some cookies may be placed by third-party service providers that help us operate our business. These may include providers for hosting and content delivery, analytics, payment processing, customer support, email delivery, security and bot detection, authentication, error monitoring, product analytics, advertising and marketing measurement, and domain and DNS services.

Third-party providers may process information according to their own privacy policies and contractual obligations with us. We do not permit third parties to use cookies to access Customer Data stored in your cloud resources unless expressly required to provide a service requested by you and covered by applicable agreements.

Cookies used on our website and dashboard are separate from the infrastructure content you upload, host, process, train, infer, or store using AhuraSense services.

For clarity, cookies do not give marketing or analytics providers access to:

• Your private datasets or model weights.
• Training data, prompts, and responses.
• Object storage contents and database records.
• Kubernetes secrets and source code.
• Containers, VM file systems, and customer workloads.

Operational telemetry may record technical events related to resource usage, access, billing, security, and performance, as described in our Privacy Policy and Terms of Service.

Where required by applicable law, we will ask for your consent before placing non-essential cookies, such as analytics or marketing cookies.

You may be able to manage cookie choices through:

• Our cookie banner and cookie preference center.
• Browser settings and device settings.
• Privacy controls provided by third-party platforms.

Strictly necessary cookies may remain active because they are required to operate and secure the services.

Most browsers allow you to block, delete, or manage cookies. Browser controls may allow you to delete existing cookies, block all or third-party cookies, allow cookies for selected websites, clear cookies after each session, or disable tracking technologies.

If you disable cookies, certain features may not work correctly. For example, you may not be able to stay logged in, complete billing flows, manage cloud resources, use dashboards, or access support tools properly.

Some browsers may send "Do Not Track" or similar signals. Because there is no single industry standard for responding to these signals in all jurisdictions, our response may vary depending on the specific signal, region, legal requirement, and technical feasibility.

Where legally required and technically supported, we will honor applicable consent or opt-out preference signals.

Cookie retention depends on the cookie type:

• Session cookies may expire when you close your browser.
• Persistent cookies may remain for a defined period unless deleted.
• Security cookies may be retained as needed for fraud prevention and abuse investigation.
• Analytics cookies may be retained for measurement and product improvement.
• Consent cookies may be retained to remember your choices.

We retain cookie-derived information only for as long as reasonably necessary for the purposes described in this policy, unless a longer period is required for legal, security, fraud prevention, billing, dispute resolution, or compliance purposes.

We may update this Cookie Policy from time to time to reflect changes in technology, law, product features, analytics tools, security practices, or business operations.

The updated version will be posted on our website or otherwise made available. The "Effective Date" above will indicate when the policy was last updated.

For questions about this Cookie Policy, contact: