FEEDBACK REPORT HANDLING / NOVEMBER 6, 2026
Your report.
Shared deliberately.
This page covers feedback you choose to send from a CPA build configured for the feedback service. It is separate from the website request form and from your AI provider’s services. Contact [email protected] about a report or deletion request.
What is sent
A report includes its ID, category, your message and supplied app/computer/console context. If you provide a reply email address, that is included. Optional diagnostics contain the text you choose to include. The current endpoint accepts short schema-1 text reports up to 96 KiB, with diagnostics up to 64 KiB. It does not accept show files, scripts, screenshots, arbitrary attachments or detailed session uploads.
Use the app’s preview and review the actual content before pressing Send. Do not include licence keys, tokens, passwords or private production material. A written report without logs is welcome. Automatic redaction cannot guarantee that free text is anonymous or secret-free.
How reports are used and protected
Reports help investigate problems, review beta feedback and prepare a reply if you supply contact details. Metadata and owner review notes are stored in a dedicated Cloudflare D1 database; the report payload is stored in a private Cloudflare R2 bucket. The report dashboard is restricted to the configured owner through Cloudflare Access. Reports are not published automatically or linked to a hidden machine identifier. We do not send an automatic email reply.
Retention and deletion
Live report access ends 90 days after first receipt. A scheduled process runs every 30 minutes to delete expired payloads and metadata; an R2 lifecycle rule provides an additional expiry safeguard. Identical retries within the retention window do not restart that period. Owner notes expire with their report.
If a report is deleted early, its message, reply address, other personal context and notes are removed from the live report store. A minimal ID/hash/expiry marker remains until the original expiry to prevent a retry from recreating the deleted report. Deduplication is limited to the retention window.
Cloudflare’s separate database recovery history can retain earlier metadata for up to 30 additional days, depending on the service plan. This is not a promise that every backup disappears immediately when a live record is deleted. See Cloudflare’s recovery documentation. Restored data must have expiry/deletion handling reapplied before use.
Email correspondence, copies you export, and clipboard/email drafts are separate from this report-store schedule. If you want a report reviewed or removed earlier, contact support with its ID or the reply address you supplied; please do not send credentials.
Abuse prevention and service records
Cloudflare processes network and security information to deliver and protect the endpoint. The service uses an hourly keyed hash derived from the connecting IP for rate limits, with short-lived counters; it does not put raw IP addresses in the report database. It also limits total accepted attempts. Application payload logging is disabled in the deployed worker configuration. Cloudflare’s own service/security records remain subject to its settings and policies. See Cloudflare’s privacy policy.
If sending is unavailable
The app does not enable sending merely because this page exists. A configured build and explicit Send action are required. Keep a local pending/export copy if you do not receive confirmation. The sender does not retry automatically; retry the same report deliberately if instructed. You can instead use the local support message helper and your email app.