Privacy Policy

1.1 Information You Provide Voluntarily

When you use ToolsMonk, you may choose to provide certain information directly to us. This includes:

• Contact form submissions: your name, email address, subject and message, which are stored in our database so we can reply.
• Donation information, if you make a voluntary donation, payment is handled by PayPal or Razorpay. Your card, UPI or bank details are entered on their systems and never reach ToolsMonk. We do store a record of the donation (your name, email, and for Razorpay your phone number, together with the amount and the processor's confirmation payload), and we pass your name and email to our email provider so a thank-you message can be sent.
• Newsletter subscription, your email address, if you choose to subscribe.
• Account details, if you create an optional account, your email address and profile details (display name, avatar, bio). Signing in with Google shares your Google email, name and profile picture with us.
• Content you deliberately save. Two features keep your own content on our servers, and neither of them happens unless you ask for it. The Resume Maker can save a resume to your account, and if you use it the resume you typed (name, job title, contact details, work history and everything else in it) is stored on our servers. Secure Cloud Storage goes further: pressing Save on a result puts that whole file into your account, so that you can open it again from another device. What goes in is entirely your choice, we never put anything there for you, and in both cases the content stays until you delete it, or until the account itself is deleted at your request, which Section 6 describes. Section 3.6 describes the file store in full, including what is kept alongside the file itself.
• Tool reviews, which are PUBLISHED PUBLICLY. Leaving a review needs an account. You choose a star rating, write a message, and confirm the display name it appears under; we never publish your email address, and if your account has no display name set we ask you to type one rather than guessing one from your address. A member of our team reads every review before it appears, so nothing is published the moment you send it, and an edit returns it for another read. Your review stays visible until you change or remove it. If your account is deleted, the name and the message are removed from it.
• Feedback and suggestions; including any information you share when reporting bugs or requesting features.

1.2 Information Collected Automatically

Some technical information reaches us simply because the site is served over the internet:

• Your IP address is seen by our hosting provider on every request. We do not store it in plain text for ordinary browsing, our abuse-prevention counters store only a one-way hash of it together with a request count and timestamp.
• Security auditing is the exception, and it applies whether or not you have an account. When a sign-in is attempted, when a write request is refused for a missing or expired security token, and when a change is made from our admin panel, we record the event type, the raw IP address, a one-way hash of the email address involved (never the address itself) and a short description. This is kept so that a break-in attempt is visible after the fact. It is readable only by our own administrators.
• If you create an account, each device you sign in from gets a session record holding your IP address, your browser's user-agent string, the country and, where our network provider can resolve one, the city that sign-in came from, and when the session was created, last used and expires. The country and city are read from the network in front of the site and are never finer than a city: no street, no coordinates and no postal code is recorded. They are stored on the session and not on your account, so they are removed when that session ends or expires rather than being kept as a running history of where you have been. You can see this list, and end any session on it, on your account's Security screen. Ending a session takes effect immediately; it is not a flag we honour later.
• If you turn on two-factor authentication, we store your authenticator secret in encrypted form and your recovery codes only as one-way hashes, so neither can be read back out of our database, by us or by anyone who obtained a copy of it. We also store the number of the last time-code you used, purely so the same code cannot be replayed within its 30-second window.
• Browser type and version, operating system and device type, and (through our analytics providers) approximate country-level location.
• Pages visited, referring URL and your browser's user-agent string, recorded with a random per-tab session identifier. This first-party analytics only runs after you accept the cookie banner.
• Which tools you open, and the search terms you type into site search, the search text is stored as you typed it. Again, only after you accept the cookie banner.
• Voice search creates a random device identifier that is kept in your browser's storage and sent with voice requests; it has no expiry until you clear site data. Several AI tools: the AI Humanizer, AI Image Generator, Image Upscaler and the Photo Editor's AI panels, additionally send a coarse device signature derived from your screen size and platform with each request. Neither is used to identify you across other websites.

1.3 Information We Do Not Collect

There are real limits on what we gather, and we would rather state them precisely than sweepingly:

• We do not require registration or an account to use any tool.
• We do not run advertising, ad networks, or cross-site advertising trackers, and we do not use fingerprinting to follow you across other websites.
• We do not sell, rent, or trade your personal data.
• We do not keep the files, images, text or documents you process with the browser-based tools, and the great majority of tools never send them anywhere at all. Where a tool does need to send your input to a server, Section 3 names the tool and says what is sent and to whom; that content is used only to produce your result and is not kept by us afterwards. Storing your content is a separate thing that you have to ask for, and today there are exactly two ways to ask: saving a resume to your account, and saving a file from a tool into Secure Cloud Storage. Both are listed in Section 1.1 as information you provide, both are described in Section 3, and neither is any part of ordinary tool use. If you use neither, nothing you open in a ToolsMonk tool is stored by us.

The limited information we collect is used exclusively for the following legitimate purposes:

• To operate, maintain, and improve the ToolsMonk platform and its 255+ tools
• To respond to your inquiries, support requests, and feedback submitted via our Contact page
• To analyze aggregate usage patterns and identify popular tools, helping us prioritize development
• To detect, prevent, and address technical issues, security threats, and potential abuse
• To send important service-related communications (e.g., major platform updates or security notices), only if you have provided your email
• To comply with legal obligations and enforce our Terms of Service

Most ToolsMonk tools do all their work inside your browser tab, nothing you load into them is transmitted anywhere. A minority cannot work that way, because they need a server, an AI model or another website to produce the result you asked for. Those tools are listed here by name. Unless stated otherwise, what is sent is used only to generate your result and is not written to any database, file or cache by us; the response is returned with caching disabled. Section 3.6 covers a separate case that is not a tool at all: files you deliberately choose to store with us.

3.1 Tools that send your content to our servers

• Image Upscaler: the image file you choose is uploaded to our server, enlarged there and sent straight back. This is the default for both the 2x and 4x settings.
• Word to PDF and PowerPoint to PDF; the document is opened in your browser, but the rendered page content (all of its text, plus its images) is then sent to our server to be printed to PDF by a headless browser. Word to PDF offers an "Offline (in-browser)" quality setting that skips this entirely; PowerPoint to PDF tries the server first and falls back to the in-browser renderer if it fails.
• HTML to Image; the URL, pasted markup or uploaded HTML file is sent to our server, which renders it and returns a screenshot. There is no in-browser alternative for this tool.
• Import from cloud → Dropbox, when you import a file from Dropbox, the file is streamed through our server on its way to your browser. The Google Drive option does not do this: those files go directly from Google to your browser.
• Resume Maker, only if you are signed in and press Save. The resume is then stored on our servers, under your account, until you delete it.

3.2 Tools that send a web address to our servers (and on to the site you named)

For these, our server makes the request instead of your browser, so the site being checked sees our server, not you. What leaves your browser is the address you typed, not a file.

• SEO Checker and Site Audit; we fetch the page you entered, and Site Audit also follows internal links to fetch a bounded number of further pages from the same site, honouring robots.txt.
• Website Speed Test, see 3.3, this one also involves Google.
• Sitemap Validator and Robots.txt Generator, when you use their "fetch" or "crawl from a live URL" features. Generating a robots.txt or reading a sitemap you paste in stays local.
• "Import from a live URL", offered by the meta tag validator, social tags, schema validator, SERP snippet preview, SEO content analyzer, keyword density checker and readability checker; the address you paste is fetched by our server so the page's text and tags can be read back into the tool.
• HTML to PDF in "From URL" mode, our server either loads the page in a headless browser or downloads its HTML and images. The "Upload HTML" and "Paste HTML" modes are fully in-browser.

3.3 Features that send your content to a third party

These features are powered by outside providers, so your input reaches that provider as well as us. Their handling of it is governed by their own terms, which we do not control.

• AI Humanizer: the text you enter is sent to Google's Gemini API to be rewritten. There is no setting that avoids this: every rewrite calls the server first, and the smaller in-browser model runs only if that call fails. Please do not paste confidential text into this tool.
• AI PDF Summarizer and the PDF Editor's AI summary / "Ask this document" - the extracted text of your document (including text recovered by in-browser OCR) and your questions are sent to Google's Gemini API. The summarizer offers an on-device mode that keeps everything local.
• Chat assistant, the messages you type are sent to Google's Gemini API.
• PDF Forms and the PDF Editor's "Design a form with AI" panel, the description you type of the form you want is sent to Google's Gemini API, which drafts the sections and fields. Your PDF itself is not sent.
• AI Image Generator, and the Photo Editor's AI panels, your text prompt is sent to Google's Gemini API and, if that is unavailable, to Hugging Face or Pollinations.
• Photo Editor Smart Crop, a downscaled copy of the image on the canvas is sent to Google's Gemini API to find the best crop. If it is unavailable, an on-device model is used instead.
• Voice search, up to ten seconds of recorded audio is sent to our server and forwarded to Google's Gemini API for transcription. Only the transcript comes back. Note also that your browser's own built-in speech recognition, used first where available, may itself transmit audio to your browser vendor.
• Website Speed Test, and the Core Web Vitals panel of the SEO Checker, the address you entered is sent to Google's PageSpeed Insights API, which loads the page itself. Any query string is removed before we forward it.
• Social Tags, the links to Facebook's Sharing Debugger and LinkedIn's Post Inspector send your URL to those companies only if you click them.

3.4 Downloading a model is not the same as uploading your file

Several tools; the Background Remover, OCR, Magic Erase in the Photo Editor, PDF to Excel table detection, and the Video Editor's captions, voiceover and translation, download an AI model or a code library to your device the first time you use them, then run it locally. Your file never leaves the browser in these cases, but the download itself is a request to our servers or to a public code CDN, which will see your IP address. The same is true of the fonts and libraries many other tools fetch on demand.

3.5 If a tool is not listed here

Then, to the best of our knowledge, it does not send your input anywhere. If you find a tool that behaves differently from this section, please tell us at support@toolsmonk.com and we will correct it.

3.6 Files you choose to store with us (Secure Cloud Storage)

Everything above is about content passing through a server on its way to a result. Secure Cloud Storage is the opposite case, and it belongs in this section for honesty rather than because a tool needs it: nothing is being processed, you are asking us to keep a file so that you can open it again somewhere else. It requires an account, and nothing goes into it unless you press Save on a result you have just made. That press is the moment you are asking us to keep something, and it is the only moment: there is no setting that has to be found first, and none that can quietly put a file there on your behalf. If you never press Save, your store is empty, none of this applies to you, and nothing about your use of ToolsMonk changes.

• What is stored: the file exactly as you uploaded it, its name, its size, its file type, a one-way fingerprint of its contents, which tool you saved it from, and when it was created and last changed. We never place a file there for you; every file in your store is one you chose to save.
• Work you have not finished, but only if you ask for it. A few tools can keep an unfinished draft in your account instead of in this browser, and each of them has a switch that is OFF until you turn it on. What is kept is the document you are working on, for example the lines of an invoice or the notes you have placed on a PDF, together with a link to the file in your store when the work was done against one. The original file itself is never copied into it. It is capped at a quarter of a megabyte per tool, we delete it when you turn the switch off and clear it, and it is removed with your account.
• One place at a time, deliberately. While that switch is on, the copy this browser used to keep is stopped, so there are never two versions of one draft quietly disagreeing about which is newer. Turn it off, or sign out, and the browser copy takes over again.
• How much: each account gets 100 MB in total, with a ceiling of 50 MB on any single file and a limit of 200 files. These are the same figures the server enforces. There is also a limit on how much the service holds in total, so on a rare occasion a save can be refused because the service itself is full rather than because your own allowance is; the message says which.
• Encrypted, but not end-to-end. The bytes are encrypted with AES-256-GCM before anything is written to our disk. Please read the rest of this sentence, because it is the part most services leave unsaid: ToolsMonk holds the encryption key, so we can technically read a file you have stored. The encryption protects your files if a disk, a server snapshot or a backup copy ends up somewhere it should not; it does not, and we will not imply that it does, put them beyond our own reach. Section 6 explains why the key is ours rather than yours.
• Nothing stored is shared or public. There is no sharing feature, no public link, and no way for another person to be given access to a file in your store: it can be read back only by your own signed-in account. That is deliberate, because a sharing feature is an entire class of accidental disclosure that cannot happen if the feature does not exist.
• We do not look inside. Stored files are not opened, read, searched or analysed by a person, and their contents are not used for analytics, for advertising, or to train or evaluate any model. Two automated things happen to an upload and nothing else: the first few bytes are read to work out what type of file it is, so that a type we cannot support is refused at the door rather than stored and broken; and a one-way fingerprint of the file is calculated and kept, so that saving the same file twice can be recognised. A fingerprint cannot be turned back into the file it came from.
• You control every file, without asking us. Rename or delete any of them yourself at any time from Secure Cloud Storage on your account (toolsmonk.com/account/storage), and deleting removes the stored bytes as well as the record of the file. The same screen carries an Export all button, which packages every file you have stored into one ZIP and downloads it to your device, so taking a complete copy away with you is a single press that involves no request to us and no wait. If you want the account itself removed, Section 6 sets out how to ask for that and exactly what it destroys.
• There is no off switch, because there is nothing running that would need one. Secure Cloud Storage is available to every signed-in account and holds nothing at all until you save something into it, so an account that has never used it has an empty store rather than a switched-off one. What removes what is already there is deleting a file, or asking for the account to be deleted; both are deliberate acts, the first is described just above and the second in Section 6, and neither can be undone.
• It is convenience storage, not a backup service. We keep one copy, in one place. There is no second copy to restore from, deleted files are not archived, and nothing here is replicated to another provider, so Secure Cloud Storage must never be the only copy of anything you cannot afford to lose. Section 6.2 of our Terms of Service says the same thing in the language of a term rather than a promise.

A lot of what ToolsMonk remembers is kept in your own browser and is never transmitted to us. It is still your data, so you should know it is there, and that clearing your browser's site data for toolsmonk.com removes all of it.

• Preferences, your favorite tools, recently used tools, preferred display currency, your cookie-banner choice, and dismissal of the install prompt.
• Tool history and drafts, saved results and history for calculators and medical tools, invoice, quote, receipt and email-signature drafts, recent unit and currency conversions, student tool state, quiz banks, audited URLs in the SEO tools, and any signatures you draw or type for the PDF signing tools.
• Autosaved work, the Image Editor, PDF Editor and Video Editor automatically keep your open project in the browser's local database so you do not lose it on refresh. For the PDF Editor this includes the original PDF file and, if you entered one, its password. Each of these editors lets you turn autosave off.
• Offline caches, the site installs a service worker that caches pages, app assets and downloaded AI models so tools keep working offline. This happens on every visit and is not tied to the cookie banner.
• A per-tab session identifier and a persistent voice-search device identifier, described in Section 1.2.

Everything in this section lives on the device you are using, which is also its limitation: it does not travel with you to another computer, another browser or a private window, and clearing your site data removes all of it at once. Secure Cloud Storage, described in Section 3.6, is the deliberate opposite of that arrangement, and the difference is worth stating rather than leaving for you to infer. A file you save there is held on our servers instead of on your device, which is exactly what lets it survive a cleared cache and open on a second device, and it is therefore governed by Section 6 and by the retention rule set out there rather than by this section. Nothing crosses from this section into that one on its own: work stays on your device until you choose to save it, and having an account does not upload anything by itself.

5.1 Cookies set without consent

A small number of cookies are strictly necessary and are set regardless of your analytics choice:

• csrf_token: a short-lived, HttpOnly security cookie (one hour) created before actions such as submitting the contact form, so that requests cannot be forged.
• Sign-in session cookies, set by our authentication provider only once you have created an account and signed in. Anonymous visitors never receive them.
• tm_cookie_consent, records the choice you made on the cookie banner, so you are not asked again. It lasts 180 days and is also mirrored in your browser's local storage.
• ToolsMonk does not set a theme cookie, and none of the analytics WE load: Google Analytics, Microsoft Clarity or our own measurement, is contacted before you accept.

5.2 Analytics: off until you accept

Nothing analytics-related runs until you press "Accept Analytics" on the banner. Declining, closing the banner, or simply ignoring it all have the same effect: no analytics loads. If you accept, these are what start:

• Google Analytics 4, page and event measurement.
• Microsoft Clarity, a session-replay and heatmap product. It records interactions with the page, so it is capable of observing what is displayed in a tool's interface. Its masking configuration is managed in Microsoft's console.
• Our own first-party measurement, page views (path, referrer, user-agent and a per-tab session id), which tools you open, and the search terms you type.
• Our own real-time monitoring, described in Section 5.5, which shows the site operator who is browsing at this moment. It records how you move through the site during your visit: the pages you open and in what order, how long you actively spend on each, how far down you scroll, and which buttons and links you click. It never records what you type into a field and never sees the contents of a file you are working on.
• Our own error reporting runs separately from this list: when a tool fails, a scrubbed technical description of the failure is recorded whether or not you accept, so that the fault can be found and fixed. What your choice changes is whether that record carries a grouping key, which is what lets us tell one browser failing forty times from forty browsers failing once. Declining means the failure is still recorded and simply cannot be connected to your other failures. Section 5.6 sets out exactly what is kept in both cases.

5.3 Withdrawing consent

We want to be straightforward about a current shortcoming: there is no button on the site today that lets you change your mind after you have accepted. Until we add one, you can withdraw consent by clearing site data for toolsmonk.com in your browser settings, this removes both the tm_cookie_consent cookie and the matching local-storage entry, after which the banner will appear again and analytics will stay off until you accept. You can also email support@toolsmonk.com and we will help. Please also note that ToolsMonk does not currently act on browser "Do Not Track" or Global Privacy Control signals, and that the banner is not shown inside embedded tool widgets (/embed/…), so we recommend making your choice on the main site.

5.4 Advertising

ToolsMonk carries no advertising. There are no ad networks, ad cookies, ad pixels, or audience-targeting scripts anywhere on the platform, and we do not share your data for advertising purposes.

5.5 Real-time visitor monitoring

We operate a first-party real-time view that shows the site operator who is on ToolsMonk at this moment, so that a broken tool or an outage is noticed while it is happening rather than days later. It is comparable to the real-time screen in a product like Google Analytics, but it is ours, it runs on our own server, and no third party receives any of it. Here is exactly what it involves:

• Your IP address is PROCESSED but never stored. It is held in the server's memory for the length of your visit and is discarded within 30 minutes of your last activity. It is not written to our database, not written to any log file, and not sent anywhere.
• Your approximate location, at country and city level, is read from the network headers that Cloudflare adds at the edge. No third-party location service is queried, so your IP address is never sent to an outside lookup provider. We do not receive or store a precise location.
• Your device type, browser and operating system, read from the user-agent your browser already sends with every request.
• Which pages you open and in what order, how long each page is actively visible, how far down each page you scroll, and which buttons and links you click. Clicks are recorded by the label of the control, for example "Merge PDFs" or "Download result".
• We deliberately do NOT record what you type. Form fields are identified only by their name, never by their value, and the recorder never reads the contents of a document, image or other file you are working on. A file you process with a ToolsMonk tool still never leaves your browser.
• A basic automated-traffic check, so that crawlers and monitoring scripts can be told apart from people.
• The whole record is deleted 30 minutes after your last activity, and a routine server restart clears it immediately. There is no long-term visitor profile, and nothing here can be linked to a later visit.

5.6 New or returning, and error reports

Two smaller measurements, both described here for completeness:

• Whether you are new or returning is counted INSIDE YOUR OWN BROWSER. If you accepted analytics, a small counter is kept in your browser's local storage under tm_visitor, and only the answer ("new" or "returning", plus how many visits) is sent to us. No identifier for you is created or stored on our servers, so we cannot recognise you across devices or browsers, and we cannot link your visits to each other. Declining analytics, or withdrawing consent, deletes that counter.
• When a tool fails, we record a technical description of the failure so it can be fixed: the error message, the code path it came from, and coarse facts about the conditions it happened in. That text is scrubbed before it is stored: filenames are replaced with just their file type (for example "invoice.pdf" becomes "[file].pdf"), and email addresses and long digit sequences are removed. The contents of your file are never included.
• The coarse facts recorded alongside a failure are these: whether you were on a mobile, a tablet or a desktop; your operating system and browser, with their version where the browser reveals it; how fast your connection was at that moment and whether it was wifi or mobile data, as your browser reports it; the network operator your connection came from, worked out from the network number our security provider already sees, never from a lookup of your address; and your country. We do not record your IP address, your city, your screen size, or anything measured from your device's graphics, fonts or audio. This is the same short list for every tool.
• If you accepted analytics, a failure also carries a grouping key so we can tell one browser failing forty times from forty browsers failing once, which are different problems with different fixes. It is a one-way keyed hash of the random first-party identifier your browser already holds for abuse prevention: it cannot be turned back into that identifier, it is not linked to any account, and it exists only inside our failure records. If you did not accept analytics, no grouping key is sent at all and your failures are recorded without any way to connect them to each other.

We take the security of your information seriously and implement appropriate technical and organizational measures to protect it:

• All data transmitted between your browser and ToolsMonk is encrypted using HTTPS/TLS protocols
• Our servers are hosted on secure, reputable cloud infrastructure with regular security updates and patches
• Access to any stored data is restricted to authorized personnel on a need-to-know basis
• We conduct regular security assessments and vulnerability scans
• For the server-assisted tools in Section 3, we hold your content only in memory for the length of the request: we do not write it to disk, to a cache or to a database, and the result is returned with caching disabled. Our error logs record the failure, not your content. The exceptions are the two features that store content on purpose because you asked them to: the Resume Maker's Save feature and Secure Cloud Storage. Where a feature forwards your content to a third-party provider, that provider's own handling is governed by its terms.
• Files held in Secure Cloud Storage are encrypted at rest with AES-256-GCM before anything reaches the disk, and each part of a file is sealed separately and bound to its position, so a copy that has been truncated, reordered or tampered with fails to open rather than opening as a plausible but wrong file. Now the exact limitation, stated plainly, because a vague security claim is worse than none at all: TOOLSMONK HOLDS THE KEY. This is not end-to-end encryption, and we can technically read a file you have stored. What it does protect you against is a stolen disk, a leaked server snapshot, or a backup copy that goes astray, in each of which somebody has your bytes and not our key.
• We chose that trade deliberately rather than arriving at it by omission. A key that only you held could not survive a password reset, and an account created with Google sign-in has no password to derive one from, so the first forgotten passphrase would destroy your files for good and every reset would do the same. Secure Cloud Storage exists so that you can sign in on a second device and carry on working, and a scheme that fails at exactly that moment would defeat the feature it was meant to protect.
• Requests to the tools that fetch a web address on your behalf are checked to prevent them being pointed at private or internal network addresses

While we strive to protect your personal information, please be aware that no method of internet transmission or electronic storage is 100% secure. We cannot guarantee absolute security but are committed to maintaining industry-standard protections.

Protecting your account

If you choose to create an account, these controls exist for it. Most of them are things you can act on yourself, from the Security screen once you are signed in:

• Your sign-in session is an opaque random token. What we store is only a one-way hash of it, so a copy of our database cannot be turned back into a working sign-in for you or for anyone else.
• Because the session is a record on our side rather than a self-contained token, ending it actually ends it. Signing out of a device stops that device working immediately, instead of waiting for a token to expire.
• You can see every device signed in to your account, with the IP address and browser each one used and when it was last active, and sign any of them out. There is also a single action to sign out every device except the one you are using.
• Two-factor authentication using any standard authenticator app is available and can be enabled at any time. Turning it off again requires your password, so someone who finds your screen unlocked cannot quietly remove it.
• Repeated failed sign-ins for the same address are temporarily blocked, which is what stops a password from being guessed by brute force. The block is counted against a one-way hash of the address, not the address itself.
• Changing your password signs out every device, including the one you changed it on.
• Our administrators' access to the panel is separated by role, so an account with a limited role cannot reach user records, settings or security screens at all.

If you ever believe your account has been accessed by someone else, sign out all other devices from the Security screen and then change your password, in that order, and email support@toolsmonk.com so we can check the audit record for you.

How long we keep things

Several of the records described in Section 1 are deleted automatically, on a schedule the database enforces rather than a promise we remember to keep. Analytics rows, which means the page views and tool-usage rows in Section 5.3, are dropped after 13 months. The search terms you type are deleted after 180 days. Technical failure records are deleted after 30 days, the security log described in Section 5.4 after 90 days, and the abuse-prevention counters that make rate limiting work after 7 days. Those are running deletions, not targets. For the remainder, which is contact messages, newsletter subscriptions, ratings and feedback, donation records and saved resumes, we have not fixed a published period, and rather than quote a number we cannot stand behind we would ask you to email support@toolsmonk.com if you want something removed; we will delete it. Content sent to the server-assisted tools in Section 3 is still not retained by us beyond the request.

• Files stored with Secure Cloud Storage are the one place where we can give you a precise rule instead of asking you to write to us, so here it is. They are kept until you delete them, or until the account itself is deleted, and nothing expires them on a timer or clears them out after a period of inactivity. There is no request to send and nobody has to approve it: every stored file can be removed by you, on your own, from Secure Cloud Storage on your account (toolsmonk.com/account/storage), and the stored bytes go with the record rather than lingering behind it.
• Closing your account deletes the files stored under it along with the rest of the account, and closing it is a request rather than a button you press. You file it from toolsmonk.com/account/delete, you confirm on that page that you understand what will be removed, and a member of our team then carries the deletion out; you can withdraw the request at any time until they do. It works that way for two reasons we would rather state than have you guess at: the deletion cannot be reversed, and somebody who had got into your account should not be able to destroy your documents with it before you noticed. What the deletion removes is the account, the records described in Section 1 that belong to it, and every file stored under it. Because Secure Cloud Storage is convenience storage rather than a backup service, there is no archived or replicated copy anywhere for us to recover from afterwards, so use Export all on your storage page to download everything before you ask. Section 8 of our Terms of Service sets out what happens if we end an account, and how long you have to retrieve your files in that case.

These are the outside companies involved in running ToolsMonk. Some are unavoidable because they are the infrastructure the site runs on; the rest are only involved when you use a specific feature. Account and application data is stored in our own PostgreSQL database on the same VPS rather than with a separate database or sign-in provider. Files you save with Secure Cloud Storage live on that same server's own disk, encrypted as described in Section 6, and are not handed to an outside storage company: no third party in the list below stores them or can read them at rest. Cloudflare, the first entry below, carries the traffic and so handles the file in transit as it does every other request to this site; nothing else in that list touches it at all. If that ever changes, this is the section where it will be named.

• Cloudflare: the CDN, DNS and security network in front of the site. Every request passes through Cloudflare's edge, so it necessarily sees your IP address, browser and the page you requested. The site itself is served from our own server behind Cloudflare.
• Google: Gemini for the AI features and voice-search transcription, PageSpeed Insights for the Speed Test and Core Web Vitals, Google Analytics if you accept analytics, Google Sign-In if you choose it, and the Google Drive picker if you import a file from Drive (see Section 3).
• Microsoft: Clarity session replay, only after you accept analytics.
• Hugging Face and Pollinations: fallback providers for AI image generation when Google is unavailable. Only your text prompt is sent.
• PayPal and Razorpay: donation payments. Your card or bank details are entered on their systems, not ours.
• Resend, sends transactional email such as donation thank-you notes, password resets and welcome messages, so it receives the recipient's email address.
• Amazon Web Services (Simple Email Service), receives the email you send US. Mail addressed to our support address is delivered to Amazon's servers in the Tokyo region before it reaches us, so a message you send to exercise the rights in Section 8, including its contents and your own address, is handled there first.
• Dropbox, the Dropbox file picker, if you use it.
• Public code and font CDNs (cdnjs, jsDelivr, esm.sh), they deliver libraries, fonts and AI runtimes to your browser on demand and will see your IP address and which file was requested. Nothing you process is sent to them. One of these, cdnjs, is contacted by the offline service worker on your first visit, before the cookie banner is answered.
• Websites you ask us to analyse, the SEO and site-audit tools cause our server to request the address you supplied. Those sites see our server, not you.

We are not responsible for the privacy practices of these services, and we cannot tell you how long each of them keeps what it receives. We encourage you to review their own privacy policies, in particular Google's terms for the AI features if you plan to use them with confidential material.

Depending on your location and applicable data protection laws (including GDPR, CCPA, and other regional regulations), you may have the following rights:

• Right of Access, request a copy of any personal data we hold about you
• Right to Rectification, request correction of inaccurate or incomplete personal data
• Right to Erasure, request deletion of your personal data ("right to be forgotten")
• Right to Restrict Processing, request that we limit how we use your data
• Right to Data Portability, request your data in a structured, machine-readable format
• Right to Object, object to processing of your data for certain purposes
• Right to Withdraw Consent, where processing is based on consent, you may withdraw it at any time

Several of these you can now act on yourself, and it is worth naming the control that serves each one rather than leaving you to hunt for it. If you have an account, the Security screen lists every device signed in to it and lets you end any of those sessions immediately, and the cookie banner choice described in Section 5.3 governs whether any analytics runs at all. The right to data portability over your stored files is Export all, on Secure Cloud Storage in your account (toolsmonk.com/account/storage): it packages every file you have stored into one ZIP and downloads it to your device, in the same formats you saved them in, with nothing to request and nobody to wait for. The right of erasure works at two levels from there. Deleting a single file on that same screen removes the stored bytes as well as the record of it, immediately and without asking us. Erasing the whole account is a request you file at toolsmonk.com/account/delete, which a member of our team carries out: it deletes the account together with every file stored under it, and you can withdraw it at any time until it is done. Everything else on the list above still goes through the address below.

8.1 Why we are allowed to hold it

Data protection law asks us to say not just what we collect but on what legal footing. For most of ToolsMonk the answer is that we hold nothing: a tool you use without an account leaves no record tied to you. Where we do hold something, this is the basis:

• Your consent, for analytics, session replay and the real-time view described in Section 5. Nothing in that list runs until you accept the banner, and you can withdraw at any time by declining it, which also erases the visit counter held in your own browser.
• Performing what you asked for, for a contact message, a newsletter subscription, an account, a saved resume, a review you submit and a file you save to Secure Cloud Storage. Each of those exists because you asked us to keep it, and deleting it is a request away.
• Our legitimate interests, for the security log in Section 5.4, the abuse-prevention counters that make rate limiting work, and the scrubbed technical record of a tool failure. These keep the site standing up and keep it free; they are the minimum that does that job, and Section 6 sets out how long each is kept.
• A legal obligation, for the record of a donation, which is a financial transaction we may be required to be able to account for.

8.2 Where your data goes, and how to complain

ToolsMonk is operated from India and the companies in Section 7 are not all in one place: Google, Microsoft, Hugging Face, Pollinations and PayPal are United States companies, Amazon receives our inbound email in Japan, and Cloudflare carries the traffic through whichever of its data centres is nearest to you. So if you are in the United Kingdom or the European Economic Area, personal data reaching those companies leaves that area. We rely on the transfer terms in each provider's own data processing agreement, which for these providers means the Standard Contractual Clauses or the EU-US Data Privacy Framework. We do not send your data to any company that is not named in Section 7, and if that changes Section 7 is where it will be named.

• If you are in the United Kingdom or the European Economic Area, you have the right to complain to your national supervisory authority. In the UK that is the Information Commissioner's Office (ico.org.uk); elsewhere it is the authority for the country you live in.
• If you are in India, you may raise a grievance with us first (Section 11) and then, if you are not satisfied, with the Data Protection Board of India under the Digital Personal Data Protection Act, 2023.
• If you are in California, you may exercise the rights above without being charged a different price or given a worse service. We do not sell or share personal information as those terms are defined there.

To exercise any of these rights, please email support@toolsmonk.com or use our Contact page. It is the only monitored address we have, and requests sent to it reach a person. We will respond within 30 days. Please note that most of what ToolsMonk holds is not linked to a name, analytics rows carry a random per-tab identifier and abuse counters carry a one-way hash, so it helps if you can tell us roughly when and what you are asking about.

ToolsMonk is not directed at children. India's Digital Personal Data Protection Act, 2023 treats anyone under 18 as a child, and the UK GDPR sets its own threshold at 13 to 16 depending on the country, so rather than pick the most convenient of those we do not knowingly collect personal information from anyone under 18 and we do not knowingly create an account for them. Since ToolsMonk does not require registration and most tools process data entirely in the browser, the risk of inadvertently collecting children's data is low. If you believe a child under 13 has provided us with personal information (e.g., through the Contact form), please contact us immediately, and we will take steps to delete such information.

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. When we make material changes, we will update the "Last Updated" date at the top of this page. We encourage you to review this Privacy Policy periodically. Continued use of ToolsMonk after changes constitutes acceptance of the updated policy.

If you have any questions, concerns, or requests regarding this Privacy Policy or our data practices, please reach out to us:

• Email: support@toolsmonk.com
• Contact Page: toolsmonk.com/contact
• Registered Office: Block C, Sector 142, Noida, Uttar Pradesh 201304, India
• Response Time: Within 3-5 business days
• Grievance Officer: write to support@toolsmonk.com with Grievance in the subject line and it will reach the person responsible for data protection questions at the registered office above. Under India's Digital Personal Data Protection Act, 2023 we will acknowledge within 3 business days and answer within 30 days.