Contact

Contact channel

Email is the primary contact channel: metarinse@gmail.com.

You may write in English or Korean about product problems, feature ideas, usage, accessibility, content, privacy, security, or a relevant business inquiry.

What you can contact us about

• Bug or error reports — something did not load, inspect, clean, verify, or download as expected.
• Feature suggestions — a practical improvement to the cleaner, supported workflow, accessibility, or documentation.
• Usage questions — help understanding formats, metadata results, quality settings, verification, or browser support.
• Privacy, security, accessibility, or content corrections — a specific concern with the product or published information.
• Business inquiries — relevant partnership, licensing, or service inquiries. MetaRinse does not accept requests to process user images on a server.

What to include in your message

• A short subject such as “Bug report,” “Feature suggestion,” “Usage question,” or “Business inquiry.”
• The page, browser, operating system, and device where the issue occurred.
• A concise sequence of steps using non-sensitive test images.
• The expected and observed result.
• For accessibility reports, the assistive technology and input method.
• For feature suggestions, the problem the change would solve rather than only a proposed interface.

Quick answers

• Is MetaRinse free? Yes. The current browser tool is free to use and requires no account.
• Are images uploaded or stored? No. Selected images are processed in the browser and are not sent to MetaRinse.
• Does it work on mobile? Yes, on supported current mobile browsers, subject to the device’s memory and image-decoding limits.
• Which formats are supported? JPEG and PNG, plus WebP when the browser can decode and re-encode it.
• Can output quality or size change? Yes. Supported images are decoded and re-encoded, so compression, file size, color handling, or subtle pixel values may change.
• Does cleaning guarantee anonymity? No. MetaRinse reports readable metadata it can detect; visible details and other forensic information may remain.

Response policy

Messages are reviewed as capacity allows. There is no guaranteed response time, urgent-response channel, or telephone support. Not every suggestion will receive an individual reply, but relevant reports may inform product and documentation improvements.

Protect your privacy when writing

Do not attach personal photos, GPS coordinates, metadata exports, passwords, account tokens, or other sensitive information. Do not send images you do not own or have permission to share. Reproduce image-processing issues with a newly created non-sensitive sample or the project’s public test fixtures when possible.

Security reports

Use the subject “Security report.” Describe the impact and minimum reproduction steps without exploiting other users, accessing data without permission, or disrupting the service. Do not include credentials or private image data. Security reports follow the same non-guaranteed response policy above.