Skip to content

Privacy policy

What each part of todkett.com receives, where it goes, how long it is kept and who sees it. Written in plain English to India's data protection law and the EU and UK rules, and not yet reviewed by a lawyer.

01In short

The free tools keep everything on your device. The idea form and the booking page send us what you type, so we can reply. Reading the site is counted without cookies, and three analytics tools load only if you accept cookies. We never sell your data and send no marketing email.

Free tools

What you give
Files, text and numbers you put into a tool.
Where it goes
Nowhere. The tools run in your browser and upload nothing.
How long it is kept
Not kept. Gone when you close the page.
Who sees it
Only you.

The idea form

What you give
Your email, the task, your two answers and any optional details.
Where it goes
Our server on Vercel, then Supabase, our n8n and Google. Cloudflare checks the form for spam.
How long it is kept
Up to 6 months after our last contact.
Who sees it
Nitin Sarkar, who runs Todkett.

Booking a call

What you give
Your name, email and the answers on the booking page.
Where it goes
Cal.com, then our n8n and our Gmail, to prepare for the call.
How long it is kept
Up to 6 months after our last contact, the same as an idea.
Who sees it
Nitin Sarkar, and Cal.com as the booking service.

Reading the site

What you give
A cookieless count of the page you read. If you accept cookies: how you move through the site, clicks and scrolls.
Where it goes
Cloudflare Web Analytics for everyone. Google Analytics, Microsoft Clarity and PostHog only after you click Accept.
How long it is kept
Counts are totals. The three cookie tools keep their data under their own retention settings.
Who sees it
Nitin Sarkar. Tool files and tool text are masked from session replays.

Talking on GitHub

What you give
What you post in Discussions or send as a submission.
Where it goes
GitHub, under your own account and GitHub's own privacy terms.
How long it is kept
Public from the moment you post, as GitHub keeps it.
Who sees it
Anyone. GitHub is a separate service, not ours.

02Who we are, and who answers

Todkett is an automation lab based in Bangalore, India. The site and this policy are run by Nitin Sarkar, a sole proprietor. Under India’s Digital Personal Data Protection Act 2023 that makes Nitin Sarkar the data fiduciary, and under the EU and UK General Data Protection Regulation the controller, for everything this policy describes.

Grievance officer
Nitin Sarkar. The same person answers every privacy question and complaint, from any country.
Privacy address
privacy@todkett.com
Everything else
hello@todkett.com
Postal address
Given on request, by email, to anyone who needs it for a legal notice.
How fast we answer
We acknowledge within 2 working days and answer within 30 days. If a request takes longer, we say why and when.

03The free tools

The ROI calculator, the ATS resume checker and the PDF toolkit run in your browser. Your files, your resume, the job description and your numbers never leave your device: no upload, no account, no email.

  • Files are read in your browser's memory and forgotten when you close the page. Nothing is saved in the browser for later.
  • The ROI calculator can put your numbers in the link, after the # sign, so you can come back to them. Browsers do not send that part of a link to any server.
  • Your numbers reach us only if you press Send this estimate, which opens the idea form with them filled in. Nothing is sent until you send that form.
  • Each tool page shows what your browser requested during a run, so you can check this yourself.

04The idea form

When you send an idea we receive your email, the task, how often it happens and how long it takes, and anything you add under Add details: tools, department, your name and your company website. We use them to reply to you, and for nothing else. Every field is listed here; there is no hidden one.

  • Your company website is shown to us as text. We never open it or follow it.
  • We note which kind of site sent you to the page you were on (for example a search engine or a social network), never the full link.
  • Your IP address is used only for the spam check and to limit how often one address can send. Our server keeps it only as a salted hash, and clears even that after 30 days. The hash cannot be turned back into the address.
  • The server's own log holds the page address and the result code for 1 day, never what you typed.
  • You get a reference number on the page. It is the receipt, and it is how you quote the idea to us later.
  • We count the ideas people send, by topic, to decide what to build next, without names or contact details.
  • If you tick the share box, a short summary in our own words may shape a public use-case page. It never names you or your company. Leave it unticked and nothing from your idea is published.
  • No model reads your idea. Fixed rules sort it, and a person reads it.

