Help desk

Support and reporting

The production support mailbox is not configured yet. During the TestFlight beta, use Apple’s built-in beta feedback channel; a direct Bureau address must be added before general App Store release.

Last updated: 14 August 2026

TestFlight feedback

Open Bureau of Odd Cases in the TestFlight app and choose Send Beta Feedback. Include the app version, iPhone model, iOS version, language, what you expected, and what happened.

The current public TestFlight listing may still show the previous working title while the Bureau rebrand is prepared for the next build.

Open the beta invitation

Purchases and restore

First open Profile, choose Restore Purchases, and make sure the device uses the Apple Account that made the purchase. Reconnect to the internet so Apple and RevenueCat can refresh the entitlement before trying the archive again.

Apple controls billing and refunds. Never send an Apple ID password, full receipt, payment-card number, or banking details in a support message.

Request help with an Apple purchase

Offline access

The included Base Archive is designed to work offline. An add-on archive must first be verified and downloaded online; after that, its cached cases should remain available without a connection. Reinstalling or clearing app data can remove that cache.

Bug report checklist

A useful report includes:

app version and build number;
iPhone model and iOS version;
selected language and case or archive title;
the exact steps that led to the problem;
a screenshot with personal information removed.

Privacy requests

A production process for access, correction, deletion, objection, and consent withdrawal must be available before public release. Because the beta uses anonymous identifiers, the support team will also need a safe way to help you locate the relevant account without asking for passwords or payment data.

Until that channel is published, do not send sensitive identity documents through TestFlight feedback.

Content and rights reports

For a harmful, inaccurate, privacy-invasive, or rights-infringing case, provide the case title or ID, language, reason for the report, and the right or concern involved. Do not include more personal information than needed.

A monitored content-reporting address and response process will be added alongside the production support contact.