idliduPrivacy Policy
1. Who we are
The data controller for personal data processed in connection with idlidu.dev is Saptarang Ventures (OPC) Pvt. Ltd. (“we,” “us”). This Privacy Policy explains how we collect, use, store, share, and delete information when you use our websites, APIs, payment flows, dashboard, and the Id coding agent.
2. Scope
This Policy applies to:
www.idlidu.dev(marketing and documentation);app.idlidu.devandapi.idlidu.dev(accounts, keys, usage, settings);gateway.idlidu.dev(inference and related agent HTTP surfaces);pay.idlidu.dev(prepaid checkout);-
the Id CLI and embeds, and the
idd·ego·segoagents as and when each is distributed, in each case when they communicate with our Services or flush telemetry to us.
It does not control third-party model providers’ own processing after we send them prompts, nor other Saptarang properties that publish separate policies (for example idlidu.com).
3. Categories of information we collect
3.1 Account and identity
- Email address and authentication credentials (or OAuth identifiers if/when enabled);
- account identifiers, profile fields you choose to provide;
- session metadata needed to keep you signed in.
3.2 Billing and payments
- prepaid pack selections, currency, face amounts, platform fees, credit ledger entries;
- payment references and status from our payment partner (PayU for INR primary);
- we do not store full card numbers on our systems — the payment partner handles card data.
3.3 API and usage metadata
- API key identifiers (not the secret after mint display), creation/revocation events;
- request timestamps, model / tier selected, token or cost estimates, latency, error codes;
- key turn budgets, hard limits, spent counters, balance and low-balance alerts;
- IP addresses and security logs reasonably needed for abuse prevention.
3.4 Content you submit for inference
Prompts, messages, tool arguments, and similar Content are transmitted to third-party model providers to generate completions. We may also store limited request/response metadata and, where product features require it, traces as described below. Do not send illegal content or data you are not permitted to process.
3.5 Device and diagnostic data
- browser type, basic device/OS signals for web sessions;
- CLI version, health-check results, crash or error reports you send or that the client emits with consent/settings.
4. Agent telemetry
Telemetry exists to operate, meter, secure, and improve the Services. Where consented traces are retained and studied, that is a result of running the Services well rather than the reason the product exists.
An earlier version of this Policy titled this section “primary product purpose” and described learning from usage as a core purpose of the product. That ordering has been corrected and this section restates it: the Services are not operated in order to collect these patterns.
Controls differ by product and are subject to this Policy and applicable law. The Id CLI
(superseded) sends telemetry unless you pass --no-telemetry. Agents in the
idd · ego · sego line are covered by this Policy as and
when each is distributed, and the controls for each will be described before it is made
available.
Where telemetry is sent, it may include:
| Class | Examples |
|---|---|
| Usage | Sessions, steps, models/tiers, latency, tool calls, budgets, parallel trees, spend |
| Behaviour | Mode switches (Ask / Plan / Agent / Debug), approvals, steers, cancels, multitask patterns |
| Thinking patterns | Plans, plan revisions, escalation reasons, subagent structure |
| Writing patterns | Prompts and follow-ups; accepted vs rejected edits; optional commit messages from agent git features |
Telemetry may be stored as structured events plus payloads (for example object storage) accessible in the dashboard (usage / traces / metrics) for your account. We take steps to redact obvious secrets in client pipelines where implemented; you remain responsible for not placing credentials in prompts when avoidable.
We do not sell prompt content as a standalone product. Aggregated or research use will be described more specifically before general availability if expanded beyond operating and improving the Services.
5. How we use information
- to provide, operate, meter, and secure the Services;
- to process prepaid purchases and maintain the credit ledger;
- to route requests (including Bottom fishing) and display balances, budgets, and alerts;
- to prevent fraud, abuse, and AUP violations;
- to analyse product performance and improve Bottom routing, agent UX, and documentation;
- to communicate transactional messages (security, billing, material Terms changes);
- to comply with law and enforce the Agreement.
We do not silently inflate reported usage for billing.
6. Legal bases (where applicable)
Depending on your location, we rely on one or more of: performance of a contract (providing the Services you request); consent (where we ask for it, including certain telemetry or cookies); legitimate interests (security, product improvement, aggregated analytics) balanced against your rights; and legal obligation. Under Indian law we will process personal data in accordance with applicable requirements of the Digital Personal Data Protection Act, 2023 and rules as they apply.
7. Sharing and processors
We share data with:
- Model providers — to generate completions for your requests;
- Infrastructure providers — e.g. Cloudflare Workers / Pages, D1, object storage;
- Payment processors — e.g. PayU for checkout and webhooks;
- Professional advisers and authorities when required by law or to protect rights;
- Successors in a merger, acquisition, or asset sale (with notice where required).
We do not sell personal data for third-party advertising. We do not permit processors to use your Content to train their public models under our instruction set except as their own terms may independently require you to accept when using certain providers — review provider policies for your use-case.
8. International transfers
We and our processors may process data in India and other countries (including where Cloudflare or model providers operate). Where required, we will use appropriate safeguards. By using the Services you understand that processing may occur outside your home country.
9. Retention
- Account data — for the life of the account and a reasonable period thereafter;
- Billing / ledger — retained as needed for accounting, tax, dispute, and fraud purposes (may outlive chat payloads);
- Security logs — typically shorter rolling windows unless needed for an investigation;
- Telemetry / traces — retention period to be disclosed and finalised before general availability; you may request deletion subject to legal and ledger constraints.
10. Security
We use administrative and technical measures appropriate to our stage and risk profile (HTTPS, hashed secrets where applicable, HttpOnly session cookies, key hashing, access controls). No method of transmission or storage is perfectly secure. Protect your passwords and API keys.
11. Your rights
Subject to applicable law, you may request access, correction, deletion, withdrawal of consent (where processing is consent-based), and grievance redressal. Email manish@idlidu.dev with sufficient detail to verify your account. We may retain information we must keep (for example completed payment records).
You may opt out of non-essential client telemetry via Id flags / settings where provided. Essential security and billing processing cannot be opted out of if you continue to use paid inference.
12. Children
The Services are not directed to children under 13 (or higher age required in your jurisdiction). We do not knowingly collect personal data from children. If you believe we have, contact us for deletion.
13. Cookies and similar technologies
See the dedicated Cookies notice for details on
idl_session and related storage. We also load Cloudflare Web Analytics
(cookieless) and Microsoft Clarity (clarity.ms / c.bing.com) on
www for aggregated metrics and session heatmaps/replay — not for advertising.
14. Changes to this Policy
We may update this Policy. The “Last updated” date will change, and material changes will be highlighted on the site or by email where appropriate. Continued use after the effective date constitutes acceptance where permitted by law.
15. Contact
Privacy inquiries: manish@idlidu.dev
Entity: Saptarang Ventures (OPC) Pvt. Ltd.