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. Eight features keep your own content on our servers, and none 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, the photo if you added one to a photo design, and everything else in it) is stored on our servers. The Invoice, Quote and Receipt generators, the Business Card Generator and the Email Signature Generator can save documents to your account in the same way: the document you typed (your business details, your client's name and contact details, line items, amounts, notes and everything else in it) is stored on our servers, so that you can open it again, including in the Android app. The QR Code Generator, the Barcode Generator and the AI Humanizer can save to your account in the same way: a QR code design with the content it encodes (for example a web address, a contact card, a WiFi network name and password, a UPI ID or an event), a barcode design with the value it encodes, or a text you humanized together with the original and the settings you used. Your brand kit is the details you enter once so that the invoice, quote, receipt, business card and email signature tools can fill them in for you: your name, job title, pronouns, email, phone numbers, website, LinkedIn and address, your business name, tagline, address, email, phone, website, tax ID and UPI ID, your logo, your social profile links, and your brand colour and fonts. While you are signed out it stays in your browser only (and is cleared when you sign out); while you are signed in it is also kept in your account as one record, so that it follows you to another device and to the Android app, and the newer copy replaces the older one each time a tool opens. The Resume Maker's candidate kit works the same way for resume details: it keeps the details of up to 20 candidates (your own, or, if you help other people with their resumes, theirs), each with the name, job title, contact details, work history, education, projects, skills and the rest of a resume (never a photo), plus any notes you add about that candidate. While you are signed out it stays in your browser or on your phone only (and is cleared when you sign out); while you are signed in it is also kept in your account as one record, and the newer copy replaces the older one. If you save someone else's details, make sure they are happy for you to keep them. The Invoice, Quote and Receipt generators keep a client book (your customers' names, companies, addresses, emails, phone numbers and tax IDs), an item list (the products and services you bill for, with their prices) and your numbering settings; while you are signed out these stay in your browser or on your phone only, and while you are signed in they are also kept in your account as one record each, so that they follow you to another device, merged entry by entry with the newer copy of each entry kept. You can also share a saved invoice or quote as a link: the person who opens it sees that one document, can download it as a PDF, can pay it by UPI if it carries your UPI ID, and can accept a quote. The link works for 60 days unless you turn it off sooner; we keep only a scrambled form of the link (never the link itself), how many times it was opened and when it was last opened, and nothing about who opened it. Reels & Shorts in the Android app can share a reel with other ToolsMonk users you invite, if you turn that on for that one reel: the reel (its slides, captions, style and timings) and the photos, video stills, videos, voiceovers and music it uses are then stored on our servers under your account, and the people you invite can see and change them. Section 3.7 describes it. 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 every case 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), a short description, and where the request came from: the browser's user-agent string (which names the device type, operating system and browser), the approximate country and city our network edge derives from the IP address, and the number that identifies the network it arrived from. No finer location than a city is read. 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. With each page view we also record whether a signed-in session was present on that visit (yes or no, never which account), and the country the connection came from. The country is read from the network in front of the site and your IP address is not stored with it. We read the device type (mobile, tablet or desktop) from the user-agent when we produce our reports. Page views are counted per day and are not linked from one day to the next. In addition, your browser keeps a random per-browser identifier, described in Section 5.6, so we can count how many different browsers use the site without signing in. 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 and the AI features (among them the AI Humanizer, AI Image Generator, Image Upscaler, the Photo Editor's AI panels, the chat assistant, AI search and the AI help in the business and resume tools) send a random identifier with each request. Your browser creates it the first time you use one of them and keeps it in local storage under the name tm_device. It is made of random characters, says nothing about you or your device, has no expiry until you clear site data, and is used only to apply the hourly usage limits. It is not 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 eight ways to ask: saving a resume to your account, saving an invoice, quote, receipt, business card, email signature, QR code design, barcode design or humanized text to your account, keeping your brand kit in your account while signed in, keeping your resume candidate kit in your account while signed in, keeping your client book, item list and numbering settings in your account while signed in, sharing a saved invoice or quote as a link, saving a file from a tool into Secure Cloud Storage, and sharing a reel from the Android app with people you invite. All eight are listed in Section 1.1 as information you provide, all are described in Section 3, and none is any part of ordinary tool use. If you use none of them, 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 186+ 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.
• Reels & Shorts in the Android app, only if you turn on Collaborate for a reel. That reel and the photos, videos and sound it uses are then uploaded and stored on our servers under your account, where the people you invite can open and change them. Section 3.7 has the details.
• 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.
• Invoice, Quote and Receipt generators, Business Card Generator, Email Signature Generator, QR Code Generator, Barcode Generator and AI Humanizer, only if you are signed in and press Save. The document, design or text is then stored on our servers, under your account, until you delete it or your account is deleted.
• Your brand kit, only while you are signed in. The details you save in it (Section 1.1) are stored on our servers as one record under your account, until you delete it with Delete my brand kit in any of those tools, or your account is deleted.
• The Resume Maker's candidate kit, only while you are signed in. The candidates you save in it (Section 1.1) are stored on our servers as one record under your account, until you delete them in the candidate kit or your account is deleted.
• The client book, item list and numbering settings of the Invoice, Quote and Receipt generators, only while you are signed in. Each is stored on our servers as one record under your account (Section 1.1) until you delete its entries or your account is deleted.
• Share links for a saved invoice or quote, only when you create one. Anyone with the link can open that one document for 60 days or until you turn the link off; the document itself is the copy already saved in your account.

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, together with the settings you chose (such as the tone, purpose and language), any terms you asked it to keep unchanged, and any extra instruction you typed. Every rewrite calls the server first. A smaller in-browser model, which runs on your device and sends nothing, is used only if that call fails, and you can turn that automatic fallback off or choose it yourself; the tool always shows which one produced your result. ToolsMonk does not keep the text after the rewrite unless you save it to your account. 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.
• AI help in the Invoice, Quote and Receipt generators, the Business Card Generator and the Email Signature Generator, what you type into the AI box (a description of the document you want, your line-item wording, or the tone and type of business for notes and terms) is sent to Google's Gemini API. For a payment reminder the client's name, the invoice number, amount and due date are sent; for card and signature wording your name, job title, company and industry are sent. Email addresses, phone numbers, postal addresses and bank details from the document are not sent. Nothing is stored.
• Ask AI to edit, in the same five tools, sends your instruction and a copy of the open document with its private details taken out. For an invoice, quote or receipt that copy carries your business name, the client's or payer's name and company, the line items, quantities, rates, discounts, taxes, dates, document number and reference, notes, terms, footer, the signer's name and title, and the design choices; for a business card your name, job title, company, back tagline and design choices; for an email signature your name, pronouns, job title, company, department, tagline, button label, disclaimer and design choices. Before the copy leaves your browser, and again on our server before anything is sent to Google's Gemini API, every email address, phone number, postal address, tax ID, bank or UPI detail, payment link, transaction reference, website and social profile link, button link, logo, photo and signature image is replaced by a placeholder, so none of them is sent. The AI can only suggest changes, which you see and approve before any is made, and it can set one of those private fields only to a value you typed into your instruction yourself. Nothing is stored.
• Resume Maker's AI writing help: for a summary, bullets, skills, tailoring to a job, a cover letter or proofreading, the parts of your resume the action needs (your headline, summary, skills, experience with its dates and places, projects, education, certifications, languages, awards and any extra sections, and a job description you paste) are sent to Google's Gemini API. If you chose a candidate in the candidate kit and the resume is for that person, the AI is also sent that candidate's saved work history, projects, education, skills and notes, so it can write from true details the resume leaves out. Rewrite whole resume for this job sends the same and returns a new version of every section for you to review. Your name and contact details are never sent. Ask AI to edit sends your instruction and a copy of the resume with your name, email, phone, address, LinkedIn and website, your project links, the job description and your cover letter replaced by placeholders, so none of them is sent. Nothing is stored.
• Resume Maker's resume import: an old resume you choose is read in your browser or on your phone, and nothing is sent. Only if that first reading is not right and you press Read it with AI, and confirm, is the whole text of that resume, including your name and contact details, sent to Google's Gemini API so it can be sorted into the right fields. You are asked every time. Nothing is stored.
• Resume Maker's Design with AI: the look you describe, your resume's headline, summary, skills, experience, projects and education (never your name or contact details), how many entries each section has, and a sample image if you add one (shrunk on your device first) are sent to Google's Gemini API, which suggests a design. Please do not use an image that shows someone else's personal details. Nothing is stored.
• 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, the Photo Editor's AI panels and the AI tab of AppIcon, 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, to a public code CDN, or, for the speech model behind the mobile app's Video Editor captions, to Hugging Face, which hosts that model; whichever it is will see your IP address and which file was requested, and nothing else. 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. Media in reels you share from the Android app (Section 3.7) counts towards the same 100 MB. 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.

