Privacy

Tools marked as local are designed to process files, text, passwords or results directly on your device, without sending that content to Rusadix Tools infrastructure.

Tools that work on your device

When a page states that content is processed on your device, Rusadix Tools does not receive or store a copy of that file, text, password or result in order to perform the task. This does not mean the website works without the internet: serving a page involves the usual technical data of a web connection. If a tool needs to send information for a specific function, that page must state it separately.

WebP fallback encoding

The “Convert image” tool first tries the browser's own image encoder. If the device can decode WebP but cannot generate it —for example, in some Safari/iOS browsers— Rusadix activates a local WebAssembly WebP encoder based on libwebp. Image pixels remain on the device. JavaScript is served from rusadixtools.com and the pinned WebAssembly binaries are delivered from the same origin through the Rusadix Worker.

C2PA provenance validation

The “View metadata” tool can validate Content Credentials (C2PA) directly in the browser. The analyzed image is not sent to Rusadix Tools or to an external provider for this check. The validator uses a local copy of the official C2PA trust list bundled with this version, disables remote-manifest fetching and does not perform OCSP requests. The JavaScript code, validation Worker and trust list are served from rusadixtools.com. The official SDK WebAssembly binary is obtained at a pinned version by the Rusadix Worker from jsDelivr and delivered to the browser from rusadixtools.com; that download does not contain the user’s file.

PDF data redaction

In the “Hide data in a PDF” tool, the document you choose is opened and rebuilt on your device. The PDF is not sent to Rusadix Tools or to an external provider. The new copy is generated from the visible representation of each page to avoid retaining original text underneath covered areas, and it does not reuse metadata, forms, comments, layers or attachments from the original PDF. PDF.js 6.4.299 and pdf-lib 1.17.1 are served from rusadixtools.com. Some PDF.js compatibility resources —such as character maps, standard fonts or decoders— may be fetched at pinned versions by the Rusadix Worker and delivered from the same origin; those requests do not contain the user’s PDF.

Optional network-exposure test

The “What my browser exposes” and “What is my IP” tools make a network check only when you press the corresponding button. The request to the Rusadix Tools Worker can show data available for that connection, such as the public IP, selected HTTP headers and, when available, provider or network organization, country, region, city and approximate coordinates supplied by the network infrastructure. The application code does not write that data to a database or add it to a user profile, and the response is sent with no-cache/no-store instructions.

Hosted counter service

Unlike local tools, counters use Cloudflare Workers and D1. On creation we store the allowed domain, label, starting number, identifier, creation date and a hash of the private recovery key. Each widget load stores an aggregate page view and daily quota counts; D1 does not store cookies, IP addresses or individual visitor identifiers. Reloads count as page views, not unique visitors.

Cloudflare receives normal technical connection data, including IP addresses, to deliver and protect the service. Creation uses Cloudflare Turnstile. When another site embeds a counter, the browser contacts counters.rusadixtools.com and sends its origin for domain verification. That site's owner must disclose the connection as applicable. The public ID displays totals and the private key allows statistics export; keep the key and export copies. The small widget credit link is nofollow and is not added to downloaded documents, images or PDFs.

Advertising and analytics

The current version does not yet load the Google AdSense script or use third-party analytics. The privacy notice can locally store your choice about optional advertising before it is enabled. You can accept or reject and reopen the preferences from the footer. Before advertising is served, this policy and the technical integration will be reviewed against the applicable current requirements.

Language preference

The language selector stores only the language preference in the browser’s local storage. That preference does not contain files or content processed by the tools.