Notice to Data Principals in India.

This is the itemised notice the DPDP Act requires us to give you before we process your personal data. It sits alongside the main privacy policy, which describes the same processing in more detail; where the two differ on your rights in India, this page governs. Last updated: 2026-10-08. Managed Cloud is in public alpha. Previous versions

00 · Who is responsible.

AGI Automation LLC, c/o registered agent, 5900 Balcones Drive STE 100, Austin, TX 78731, USA, is the Data Fiduciary for the processing described here: it decides why and how your personal data is processed. You are the Data Principal. AGI has no establishment in India and no data centre in India; your data is hosted in the United States, which section 06 explains.

01 · The mode decides what we hold.

Most of this notice depends on which mode you run, because Local, BYOK and Managed Cloud are separate trust boundaries and your data goes to genuinely different places in each. Read this first.

• LocalWhere it goes: from the CLI to Ollama or LM Studio on loopback. Nothing is transmitted to us and nothing is silently routed to BYOK or Managed Cloud.
  What we hold: nothing about the local model request. The current Desktop and web apps use Managed Cloud and do not expose Local inference.
• BYOKWhere it goes: from your client straight to the provider you targeted, on your own API key. We are not in that request path.
  What we hold: not the provider key or prompt traffic. BYOK is part of the CLI, which stores provider credentials in the operating system credential store, or in owner-only files on Linux or when the keyring is turned off, and calls the provider directly. The VS Code extension is coming soon; Desktop and web do not expose provider-key entry.
• Managed CloudWhere it goes: through our gateway to the provider serving the model you selected, or, on the Free plan’s default model, the provider AGI chooses for that turn.
  What we hold: conversations, files, projects, memories, schedules and settings, so they sync across your devices.

02 · What we process, and for which purpose.

The Act requires the purpose to be specific and the data to be limited to what that purpose needs. Each row below is one purpose, not a category we might later reuse.

• Email address, account identifier, authentication metadataPurpose: creating and securing your account. Optionally, the account choice “Email me product news, tips and offers.” is a separate box at sign-up that you can leave unticked or turn off on its own. Held by our identity provider. We do not store your password. Sign-up also asks for your age; it is checked in your browser and is not stored or sent to us. Basis: your request for the account; your consent for marketing email.
• Billing identifiers, plan, invoice metadataPurpose: taking payment and managing your subscription. Card details go to Stripe directly and never reach us. Basis: performing the paid service you signed up for.
• Conversations, files, projects, memories (Managed Cloud only)Purpose: running the assistant and syncing your work across your devices. Basis: providing the Managed Cloud service you chose to use. Local and BYOK do not produce this data for us.
• Error reports and performance traces (Sentry)Purpose: diagnosing crashes. Content-scrubbed, but a stable user id is retained so a crash can be tied to a session, so they are pseudonymous, not anonymous. Basis: your consent. Off until you turn it on.
• Aggregated page views (Google Analytics 4)Purpose: understanding which parts of the product get used. Basis: your consent, recorded per purpose. The gate fails closed: if your choice cannot be read, analytics stays off.
• Email address given for Enterprise accessPurpose: discussing contract-scoped Enterprise access and additional Enterprise capabilities with you. Optionally, product updates: a separate box you can leave unticked or withdraw on its own. Basis: your consent, recorded before the address is stored.
• Server logs and an append-only security audit logPurpose: debugging, preventing abuse, and investigating security incidents. Bearer tokens are redacted. Basis: keeping the service secure and available.

What we do not do with it. AGI does not train AGI-owned models on your prompts, responses or files. We run no advertising, set no advertising cookies, and do not sell or share personal data for cross-context behavioural advertising.

03 · The consent we ask for, one purpose at a time.

Consent under this Act has to be specific, unbundled, and given by a clear affirmative action. New optional choices start unticked, and an optional purpose never blocks a necessary one. Decisions are recorded against the revision of the privacy notice that was on screen. On the early-access forms this includes the boxes you leave unticked; at sign-up a marketing email box you leave unticked records no decision. These are the purposes we ask about:

