Skip to content
Handy Tools

Privacy Policy

This Privacy Policy explains how the operator of this site ("we", "us", or "the Service") handles information about the people who use it.

Advertising

The Service uses Google AdSense, a third-party advertising service.

To serve ads, scripts provided by third parties such as Google run on the Service's pages. Statements in this policy and in each app that processing happens in your browser refer to our own servers. As described above, these ad scripts send cookies and browsing information to third-party ad vendors, but they do not send the files you process in an app.

For visitors from the European Economic Area (EEA), the United Kingdom, and Switzerland, we ask for your consent to the use of cookies and similar technologies through a Google-certified consent management platform (CMP). You can make or change your choices through the consent message shown on the site.

Analytics

To understand how the Service is used and to improve it, we use Cloudflare Web Analytics.

  • Cloudflare Web Analytics does not use cookies.
  • It collects aggregate information such as the URL of the pages you visit, the referring page, your browser and operating system type, and page load performance. We do not use it to identify individuals.
  • For details on how Cloudflare handles information, see the Cloudflare Privacy Policy.

Information Stored on Your Device

The Service stores the following information in your browser on your device. None of it is sent to us.

  • Display preferences: Your chosen theme and language are saved in your browser's localStorage. To keep them separate from other services on the same domain, the keys are prefixed with "site:".

You can clear all of this at any time by deleting the site's data in your browser settings.

Disclosure of External Transmission (Japan Telecommunications Business Act)

In accordance with Article 27-12 of Japan's Telecommunications Business Act (the external transmission rules), we disclose below the information sent from your device to outside companies when you view the Service's pages.

Recipient (company)Information sentPurposePrivacy policy / opt-out
Google AdSense (Google LLC)Identifiers such as cookies, the URL of the page you're viewing, referrer, IP address, browser and device information, date and time of access, and ad impressions and clicksServing ads, measuring ad performance, preventing invalid clicks, and showing ads based on your interestsPrivacy policy, Opt out (Ads Settings)
Cloudflare Web Analytics (Cloudflare, Inc.)URL of the page you're viewing, referrer, browser and OS type, screen size, page load performance, and date and time of accessUnderstanding and improving how the Service is usedPrivacy policy (no cookies are used, and there is no opt-out mechanism)

External transmissions specific to an app (those that happen only when you use one of its features) and other app-specific handling of information are described per app later on this page.

Personal Information

The Service has no user accounts, and you don't need to provide any personal information, such as your name or email address, to use it.

We receive inquiries through Issues on the GitHub repository where the Service's source code is published. What you write in an issue, along with your account name, is publicly visible to anyone. Please don't include personal information such as your name, email address, or postal address.

  • We use the content of issues only to respond to your inquiry and to improve the Service.
  • Issues are stored on services provided by GitHub, Inc. and handled under its Privacy Statement.
  • If an issue accidentally contains personal information, we'll edit or delete it as soon as we notice.

If you have a privacy-related request that you'd rather not make public, just write "I'd like to contact you privately" in an issue (without any personal information), and we'll tell you how to reach us individually.

Changes to This Policy

We may update this Privacy Policy to reflect changes in the law or in the Service. The updated policy takes effect when it is posted on this page. If we make significant changes, we'll note them on this page.

Contact

