Privacy Policy

1. Two kinds of data, handled separately

To avoid ambiguity, this policy splits data into two categories:

• "Tool content" — files you upload to a tool (PDF, image), and text you paste into a tool (JSON, SQL, strings to parse, etc.).
• "Browsing data" — the usual network signals your browser sends when visiting any site (IP, user agent, referer, page path).

The rules for the two categories are different. Please read sections 2 and 3 accordingly.

2. Tool content (core promise)

Most tools on this site are pure-frontend. Your tool content is processed locally by your browser and never sent to any server. You can verify this in your browser's DevTools Network panel.

A small number of tools may need server-side processing (e.g. future AI features). When they do, we will clearly label them at the top of the tool page as "this tool requires a network call". Even then, the following long-term commitments apply to your tool content (independent of whether ads are ever introduced):

• Submitted content is used only to complete that single request and discarded immediately after; it is not written to a database or log body.
• It is not used to train models.
• It is not used to build user profiles, and is not linked to ads or marketing.
• It is not sold, exchanged, or proactively shared with third parties (lawful response to a legitimate authority request excepted).

3. Browsing data and server logs

Our server records standard access logs for troubleshooting and abuse prevention, and the logs roll off automatically after a short retention window.

Aside from a self-hosted anonymous traffic counter (see section 5), we do not integrate any third-party analytics panel. If we ever integrate another analytics service, we will update this page.

4. Local storage (localStorage / SessionStorage / IndexedDB)

We keep a small amount of data in your browser's storage purely to improve your experience. It is not actively sent to our servers:

• *-theme: light / dark / system theme preference.
• A tool's recent inputs, form options, or recently-used list (kept locally on your device).

Clearing your browser's site data removes everything.

5. Cookies and third-party services

Seanhan does not set cookies from its own code. We currently enable two self-hosted observability capabilities — anonymous traffic stats and error diagnostics — described below. If we later introduce third-party advertising or other tracking scripts, this page will be updated and the change announced on the home page.

In use: self-hosted anonymous traffic stats

• Hosted on our own server. No data is forwarded to any third party.
• No cookies, no localStorage, no IndexedDB — a single HTTP request is fired per pageview.
• Fields collected are limited to generic page-visit signals (page URL, referer, user agent, screen resolution, language); geolocation is derived only to country / city level, and the visitor IP itself is not persisted.
• No long-lived visitor ID; the same visitor cannot be linked across days or devices.
• Used only for aggregate traffic / referrer analysis. Never joined with the "tool content" defined in section 2.
• Only the site owner can access the analytics dashboard; data is not shared with anyone else.
• If you don't want to be counted, you can block the relevant requests with a common browser extension.

In use: self-hosted error diagnostics

• Hosted on our own server. Captures front-end runtime errors so we can locate and fix bugs. No data is forwarded to any third party.
• No cookies, no localStorage, no IndexedDB. A single request is sent only when a page you visit actually triggers an error.
• Payload is limited to information necessary for debugging (error message, stack trace, the offending page path, and your user agent), with possibly-sensitive fields scrubbed. Visitor IP is not actively sent in the payload.
• No long-lived visitor ID. Identical errors are de-duplicated server-side.
• Collected data is used only by the site owner to locate and fix bugs. It is never joined with the "tool content" defined in section 2, and never sold or exchanged.
• Only the site owner can access the diagnostics dashboard; if you don't want to participate in error reporting, you can block the relevant requests with a common browser extension.

If in the future we introduce any of the following other services, we will update this policy and announce the change prominently on the home page:

• Advertising (e.g. common programmatic ad networks);
• Other third-party analytics services.

Regardless of which is added, we will follow these principles:

• We will list each service used, the type of cookies it sets, and what it's roughly used for;
• We will distinguish "strictly necessary cookies" from "optional ads / personalization cookies", and provide a consent manager in jurisdictions where applicable law requires it;
• Browsing data shared with third parties will not be joined with the "tool content" defined in section 2;
• We will not hand the raw content you submit to a tool over to third parties.

6. PWA and Service Worker

Some sub-sites enable a Service Worker so they work offline. It caches our own scripts, styles, fonts and icons only. It does not cache the content you upload into a tool.

7. Your rights

To the extent permitted by applicable law, you may:

• Clear our site's local storage and cookies via your browser settings at any time;
• Email us via the contact link to ask whether any data about you is on file, or request its deletion (within the server log retention window).

8. Children

This site is intended for a general audience. We do not knowingly collect personal information from children under 14; any inadvertent collection will be deleted on request as required by law.

9. Contact

Questions, access requests, or deletion requests can be sent to the email link on the home page.

10. Changes

This policy may be revised when features or compliance requirements change. Material changes — such as introducing person-identifying tracking or any expansion of data use — will be announced prominently on the home page at least 7 days before taking effect. General observability or wording adjustments are reflected by updating this page and bumping the "Last updated" date.