3.7 Reels you share with other people (Reels & Shorts in the Android app)

Reels you make in the Android app are kept on your phone. If you want to edit one together with someone else, you can turn on Collaborate for that one reel. It needs an account, and the app asks you to confirm before anything is uploaded. Until you do, none of this applies to that reel, and turning it on for one reel does not share any other.

• What is uploaded: the reel itself (its slides, captions, title, style choices, timings, and its music and voiceover settings, including the text of any spoken voiceover) and the media it uses: photos, stills from video slides, video clips, voiceover recordings, spoken text-to-speech audio and the music you added. A video picked from your gallery is uploaded only if it is 50 MB or smaller; if one is larger, the reel cannot be shared and the app says which video.
• Who can see it: you, and the ToolsMonk users you invite who accept. They can open the reel, change it, and add or replace media in it, and they see the names of the other people editing it; only you see their email addresses. Only you can invite people, remove them, or stop sharing. There is no public link, and the reel is not shown anywhere else.
• Invites: you invite people by email address. We keep the address you typed with the invite until it is accepted, declined or withdrawn, or the reel is deleted. We send that address one email about the invite, whether or not it has a ToolsMonk account; if it has none, the email says how to get the app and sign up with that address to accept, and the invite waits until they do. Inviting the same address to the same reel again does not send another email, and one account can cause at most 20 invite emails a day; invites beyond that are still shown in the app, without an email. You can also send the person a message about it yourself, for example on WhatsApp, from your own phone; that message goes through the app you choose, not through us. To keep addresses private, the app answers and lists invites the same way whether or not an address has an account, so it cannot be used to find out who uses ToolsMonk. Nothing is shared with the person you invite until they accept.
• While you have a shared reel open: the others in that reel can see that you have it open, which part of the editor you are on (for example Text or Audio) and which slide, so two people do not change the same thing at once. Your app sends this every few seconds while the reel is open. It is held only in our server's memory, for at most 45 seconds, and is never written to our database or logs.
• Encrypted, but not end-to-end: the media is encrypted with AES-256-GCM before it is written to our disk, the same way as files in Secure Cloud Storage, and ToolsMonk holds the key, as Section 6 explains. The reel's text and settings are stored in our database.
• How much: the media counts against your own Secure Cloud Storage allowance, the same 100 MB as the files you save, and that includes media the people you invite add, because the reel is yours. Each file can be up to 50 MB, and up to 8 people can edit a reel besides you. If a file does not fit, it is refused and the app says your storage is full; nothing else is changed. Removing media from the reel or stopping sharing gives the space back.
• How long: a shared reel is kept until you stop sharing it, delete it, or your account is deleted, and its media goes with it. Media the reel no longer uses is removed automatically after about an hour. If someone you invited leaves, is removed or deletes their account, what they added stays in the reel, because the reel is yours. If you join someone else's reel, what you add belongs to that reel and stays when you leave.
• We do not look inside: the media is not opened, analysed, or used for anything except giving it back to you and the people you invited. Its first few bytes are read to check that it is a photo, video or sound file, and a one-way fingerprint is kept to recognise a file sent twice.
• Your phone keeps its own copy, as before. Stopping sharing deletes the copy on our server only; the reel stays in My reels on your phone. If someone else changed the reel while you were also changing it, the app keeps your version as a separate draft on your phone instead of losing it.

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, invoice, quote, receipt and email-signature drafts, 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.
• tm_device, which is not a cookie but an entry in your browser's local storage: the random identifier described in Section 1.2, created only when you first use voice search or an AI feature, and used only for usage limits.
• 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, a per-tab session id, whether a signed-in session was present, and the country of the connection, without your IP address), a random per-browser identifier (Section 5.6), 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.
• Counting downloads of the desktop and Android apps also runs separately from this list, because it holds nothing that could identify you: using a download link adds one to a daily count for that platform and country, with no cookie, IP address or identifier stored. Section 5.8 describes it.

