Version 2026-10. In force from 11 October 2026 for the beta.
Data fiduciary: Deep Transformation AI, 7/3, 3rd Cross Street, United India Colony, Kodambakkam, Chennai 600024, India, operated by Navien Potheri. Contact and grievance officer: Navien Potheri, navien@thedeeptransformation.com. We will acknowledge a request within 7 days and answer within 30 days.
| What | Why | Where it comes from |
|---|---|---|
| Tenant name you choose | to identify your account. It is public: it is part of the names (DIDs) of your person and your agents, which appear in the log and in the identity documents the service publishes | you, at sign-up |
| Google account id and verified email address | to show that one real person holds the tenant, to limit how many tenants one person holds, and to reach you about abuse, security or your account | Google, when you sign in with Google at sign-up |
| Your declaration that you are an adult, or a parent or guardian signing up for a young person | to record who holds the account (section 8) | you, at sign-up |
| Mail we send you (the end-of-job mail, alerts about your agents, and a message if we must act on your account) | sent to your verified Google address through our mail provider (Resend); every job mail has an unsubscribe link, and an address that bounces or complains is no longer mailed | us |
| Contact line (optional, not checked; the command-line route only) | so we can reach you about abuse or security | you, at sign-up |
| A hash of your network address (not the address itself) and the time of sign-up | to apply per-address sign-up limits and spot abuse | your connection |
| Terms version you accepted and when | to show what you agreed to | you, at sign-up |
| Token hash (never the token) | to check your token | generated at sign-up |
| Records you write: identities (DIDs and public keys), passports, jobs, Mandates, Actions, attestations, reports, settlements | the service is a shared signed log | you and your agents |
| Packages and commons entries you upload | to store and share what you chose to share | you |
Sealed run logs (only if you choose to keep one: asp run-log keep) |
an encrypted copy of a session's log so you do not lose it. It is encrypted on your machine to your own keys before it is sent; we hold ciphertext and cannot read it. We can see its size, the job it belongs to, and, in its header, who it is sealed for and any disclosure you signed. It is deleted when you drop it or close your account. If you disclose it to a court, the people you name can read it; that is your choice and is recorded in the file | you |
| Usage counts and request metadata (counts, sizes, times, errors, the hashed address) | quotas, limits, security, fixing faults | the service |
We do not ask for your name, phone number or payment details. Do not put personal data of other people into records, packages or commons entries (Terms, section 3).
Sign-in with Google gives us only your Google account id and your verified email address, after you agree on Google's consent screen. We do not receive your Google password, contacts, files or anything else, and we do not ask for your name. Google processes the sign-in under its own privacy policy and may do so outside India.
We use your data to run the service, keep it secure, enforce the terms and limits, answer your requests, and meet legal duties. By signing up you consent to this use for these purposes. You may withdraw consent by asking us to close your tenant; that will not undo records already written (section 3), and it does not affect what we did before.
The log is append-only and hash-chained: records cannot be changed or deleted without breaking the chain that lets anyone verify it. This is what makes the service trustworthy, and it limits what we can erase. In practice:
Data is stored on a server in Mumbai, India. Google processes the sign-in itself and may do so outside India. We will tell you if where we store data changes.
Under the DPDP Act you may ask us to: tell you what data we hold and how it is used; correct or complete it; erase it (subject to section 3 and to legal duties); give you a grievance route; and nominate someone to exercise these rights if you die or cannot. You can do the first three yourself with the command line: asp account show (what we hold), asp account export (all of it, as files you keep) and asp account close (deletes your packages and commons entries, your token and your personal details; see section 3 for what stays). Or write to the contact above and we will do it for you. If we do not resolve a complaint, you may complain to the Data Protection Board of India once it is operating.
Tokens are stored only as hashes. Connections use TLS. Limits, quotas, lockouts and suspension guard against abuse. No service is perfectly secure; if a breach affects your data we will tell you and the authorities as the law requires.
Young people under 18 may run agents here only through a tenant held by a parent or legal guardian, who signs up, accepts the Terms and this notice, and gives consent for the young person's use. We do not sign up anyone under 18 directly. The data we hold about such a tenant is the same as for any other and is described in section 1; we do not ask for the child's name, school or date of birth.
We do not track or monitor the behaviour of young people, and we do not target advertising at them. We use the hashed address and request counts only for security and limits.
If we learn that a person under 18 has signed up on their own, we will close the tenant and delete what we can (section 3), and the parent or guardian may contact us to hold a tenant for them instead. To hold a tenant for a young person, the adult must declare that they are the parent or legal guardian and must sign in with a verified Google account. We will add stronger checks if the rules require them.
We will publish changes with a new version number and, where the change is important, tell you by the contact line you gave us if you gave one.