This policy covers the Ice website and the early access list, operated by Nara Virtual Private Limited. It is written to meet the Digital Personal Data Protection Act, 2023 and the Information Technology Act, 2000. The desktop app keeps its own data on your computer and has its own in-app disclosures.
What we collect
- What you type into the reservation form: name, email, mobile number, and which computer you use.
- Your answers to our welcome questions, after you join: things like which AI tools you already use. Every question can be skipped unless it says otherwise.
- Payment records from Razorpay: order and payment reference, amount, status and time. Not your card, UPI or bank details.
- How you found us: the referring page, the page you landed on, and campaign tags in the link (utm parameters), if any.
- Technical details: IP address and browser user agent at the time you submit the form, used to stop abuse and fraud.
We do not use advertising trackers or sell data. Internal traffic monitoring and optional masked recordings are described below. Microsoft Clarity is no longer loaded by this website.
Internal traffic and security monitoring
Our servers send sanitized page views and campaign tags to Nara’s self-hosted PostHog for internal reporting. They use a daily pseudonymous visitor identifier, omit raw IP addresses, names, email addresses, chat content and general query strings, and honor Do Not Track and Global Privacy Control for analytics. First-campaign tags can be retained in a session cookie. Signed-in activity uses a stable product-scoped pseudonymous account ID for usage profiles without your email or name. Anonymous and security events do not create profiles. This does not send conversions back to advertising networks.
Separately, request metadata supports abuse investigation: method, route template (unknown routes are grouped), response status and timing, country when available, and a daily keyed network identifier. Sanitized security summaries are also sent to our internal PostHog project. These security logs include bot and API requests regardless of analytics preferences. They exclude request bodies, cookies, authorization headers and query strings. Requests blocked at the network edge are recorded separately by our network provider. Logging alone does not block attacks.
Optional browser analytics
Optional browser analytics measures public-page visits, exits, scroll depth and loading/responsiveness metrics (Web Vitals). It uses a random browser/session identifier in first-party browser storage, sends only to Nara’s self-hosted PostHog through this site’s /relay path, and honors Do Not Track and Global Privacy Control. It excludes account/admin, authentication, billing, chat, widget and meeting pages, general URL queries, form contents and raw IP addresses. Server request counts and browser sessions are separate reports. Masked recording remains a separate choice.
Browser analytics: Off
Optional session recordings
Masked recordings of public-page navigation help us diagnose usability problems. They are sent only to Nara’s own PostHog server. All text and inputs are masked; forms, embedded widgets, media, account/admin, authentication, billing and meeting screens are excluded. We do not capture network bodies, headers or console messages. Recording is off until you enable it here, and Do Not Track and Global Privacy Control take priority.
Recording preference: Off
Crash reports from the app
When something breaks, the Ice app sends us a crash or error report: the error message, the stack trace, the app version, your operating system and processor type, which Ice window it happened in, and a random id made once per install so we can tell one computer’s crash loop from many people hitting the same bug. It never includes your messages, what is on your screen, your files or your keys, and the id is not linked to your account (the same id is used for the speed and usage numbers below). Reports are on by default; turn them off any time in Ice’s Settings. We don’t store the IP address a report comes from, and reports are deleted after 90 days.
Speed and usage numbers from the app
Separately from crash reports, the Ice app sends one small batch of numbers per day. Speed and errors (how long Ice takes to open, how smooth screens are, which models, agents and tools failed and how often, update results, error codes shown, and whether Ice’s own code signature is intact) is on by default. How you use Ice (which screens and controls you use, which settings you change, which features are on, and how far you get in setup) is sent only if you say yes. Both have a switch in Ice’s Settings.
It never includes your messages, prompts or answers, what tools were given or returned, file names or paths, web addresses or page titles, what is on your screen, what you type, your contacts, or your keys. Settings are reported by name, never by value. Each batch carries the same random id as crash reports, made on your computer. It is not linked to your account, and it lets us follow one computer’s problems across crash reports and these numbers. “New anonymous ID” in Settings replaces it, for both, any time. We don’t store your IP address (it is used for a rate limit and then dropped); we keep your country, taken from the connection, and only the language code of your system (like “en”), not the region. In our reports any group seen on fewer than five installs is hidden. Batches are deleted after 90 days. “See what Ice sends” in Settings shows today’s batch and what was sent.
Ice Cloud requests
When you use Ice Cloud, your messages pass through our server to the model and back. We never store or log what you or Ice said. For each request we keep metadata only: timings, sizes, token counts, the model and the provider that ran it, why the answer ended, the app version, your country, and a hash of your IP address made with a key that changes every day, so the address itself is never kept. We use it to run and bill the service, fix problems and stop abuse. Refused requests are deleted after 90 days.
Connecting Google, Slack, Notion and other services
When you connect a service to Ice with Ice’s own sign-in (not your own app keys), the sign-in passes through our server because that is where Ice’s app secret lives. The service sends a one-time code back through us to Ice on your computer, and Ice trades it, through us, for the access that lets it act for you. That access goes straight to your device and is kept there. We never store or log the code or the access: we keep only a short note of where to send you back, for ten minutes, and counters that stop abuse. We don’t need an Ice account for this. Refreshing that access later passes through us the same way, and is not kept either.
Why we use it
- To take and confirm your reservation, and to refund it (performance of our agreement with you).
- To email you about your reservation and your early access build (your consent, given on the form).
- To understand which channels bring people who reserve, in aggregate.
- To prevent fraud and meet tax and accounting obligations (legal obligation).
Who we share it with
- Razorpay, to process payments and refunds.
- Our hosting provider, which stores the database the site runs on.
- Authorities, where the law requires it.
How long we keep it
Reservation details are kept until one year after public launch or until you ask us to delete them, whichever is first. Payment records are kept for eight years because Indian tax law requires it.
Your rights
You can ask to see, correct or delete your data, withdraw consent to emails, or nominate someone to exercise these rights for you. Write to [email protected] from the email you reserved with. We respond within 30 days. If you are not satisfied, you may complain to the Data Protection Board of India.
Security
The site is served over HTTPS, the admin area is password-protected, and payment signatures are verified server-side before a reservation is confirmed.
Grievance officer
Subhash Kumar, Nara Virtual Private Limited, House No. 40, Atal Awas Colony, Belbhata, Abhanpur, Raipur, Chhattisgarh 493661, India. Email [email protected].