5.3 Withdrawing consent

You can change your mind at any time, and it takes one click, the same as accepting: press Privacy choices at the bottom of any page and choose Decline. Declining stops analytics straight away in the page you are on, and erases the visit counter kept in your own browser. Please accept analytics only if you are 18 or older. 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, browser count, and error reports

Three smaller measurements, all 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.
• If you accepted analytics, your browser also creates a random identifier and keeps it in local storage under tm_visitor_id. It is made of random characters and says nothing about you or your device. It is sent with each page view, and we store only a one-way keyed hash of it, together with one summary record for that browser: when it was first and last seen, how many pages it has viewed, the device type, browser and operating system read from the user-agent, the country of the connection, and whether the latest visit had a signed-in session (yes or no, never which account). We do not store which pages it viewed, your IP address or your city with it, and it is not linked to an account. It lets us count how many different browsers use the site with and without signing in. It cannot recognise you in a different browser, a private window or after you clear site data. Declining analytics, or withdrawing consent, deletes the summary record on our servers and then the identifier and the counter in your browser. A record that has not been seen for 13 months is deleted automatically.
• 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.

5.7 The desktop and mobile apps: usage statistics, only if you allow

The ToolsMonk desktop app (including its Microsoft Store version) and the Android app (including the version downloaded from this website rather than Google Play) ask you, inside the app, whether to share usage statistics. Nothing is sent unless you press Allow. Pressing Not now, or never answering, means nothing is sent, and this is the same however you installed the app. If you allow it, this is the complete list of what the app sends:

• A random installation ID, which the app creates at the moment you press Allow. It is not a hardware identifier or an advertising identifier, it is not linked to your account if you have one, and it is not the value the app uses to prevent abuse of our servers. We store only a keyed one-way hash of it.
• The platform, the app version, the version of your operating system, and how the app was installed, for example Google Play, the Microsoft Store or a download from this website.
• Whether an account is signed in on the app (yes or no, never which account). This is collected only from people who accepted the updated usage statistics prompt.
• That the app was opened, and which tools you opened, counted per day. We do not record the time of each action, and nothing you open, type or create inside a tool is sent.
• Your country, which our server works out from the connection. Your IP address is not stored.
• This goes only to ToolsMonk's own server. It is used to understand how many people use the apps, where, and which tools, and it is never sold, never used for advertising and never combined with the website analytics in Section 5.2. It is deleted after 13 months. You can turn it off at any time, in the desktop app under About ToolsMonk and in the Android app under Settings, and turning it off deletes what was collected for that installation as well as the installation ID on your device.

5.8 App download counts

When somebody uses a download link for the desktop or Android app on this website, we add one to a count for that day, that platform and the country the request came from. No cookie, IP address or identifier of any kind is kept with it, so it cannot tell us who downloaded anything, and requests from automated crawlers are not counted. These counts are deleted after 25 months. The Google Play Console and Microsoft Partner Center also show us install numbers for their store versions; Google and Microsoft compile those under their own privacy policies.

5.9 The Android app: notifications, and what it asks our server for

Four things the Android app does over the network that are not tools and not the usage statistics in Section 5.7, and one permission it asks for:

