How diagnostic counts work
Optional diagnostic counts help us find recurring problems and prioritise fixes in Offisen. Collection is off until you choose Turn on collection after the explanation. Declining or closing the window leaves it off and does not limit ordinary use.
What is collected
Each entry contains the Offisen version, a diagnostic code such as OFS-1807, its severity and the number of occurrences.
A batch has a random one-time identifier to recognise repeated delivery. It contains no recorded text, sequences, window titles, file paths, name, email address or permanent user or device identifier. This feature does not send usage statistics, exception text or full crash reports.
A report you copy or export for support can contain more technical detail. Review it before sharing.
When it is sent
You can preview each batch and decide whether to select Send. Each batch needs a separate confirmation. There is no automatic sending or automatic retry. Failed attempts leave the batch for a manual retry, deletion or expiry; confirmed receipt removes it from the local queue.
Occasional questions wait at least seven days after you activate collection or turn questions on. Further questions are at least seven days apart and appear only while Offisen is idle. You can open the preview yourself sooner.
How we protect your data
Confirmed batches go to Offisen over an encrypted HTTPS connection. Websupport provides hosting and the connection passes through Cloudflare. The upload does not send cookies or sign-in credentials.
Your connection’s IP address is also processed to secure the service and prevent abuse. Our diagnostic receiver keeps a short-lived security record derived from it, rather than the IP address itself. Websupport and Cloudflare may retain separate connection and security logs.
How long counts are kept
On your device: each new group has one 90-day period starting with its first occurrence. Later counts, saving or preparing the batch, retrying and restarting do not renew it. Expired groups are removed without sending at the next check at startup or when Offisen works with the queue, not while it is closed. Older saved data uses available original dates.
On the server: received batches have a 180-day retention period and the receiver’s short-lived security records have a 48-hour period. Regular cleanup removes expired records. Hosting backups and provider logs have separate retention arrangements.
You are in control
Open Settings → Help improve Offisen.
- Start or stop counting: use Collect diagnostic data and ask before sending. Turning it on opens the explanation; choose Turn on collection to start. Turning it off stops new counting and discards unsaved counts. Saved counts remain until deletion or expiry.
- Review a batch: choose Review and send diagnostic data.... Select Send only if you want to share it. Not now sends nothing.
- Stop questions: turn off Ask me occasionally to send the data or select Don't ask again. This does not send or delete counts, and the question setting alone cannot turn collection on.
- Delete local counts: choose Delete collected diagnostic data... and confirm. This clears existing counts in memory and the saved queue. Offisen reports if deletion is incomplete and lets you retry.
Local deletion does not remove sequences, run history, exported reports or server data, and cannot recall an upload already started. New problems can be counted afterwards if collection remains on.
A saved choice to turn counting off survives restarting and updating. An older saved activation pauses until you confirm the new explanation. The initial offer is shown once and remains available in settings.
Offisen is published by Rudolf Mendzezof. For questions or privacy requests, contact [email protected]. See the Privacy Policy for further information and your rights.