• Store my email address so AGI can discuss contract-scoped Enterprise access with me.Your address is stored so a person can discuss contract-scoped Enterprise access and contact you as additional Enterprise capabilities become available. Organisation, SSO, SCIM, audit export, and retention controls are already live for entitled workspaces. It is used for this Enterprise conversation and nothing else; nothing in the product mails this list automatically.
  Required for the thing you asked for
• Store my email address so we can tell you when this platform ships.Your address is stored so we can email you once AGI Mobile, AGI in Chrome or AGI in VS Code has a verified installer to download. It is used for that and nothing else, and is unrelated to the Enterprise contract-access contact list.
  Required for the thing you asked for
• Also email me product updates and launch news.Occasional email about new releases and capabilities, sent by a person rather than an automated system. Separate from the early-access list, so you can withdraw it without leaving that list.
  Optional, declining costs you nothing
• Allow product analytics.Aggregated page views on this site via Google Analytics 4, and product usage events from the AGI apps on web, desktop, mobile, Chrome, VS Code and the command line, recorded against your account: that a response was stopped or regenerated, or that a suggested edit was accepted or dismissed, with fixed labels such as your plan or the model provider. Never your messages, code, files or file names. Used to understand which parts of the product work. Off unless you turn it on, and a workspace administrator can turn it off for every member. This is the same choice as the analytics switch in the cookie banner.
  Optional, declining costs you nothing
• Email me product news, tips and offers.Email about new features, ways to get more from AGI, and offers such as discounts or free allowances. Off unless you turn it on. You can turn it off at any time in Settings or on the privacy requests page.
  Optional, declining costs you nothing

Withdrawing is as easy as giving: change any of them at /privacy/requests, with no email and no support ticket. Withdrawal stops the future processing that depended on it; it does not undo processing that already lawfully happened, and it does not delete your account. That is a separate request on the same page. AGI is not registered with a Consent Manager under section 6(7), so consent is given to us directly rather than through one.

04 · Who else receives it.

The published list, with what each one receives and where it runs, is at /subprocessors. In summary: an identity provider holds your login, Stripe holds your payments, our hosting and database vendors hold what you store in Managed Cloud, object storage holds your files, and error/analytics vendors receive only what section 02 describes and only with your consent.

An earlier version of this notice said that list was incomplete. It named an email provider, a video-generation provider, a geocoding service and the Apple and Google store APIs as recipients missing from it. The email, video-generation and geocoding providers and Google’s purchase verification API are on the list now, and the corrections are recorded on that page. Apple was named in error: purchases on iOS are verified on our own servers and nothing is sent to Apple. If your decision to use this service depends on the full recipient list, ask the grievance contact in section 08 before you sign up.

Model providers. In Managed Cloud, the prompt and any attached content go to the provider serving the model you selected, and for routed models the request passes through OpenRouter. On the Free plan, a chat on the default model goes to a provider AGI chooses, not one you pick: Alibaba Cloud Model Studio, on AGI’s own key at its international endpoint in Singapore, or OpenRouter’s free router. Which one answers depends on what is available for that turn, and the reply shows the model that answered. Those providers handle that content under their own terms and data-use policies; our no-training statement is about AGI-owned models and is not a promise on their behalf. In BYOK the request goes from your client straight to the provider on your key, governed by your own account with them. In Local, none of them are contacted.

05 · How long we keep it.

The Act requires erasure once the purpose is no longer being served, unless retention is required by law. Every row below is a job or a mechanism that exists in the product, and the ones we do not control are named as such. The full schedule, including billing records, is section 05 of the privacy policy.

• Account and its contentKept while your account is active. Permanently erased 24 hours after a deletion request, by a daily scheduled job that also deletes your identity at our authentication provider.
• Conversations (Managed Cloud)Kept until you delete them or delete your account. There is no automatic expiry on ordinary conversations today, and we will not describe one until it runs.
• Temporary chatsAbout 30 days, hard-deleted by a daily job unless a workspace legal hold covers them.
• Deleted files30 days in the recently-deleted bin, then the underlying objects are removed.
• Security audit log90 days. A scheduled job deletes older entries every night at 02:07 UTC.
• Consent recordsKept for as long as the account exists, including withdrawn consents, because a record that consent was once held is the evidence this Act asks us to be able to produce. Erased with the account.
• Early-access list email addressesNo maximum age is enforced today. The address is removed on request via the grievance contact below. We will not publish a window until a job deletes them.
• Server logs and backupsVendor-governed. We do not operate a process that reaches into vendor snapshots to remove individual records, and we will not claim a number we do not set.

