Cookie and Device Storage Policy
This policy explains how Murelio uses cookies, browser-local storage, and similar technologies. Cookies, localStorage, and IndexedDB are different mechanisms and are described separately.
1. What cookies are
Cookies are small pieces of data that a browser can store when a website is visited. They may be used for sessions, preferences, security, measurement, advertising, and other purposes.
Cookies can have different purposes, retention periods, and owners. They are often described as first-party or third-party depending on which domain sets or reads them.
2. Current Murelio authentication cookies
Ordinary Murelio tools do not require registration or login, so Murelio currently does not operate an authentication cookie for a user-account session.
If account functionality or another cookie-dependent feature is introduced later, the actual purpose and user choices will be added to this policy.
3. localStorage and IndexedDB
Theme, language, favorites, recent tools, UI preferences, and consent state may be stored in localStorage or IndexedDB. Unlike cookies, these mechanisms are not ordinarily sent automatically with every web request.
Users can delete this data through browser site-data controls. Doing so may reset personalization such as theme, favorites, and recent tools.
4. Tool inputs
Murelio does not use ordinary tool inputs, calculated outputs, file contents, passwords, or cryptographic keys as a persistent user profile for later reuse.
A browser itself may provide form restoration, download history, or autofill depending on local browser settings.
5. Service statistics and cookies
Murelio’s own public statistics are aggregate and centered on tool ID, category, locale, device class, time bucket, and usage counts rather than a Murelio user account.
Infrastructure providers may process ordinary request metadata as part of web delivery, but Murelio does not aim to place tool inputs or outputs in an analytics cookie for behavioral tracking.
6. Advertising cookies and similar technologies
Murelio is currently undergoing Google AdSense review and monetized ad slots remain disabled. AdSense connection code and publisher-verification information may be present on pages for site connection and review, but Murelio does not enable monetized ad slots before approval. The Privacy Policy and Cookie Policy will be updated again when advertising is actually enabled after approval.
When ads are enabled, advertising providers may process cookies, local storage, IP addresses, and advertising-related signals for delivery, measurement, fraud prevention, frequency control, personalization, or non-personalized ads.
7. Regions requiring consent
Where applicable law or advertising-provider policy requires consent for advertising or non-essential storage, an appropriate consent process is presented and the user’s refusal or withdrawal is reflected in the actual behavior of those technologies.
Requirements change over time, so this policy is updated based on the active advertising configuration.
8. Browser deletion and blocking
Most browsers allow users to inspect or delete site data and cookies, or block some or all cookies. Menu names differ by browser and version.
Deleting all site data may also remove Murelio language, theme, favorites, and recent-tool preferences. Blocking all cookies can affect future features or third-party services that depend on them.
9. Private browsing
Private or incognito modes often retain site data differently and may remove it when the private session closes. Murelio preferences may therefore not persist.
Private browsing is not the same as making all network communication anonymous. Ordinary request information can still be processed by network and web-infrastructure providers.
10. Questions and changes
Send private questions about this policy to [email protected]; ordinary product questions can use public GitHub Support.
If the use of cookies or device storage changes materially, this policy and its last-updated date will be revised.