Privacy Policy
Effective 2026-08-19. Operator HRuin follows a data-minimization approach: ordinary Murelio tools do not require an account, and tool inputs and files are not stored as user-account records.
1. Scope
This Privacy Policy applies to the Murelio website, the tools provided through it, aggregate usage statistics, and support channels operated by Murelio.
Third-party websites and account areas such as GitHub and Google are governed by their own privacy policies and terms. Linking to a third-party service does not mean Murelio controls all processing performed by that provider.
2. Data-minimization principles
Ordinary tool use does not require registration or sign-in and does not require a name, phone number, postal address, or user profile. Murelio does not operate a system that combines tool inputs with a user account for long-term storage.
Information is handled only to the extent needed for service operation. Aggregate statistics are kept separate from the contents users enter into tools.
3. Tool inputs and files
Calculator values, dates of birth, text, code, passwords, cryptographic keys, colors, images, PDFs, ZIP files, audio, video, filenames, and generated outputs are designed to be processed on the user’s browser or device whenever practical.
Murelio does not store these tool inputs and outputs as per-user server records for ordinary tool operation. Results downloaded by a user remain subject to the storage behavior and settings of that user’s device and browser.
4. Information stored on the device
Language, theme, favorites, recently used tools, selected UI preferences, and consent state may be stored using browser-local storage so those preferences remain available on the same browser.
Users can clear this information through browser site-data controls. Private browsing or clearing site data may prevent these preferences from persisting.
5. Anonymous and aggregate usage statistics
For service improvement and public statistics, Murelio may aggregate tool ID, category, locale, device class, time bucket, and visit or execution counts.
The statistics store is not designed to contain tool inputs, calculated outputs, file contents, passwords, cryptographic keys, user account IDs, email addresses, phone numbers, or precise location. The purpose is to understand aggregate tool usage rather than reconstruct an identified person’s history.
6. Network and security logs
Like other web services, requests may cause ordinary network metadata such as request time, IP address, browser or device information, requested path, and security events to be processed temporarily by hosting and security providers.
Such processing may support content delivery, troubleshooting, abuse prevention, and security. It is separate from the Murelio public statistics database, which is not designed to store precise IP addresses as persistent user identifiers.
7. Information handled through support
When an ordinary inquiry is submitted through GitHub Issues, the user’s public GitHub account information and the content posted may be publicly visible. Personal or sensitive information should not be placed in a public issue and should instead be sent to [email protected].
An email inquiry can contain the sender’s email address, display name, message, attachments, and sending time. This information is processed to answer the inquiry and provide appropriate follow-up.
8. Purpose and retention of support information
Support information is used to answer questions, investigate bugs, handle rights requests, investigate security issues, improve the service, and identify duplicate inquiries where relevant.
Support records may be retained for the period reasonably needed to handle the matter and follow up. They are removed or cleaned up when no longer needed, except where a legal obligation, dispute, or security-investigation need justifies longer retention.
9. Cookies and similar technologies
Murelio currently does not need an authentication cookie for a user-account session because ordinary tools do not require accounts. Browser-local storage technologies such as localStorage or IndexedDB may be used for preferences and are distinct from cookies.
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. See the Cookie Policy for more detail about browser storage and user choices.
10. Advertising
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.
If ads are enabled, third-party advertising providers may process information for delivery, frequency management, fraud prevention, measurement, personalization, or non-personalized advertising. Murelio is not designed to send tool inputs, file contents, passwords, or cryptographic keys to advertising providers for targeting.
11. Third parties and external services
Murelio does not sell ordinary tool inputs or outputs to advertisers. External service providers may nevertheless process information within their own role when they provide delivery, security, support, or advertising services.
GitHub is used for public support, Gmail is used for private support email, and Cloudflare may be involved in network delivery and security. Google AdSense-related processing may be added if advertising is enabled.
12. International processing
Murelio is accessible internationally, and global service providers such as GitHub, Google, and Cloudflare may process information in infrastructure located in multiple countries. Depending on the user’s location and provider configuration, information may therefore be processed outside the user’s country.
Third-party processing is also governed by the relevant provider’s policies and contractual terms. This policy is updated when the actual providers or processing scope materially change.
13. Sale of personal information and profiling
Murelio does not sell users’ tool inputs or personal information and does not use ordinary tool inputs to build individual behavioral profiles for sale.
If advertising is enabled later and an advertising provider uses identifiers that are legally treated as personal data, the active processing and available choices will be disclosed accordingly.
14. User choices and rights
Users can delete Murelio browser-local data through browser controls and may request applicable access, correction, or deletion relating to personal information they provided through support. Contact [email protected] for a private rights request.
There may be nothing to delete from Murelio servers for tool inputs or files that were never stored there. Public GitHub posts can be managed through GitHub functionality and the Murelio Support moderation process.
15. Age and children
Murelio does not impose a separate age restriction, but it is not designed to collect children’s personal information. Ordinary tool use does not require age information to be registered as account data.
Guardians may wish to ensure that minors do not place personal information in public support posts. Public support channels should not be used to disclose identifying information.
16. Security
The service reduces exposure by minimizing collection, processing tool data locally where practical, protecting network transport, and separating public support from private support.
No internet service can guarantee absolute security. Security vulnerabilities should be sent privately rather than disclosed in detail in a public issue.
17. Changes to this policy
This policy may be updated when features, statistics, advertising status, external providers, laws, or operating practices change. Material changes are reflected in the effective date and related documents.
The version published on the Murelio website is the current public policy.
18. Privacy contact
Operator: HRuin. Send privacy, rights, or private security inquiries to [email protected]. Use the public GitHub Support repository for ordinary feature and usage questions.
Murelio is a personal project and does not operate a separate phone call center or physical customer-service location.
19. Personal information processed and purposes
Ordinary Murelio tools do not directly collect personal information for a Murelio user account. If a private email inquiry is sent, the sender email address, display name, message, voluntarily attached files, and sending time may be processed to answer the inquiry, investigate a problem, handle a rights request, or address a security matter.
Ordinary network information such as IP address, request time, requested path, browser or device information, and security events may be processed by infrastructure providers for delivery and security. Murelio’s own public statistics are separate aggregate counts centered on tool ID, category, locale, device class, time bucket, visits, and executions.
20. Disclosure to third parties
Murelio does not sell tool inputs, outputs, files, or personal information received through support and does not routinely disclose them directly to advertisers or arbitrary third parties. If a lawful basis such as consent or a legal requirement becomes relevant, the applicable scope and purpose will be disclosed.
When a user posts directly in public GitHub Support, that information is provided by the user to GitHub and may be public. Personal or sensitive material should therefore be sent through private support email instead of a public issue.
21. Service providers and entrusted processing
Murelio uses external providers for website delivery, security, and private support email. Cloudflare is used for delivery, security, and network processing, while Google Gmail is used to receive, retain, and reply to private support email. Each provider also operates under its own contracts and policies.
To the extent a provider relationship constitutes entrusted personal-information processing under applicable Korean law, the operator applies the management and oversight obligations that apply to that relationship. Material changes to providers or processing are reflected in this policy.
22. Deletion procedure and method
When a support purpose is completed and there is no remaining need for reasonable follow-up, a legal retention requirement, dispute handling, or a security investigation, personal information is deleted or cleaned up as it is no longer needed.
Electronic support records are destroyed by deleting the relevant email or service record. Tool inputs and files that were never stored on Murelio servers may have no server-side record to destroy. Browser-local preferences can be removed by the user through browser site-data controls.
23. Sensitive identifiers and pseudonymized information
Murelio does not require national identifiers, financial passwords, authentication codes, health information, or similarly high-risk information for ordinary tool use or routine support. Such information must not be placed in public GitHub Support.
Murelio does not currently operate a separate pseudonymized user dataset for analytics. If that changes, the purpose, categories, retention, and safeguards will be disclosed according to the actual processing.
24. Privacy contact and previous policy
Privacy complaints and rights requests are handled by operator HRuin at [email protected]. Ordinary feature questions should use public GitHub Support.
This policy applies from 2026-08-19. The immediately preceding public Privacy Policy applied from 2026-08-14 through 2026-08-18. Future changes will identify the applicable date and record material user-facing changes in the changelog.