Privacy approach

Content processed on your device

The following content may be held in temporary memory tied to the lifecycle of the browser tab and work session during processing:

• The main PDF document or the main JPG/JPEG, PNG and WebP images,
• Signature, stamp and image watermark files in PNG, JPEG or WebP format, as well as text watermarks,
• PDF, JPEG and PNG outputs created in the browser, and ZIP download packages prepared for multi-page JPEG/PNG results.

An output you download becomes a file on your device in the download location you choose and remains under your control.

Settings stored locally

A saved appearance stores only the appearance name, effect settings and regional application settings in this browser’s local storage.

Document content, the layer file, the output file, page layout, output format and output quality are not included in a saved appearance. There is no user account, processing history or cloud synchronisation.

PWA and offline storage

During offline preparation, Cache Storage may contain the application’s public HTML, JavaScript, CSS, font, icon and worker resources.

User PDFs and main images, layer images, generated outputs and saved-appearance JSON are not written to Cache Storage. The browser or operating system may delete offline application resources; in that case, a network connection may be required to prepare Muare again.

Usage analytics

Muare may use its self-hosted Umami analytics service at stats.muare.ahmettosun.tr to measure basic page visits and understand usage. Analytics runs only when explicitly enabled in the production configuration and permitted by your browser preferences.

Muare limits the pageview data sent by the browser to the site identifier, hostname and an allowed page path. Umami may produce standard aggregate information such as browser, operating system and device type. Muare does not create a client-side browser fingerprint for analytics. The Umami server may instead use site and source information, a network-derived IP address, the User-Agent and a rotating salt to derive a rotating pseudonymous technical session. This information may be processed transiently to produce an approximate country, region or city; approximate location is not a precise physical location. Muare does not add an IP field to the browser payload.

Umami analytics may also record a small, bounded set of editor usage actions, such as successfully importing a document or image, successfully exporting output, applying a built-in or saved appearance, using an adjustment group, opening the compare view, or adding a layer. These events do not include document, PDF or image bytes or content; file names or local paths; document, page or OCR text; watermark or other free text; signature or stamp image content; saved appearance names or IDs; raw slider or control values; keyboard input; mouse or touch coordinates; raw error messages or stack traces; or account or payment identifiers. This Umami flow does not include user identity, performance analytics, session replay or heatmaps.

Optional analytics can run only with your explicit permission and when the relevant feature is enabled in the configuration. When activated, Microsoft Clarity may be used only on the Turkish/English home and About pages to study usability through interaction patterns, heatmaps and session recordings reconstructed from page behavior. The editor, Privacy and Terms pages are excluded; unknown and future sensitive pages are excluded by default. An allowed preference alone does not mean recording is taking place.

Clarity may process clicks, scrolling and pointer movements, DOM/page layout and diagnostic signals, along with URLs, referrers, browser/device, screen, time zone and network/IP-derived approximate location information. Muare requires Strict content masking for Clarity; this does not eliminate collection of interaction and layout information. Clarity may use its own pseudonymous identifiers, first/third-party cookies and browser storage; these are separate from the Muare preference record below.

Muare does not supply custom user identity or custom events to Clarity, duplicate editor usage events into Clarity, or join Umami and Clarity identities. Muare does not intentionally send document/file content, file names or local paths, OCR text, watermark/free text, signature/stamp images, saved appearance identifiers or account/payment identity to Clarity. Editor exclusion relies on the absence of Clarity code in that document, not on masking.

Clarity data is processed on Microsoft Azure; Microsoft/Clarity can access it and cross-border processing may occur. Microsoft’s Privacy Statement and Clarity’s data retention policy apply; the Umami 180-day target below does not apply to Clarity. Withdrawing permission does not erase previously transmitted data; complete provider-cookie cleanup or deletion of individual records is not guaranteed.

The Umami flow does not use analytics cookies; no persistent visitor identifier is written to cookies, localStorage, sessionStorage or IndexedDB. Muare’s own loading gate respects your browser’s Do Not Track and Global Privacy Control preferences. You can use the visible control below to disable all optional analytics in this browser or allow it again at any time. Disabling persists the preference first; a page with loaded Clarity transitions to a fresh document without Clarity code and future loading is prevented.

The analytics preference is stored only in this browser under localStorage["muare:analytics-preference:v1"]; the localStorage["umami.disabled"] disable marker is also respected for safe compatibility with older versions. Allowing analytics again does not send page visits from the disabled or offline period later.

The target retention period for Umami analytics data is 180 days. This target is not a guarantee that every record is deleted automatically on exactly day 180.

Server and third parties

The current application code does not include a file-upload API, an external error-reporting integration, external file processing or a runtime translation service. Optional analytics can operate only within the Umami and conditional Microsoft Clarity boundaries described above. Application fonts and worker files are served as Muare’s own static resources.

Muare’s application code does not read or create cookies for document processing or saved appearances. Standard web requests are made to the hosting server to deliver pages and application resources; the source code does not determine the scope of the hosting infrastructure’s access logs, its IP logging behaviour, retention periods or platform-provided cookies.

Clearing browser data

Clearing browser data may delete saved appearances and offline application resources. Muare may then require offline preparation again. Outputs previously downloaded to your device may be operating-system files separate from browser data and are not necessarily deleted by this action.

User responsibility

You are responsible for managing access to your device, browser profile and download folder. Process personal or confidential documents, documents belonging to third parties and layer content only when you have the necessary rights and authorisation.