Trust center
Evidence before promises.
FreNiMi Tools is operated by FreNiMi LLC in Chicago. This page explains what happens to your files and inputs, which network requests still occur, what the tools can and cannot guarantee, and how to report a concern.
Early usage
Used by more than 100 people.
This figure represents distinct early users—not sessions, ratings, reviews, or certification.
File handling
Your selected content is processed on your device
For the currently published PDF, image, text, password, hash, JSON, QR-code, and audio tools, the selected content is read and processed by code running in the browser tab. FreNiMi does not receive the file bytes, filename, document text, password, hash input, QR content, or generated output.
Working data can remain temporarily in browser memory while the page is open. Refreshing or closing the page clears that working state. Downloads are created as new files; the original file on your device is not overwritten.
Network transparency
Local processing does not mean an entirely offline webpage
The page itself must load HTML, styles, scripts, fonts, and processing libraries. FreNiMi also sends limited first-party page and interaction events to api.frenimi.com. Those events identify the tool and event type with a short-lived browsing-session identifier; they do not contain selected files, filenames, document contents, passwords, generated output, or email addresses.
FreNiMi Tools currently does not display advertising or load an advertising network. You can inspect browser developer tools while processing a non-sensitive sample file: page requests may appear, but the selected file bytes must not be included in a processing request.
Technology
Versioned processing libraries are served with the site
Depending on the tool, FreNiMi uses browser APIs and locally served copies of open-source components including pdf-lib 1.17.1, Mozilla PDF.js, qpdf WebAssembly, QR Code Generator 1.4.4, jsQR 1.4.0, heic2any 0.0.4, SheetJS 0.20.3, and the Squoosh JPEG codec. License and notice files are distributed beside those components.
Local processing reduces file-transfer and server-retention exposure. It does not protect a device that is already compromised, an unsafe browser extension, someone with access to your screen or downloads, or mistakes in the source document. Follow your employer's approved data-handling requirements for regulated or highly sensitive material.
Testing and limitations
We test the workflow and state the boundaries
Release checks cover public-page structure, internal links, metadata, content status, and shared engine behavior. Tool testing also includes representative valid and invalid input, visible result states, download naming, keyboard controls, and mobile layouts when relevant. Important limitations are published on each tool page instead of being hidden behind a generic compatibility promise.
FreNiMi Tools is not currently represented as ISO 27001, SOC 2, or independently security-certified. We will not display certification marks or audit claims unless a qualified independent process supports them.
Responsible disclosure
Report security and privacy concerns without sending sensitive files
Email info@frenimi.com with “FreNiMi Tools security report” in the subject, or use the contact page. Include the affected URL, browser, steps to reproduce, expected behavior, and a non-sensitive sample when possible. Do not send confidential documents, passwords, access tokens, personal records, or exploit data belonging to another person.
The machine-readable disclosure contact is published at /.well-known/security.txt.
Accountability
A real company and reachable contact
FreNiMi Tools is a product of FreNiMi LLC, a Chicago-based technology company. Privacy questions, correction requests, accessibility problems, and functional issues can be sent through the contact page or to info@frenimi.com.
Mailing address: FreNiMi LLC, 1655 S Blue Island Ave, Suite 4050, Chicago, IL 60608, USA.
Trust center questions
Can FreNiMi read the PDF or image I select?
Not through the current tool-processing flow. Supported content is read by code executing in your browser and is not sent to FreNiMi's API.
Does the page make any network requests?
Yes. Page assets load normally and limited first-party usage events may be sent. The privacy claim concerns your selected file and tool content, which are not included in those requests.
Are FreNiMi Tools independently certified?
No independent security certification is currently claimed for FreNiMi Tools. This page distinguishes implemented behavior from certifications the company does not hold.
What should I do with a highly sensitive company document?
Follow your organization's approved policy. Local browser processing reduces upload exposure, but it cannot make an unmanaged or compromised device safe.