• Push notifications, only if you turn them on. The app asks once whether you want notifications about new tools and app updates, and again for Android's own permission. If you say yes, the app subscribes to a single announcement channel with Google's Firebase Cloud Messaging, which gives your installation a push token so messages can reach it. Announcements go to that channel as a whole. If you are also signed in, the app sends us that token so we can send a message to your account alone, such as a reply about your support request; we keep it with your account, together with the device type and the app's user agent, until you turn notifications off, sign out, or delete your account, and delete it sooner if Google tells us it no longer works. The website and the Windows desktop app offer the same notifications from your profile page, only while you are signed in and only after you turn them on (and, on the website, allow them in your browser); they register a token the same way and remove it the same way. You can turn notifications off in the app under Settings, on your profile page, or in Android's or your browser's settings, and turning it off with ToolsMonk's own switch unsubscribes your installation and deletes the token we hold.
• The home screen's Popular tools. Each time it opens, the app asks toolsmonk.com which tools to show there, so the list can change without a new version. The request carries no identifier and nothing about you; like any request, our server sees the connection's IP address, which is used only to limit abuse and is not stored.
• Checking for a newer version. A copy installed from Google Play asks Google Play whether an update exists, using Google Play's own update service. A copy downloaded from this website asks GitHub, where our releases are published, at most once a day. Neither check sends anything about you or your files.
• Online music in Reels & Shorts, only if you search for it. The words you search for, and any mood, genre or language you pick, are sent to Openverse (api.openverse.org), a music search service run by the WordPress Foundation; no identifier, account or file of yours goes with them. Previewing or adding a track downloads it from the site that hosts it, such as Jamendo or Freesound, which sees your IP address. Only music licensed for commercial use is offered, and the app shows the credit the licence asks for.
• The microphone, only to record a voiceover for a reel when you press Record. The recording stays on your phone and is mixed into your video there. It is uploaded only if you turn on Collaborate for that reel (Section 3.7). Spoken voiceovers use the text-to-speech engine installed on your phone. The full details are in the Android app's own privacy policy, under Settings, then Privacy Policy.

5.10 Running tools from an AI assistant (MCP access keys)

ToolsMonk offers a Model Context Protocol (MCP) server so that an AI assistant you use can find our tools, and run most of them on your behalf: business, finance and student calculators, text, developer and document utilities, three web tools (SEO Checker, Site Audit and Website Speed Test), the regex tools, the AI writing and image tools, and the lighter file tools such as merging, splitting or rotating a PDF and resizing or converting an image. Looking tools up needs nothing. Running one needs your account to be connected, in one of two ways: an MCP access key that you create yourself under My Account, or an assistant such as ChatGPT or Claude that you connect by signing in to ToolsMonk and approving it, which gives that assistant an access token of its own. This is what that involves:

• The key. We store a one-way hash of it, its name, when it was created and last used, and its daily limit. The key itself is shown to you once and is never stored, so we cannot show it to you again or to anyone else. You can revoke it at any time under My Account, and ToolsMonk staff can revoke it or suspend MCP access for an account that misuses it.
• A connected assistant. When you approve an assistant, we store the name it registered with, the address it asked to be sent back to, and a one-way hash of the access and refresh tokens we give it. It appears under My Account as a connected app, can be disconnected there at any time, and can only run tools: it cannot see your files, your saved resumes, your password or anything else in your account.
• Web tools. When your assistant runs SEO Checker, Site Audit or Website Speed Test, the web address it gives is fetched by our server exactly as when you use those tools on the website, and Website Speed Test passes the address to Google PageSpeed Insights. Only public addresses are fetched; private and internal ones are refused.
• AI tools. When your assistant runs the AI Humanizer, AI Image Generator, AI PDF Summarizer or the Resume Maker's writing help, the text or prompt it gives is sent to the same AI providers named in Section 7 that the website uses for those tools, and nothing else about you is sent with it. Each account may run each of these a few times a day, and assistants together may use only a small share of the site's daily AI capacity, so that website visitors are never turned away because of them.
• Files. The lighter file tools work on a file you attached in your assistant, or on a file your assistant gives as a public web address (at most 10 MB each). For an attached file, your assistant gives us a short-lived link to it that its own service created. Our server downloads the file from that link or address, processes it in memory once, and returns the result as a download link that works for one hour and is then deleted. Neither the file you gave nor the result is written to disk, kept in a database or included in any backup, and only public addresses are fetched. Heavier file tools, such as OCR, conversion to Word or PowerPoint, background removal and the editors, are not run this way and are answered with a link to open in your browser, where the file stays on your device.
• A record of each run. For every tool run with your key we record which account and key ran it, which tool, when, whether it succeeded and how long it took, and the name your assistant's software sends to identify itself. This lets you see your own recent runs, and lets our team see who is using which tool so the service can be kept fair and free of abuse.
• What we never record. The text, numbers or other input you or your assistant give the tool, and the result it returns, are processed only to produce that result and are not stored or logged. The one exception is a result file, which is held in memory for one hour so that the link to it works, as described above.
• How long. Run records are deleted automatically after 180 days, and all of them, together with your keys, are deleted with your account.

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 features that store content on purpose because you asked them to: the Resume Maker's Save feature and candidate kit, saved documents in the business document tools, your brand kit while you are signed in, Secure Cloud Storage, and reels you share for collaboration (Section 3.7). 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.

