MergeImage Privacy Policy

01

Scope and core image processing

Selected images stay in the current browser session

When you choose files, the browser grants the page access to those selected files for the active session. The tool decodes compatible images, arranges pixels on a local canvas, creates a preview, and encodes the requested download on your device. MergeImage does not need to receive the source images to perform the core merge.

The page does not create an account, cloud gallery, or server-side project record. Closing or reloading the page clears in-memory image objects. A downloaded result is written only where your browser and operating system place downloads; MergeImage cannot inspect other files on your device.

The current product limit is 30 selected images and 20 MB per image. An output above a 12,000-pixel edge or 80 megapixels is proportionally reduced. These limits describe local product behavior and do not imply that images are transferred for enforcement.

• Source images are processed locally for the core tool.
• No MergeImage account or cloud project is created.
• Original files are not modified by reorder, remove, layout, sizing, or export actions.
• A result is saved only after you activate the browser download.

02

Site data and local preferences

Theme settings may remain on the device

The site may store a small preference such as light or dark theme in browser Web Storage. That preference is a local key-value setting and does not contain the image files or the merged output. You can remove it through browser site-data controls.

Ordinary hosting infrastructure may process technical request data needed to deliver public files, such as IP address, timestamp, requested path, user agent, and security diagnostics. The exact retention and access depend on the production host when deployment is configured. This policy should be updated with host-specific details before launch if they differ from this description.

MergeImage does not intentionally ask for a name, phone number, physical address, or payment information in the core tool. If you email [email protected], the message and sender information are handled by the email provider and used to review and reply to the request.

03

Cookies, advertising, and third parties

Conditional disclosure before advertising is enabled

No third-party advertising is active in the initial build. If third-party advertising is enabled in the future, third-party advertisers, including Google, may use cookies and web beacons to serve ads on this site. This policy and any required consent controls must be updated before that advertising goes live.

Cookies are small values a site or third party can ask a browser to store. Web beacons are small resources or signals that can record an interaction when loaded. Advertising providers may use them for delivery, measurement, frequency control, or personalization according to their policies and applicable choices.

Google publishes official explanations of advertising data and cookie technologies. Those references explain Google services; they do not mean Google advertising is currently installed on MergeImage. Users should be given clear controls and current provider details before any optional advertising technology becomes active.

04

Security, retention, and user choices

Local processing reduces transfer but not every risk

Keeping source images in the browser removes the ordinary upload path to an image-processing server, but no website can promise absolute security. A compromised device, malicious browser extension, unsafe network environment, or modified copy of the site can create risks outside this product’s control. Use a trusted device and verify the canonical mergeimage.app address.

In-memory image data normally lasts until files are removed, the workspace is cleared, or the page is closed or reloaded. Theme preference can remain until local site data is cleared. Contact email may remain according to the email provider and the operational need to understand or resolve the message.

You can choose not to select files, remove queued images, clear the workspace, disable local storage through browser controls, avoid emailing personal information, and delete downloaded outputs from your device. If a future optional service changes these choices, it requires a separate, visible explanation.

05

Changes and contact

Policy updates must follow product changes

This policy reflects the initial product verified on 2026-07-31. Material changes to image transfer, accounts, analytics, advertising, storage, or providers should be described here before or when they take effect, with an updated verification date.

Questions about this policy can be sent to [email protected]. Do not include confidential source images in the message. Provide a short description of the privacy concern and the page or feature involved.

The official MDN Web Storage documentation, W3C File API, and Google advertising and cookie policy pages are linked as technical references. They support statements about those technologies; they are not endorsements of MergeImage.

06

What MergeImage is built to do

A focused utility instead of an oversized editing suite

MergeImage starts from a common problem: several related pictures need to become one shareable file, but a full desktop editor is unnecessary. The product keeps file selection, ordering, layout, preview, and download in one page. It supports horizontal, vertical, grid, and smart screenshot stitching, plus sizing, spacing, alignment, background, and transparency.