Contact Framekeep
Use the Feedback button at the lower right of any Framekeep page to contact the team about product help, privacy, security, corrections, or developer resources. The guidance below explains what to include so a request can be routed quickly and what to leave out so client galleries stay private.
Describe what you were trying to do, the public page or product area involved, what happened, and what you expected. Do not include gallery passwords, private capability links, session cookies, client names, or image files in the first report.
State whether your request concerns an account, an anonymous gallery, analytics, or public website content. Framekeep may need to verify control through the product before changing private data, but the first message should contain only the minimum context needed to route the request.
Explain the affected public surface, the impact, and safe reproduction steps. Do not access another person's gallery, download private images, publish secrets, or include a live token in the report. Framekeep will request a safer follow-up channel if sensitive evidence is necessary.
Include the public page URL, the statement that appears inaccurate, and a primary source supporting the correction. Material product or competitor claims are reviewed before the page date or structured data is updated.
Reference the OpenAPI operation, MCP tool, discovery document, status code, or response header involved. Public interfaces are read-only and need no API key. Private gallery and studio workflows are intentionally outside the public agent contract.