Privacy Policy

01What this website collects

thegradlew.com is a statically generated site. There is no application server behind it, no database and no session. We do not run Google Analytics, Meta Pixel, Hotjar, or any other analytics or advertising script, and we do not set cookies.

Our hosting provider keeps standard server logs — IP address, user agent, requested path, timestamp — for delivery and abuse prevention. We do not read those logs for marketing and we do not combine them with anything else.

02The contact form

The form on this site does not submit to us. It assembles the text you typed into a message and opens it in your own email application, where you can edit or discard it before sending. Nothing is transmitted until you press send in your mail client.

If you do send it, we receive an ordinary email at admin@thegradlew.com and it is stored in our mailbox like any other correspondence.

03Embedded demonstrations

Several pages embed working demonstration applications. Those run entirely in your browser and keep their state in your browser's own storage. The data in them is invented sample data. Nothing you type into a demonstration reaches us, and clearing your browser storage removes it.

Some pages link out to third-party services — a calendar booking page, for example. Once you follow such a link, that service's own privacy policy applies, not ours.

04What we hold if you become a client

A project involves real data, and this is where the policy matters. During an engagement we may hold:

• Contact and billing details — name, work email, phone, company, GSTIN, and the invoices themselves, which we are required to retain for tax purposes.
• Project correspondence — email, meeting notes, requirements and specifications.
• Credentials and access you grant us to your systems, held in a password manager and never in a repository, a document or a chat message.
• Production or sample data where the work requires it — for example, documents used to build and evaluate a retrieval system, or telemetry used to test a dashboard.

05How we handle it

• Access is limited to the engineers actually working on your project, by name.
• Credentials live in a password manager with per-project sharing, and we ask you to revoke them when the engagement ends. We will remind you.
• Source code goes into your repository and infrastructure into your cloud account, so your data stays in systems you control rather than ours.
• Where we must hold a copy of your data to work on it, we agree the scope in writing first, keep it for the duration of the engagement, and delete it on request or at the end.
• We do not sell, rent or share client data with anyone, and we do not use it to train models.

06Sub-processors

We use ordinary business tools — email and calendar hosting, a password manager, a code host, a cloud provider, and an accounting system. Where a project requires a specific third-party service, such as a model provider or an SMS gateway, we name it during scoping and it is your decision.

We do not add a sub-processor that touches your data without telling you.

07Your rights

Under the Digital Personal Data Protection Act, 2023 you may ask us what personal data of yours we hold, ask us to correct it, ask us to erase it where we are not required to keep it, and withdraw a consent you previously gave.

Write to admin@thegradlew.com and we will respond within thirty days. If we have to keep something — tax records, for instance — we will say which and why rather than refuse without explanation.

08Retention

Correspondence is kept for as long as the commercial relationship and any warranty period runs. Invoices and tax records are kept for the period Indian law requires. Access credentials are deleted at the end of an engagement. Project data copies are deleted on request or at project close, whichever comes first.

09Security, stated honestly

We follow sensible practice: least-privilege access, a password manager, multi-factor authentication, encrypted disks, and code review. We will describe any of it in detail during procurement.

We do not hold SOC 2, ISO 27001 or any equivalent certification, and we will not imply otherwise to win work. If your procurement process requires a certified vendor, we are not the right fit and we would rather tell you on the first call.

10Changes

If this policy changes materially we will update the date at the top. There is no mailing list to notify, because we do not keep one.