Privacy

Reqly is designed to process PDFs, images, short video and audio, and supported archives in your browser. There is no file-upload endpoint or server-side conversion service. Free tools need no account. Pro uses an account and Stripe billing; neither receives your images.

Selected files

File bytes, filenames, and metadata are used locally for the tool you choose. They are not sent to Reqly or to an external converter. Most tools keep them in memory only. Background removal offers optional local batch recovery, described below.

PDFs

PDF tools parse, rewrite and preview documents locally. Only public processing code, fonts and decoding assets are downloaded from Reqly. Selected PDFs, filenames and extracted text are not transmitted. Page checks compare text and small rendered previews; they are not a guarantee of perfect fidelity or metadata sanitization. Reset cancels workers and clears references. No PDF scripts are executed.

Video and encoded audio

These tools download a first-party FFmpeg WebAssembly engine when processing starts. Files and outputs remain in browser memory; there is no upload fallback. A dedicated worker processes one file at a time. Cancel terminates that worker and retains already completed results. Files are not stored in browser storage. Reset releases references, which is not a guarantee of secure memory erasure.

Browser-native audio tools

Audio tools decode selected recordings with your browser and create WAV files in a local worker. Samples, names, and outputs are not uploaded or stored by Reqly. Preview playback starts only when you choose it. Cancellation closes the decoder and discards pending results, but a browser may finish a native decode internally before releasing its memory.

Memory and downloads

Files and results are held temporarily in browser memory. Reset releases the references held by the tool and ends its active worker. This is not a guarantee of immediate secure memory erasure. Downloaded files stay wherever you save them. Your original file is not overwritten.

Website requests

Your browser requests pages, styles, scripts, and decoding code from the website host. The host receives ordinary connection information, including your IP address. These requests do not contain the images you select. Hosting request handling must be checked against the final deployment configuration.

Background removal

Starting background removal downloads roughly 113 MB of public model and runtime assets from Reqly. If the first result is empty, one alternate local model adds an 88 MB download. Your browser runs the model locally; it does not send the photo to a model provider. Batches process one image at a time. Completed results remain available if another image fails or the queue is paused. By default, closing or refreshing loses selected files and results. You may explicitly enable “Save this batch on this browser” to store original photos, decoded copies, cutouts, completed outputs, filenames and batch options in IndexedDB on this browser. This is off for each new batch. Wait for the saved confirmation before closing; work after the latest checkpoint may need to run again. Resume does not start processing automatically. One saved batch is kept until you uncheck that option, select Delete saved batch, or clear this site’s browser data. Clearing the current workspace leaves the saved copy available. Browser cleanup, private browsing or storage limits can remove or prevent recovery. Avoid enabling it on a shared device. Deletion removes the browser database record; it does not securely erase device storage or downloads. Refinement changes an in-memory transparency mask. The browser may cache the public model files, separately from any batch you choose to save. Background, canvas size, format, quality and adjustment choices are saved in localStorage when available, so they can be reused on this browser. Reset options restores the defaults. Browser settings can clear these preferences. These export preferences contain no photo, filename or pixel data; the optional batch recovery record is separate.

Analytics and other services

There are no advertising scripts, session replay, remote fonts or third-party file processors in this version. Optional Pro usage measurement is off by default. When enabled in Prepare images, it sends only an allow-listed event name, such as a completed workflow or reused recipe. It never sends file details, recipe names, pixels or settings. You can also explicitly send one optional feedback category after using Pro; no free-text response or files are collected. Measurements and feedback categories are stored as daily totals, not individual event histories. Reqly does not log file contents or metadata to the browser console.

Clipboard and exports

On the image color picker, an explicit paste action can supply an image from your clipboard. Reqly handles only pasted image files and does not automatically read the clipboard. A color copy button writes its displayed code to your clipboard only when you press it. Image, ZIP and CSS downloads are created locally. Reqly does not transmit their contents or record which files you selected.

Screen color picking

On supported browsers, pressing Pick from screen opens the browser’s native eyedropper. Reqly receives only the color you select, not a screen image, coordinates or recording. The color stays in page memory until reset or navigation; copying it requires your action. No screen-sharing or screen-recording fallback is used.

Pro recipes and preferences

Saving a recipe stores its name and settings in this browser’s local storage. Files, previews and outputs are not saved there. Recipes do not sync across devices. Clear local Pro preferences in Prepare images to remove saved recipes and the measurement preference; browser backups and downloaded files are unaffected.

Pro accounts and billing

Reqly stores an account identifier, your verified email when supplied, session records and subscription status in Cloudflare D1. Google sign-in requests identity and email only. Email sign-in uses Resend to deliver a one-time link; it receives your email address and the link, never a photo. Links expire after 15 minutes and are stored as hashes. Essential secure cookies keep you signed in. Stripe hosts checkout and the billing portal and handles payment details. Reqly stores Stripe customer and subscription identifiers, not card details. None of these services adds a third-party script to the free editing screen.

Optional cutout feedback

The cutout-feedback form is not connected yet and sends nothing. For help or account-data requests, email notifications.reqly@gmail.com. Send an image only if you choose to share it.

Local remover preferences

Saved presets contain your chosen name, export options, and optional filename prefix/suffix and numbering preference; no photo bytes. They stay in localStorage until deleted or cleared through browser settings. The browser also stores when optional feedback was last shown, to avoid asking again for 30 days. These values are not sent to an analytics service. Clearing browser storage resets them.

Your device

Browser extensions, operating-system features, and software outside Reqly are beyond the website’s control. Keep originals when they matter, and review your downloaded result before sharing it.

See how local processing works for the processing steps and limits.