Reporting bugs in Limestone

Limestone can send us bug reports and crash logs so we can fix problems fast — without ever sending your notes (ADR-0095). Open Settings ▸ Report a Bug.

What's in a report — and what isn't

A report is built from a fixed allowlist of fields. It includes:

• what you wrote in the form (summary, what happened, what you expected, steps),
• the app version and build revision, your platform (web/desktop), and locale,
• for a crash: the error type/message/stack, scrubbed of any file paths, and
• a short trail of recent action kinds (e.g. "opened-settings") — never their contents.

It never includes note bodies or titles, collection names, file listings, vault paths, encryption keys, or your passphrase. Before you send, the "What we'll send" panel shows the exact JSON — so you can see for yourself that nothing private is in it. This is the same promise as the rest of the app: no vault content ever reaches a Limestone server (ADR-0091).

Anonymous by default

You don't need an account to report a bug. If you're signed in, you can tick "Include my account so we can follow up" to attach your handle and email; leave it off and the report is fully anonymous. Nothing is ever sent automatically — a report goes out only when you click Send.

Crashes

If the app hits an unexpected error, you'll see a recovery screen with Reload and Report this problem. Choosing to report opens the form prefilled with the (scrubbed) error — you still review and send it yourself.

No connection? Send it yourself

If no report service is configured, or the send fails, Limestone offers to download the report, copy it to the clipboard, or open a prefilled email — so you're always in control of exactly what leaves your device.