Support and reporting
How to contact Clipo
Use this page to prepare safe, useful product support, privacy, accessibility, abuse, and security reports for Clipo.
Last reviewed: July 14, 2026
Contact categories
Product support
Upload, processing, sign-in, result, download, browser-storage, or account-session problems.
Include the exact page, error message, time, browser, and device.
Privacy requests
Questions about data handling or requests to access, correct, delete, restrict, or object where applicable.
Include enough detail to identify the relevant account, browser session, or saved result.
Accessibility feedback
Barriers affecting keyboard, screen-reader, zoom, contrast, motion, touch, or other assistive use.
Include the affected workflow, assistive technology, browser, and preferred follow-up method.
Abuse, rights, and safety
Suspected unlawful use, privacy abuse, intellectual-property concerns, or content-safety reports.
Describe the issue clearly without sending private images or unnecessary personal data.
Security vulnerabilities
Good-faith reports about a potential vulnerability in Clipo's web application or service configuration.
Share only safe reproduction details and avoid accessing data that is not yours.
What to include in a report
- The affected page or workflow and what you were trying to do.
- Steps that reproduce the problem, what happened, and what you expected.
- Browser, operating system, device type, and assistive technology when relevant.
- The safe request ID shown with an error, approximate time, and time zone when available.
- For accessibility feedback, the barrier and a preferred accessible response method.
Do not send sensitive material
Do not send source images, image results, passwords, cookies, OAuth codes, session tokens, raw device identifiers, Google account IDs, government identifiers, payment details, or other unnecessary personal information through a general contact channel.
A screenshot should exclude private images, browser storage values, authentication data, and unrelated personal information. Clipo should request additional evidence only through an approved secure process when it is genuinely needed.
Privacy-request safeguards
Privacy requests may require verification before Clipo can act. Include only the information needed to locate the relevant account, browser session, saved result, or service record.
Security-reporting safeguards
Until a vulnerability disclosure policy is published, do not access another person's data, disrupt availability, run destructive tests, upload malware, use social engineering, or retain sensitive data. There is currently no published safe-harbor or bounty commitment.
Production security intake must define an encrypted or otherwise appropriate reporting option, acknowledgement and triage targets, escalation ownership, coordinated-disclosure expectations, and safe evidence retention.
Self-service information available now
- Review how uploaded images and operational data are handled in the Privacy Notice.
- Review cookies, local storage, result storage, and deletion controls in Cookies and Browser Storage.
- Review implemented measures and known barriers in the Accessibility Statement.
- Delete one result or all browser-saved results directly from the result page.