Once our email sender is set up, you get one email that says we received your idea, with your reference. It never repeats what you wrote. We send no newsletters and no marketing email, and we never add you to a list.

Where an idea goes

  1. You send the form

    From your browser, over an encrypted connection.

  2. Spam check

    Cloudflare Turnstile sees your IP address and browser signals.

  3. Our server

    Vercel checks every field. Your IP address is kept only as a salted hash.

  4. Lead store

    Supabase keeps the lead and its reference.

  5. Our workflow

    n8n, on our own Oracle Cloud machine, files it with fixed rules.

  6. Our inbox

    Google: a sheet of leads and an email alert to us.

The route planned for launch, on free plans of each service. Until the lead store is connected, the form stores nothing and shows our email address instead.

05Booking a call

Booking happens on Cal.com, under Cal.com’s own privacy terms as well as ours. Cal.com receives your name, email and answers; we receive the booking to prepare for the call, and the calendar invite goes to the address you gave.

Our n8n reads new bookings and emails us a short brief from a fixed template. Your website, if you give one, is shown as text and never opened. No model reads your answers. The call itself is not recorded unless you and we agree to it on the call.

06Reading the site: analytics and cookies

We use Cloudflare Web Analytics to count page views. It runs without cookies and without storing your IP address with the count. It records the page address, the site you came from, your browser and device type, your country and how fast the page loaded, and gives us totals. It does not follow you across other sites and does not build a profile.

Google Search Console tells us which searches showed our pages on Google and how often they were clicked. Nothing on this site sends it anything about you: it is Google’s own report, confirmed by a record on our domain, and it shows queries and counts, never who searched.

We ask before setting any other cookie. If you click Accept in the cookie banner, we also load Google Analytics 4 (Google, United States: which pages are visited and how, with IP addresses anonymised), Microsoft Clarity (Microsoft, United States: heatmaps and session replays, so we can fix confusing pages) and PostHog (United States: how people move through the tools and pages). None of these load, and nothing is sent to them, until you click Accept. If you click “Only essential”, they stay off.

  • Session replays mask form fields, and the free tools' file and text areas are masked completely: your files, resume and job text are never recorded.
  • No advertising pixels and no fingerprinting.
  • You can change your choice at any time with Cookie settings in the footer.
  • Your cookie choice and your light or dark theme are saved in your own browser and never sent to us.

07Talking on GitHub

Questions, builds and workflow submissions happen in GitHub Discussions and GitHub issues under the Todkett organisation. To post you use your own GitHub account, and GitHub handles your account data as a separate controller under its own privacy statement. We moderate; we do not run GitHub.

  • Anything you post there is public the moment you post it, and GitHub keeps history even if you delete it later. Remove every key, password, address, email and name first.
  • If you submit a workflow, we read the file you link and publish the summary and your chosen name on this site under the licence in the terms. Ask us and we remove your name or the item from our pages; what GitHub keeps is GitHub's.
  • You can take part without a GitHub account by writing to us through the idea form. Then only this policy applies.

08Services that handle your data

Every service that can see what you send us, or that runs part of the site, is listed here with what it does. Each is on a free plan. We will add any new one here before it is used, and we never name one we do not use.

