Security

OnlineToolPot serves every page over HTTPS with HSTS and a strict Content Security Policy. Most tools process input in your browser; tools that need a server say so on the page. This page explains transport security, how tool data is handled, what accounts store, and how to report a vulnerability.

Scope

This page covers the website at onlinetoolpot.com and the tools it hosts. It does not cover your device, your browser extensions or third-party sites we link to. Those have their own security. The methodology page explains how tools are built, the editorial policy covers content standards, and the About page explains who runs the site.

Transport and platform

The site is served through Cloudflare with HTTPS. Verified on 16 November 2026, responses include:

·        Strict-Transport-Security: max-age=31536000; includeSubDomains; preload, so browsers are told to use HTTPS for a year.

·        A Content Security Policy that restricts scripts, frames and connections to named sources, with object-src 'none' and frame-ancestors 'self'.

·        X-Frame-Options: SAMEORIGIN, X-Content-Type-Options: nosniff and Referrer-Policy: strict-origin-when-cross-origin.

These controls reduce common injection and clickjacking risks. They do not make the site immune to every attack, and we do not claim a security certification.

How tools process your input

Most tools run in your browser. Text you paste and files you select are processed by JavaScript on your device, and the result is produced without sending the input to our servers. This covers the calculators, converters, encoders, hash tools, text tools and most design tools.

Some tools need a server. Their pages say so:

AI image detector: uploads an image to our analysis service to produce a score. The tool page explains what is sent; the privacy policy explains what we collect and how long we keep it.

XML sitemap generator: a server-side crawler visits up to 1,000 public pages of the site you enter. Private and internal addresses are blocked, and pages behind a login are out of reach.

Text to handwriting: your text is rendered in your browser; the only external requests are for font files used by the preview and the PDF export.

If a tool page does not say how input is processed, treat the input as potentially sent to a server and do not paste secrets or confidential files. The privacy policy explains the general data rules.

Accounts

You can use the tools without an account. If you register, the site supports email and password sign-in and Google sign-in. Account data includes your name, email address and the account information described in the privacy policy. We do not ask for payment details. To request access, correction or deletion of account data, email [email protected].

Analytics, advertising and chat

The site loads Google Analytics 4, Microsoft Clarity, Google AdSense and a Tawk.to chat widget. These services may set cookies and collect usage data under their own policies. The cookie policy explains the categories, and the privacy policy explains what we collect and why. You can block cookies in your browser; some site features may then behave differently.

Reporting a vulnerability

Email [email protected] or use the contact page with the subject "Security report". Include the affected URL, the steps to reproduce, the impact you believe it has, and a way to contact you. Please do not access other users' data, run denial-of-service tests, or test against accounts you do not own. We aim to acknowledge reports within 24 hours, investigate, and tell you the outcome. We do not currently run a paid bug bounty.

If something goes wrong

If we confirm a security incident that affects user data, we investigate, contain it, and notify affected users and authorities where the law requires it. We do not publish a fixed response time for incidents because the scope and cause vary.

Limits

No website can promise absolute security. Your browser, device, network and the third-party services you use are part of the chain. Do not paste passwords, payment details, private keys, or confidential documents into any online tool, including ours, unless the tool page explicitly says the input is processed locally. If you are unsure, use the offline alternative or ask us first.