Last updated 11 November 2026
Overview
This policy explains what personal data TP Doc Gen AI handles, why we handle it, who else can see it, how long we keep it, and what you can ask us to do about it.
Where your organisation has a signed engagement letter or data-processing agreement with us, that document governs and takes precedence over this page.
Contents
TP Doc Gen AI is a transfer-pricing documentation, benchmarking and filing platform operated by Steadfast Business Consulting LLP (“SBC”, “we”, “us”) and built by EchorTech. This policy explains what personal data the platform handles, why, and what you can ask us to do about it.
It applies to the TP Doc Gen AI web application, the client portal on tenant subdomains, and the public marketing pages on this site. It does not apply to information you give us offline, or to a third-party site we happen to link to.
The platform handles two different kinds of data, and our responsibility differs between them. Reading this section first makes the rest of the policy easier to place.
If you are a taxpayer, a director or an employee whose details were loaded by an advisory firm, that firm decides what is collected and how long it is kept. Send your request to them first; we will support them in answering it.
We do not ask for, and the platform is not designed to hold, special-category personal data such as health, biometric or political information. Please do not upload it.
We do not sell personal data, we do not share it for cross-context behavioural advertising, we do not give it to data brokers or advertising networks, and we do not use engagement content to market to anyone.
Where the UK or EU GDPR applies to our processing, we rely on the following bases.
Where India’s Digital Personal Data Protection Act or the UAE’s Federal Decree-Law on personal data protection applies instead, we process on the equivalent lawful ground under that law.
Document understanding and narrative drafting use Claude Enterprise. Every model call runs under a zero-data-retention agreement enforced at the provider’s organisation level: prompt and response content is not logged, not cached beyond the request, and never used to train a model.
Every service routes its model calls through a single internal gateway, which records only metadata — the model, the prompt version, an input hash, token counts, latency and status. Prompt text and model output are never written to our logs.
No figure a tax authority could recompute is produced by a model. Profit-level indicators, quartiles, the arm’s-length range and every adjustment are computed in code and tested against manual workpapers. The model reads documents and drafts narrative; it does not generate numbers that reach a filing.
A firm can let outside AI agents, such as Claude, read and work with its data through our connector at tpdocgenai.com/mcp. It is off until a Firm Admin turns it on in Settings → Connected agents, and each person then connects their own agent by signing in and choosing what it may do.
Setup, permissions and support for the connector are described at tpdocgenai.com/docs/claude-connector.
We do not make decisions about you based solely on automated processing that produce legal effects or similarly significantly affect you, and the platform is not designed to.
The platform scores and screens comparable companies, and drafts narrative, but those outputs are proposals for a qualified practitioner to accept, reject or change — every accept or reject carries a recorded human reason, and a named professional signs the filing. That is a design property of the product, not only a policy commitment.
We keep the list of parties that can touch data deliberately short. These are the only ones.
| Provider | What it does | Where |
|---|---|---|
| Amazon Web Services | Hosting, database, document storage, audit trail and email delivery | Mumbai, India — our primary region |
| Anthropic (Claude Enterprise) | Document understanding and narrative drafting, under zero data retention | Model API; no content retained after the request |
| Auth0 by Okta | Sign-in and multi-factor authentication on staging and production | Managed identity service |
| Google Tag Manager | Traffic measurement on the public marketing pages, only with your consent | Not loaded in the signed-in application |
Each is bound by a written agreement covering confidentiality and security. There is no data broker, analytics reseller or advertising partner in the pipeline.
Before we add or replace a sub-processor that handles engagement data, we will give at least 30 days’ notice to the firms whose data it would touch. A firm may object on reasonable data-protection grounds within that period; if we cannot offer a workable alternative, it may terminate the affected part of the service without penalty.
Benchmarking draws on licensed company databases, used under licence for our internal operations and never resold. These hold published company financial and industry information, not personal data about you.
The flow is one-way. We query those providers for company reference data; we do not send them your engagement content, your documents or your clients’ identities.
Application data, uploaded documents and derived records are held in our primary cloud region in Mumbai, India. Material classified strictly confidential does not leave that region in any form — not in application data, not in logs, not in a backup.
India is not covered by a European Commission adequacy decision. So where personal data moves from the EEA or the UK to us, the transfer is made under the European Commission’s standard contractual clauses (with the UK addendum where the UK GDPR applies), supported by an assessment of the destination and the technical measures set out in this policy. A copy of the clauses we rely on is available on request.
The platform serves India, the UAE and Europe, so a transfer across borders may also be necessary to support you. Where it is, we put an appropriate safeguard in place before the transfer.
Every table carries a tenant identifier and a database-level row-security policy keyed to the tenant on the connection. Isolation is enforced in Postgres, not by a filter in application code that someone could forget to write.
Access is further scoped by role, by perspective and by data classification. A practitioner cannot read through to the tax-authority view of the same case, and every document and knowledge record carries a classification from public through strictly confidential that is checked on each read.
Internally, access is limited to the people who need it to run and support the service, and their actions are subject to the same audit trail as everyone else’s.
| Category | Retention |
|---|---|
| Engagement, entity and study records | For the life of the engagement, then as long as law or your agreement with us requires |
| Uploaded documents | The same period as the engagement they belong to |
| Audit events | Retained to meet regulatory and evidential requirements for the filing they support |
| Account and access records | While the account is active, plus the period needed to resolve any dispute |
| Model prompts and responses | Not retained — zero data retention applies to every call |
| Enquiries and support correspondence | Until the matter is closed and any follow-up period ends |
There is no silent auto-delete running in the background. Retention beyond the life of an engagement is a conversation with your account team, not a default we impose on you.
Transfer-pricing documentation carries its own statutory retention period — broadly eight years in India and seven in the UAE — which continues to bind the firm after it stops using the platform. On request within 60 days of an engagement ending we provide an export of that data in a machine-readable format, and remove it from primary storage afterwards on instruction.
We are not SOC 2 or ISO 27001 certified today, and you should treat any claim otherwise as wrong. Formal certification is on our roadmap; the individual controls those audits test are already running, and the Trust Centre sets them out in full.
No method of transmission or storage is completely secure, so we cannot guarantee absolute security.
If a personal data breach affects data we hold, we will notify the affected firm without undue delay after becoming aware of it, and give them the information they need to meet their own notification duties — what happened, the categories and approximate volume of data involved, the likely consequences, and the steps we are taking.
Where we are the controller, we will notify the competent authority and, where the law requires it, the individuals affected — within 72 hours under the GDPR, and within the periods India’s Digital Personal Data Protection Act and the UAE’s personal data protection law set.
If you believe you have found a vulnerability, report it to info@sbcllp.in rather than disclosing it publicly. We will acknowledge the report, keep you updated, and will not pursue anyone who reports a genuine issue in good faith and does not access or alter other people’s data.
Subject to the law that applies to you, you can ask us to do the following.
You can also complain to a supervisory authority: in the EEA, the authority for the country where you live, work, or where the issue arose; in the UK, the Information Commissioner’s Office; in India, the Data Protection Board; in the UAE, the UAE Data Office. We would rather you raised it with us first so we can put it right.
Write to info@sbcllp.in, marked for the attention of the privacy contact, who handles privacy questions and grievances for SBC. We will verify who you are before acting, and respond within the period the applicable law sets — one month under the GDPR unless the request is complex, in which case we will tell you.
If your request concerns engagement data that an advisory firm loaded, we will refer it to that firm as controller and help them respond. On a firm’s instruction we export a tenant’s data and then remove it from primary storage.
This is a professional service for businesses and their advisers. It is not directed at children and we do not knowingly collect data from anyone under 18. If you believe a child has given us personal data, contact us and we will delete it.
We update this policy when the platform changes. The date at the top always reflects the current version. Where a change materially affects how we handle your data we will tell you directly rather than relying on you noticing this page. Previous versions are available from us on request.
Privacy questions, requests and complaints go to info@sbcllp.in. For anything specific to a transfer-pricing engagement, tpdocteam@sbcllp.in reaches the team directly.
Steadfast Business Consulting LLP, Suite 5, Level 3, Reliance Cyber Ville, Vittal Rao Nagar, Madhapur, Hitech City, Hyderabad – 500081, Telangana, India. Telephone +91 9014 079 600.
We use Google Analytics to see which pages are useful. It only loads if you accept, and you can change your choice later from Cookie settings. Privacy policy