Vercel
Hosts the site and runs the form's server code. Keeps its request log for 1 day: the page address and the result, never what you typed.
Cloudflare
Runs our domain's name servers, so every request to todkett.com passes through it. Cloudflare Web Analytics counts page views without cookies. Turnstile, the spam check on the form, receives your IP address and browser signals once the form is live.
Google Search Console
Google's report of searches that showed our pages. Verified by a record on our domain. Sends us no data about you.
Google Analytics
Only if you accept cookies. Which pages are visited and how, with IP addresses anonymised.
Microsoft Clarity
Only if you accept cookies. Heatmaps and session replays, with form fields and tool content masked.
PostHog
Only if you accept cookies. How people move through the pages and tools.
Bing Webmaster Tools
Microsoft's report of searches on Bing. Verified by a tag on our pages. Sends us no data about you.
Cal.com
The booking page and the calendar invite. Your booking data sits with Cal.com under its own privacy terms.
GitHub
Discussions, issues and the public library repository. A separate controller for your account and your posts.
Supabase
Stores each lead and its reference once the lead store is connected. Not connected yet.
n8n on Oracle Cloud
Our own workflow machine, reachable only by us. Files leads and prepares call briefs with fixed rules, no model.
Google Sheets and Gmail
A sheet of leads and the inbox that alerts us. Both on the owner's own Google account.
Resend
Will send the one email that says we received your idea, once it is set up. Nothing is sent through it today.
OpenRouter
Not used. It would carry an AI model step, and none exists on any form or booking path. We will name it here before one does.

09Why we use your data, and on what basis

India’s law asks us to tell you each item of data and each purpose before you give it, and to use it for that purpose only. The EU and UK rules ask for a lawful basis per purpose. Both are in one table.

Answer your idea

What we use
Your email, the task, how often it happens and how long it takes, and anything you add under Add details.
Why we may
You asked us to. You tick the contact box before sending (consent), and the reply is the step you requested.
How long
6 months after our last contact.

Prepare and hold a call

What we use
Your name, email, the booking time and your answers on the booking page.
Why we may
The steps you asked for before any agreement, so we can hold the call you booked.
How long
6 months after our last contact.

Keep the form safe

What we use
A salted hash of your IP address, the time the form took, and the spam check's result. Never the address itself.
Why we may
Our legitimate interest in running a site that is not abused, and the duty of reasonable security under India's information technology law.
How long
Hashes are cleared after 30 days. Server logs last 1 day.

Count visits

What we use
The page address, the site you came from, your browser and device type, your country, and how fast the page loaded. No cookie, no stored address.
Why we may
Our legitimate interest in knowing which pages are read. Nothing in the count identifies you, so it runs whatever you choose in the cookie banner.
How long
We hold totals only. The service keeps its own aggregates under its own terms.

Understand how the site is used (only if you accept cookies)

What we use
Pages visited, clicks, scrolls and session replays, tied to a random browser ID in a cookie. Form fields and the free tools' file and text areas are masked.
Why we may
Your consent, given by clicking Accept in the cookie banner. You can withdraw it at any time with Cookie settings in the footer.
How long
Google Analytics: 14 months. Clarity: replays 30 days, heatmaps 13 months. PostHog: under its plan's retention.

Shape a public page

What we use
A short summary of your idea in our own words, with no name, company or contact detail.
Why we may
Only if you tick the share box (consent). Untick it and nothing from your idea appears anywhere.
How long
For as long as that page exists. The idea itself follows the first row.

Decide what to build next

What we use
Counts of ideas by topic.
Why we may
Our legitimate interest. Once counted, nothing is about you.
How long
Counts are kept; they hold no personal data.

Meet a legal duty

What we use
Whatever a law, a court or a regulator requires, and only that.
Why we may
A legal obligation, or the defence of a legal claim.
How long
For as long as that duty lasts.

Where we rely on consent, you can withdraw it as easily as you gave it: write to the privacy address, and we stop. Where we rely on our legitimate interest, you can object, and we stop unless the law requires us to keep going. We never use your data for a new purpose without telling you first.

10How long we keep it

Ideas and estimates
Up to 6 months after our last contact, then deleted.
Bookings and call briefs
Up to 6 months after our last contact, then deleted from our inbox and sheet.
Server logs
1 day. They hold the address of the page and the result, never what you typed.
IP address hashes
Cleared after 30 days.
Visit counts
Totals only, with nothing about you as a person.
Tool files and text
Never kept. They stay on your device.
Anything you ask us to delete
Deleted within 30 days, unless a law requires us to keep it, and then we tell you which law.

