ismust.

Privacy

Last updated:

This policy explains how isMust handles tool inputs, browser preferences and information used to deliver and measure the website. No account is required to use the current tools.

Files and tool inputs

The following file tools process your selected files in your browser, using browser code and, where needed, local workers. Their processing does not upload your files to isMust servers or an external conversion API:

Calculator inputs, generated passwords, QR content and invoice details are also handled in the browser. Logos and signatures selected for invoices, QR codes or PDFs are processed locally. These tools do not submit inputs to a conversion API or store drafts on our servers. This is separate from the website and analytics requests described below.

SEO Checker and AEO Checker: server-side webpage audits

SEO Checker and the experimental AEO Checker send the URL you enter to an isMust server endpoint, which requests the public page, its robots.txt and limited sitemap resources. The target website receives those requests, including our server’s connection information and checker user agent. URL paths and query parameters are part of the requested URL; avoid URLs containing private tokens or personal information. Private network addresses are blocked.

The application does not permanently save submitted URLs, fetched pages or audit reports. They are processed temporarily and the result is shown in your browser. Custom analytics records only audit actions, severity counts, broad score buckets and confidence, not the inspected URL or page content. Hosting request information is separate, as described below; there is no application-defined retention period for provider logs. Pinned and recent-tool storage contains tool slugs, not audited URLs.

Preferences and browser storage

isMust uses localStorage on your browser/device for:

These are browser preferences, not an account or cloud-synced history. The tools do not persist file contents, passwords or invoice drafts in this storage. Background Remover also uses the browser Cache API to retain its downloaded model for reuse; that cache contains model bytes, not your photos, masks or results.

Analytics and performance

Vercel Web Analytics and Vercel Speed Insights are integrated site-wide to measure page usage and performance when enabled by the deployment. Measurements can include page URLs, referrers, browser/device details, approximate location and page-loading metrics. Vercel describes Web Analytics as cookie-free; this does not mean that every service on the site is anonymous or uses no cookies.

Google Analytics 4 loads when a measurement ID is configured. It can collect page views, interactions, browser/device information and identifiers, and use first-party cookies to distinguish visits. Blocking cookies alone may not prevent analytics requests. See Google's cookie documentation and Google's Privacy Policy.

Our custom tool events use a validated allowlist: actions such as processing, downloading or copying, plus limited settings such as mode, currency, password length/options, file/item counts or page-count ranges. These custom events exclude file bytes, filenames, signatures, passwords, dates of birth, QR payloads, invoice contents and search text. They are sent through Google Analytics when available. Automatic page analytics is separate and may include URLs and query parameters; avoid putting sensitive information in page URLs.

Hosting and external resources

Vercel delivers the website. Hosting and analytics providers receive ordinary request information, which can include IP addresses, requested URLs, timestamps and browser information, to provide and protect their services. See Vercel's Privacy Notice and Web Analytics privacy information.

Background Remover downloads a model from Hugging Face and its delivery infrastructure when a valid cached copy is unavailable. This request sends no image, uses no credentials and omits the page referrer, but the download provider still receives connection information such as your IP address. See Hugging Face's Privacy Policy. PDF rendering resources and the background-removal runtime are served from this site. Installed processing libraries run locally; using them does not itself upload your files to their authors.

Advertising

Advertising is not currently active: there is no AdSense integration or advertising network script. Ad slots are layout placeholders, visible by default in development and hidden by default in production, with a configuration override. These placeholders do not set advertising cookies or send ad requests. If advertising is introduced, this policy will need to describe the actual provider, cookies and available choices.

Retention and your choices

Tool inputs and working results are held in page memory rather than saved as drafts. Resetting, refreshing or leaving a tool can discard them. Downloads, copied text and anything you share are handled by your device, clipboard or chosen destination and are not removed by resetting a tool.

Preferences and cached model files have no app-defined expiry and may remain until you clear site data or your browser removes them. Use your browser settings to clear site storage/cache, manage or block cookies, or restrict analytics scripts. Clearing data may remove pins, history and theme settings and require the model to download again. Blocking storage may limit these conveniences. The application does not set a retention period for hosting or analytics records; provider settings and policies govern those records.

Contact page and policy updates

The Contact page currently contains a preview form. It does not submit or save messages and is not an active channel for privacy requests. We will update this policy as the service changes; the date above identifies this version. See also our Terms of use.