If a breach happens

If there is ever a personal data breach that affects you, we will tell you without delay, by email to the address on your account or by the contact details you gave us, and say what happened and when, what it is likely to mean for you, what we are doing about it, what you can do to protect yourself, and who to contact. We will also report it to the Data Protection Board of India as the Digital Personal Data Protection Rules, 2025 require, with a full report within 72 hours of finding out.

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.2, 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 1.2 after one year (365 days), and the abuse-prevention counters that make rate limiting work after 7 days. The record of each signed-in device is kept for one year after that session ends. Unfinished work saved from a tool is deleted after 180 days without use, a signup that was never confirmed 24 hours after its code expired, and a closed report about AI output one year after it was closed. The security log and session records are kept for one year because India's Digital Personal Data Protection Rules, 2025 (Rules 6 and 8) require logs of processing to be kept for at least that long; they are kept for that year even after the account they belong to is deleted, and then deleted. Usage statistics from the desktop and mobile apps, described in Section 5.7, are deleted after 13 months, and the app download counts in Section 5.8, which carry no identifier, after 25 months. Records of tools run with an MCP access key, described in Section 5.10, are deleted after 180 days. Those are running deletions, not targets. For the remainder there is no timer, so here are the rules that decide how long each is kept. Saved resumes, saved business documents, your brand kit and your candidate kit are kept until you delete them or your account is deleted, and deleting the account deletes them. Contact messages and newsletter subscriptions are kept until you ask us to remove them, or until an account with the same email address is deleted, which deletes them too. Ratings and reviews are kept while the tool they describe is listed, because they are part of its public average; deleting your account removes your name from them. Donation records are kept for as long as the law requires us to keep records of financial transactions, and are not deleted with the account. To have any of these removed sooner, email support@toolsmonk.com and we will delete it, except a donation record we are required to keep. 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 within 30 days; 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, every file stored under it, and the reels you shared with their media. 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. Cloudflare also runs Turnstile, the security check that appears only when sign-in attempts to an account or from a network start to look automated, for example after several wrong passwords. It runs in your browser (or inside the app), reads technical signals from it to tell a person from a script, and tells us only whether the check passed; we receive nothing else from it and it sets no advertising cookie.
• 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. Hugging Face also hosts the speech model the mobile app downloads once for Video Editor captions (Section 3.4); that download sends nothing about you or your video, and the captions are then made on your phone.
• PayPal and Razorpay: donation payments. Your card or bank details are entered on their systems, not ours.
• Openverse (WordPress Foundation): the online music search in the Android app's Reels & Shorts, only when you search (Section 5.9). It receives your search words; the music itself comes from the sites Openverse lists, such as Jamendo and Freesound, which see your IP address when a track is played or downloaded.
• Resend, sends transactional email such as donation thank-you notes, password resets, welcome messages and invites to edit a shared reel, 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.
• Unsplash, some of the photos on our pages, including the home page, are loaded from Unsplash's image servers, so Unsplash sees your IP address, browser and the image requested when the page loads. Nothing you type or process is sent to it.
• YouTube, Vimeo and X, a blog article can embed a video or post from one of them. The embedded player loads from that company's servers when you open the article, so it sees your IP address and browser; YouTube videos use its youtube-nocookie.com player, which sets no cookie until you press play.
• Google Firebase Cloud Messaging, delivers notifications in the Android app, the desktop app and the website if you turn them on (Section 5.9). It issues the push token for your installation; we keep that token with your account only while you are signed in with notifications on.
• 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

