Effective date: 15 October 2026
Scope: hosted feedback only
This notice covers only BusyStack's hosted production feedback service for BusyMark and BusyMax on Linux. It applies only to feedback sent to the live hosted feedback service. It does not describe other behavior of either application or add support for other applications or platforms.
Cloudflare hosts the live BusyStack website and production feedback service at busystack.org. The isolated staging website and staging feedback service are separate and are outside the scope of this production notice.
Explicit feedback and delivery
When you explicitly submit feedback to the production feedback service, Cloudflare processes the submission and forwards its content to a BusyStack-controlled production Telegram destination. Submitted fields are the feedback category, subject, message, random submission identifier, application name/version/build/platform, optional reply email, and optional operating-system version and application locale. This notice makes no additional claims about application data or connected accounts.
The service returns a successful receipt only after Telegram acknowledges every required message chunk. Delivery failures or timeouts return a failure response. Telegram has no upstream idempotency support for this relay: an uncertain acknowledgement, partial delivery or loss before the receipt is committed can cause an explicit retry to repeat a message. The service does not queue feedback or retry delivery in the background.
Cloudflare anti-spam and duplicate-detection metadata
To prevent excessive and duplicate submissions, the production service retains limited enforcement metadata in Cloudflare's SQLite-backed Durable Objects: a keyed pseudonymous identifier derived from the request IP address, attempt timestamps, a digest of normalized feedback, submission and receipt identifiers, expiry times, and short-lived delivery reservations. These identifiers are pseudonymous, not anonymous.
The service does not store raw IP addresses, subjects, message text, reply email addresses or technical-detail values in that database or its application logs. Cloudflare receives the request IP address and feedback submission during request processing.
Rate-limit windows extend up to 24 hours. Submission-ID and normalized-content receipts have separate 24-hour expiry windows. A replay under another submission ID can create a new submission-ID receipt without extending the original content receipt. Capacity limits can remove metadata earlier. Expired metadata is physically deleted from active tables through bounded cleanup. Cloudflare's point-in-time recovery history can retain earlier database states within a 30-day recovery window; active expiry does not mean all provider-held copies disappear after exactly 24 hours.
Telegram feedback retention
BusyStack retains feedback messages delivered to the production Telegram destination until BusyStack deletes them manually. There is no automatic deletion schedule for these Telegram messages.
Telegram message retention is separate from Cloudflare's anti-spam and duplicate-detection metadata expiry. Expiry or removal of Cloudflare metadata does not delete Telegram messages. Contact support@busystack.org about deletion of feedback you submitted.
Provider policies
Cloudflare and Telegram may process service data under their own applicable terms and policies. See Cloudflare's privacy policy and Telegram's privacy policy.