TwinEthos homeRequest access

Market

AI law in India

3 binding provisions TwinEthos encodes that reach India (IN): 3 in force, 0 enacted but not yet applying. Start from the guards to add.

Informational data, not legal advice. Summaries and rules have not been reviewed by a lawyer: always verify official law text for decisions. A suggested guard is intended to address each rule; adding it is not a statement of compliance to that law.

Get the build plan for India

The guards that cover the most here

41 guards address 56 items across 1 jurisdiction with binding law: 3 binding law in force, 0 enacted but not yet applying, 29 standards and frameworks, 24 TwinEthos recommended guardrails.

  1. Generated content reaches users with no input or output content filter

    Screen user input and model output with a moderation or safety-classifier call that blocks, redacts, or escalates flagged content, and keep provider safety filters on.

    Addresses 2 items: 1 binding law in force · 1 standard

    Law in force in India (IN).

  2. GenAI content lacking explicit and implicit labels

    Add both a visible AI-generated label and implicit metadata naming the provider and a content ID to synthetic content before the file is saved, returned, or exported.

    Addresses 1 item: 1 binding law in force

    Law in force in India (IN).

  3. Large online platform doesn't detect/display content provenance

    Read embedded C2PA provenance on upload, preserve it through media processing, and show users a Content Credentials indicator with a way to inspect the data.

    Addresses 1 item: 1 binding law in force

    Law in force in India (IN).

  4. Adverse AI decision without explanation/appeal

    Send each adverse AI-assisted decision with its main reasons and the AI's role, plus a way to correct data and appeal to a human who can change the outcome.

    Addresses 3 items: 2 standards · 1 recommended guardrail

  5. AI chat interaction without disclosure

    Show an AI-identity notice at or before the first assistant turn, in the UI or as the opening message, and answer truthfully when asked if it is a bot.

    Addresses 3 items: 2 standards · 1 recommended guardrail

  6. Untrusted content influences instructions or tools

    Keep fetched, retrieved, and tool-returned content out of the system prompt, pass it as delimited data, and restrict which tools a turn holding that content can call.

    Addresses 3 items: 2 standards · 1 recommended guardrail

  7. Agent actions not traceable to identity and owner

    Give each agent its own credential and a registry entry naming an accountable owner, and log every tool action with agent_id, owner, action, target, and timestamp.

    Addresses 2 items: 1 standard · 1 recommended guardrail

  8. Agent high-impact action without human approval

    Classify agent tools by impact and route every high-impact or irreversible call through an enforced human-approval step in the executor, with the decision logged.

    Addresses 2 items: 1 standard · 1 recommended guardrail

  9. AI usage, agent steps, and spend not bounded

    Cap agent steps and output tokens on every model call, set per-key and per-project budgets with usage alerts, and issue scoped, expiring model keys.

    Addresses 2 items: 1 standard · 1 recommended guardrail

  10. GenAI in consequential decisions without confabulation/output-validation controls

    Validate GenAI output against a schema and its cited sources, and send unverifiable claims to review, before it drives a consequential decision or record.

    Addresses 2 items: 1 standard · 1 recommended guardrail

The top 10 of 41; the build plan ranks all of them and lets you narrow by AI feature.

By AI feature

Plans for one feature in India:

Laws

Informational data, not legal advice. Summaries are TwinEthos's own words and rules have not been reviewed by a lawyer: check the official text before relying on any of it. A guard addresses an item; adding it is not a statement that your code meets any law.