06 · Where it goes, and out of India.

Your personal data is processed and stored in the United States. AGI does not offer data residency in India, so using this service means your personal data leaves India. The Act permits transfer outside India except to territories the Central Government restricts by notification; whether any notification affects the United States is a question of the live notification list on the date you read this, and we will not assert an answer to it here. If you need Indian data residency, we do not have it, and you should not sign up expecting it.

07 · Your rights, and what actually happens.

• Access: a summary of your data and who it has been shared withSigned in, export your data from the account export endpoint at any time. It is rate limited and each export is recorded in the security audit log. The list of recipients is section 04 and /subprocessors; the export does not enumerate them per record.
• Correction, completion and updatingProfile and settings are editable in the product. For anything you cannot edit yourself, use the request form below and say what is wrong; we correct it.
• ErasureRequest account deletion in the product. Erasure is scheduled 24 hours later and then performed. You get no confirmation email. Cancellation is self-serve: sign back in and cancel from Settings > Account any time before erasure begins.
• Withdraw consent/privacy/requests, per purpose, immediately, without contacting anyone.
• Grievance redressalSection 08. Use it before approaching the Data Protection Board: the Act expects you to have exhausted our route first.
• Nominate someone to exercise your rights if you die or become incapacitatedNot self-serve. There is no nomination field in the product today. Send the nomination to the grievance contact in section 08 and we will record it against your account manually. This is an open item, not a finished feature.

The Act also places duties on you: do not impersonate someone else when giving your data, do not suppress material information when it is legally required, and do not file false or frivolous grievances.

08 · Grievance redressal.

Grievance Officer, AGI Automation LLC

Email contact@agiworkforce.com with the subject line “DPDP grievance”, or post to AGI Automation LLC, c/o registered agent, 5900 Balcones Drive STE 100, Austin, TX 78731, USA. We aim to respond within 30 days. That target is our commitment, not a statutory deadline we are quoting.

Subject-line routing is used because this is the one mailbox proven to receive mail; a dedicated grievance address is not provisioned, and we would rather publish a working inbox than a dedicated one that bounces. If our response does not resolve it, you may complain to the Data Protection Board of India.

09 · Children, stated honestly.

Under this Act a child is anyone under 18, and processing a child’s data requires verifiable consent from a parent or guardian. Sign-up asks for your age and refuses anyone under 13, and the terms require anyone under 18 to have permission from a parent or guardian. We do not currently perform verifiable parental consent or age verification. The age is whatever is typed, it is checked once in the browser and not kept, and nobody checks the permission. That is a gap against this Act, we are naming it rather than implying otherwise, and it is tracked as an open item. Because an account can be created from the age of 13, people this Act treats as children can hold accounts here, and we cannot tell which accounts those are. If you believe we hold a child’s personal data without a parent’s consent, use the grievance contact above and we will delete it. We do not run behavioural advertising or tracking directed at children in any mode.

10 · Security and breach.

We are required to protect your data with reasonable security safeguards, and to notify the Data Protection Board and every affected Data Principal if there is a breach. Our operational posture is at /security. The internal procedure for a breach (who declares it, what goes in the Board notification, and what you would receive) is written down and rehearsed against a 72-hour clock. The product sends email to one account at a time, and no procedure for emailing a set of affected users has been built or exercised, so a user-facing breach notice would be delivered in-product and at a public URL rather than by email. We would rather tell you that now than discover it during an incident.

11 · Language, and changes.

This notice is published in English. The Act entitles you to it in any language in the Eighth Schedule to the Constitution; translations are not yet published, and that is an open item. The current version is always at this URL with the revision date at the top, and material changes are recorded on /changelog. No mailing path for policy changes exists in the product, so we do not promise emailed notice of a change.

• Exercise your rights
• Full privacy policy
• Subprocessors
• Security