If you have any questions about this policy, please open an issue on GitHub (issues are public, so please don't include personal information).

Effective Date

Effective October 12, 2026

Image Converter & Compressor

How We Handle Your Images

All converting, compressing, and icon generation in Image Adjust happens inside your browser. The images you add, and the processed results, are never sent to or stored on our servers.

Loading an Image from a URL

Only when you use the "load an image from a URL" feature, the request goes through our relay server, as follows:

  • The URL you enter is sent to our relay server, which runs on Cloudflare Workers.
  • The relay server fetches the image from that URL and streams it back to your browser. The image is then processed in your browser, just like with every other feature.
  • The relay server does not store the fetched image or the URL you entered.
  • However, to operate Image Adjust and prevent abuse (for rate limiting), Cloudflare, Inc.'s systems may temporarily record access logs, including your IP address, the request URL, and your User-Agent.

Unless you use this feature, no information about your images is sent to our servers.

Information Stored on Your Device

  • The app itself: So Image Adjust can work offline, its program files (HTML, JavaScript, CSS, and so on) are stored using a Service Worker and Cache Storage.
  • Images shared from other apps: When you share an image to Image Adjust from another app, it's kept briefly in a cache on your device only until it's handed to the converter, and is deleted once the converter has received it.

External Transmission When Loading an Image URL

Recipient (company)Information sentPurposePrivacy policy / opt-out
Cloudflare (Cloudflare, Inc.), only when you load an image from a URLThe image URL you entered, IP address, User-Agent, and date and time of the requestFetching (relaying) the image from the URL you specified, operating Image Adjust, and preventing abuse (rate limiting)Privacy policy (nothing is sent unless you use this feature)

Markdown to PDF

How We Handle Your Documents

All Markdown conversion, previewing, and PDF saving in Markdown to PDF happens inside your browser. The documents you enter and the images you add are never sent to or stored on our servers. Images referenced by external URLs in your document are not loaded.

Information Stored on Your Device

  • The document you are editing and your page setup: So they survive a reload, they are kept temporarily in that tab's sessionStorage and are cleared when you close the tab. Images you add are not stored.

QR Code Generator

How We Handle URLs and Images

All QR code creation, previewing, and PNG / SVG saving in QR Code Generator happens inside your browser.

  • The URL you enter is never sent to or stored on our servers.
  • We do not access the URL you enter to fetch its contents, and we do not fetch its favicon.
  • An image you load for the center of the QR code is never sent to or stored on our servers.

Information Stored on Your Device

  • The URL, settings, icon choice, and image you are working with: So they survive a language switch, they are kept only in this tab's memory. They are not written to your device (the browser's localStorage or IndexedDB) and are not kept on our servers. They are cleared when you reload the page.
  • An image you load is used only to convert it into the PNG that is embedded in the center, and is never saved as is.

Reading and Distributing the QR Code

  • Whether a QR code can be read depends on the device, the scanning app, the printing quality, and the size it is displayed at. We do not guarantee that it will be readable.
  • The center icon and the color affect readability. Before distributing or printing a QR code for others, check that it can be read with the device and app you actually plan to use.
  • You are responsible for the contents of the QR codes you create and for where you distribute them.

Bundled Icons and Logos

  • Some of the shapes you can choose (other than no icon) are bundled from Lucide (ISC License) and Simple Icons (CC0 1.0 Universal). Nothing is fetched from the network while a QR code is being created.
  • Service names and logos are trademarks of their respective owners, and all rights belong to them. We are not affiliated with any of those companies, and none of them endorses this tool.
  • Brand logos included in Simple Icons remain trademarks of their respective owners even though they are covered by CC0 1.0 Universal. If you distribute a QR code that uses a logo, follow that company's brand guidelines.

Sound Level Meter

How We Handle Microphone Audio

Sound Level Meter uses your microphone through the browser only after you press the measure button. The audio is turned into numbers (loudness, frequency, and so on) inside your browser. It is never recorded, and never sent to or stored on our servers. Microphone use ends when the measurement finishes or you stop it.

Information Stored on Your Device

  • Measurement settings: The duration and calibration offset are kept in localStorage so they can be used next time. Measurement results are not stored (they are cleared when you close or reload the tab).

Internet Speed Test

Network Traffic in Internet Speed Test

Internet Speed Test sends and receives random test data to and from our server (Cloudflare Workers) only after you press the start button, and calculates your speed from the time it takes. Only test data is transferred. No files or information from your device are sent.

As with any connection, the server receives your IP address and similar details. The information Cloudflare attaches (the nearby data center, country, and provider name) is used only for display on the page. Test data and results are never stored or logged on the server. To stop bursts of tests in a short time, the number of tests per IP address is counted temporarily.

Information Stored on Your Device

  • Result history: The latest 10 results are kept in this device's localStorage. You can delete them with “Clear history”.