Privacy policy

Effective 2026-11-11

This page covers tanod.dev and its subdomains: the website, Tanod Tools, the Tanod API and MCP server, and Tanod Monitor. Questions or requests: ops@tanod.dev.

Server logs

Every request to tanod.dev and our API hosts is logged: time, your IP address, user agent, the requested URL, referrer, response status and size. We remove credentials and payment headers, any token or key URL parameter, and do not log Tanod Monitor push URLs. Logs are kept for up to 30 days and used for security, abuse prevention, debugging and usage statistics.

API and MCP usage

Prepaid credits

We store the SHA-256 hash of your key (never the key), its balance, your purchases (amount and the payment's transaction) and your charges (route, amount, time). We do not store an email, name or IP address in these records. Details: prepaid credits.

Skill quest

The answer check stores no answers. A correct answer sent with a payout address takes a prize slot: we keep the week, the slot, the address, the time and keyed hashes of your IP address and its network (one slot per person), only to pay the prize, and delete them 60 days after the week ends. To limit checks we count them per UTC day under the same keyed hashes, and delete the counts after that day. The prize payment is public on its blockchain. Rules.

Tanod Tools

Most tools run entirely in your browser: your files never leave your device. The server tools (compress PDF, OCR, protect or unlock PDF, web page to PDF, image to text) upload your file for that one job. It is processed in a temporary directory, deleted when the job ends, and never logged. We keep the tool name, status and duration and a daily job count per IP address. These pages use Cloudflare Turnstile to block automated abuse.

Tanod Monitor

We store what you enter (targets, names, alert settings), the metrics your router or jobs send us (about a day of history per monitor), check results and exposure-scan results (up to 90 days). Manage tokens are stored only as hashes. Groups that are never opened and never report for 30 days are deleted with their data. Exposure scans run only against IPs and hosts whose control you have proven; how to opt out: scanner page.

Chrome extension

The Tanod Chrome extension (Tanod OCR) sends data only when you choose a file or select an area of a tab. It sends the address (URL) of the image or PDF you right-click and choose to read to tanod.dev, which fetches that file and returns its text. When you click its toolbar button or its "Select an area and read text with Tanod" menu item, it captures the visible part of that tab. The capture stays in the extension's memory and is never stored or sent. You drag a box around the text on the extension's own page, and only that selected area is sent to tanod.dev, as a PNG image, when you click to read it; tanod.dev reads its text and returns it. The address of the page is not sent. The extension does not read the pages you visit, does not collect your browsing history, and sends nothing until you choose a file or an area. Links to private or local addresses are not sent, and links with common token, key or signature parameters are not sent.

If you save a prepaid credit key in the extension, it is kept only in the extension's local storage on your device (not synced) until you remove it in the extension's options. It is sent only to tanod.dev, in a request header and never in a URL: to check your balance, and with each paid job after you confirm its price. Before asking you to confirm, the extension reads the current price from tanod.dev with a request that contains neither the file's address nor any image.

These requests are handled like any other API call: they appear in the server logs described above (kept for up to 30 days, with credential headers such as the key removed) and in the API usage records. A paid job also adds a charge to the credit records described under Prepaid credits. The file's address, or the selected area, is in the request body, which we do not store. The extension never writes the capture or the selected area to its storage: they stay in the memory of the extension and its area page. Your IP address is also used to count the free daily allowance. Your extension settings (OCR language, pages to read, how results are shown) are kept in Chrome sync storage, not on our servers. The extension has no analytics and no tracking and loads no remote code.

The use of information received from the Tanod Chrome extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We use it only to provide and secure this feature (including abuse prevention, debugging, the free-allowance count and aggregated usage statistics, as described under Server logs); never for advertising or credit decisions; and it is not sold.

Chrome extension: Tanod Markdown

The Tanod Markdown Chrome extension has two features. Clipping a page or a selection to Markdown runs entirely in your browser: the extension reads the tab you are on only when you click its toolbar button or a Clip menu item there, makes the Markdown on your device with a library bundled in the extension, and sends nothing to us or anyone else. It does not collect your browsing history.

Converting a PDF or Office file to Markdown is paid per file with a prepaid credit key, apart from one free preview a day without a key (from version 0.1.3). It sends data only when you choose a file: the address (URL) of the file you right-click and choose to convert goes to tanod.dev, which fetches that file and returns it as Markdown. If you use "Convert a file from my computer" instead, the contents of the file you pick (at most 10 MB, not its name) are uploaded to tanod.dev, which converts the file and returns it as Markdown. Links to private or local addresses are not sent, and links with common token, key or signature parameters are not sent. Without a saved credit key, version 0.1.3 and later send the same request without a key, as the free preview (tanod.dev returns only the start of the file), and your IP address is used to count it; earlier versions send nothing.

Your credit key is kept only in the extension's local storage on your device (not synced) until you remove it in the extension's options. It is sent only to tanod.dev, in a request header and never in a URL: to check your balance, and with each conversion after you confirm its price. Before asking you to confirm, the extension reads the current price from tanod.dev with a request that does not contain the file's address.

These requests are handled like any other API call: they appear in the server logs described above (kept for up to 30 days, with credential headers such as the key removed) and in the API usage records. A paid conversion also adds a charge to the credit records described under Prepaid credits. The file's address, or the uploaded file, is in the request body, which we do not store; the extension keeps a picked file only in its page's memory until it is sent. Your extension setting (whether to add a YAML header) is kept in Chrome sync storage, not on our servers. The extension has no analytics and no tracking and loads no remote code.

The use of information received from the Tanod Markdown Chrome extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We use it only to provide and secure this feature (including abuse prevention, debugging, the free-preview count and aggregated usage statistics, as described under Server logs); never for advertising or credit decisions; and it is not sold.

Chrome extension: Tanod Statements

The Tanod Statements Chrome extension converts a bank-statement PDF into a CSV, Excel, OFX, QIF or QBO file of its transactions. It sends a statement only when you confirm a conversion: the PDF you choose on your computer is uploaded to tanod.dev, or, for a link to a PDF that you right-click and choose to convert, only the address (URL) of that file is sent and tanod.dev fetches it. tanod.dev reads the transactions and returns the file. If the PDF is password protected, the extension asks for the password and sends it to tanod.dev with that one request. Neither tanod.dev nor the extension stores it. Links to private or local addresses are not sent, and links with common token, key or signature parameters are not sent. Without a saved credit key nothing is sent, except the balance check of a key you are saving in the extension's options. The extension does not read the pages you visit and does not collect your browsing history.

A bank statement holds personal financial data, such as your name, account number, balances and transactions. We do not store the PDF, its address or the converted file: they are in the request body and the response, which we do not store, and the file is returned directly, not as a stored link. The extension never writes the PDF or the converted file to its storage: they stay in the memory of its confirmation page, and the only copy that remains is the file you download. While a conversion waits for you to confirm it, the extension keeps the address of a right-clicked link (or, for a file, only a marker) and the quoted price in the browser's session storage, which is held in memory: until you pay or cancel, or, if you close the page without either, until it expires after 10 minutes and is removed the next time the extension runs, and at the latest when the browser closes.

Your credit key is kept only in the extension's local storage on your device (not synced) until you remove it in the extension's options. It is sent only to tanod.dev, in a request header and never in a URL: to check your balance, and with each conversion after you confirm its price. Before asking you to confirm, the extension reads the current price from tanod.dev with a request that contains neither the PDF nor its address.

These requests are handled like any other API call: they appear in the server logs described above (kept for up to 30 days, with credential headers such as the key removed) and in the API usage records. A paid conversion also adds a charge to the credit records described under Prepaid credits. Your extension setting (whether CSV, Excel, OFX, QIF or QBO is offered first) is kept in Chrome sync storage, not on our servers. The extension has no analytics and no tracking and loads no remote code.

The use of information received from the Tanod Statements Chrome extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We use it only to provide and secure this feature (including abuse prevention, debugging and aggregated usage statistics, as described under Server logs); never for advertising or credit decisions; and it is not sold.

Chrome extension: Tanod Logo to SVG

The Tanod Logo to SVG Chrome extension traces a logo or icon shown in a browser tab into an SVG file of vector paths. When you click its toolbar button, it captures the visible part of that tab. The capture stays in the extension's memory and is never stored or sent. You select the logo on the extension's own page, which shows the exact image that will be uploaded. Only when you confirm a trace is that selected area sent to tanod.dev, as a PNG image; tanod.dev traces it and returns the SVG. The address of the page is never sent. Without a saved credit key nothing is captured or sent, except the balance check of a key you are saving in the extension's options. The extension does not read the pages you visit and does not collect your browsing history.

We do not store the image or the SVG: they are in the request body and the response, which we do not store, and the SVG is returned directly, not as a stored link. The extension never writes the capture, the selected image or the SVG to its storage: they stay in the memory of its pages, and the only copies that remain are the files you download (the SVG and a receipt with sizes, hashes, the path count and the charge). While a trace waits for you to confirm it, the extension keeps a marker and the quoted price in the browser's session storage, which is held in memory: until you pay or cancel, or, if you close the page without either, until it expires after 10 minutes and is removed the next time the extension runs, and at the latest when the browser closes.

Your credit key is kept only in the extension's local storage on your device (not synced) until you remove it in the extension's options. It is sent only to tanod.dev, in a request header and never in a URL: to check your balance, and with each trace after you confirm its price. Before asking you to confirm, the extension reads the current price from tanod.dev with a request that contains no image.

These requests are handled like any other API call: they appear in the server logs described above (kept for up to 30 days, with credential headers such as the key removed) and in the API usage records. A paid trace also adds a charge to the credit records described under Prepaid credits. Your extension settings (colour or black and white, and the trace size) are kept in Chrome sync storage, not on our servers. The extension has no analytics and no tracking and loads no remote code.

The use of information received from the Tanod Logo to SVG Chrome extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. We use it only to provide and secure this feature (including abuse prevention, debugging and aggregated usage statistics, as described under Server logs); never for advertising or credit decisions; and it is not sold.

Other browser extensions

These extensions have their own privacy pages: Tanod JSON to TypeScript, Tanod Product Schema Check, Tanod QR Code Maker, Tanod Save Image As and Tanod Text Pair Diff.

Cookies and analytics

We do not set cookies. Cloudflare, which serves and protects the site, may set strictly necessary security cookies. We use Cloudflare Web Analytics, which does not use cookies, and Cloudflare's aggregated traffic statistics.

Who else processes data

We do not sell personal data.

Your choices

To ask what we hold about your IP address or wallet, or to have log entries deleted before the 30 days are up, email ops@tanod.dev. On-chain payment records cannot be deleted by anyone. If this policy changes, we update this page and its date.

See also our crawlers and how to opt out. Back to tanod.dev.