If you are in India, the Digital Personal Data Protection Act, 2023 gives you these rights, and toolsmonk.com/your-data-rights sets out how to use each one and what we need to know it is you:

• A summary of your personal data, what we do with it, and every company it was shared with (Section 11). With an account, Download my data on your account screen gives you this straight away
• Correction, completion, updating and erasure (Section 12)
• Grievance redressal (Section 13): we acknowledge within 3 business days and answer within 30 days, and never later than the 90 days the Rules allow
• Nominating a person to exercise these rights for you if you die or become unable to (Section 14)
• Withdrawing consent at any time, as easily as you gave it (Section 6)
• Complaining to the Data Protection Board of India if you are not satisfied with our answer to a grievance

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 Download my data on your account screen gives you a copy of everything linked to the account. Privacy choices, at the bottom of every page, changes the cookie banner answer described in Section 5.3, which 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. The same basis covers the usage statistics the desktop and mobile apps send only after you press Allow (Section 5.7), and the Android app's notifications (Section 5.9), each of which you withdraw with its switch in the app.
• Performing what you asked for, for a contact message, a newsletter subscription, an account, a saved resume, a review you submit, a file you save to Secure Cloud Storage, a reel you share with people you invite (Section 3.7), and an MCP access key together with the record of the tools run with it (Section 5.10). 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 1.2, the abuse-prevention counters that make rate limiting work, the scrubbed technical record of a tool failure, and the identifier-free app download counts in Section 5.8. 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. That basis is for visitors in the United Kingdom and the European Economic Area; Indian law has no equivalent, so see the next point.
• For visitors in India, under the Digital Personal Data Protection Act, 2023: your consent for everything in the first point; the personal data you chose to give us for the purpose you gave it, such as an account, a message or a saved file (Section 7(a)); and a legal obligation for the security log and session records, which the Digital Personal Data Protection Rules, 2025 require us to keep for one year, and for donation records. Abuse-prevention counters, tool failure records and download counts carry no name, email or IP address and are not linked to you.
• 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, PayPal, Resend, Dropbox, Vimeo, X and the WordPress Foundation (Openverse) are United States companies, Unsplash is in Canada, Razorpay is in India, 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. India's Digital Personal Data Protection Act, 2023 allows personal data to be transferred outside India except to countries the Government of India restricts by notification, and none of these companies is in such a country.

• 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, at grievance@toolsmonk.com (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 grievance@toolsmonk.com, or use our Contact page and choose Privacy or data request, or, signed in, open a support ticket in that category. Requests reach a person. We acknowledge within 3 business days and answer within 30 days. The full list of rights and how to use each one is at toolsmonk.com/your-data-rights, and a short privacy notice in English and Hindi is at toolsmonk.com/privacy-notice. 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. Creating an account requires confirming that you are 18 or older, and the cookie banner asks anyone under 18 to decline analytics. We do not track or monitor the behaviour of children or show them targeted advertising, and we run no advertising at all. Anyone under 18 can use every tool without an account. Since most tools process data entirely in the browser, the risk of collecting children's data is low. If you believe someone under 18 has given us personal information (for example through the Contact form or by creating an account), please write to grievance@toolsmonk.com and we will delete it.

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. If a change affects what personal data we collect or why, account holders are shown the new privacy notice at their next sign-in and asked to confirm it; we do not treat silence or continued use as agreement to a new purpose.

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

• Data Controller: ToolsMonk Labs LLP, the company that operates ToolsMonk and is responsible for the personal data described in this policy
• Privacy questions and grievances: grievance@toolsmonk.com
• Everything else: support@toolsmonk.com
• Contact Page: toolsmonk.com/contact
• Registered Office: 440 Mann, Narmadapuram Road, Bhopal 462026, MP, India
• Response Time: we acknowledge within 3 business days and answer within 30 days
• Grievance Officer: write to grievance@toolsmonk.com. It reaches the person responsible for data protection questions at the registered office above, who can answer questions about how we process your personal data. Under India's Digital Personal Data Protection Act, 2023 we acknowledge within 3 business days and answer within 30 days, and never later than 90 days.