When the purpose ends, so does the data. We do not keep it in case it is useful later.

11Where your data goes: India and other countries

We work from Bangalore, so your data is handled in India, and by the services above where they run, which may be the United States or Europe. India has no adequacy decision from the EU or the UK, so here is the basis we rely on.

  • You send us the form or the booking yourself, asking us to reply or to hold a call. The transfer to India is necessary for the steps you request, which the European regulation allows (Article 49(1)(b)), and we tell you here, before you send, that it happens.
  • The services that process your data for us hold it under their own standard contractual clauses and data processing terms, which we accept when we set them up.
  • If you would rather not send anything to India, do not use the form or the booking page. Every other part of the site works without them.
  • Under India's law, a person outside India who sends us data is covered by this policy in the same way as anyone in India.

12Your rights, and how to use them

Write to the privacy address from the email address you used with us, so we know it is you. We ask for nothing more unless we cannot tell who is asking. We acknowledge within 2 working days and answer within 30 days, free of charge. Nobody is treated worse for asking.

In India
Under the Digital Personal Data Protection Act 2023: a summary of what we hold and what we did with it; correction, completion and updating; erasure once the purpose is served; withdrawal of consent; a person you nominate to act for you if you cannot; and a complaint to the grievance officer first, then to the Data Protection Board of India.
In the EU and the UK
Under the General Data Protection Regulation: access to a copy; rectification; erasure; restriction; portability in a common format; objection, which always stops marketing, and there is none; withdrawal of consent; and a complaint to your supervisory authority, which in the UK is the Information Commissioner's Office. We make no decision about you by automated means alone.
In California
Under the California Consumer Privacy Act: to know what we collect and why; to delete it; to correct it; and to be told that we do not sell or share personal information for advertising, which we do not. We honour these requests whatever our size.
Anywhere else
The same choices, by the same email. We do not keep two standards of care.

Sending an idea or booking a call is always your choice: the free tools and every page work without it.

13Children

This site is for adults. India’s law treats everyone under 18 as a child and requires a parent’s verifiable consent before their data is processed, and we have no way to take that consent. So if you are under 18, read and use the free tools as much as you like, but do not send the form, book a call or post on GitHub.

We do not knowingly collect data from anyone under 18. If we learn that we have, we delete it and tell the parent or guardian who writes to us. Nothing on the site tracks, profiles or advertises to a child.

14How we protect it

  • Every page and form travels over an encrypted connection.
  • Raw IP addresses are never stored. The form's server refuses to run without the secret that salts the hash.
  • Secrets live in the hosting settings, never in the code or on the page. The browser never talks to the lead store or to n8n directly.
  • Only Nitin Sarkar can read leads and bookings. There is no team account and no shared login.
  • If a breach affects your data, we tell you and the Data Protection Board of India as the law requires, and the EU or UK authority where that applies, without undue delay.
  • This is the reasonable security practice India's information technology law asks of us, kept in proportion to a one-person site that stores little.

15What we never do

  • Sell, rent or share your data for advertising.
  • Profile you, score you or make a decision about you by automated means.
  • Send marketing email, newsletters or follow-ups you did not ask for.
  • Run a model on your form, your booking or your files.
  • Add a service to the list above without changing this page first.

16Changes, and the standing of this policy

This policy was written by the owner, without a lawyer’s review, to the standard of India’s Digital Personal Data Protection Act 2023 and the EU and UK General Data Protection Regulation. A lawyer will review it, and this line will change when that has happened. Until then, if a line here is unclear, the stricter reading applies.

When this policy changes, its “Last updated” date in the contents list changes with it, and the new version applies from that date. For a change that affects what we do with data you have already given us, we tell you by email first. Earlier versions are available on request.

The rules for using the site are in our terms of use. How the community works is on the community page. To send us a task, use the idea form.