Privacybeleid

Effective: 5 October 2026

BetaSuite ("we", "us") provides the BetaSuite mobile app ("the App") for iPhone, iPad and Android. There is no account or sign-in. Your projects, sessions, notes, markers, photos and videos are stored on your device. A few features send data off the device. This policy lists each one, what is sent and where it goes.

When you use one of those features, data goes from your device to the service that provides it, and that service handles it under its own privacy policy, which we link below. We process your personal information in accordance with applicable privacy and data-protection laws in your country of residence.

BetaSuite is based in South Australia, Australia, and handles personal information in line with the Australian Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs). If you use BetaSuite from the European Economic Area (EEA), the United Kingdom, California, or another region with its own data-protection law, the additional information and rights in section 9 also apply to you. For the limited personal information BetaSuite itself handles, BetaSuite is the data "controller" for the purposes of the EU and UK General Data Protection Regulation (GDPR).

In short

1. What stays on your device

Feedback entries, notes, voice memos, photos, videos, screen recordings, projects, sessions, markers, test-protocol results, and the device details the App adds to them (model, OS and app version; battery and network state only if you turn that on). None of it is stored on a BetaSuite server.

What we never collect

BetaSuite has no server that stores your projects, recordings or notes. The only online service BetaSuite operates is a small Cloudflare Worker for the public feedback board and upvote counts (section 5). We never see your AI requests or the files you save to a folder. We do not sell or trade personal information, run ads, or track you across other apps or websites. The App contains no product-analytics SDK and sends us no feature-usage or behavioural events (on Android, Google's ML Kit barcode scanner sends Google its own diagnostics; see section 3).

2. Saving and sharing files

Camera roll (on by default)

New photos and videos are saved in the App and, by default, also to your device's photo library (camera roll). If your photo library syncs to iCloud Photos, Google Photos or another service, those copies sync too, under that provider's terms. You can untick this during setup, or turn it off at any time in Settings → Save Destinations → Camera Roll. Save Destinations is hidden while Confidential Mode is on, so change it before you turn Confidential Mode on. Reports are never saved to the photo library.

A folder you choose

In Settings → Save Destinations → Custom Folder you can pick a folder with the system file picker, and captures and reports are copied there too. On iPhone and iPad that can be iCloud Drive or a folder on the device (Google Drive, OneDrive and Dropbox folders usually can't be picked there); on Android, any folder the picker shows, including Drive, OneDrive or Dropbox. That provider's own app syncs the folder. There is no in-app cloud sign-in: BetaSuite never signs in to those services and never sees the files.

Sharing and exporting

Reports, backups and other exports leave the App only when you share, save or email them yourself, through the system share sheet or your own mail app. Where they go after that is up to you and the app or service you pick.

3. Weather, place names, dictation and crash reports

Weather

The weather stamp on captures and the weather snapshot at the start of a session are on by default and work only if you allow location access. The App then sends your coordinates, with no identifier, to a weather service while the camera is open and when a session starts. Opening Settings → Camera & Recording → Overlay Settings also looks up your current location and weather for its live preview, whatever your stamp settings (if you haven't decided on location access yet, it asks). When you import a photo or video that contains GPS data and a date, the App always looks up the weather for that place and time, whatever your settings and even if you haven't allowed location access. For anything taken more than two days ago it sends the coordinates and capture date to Open-Meteo's historical-weather service, on every device. For anything newer it uses the services below.

Wherever weather appears in the App, the source's attribution is shown with it: for Apple Weather, the Apple Weather symbol, the "Weather" wordmark and a link to Apple's data-source page. Turn the weather stamp and the session snapshot off in Settings → Camera & Recording → Overlay Settings. That doesn't stop the preview lookup or the lookups for imported photos and videos. Each weather service sees your IP address, as with any web request.

Apple Weather — gegevensbronnen bekijken (opent in nieuw tabblad)

Place names

The App asks your phone's built-in geocoding service to turn coordinates into a town, region and country in three cases. While the camera is open, if the location stamp is on (it is off by default; Settings → Camera & Recording → Overlay Settings → GPS / location). Whenever you open Overlay Settings, for its live preview, whether or not the location stamp is on. And whenever you import a photo or video that contains location data, whatever your settings. On iPhone and iPad that is Apple's service; on Android it is the one supplied with your device, usually Google's. It receives the coordinates under its own privacy terms.

Dictation

The microphone button on text fields uses your phone's own speech recognition: Apple's on iPhone and iPad; on Android, the one supplied with your device, usually Google's. Depending on your device, language and settings, the audio may be processed on the device or on that company's servers, under its terms. Nothing is sent unless you tap the microphone. Dictation is separate from AI transcription (section 4) and is not switched off by Confidential Mode, so type instead if you need to. Apple Siri, Dictation & Privacy.

Barcode scanning

You can scan a product's barcode or QR code into a project's serial-number field. The image and the code stay on your device. On iPhone and iPad the scan uses Apple's on-device frameworks. On Android it uses Google's ML Kit, which, according to Google, sends Google technical data about the scanner (device and app information, performance metrics and a per-installation identifier) for diagnostics and usage analytics. ML Kit terms.

Crash reports (off by default)

Crash reporting uses Firebase Crashlytics (Google) and is off until you turn it on. It is offered unticked during setup and can be switched on or off at any time in Settings → Data → Crash reporting. When it is on, a crash report contains technical details: the error and where in the code it happened, the device model and its state (such as free memory and storage), the OS and app version, and a random installation ID created by Crashlytics. The App does not add your projects, captures or notes to crash reports, although an error message can occasionally include a file or folder name, which may contain a project or session name.

If crash reporting is off and the App closes unexpectedly, the next launch may ask you once whether to send the report(s) waiting on your device or delete them. Either choice leaves the setting off. This question is never shown in Confidential Mode or on the China mainland storefront.

App integrity check

When the App starts, it connects to Google Firebase, which BetaSuite Assist and crash reporting use. Firebase App Check asks Apple App Attest (iPhone and iPad) or Google Play Integrity (Android) to confirm that requests come from a genuine copy of the App. This exchange carries device-attestation data, not your projects, captures or notes.

4. AI features

AI features are switched on by default, but nothing is sent to a cloud AI service until you allow that feature (see "Your permission" below). You can change provider, change your permissions or turn AI off at any time in Settings → AI Features.

Which service handles your request

What each feature sends

Your permission

Before a feature first sends anything to a cloud AI service, the App asks your permission for that feature, naming the service and the kinds of data it sends (for example session notes, marker notes or audio; never your tester name). You can allow or decline each feature, and change your choices at any time in Settings → AI Features → Manage AI permissions. Apple Intelligence runs on your device and doesn't need this permission. For transcription, iOS also shows its own Speech Recognition permission, which you can change in iOS Settings → Privacy & Security → Speech Recognition.

Confidential Mode and regional limits

Confidential Mode (section 6) blocks every cloud AI service: only Apple Intelligence on your device is allowed, and transcription and reading protocols from documents are switched off. Where local law requires it, for example on the China mainland storefront, the App offers only Apple Intelligence on the device, offers transcription only on devices with Apple's on-device speech recognition, and makes no cloud AI provider available.

5. Feedback board, brand suggestions and contact

Feature requests

The Feature Requests screen (Settings → Help & Feedback → Feature Requests) posts ideas to BetaSuite's public feedback board, a GitHub repository at github.com/brilt9/betasuite-feedback. Everything posted there can be read by anyone. You can browse and upvote without signing in.

GitHub privacy statement.

Brand suggestions

Project settings include a list of known company brands. When you enter a company that isn't on the list:

Either way the request goes through the same Worker, which runs its own check, with only the app version and OS version; nothing else from your project is sent, and each name is suggested at most once per install.

Upvotes

The first time you upvote (or report) a request, the App creates a random ID and keeps it in the iOS Keychain or Android Keystore. It is sent to the Worker so each install's vote counts once, and the Worker stores it with the request number in Cloudflare. It is not your name, email, account or any identifier from your device's operating system, and it is never sent to GitHub. Wiping all app data deletes it from your device, and a new one is created the next time you upvote or report. On iPhone and iPad the iOS Keychain can keep it after you delete the App, so reinstalling may reuse the same ID; use Wipe all app data to reset it.

Reporting a request

The Report button on a public request sends us the request number and title, the reason you pick, any details you add (after redaction) and the random upvote ID. It goes by email through EmailJS, an email-delivery service that processes data in the United States. Reports are not posted publicly.

Contact Us and Report a problem

Settings → Help & Feedback → Contact Us (also opened by Report a problem and from some error messages) sends the name and reply email you enter (filled in from your profile if you set one), the category and your message to us through EmailJS, which delivers it to our support mailbox, hosted by Google. A bug report can include a diagnostics block: app version, device model, OS version, language, app mode, AI provider setting, whether Confidential Mode is on, recent error messages (with project and session names and obvious personal details removed) and, on iPhone and iPad, recent dual-recording diagnostics. You can read and edit it before sending, or untick it to leave it out. Nothing is sent until you tap Send. On the China mainland storefront the form opens your own mail app instead.

EmailJS privacy policy.

6. Confidential Mode

Turn Confidential Mode on for one project (in that project's settings) or for everything (Settings → Confidential Mode). While it is on, the App:

These keep working in Confidential Mode, so you can decide what else to switch off:

Confidential Mode is best-effort enforcement of the App's data-flow paths. It is not a substitute for your own review of where data goes when you take a manual action (e.g. taking a screenshot, sharing via the system sheet after the dialog).

7. This website

This section covers the betasuite.app website, not the App.

8. International transfers

The services named in this policy operate from various countries. When you use one, the data you choose to send may be processed in a country whose privacy and data-protection laws differ from yours. Google, GitHub, Anthropic and OpenAI are based in the United States; EmailJS is based in Singapore and processes data on servers in the United States; and DeepSeek processes data in China. The BetaSuite Cloudflare Worker (section 5) and this website run on Cloudflare's global network, so a request may be handled in a data centre outside your country. Each service's privacy policy (linked above) describes how it handles transfers and what protections apply.

9. Legal bases, retention, and your rights

Legal bases for processing (where the GDPR applies)

For users in the EEA or the UK, the limited personal information BetaSuite handles is processed on these bases: performance of a contract (providing the App you purchased and the features you choose to use); your consent (cloud AI features, crash reporting, brand suggestions you choose to send, and any other optional flow that asks before it sends data off your device; you can withdraw consent at any time in Settings, without affecting processing already carried out); and our legitimate interests (keeping the App, the feedback board and this website secure and free of abuse, answering your messages, improving the App from redacted public feedback, the automatic brand suggestions in version 1.3.5 and earlier, and measuring aggregate audience on this website), balanced against your rights and freedoms.

How long we keep your data

Your rights — everyone

Because the App stores data locally, you can exercise most rights directly inside the App:

For data you have sent to a third-party service (a folder synced by its provider, an AI provider you used, your phone's geocoding or speech service, the public feedback repository), exercise your rights with that service directly using the contact channel in its privacy policy. To remove or change a feature request or brand suggestion, contact us through Settings → Help & Feedback → Contact Us and we'll act on your behalf in the public repository. For the limited data BetaSuite itself handles (messages you send us, crash reports if you enabled them, upvote records, short-lived rate-limit counters keyed to your IP address and website analytics measurements), contact us using the channel in section 11 and we will respond within a reasonable time, and within any period required by applicable law.

Australia (Privacy Act 1988 / APPs)

You may ask us to access or correct personal information BetaSuite holds about you, and you may make a privacy complaint to us via the contact channel in section 11. If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au.

EEA / United Kingdom (GDPR)

You have the right to access, rectify, erase, restrict, or object to processing of your personal data, the right to data portability, and the right to withdraw consent at any time. You also have the right to lodge a complaint with your local data-protection supervisory authority (in the UK, the Information Commissioner's Office, ico.org.uk). BetaSuite itself handles only a small amount of personal data (messages you send us, crash reports if you enable them, redacted public feedback, upvote records, short-lived rate-limit counters keyed to your IP address and aggregate website audience measurements), while almost everything else stays on your device or is sent directly to providers you choose. On that basis we consider BetaSuite's own processing of EEA/UK personal data to be limited and occasional, not to involve large-scale special-category data, and to be unlikely to result in a risk to your rights and freedoms within the meaning of GDPR Article 27(2), and we have not appointed an EU or UK representative. You can reach us through the contact channel in section 11.

California (CCPA / CPRA)

We do not sell or share your personal information, and we do not use it for cross-context behavioural ("targeted") advertising. Subject to verifying your request, California residents may ask to know, delete, or correct personal information, and will not be discriminated against for exercising these rights. Because almost everything stays on your device, you can exercise the know / delete / correct rights directly in the App; for anything BetaSuite itself handles, use the contact channel in section 11.

Automated decisions

BetaSuite's AI features draft summaries, transcripts, redactions, and reports to assist you, but they do not make automated decisions that produce legal or similarly significant effects about you. You review and control everything before it is used or shared.

10. Children

The App is not directed at children, and we do not knowingly collect personal information from a child. Because the App holds data locally, a parent or guardian can remove it directly via Settings → Data → Wipe all app data, or by uninstalling the App. For a public feature request posted by a child, contact us and we'll remove it on your behalf.

11. Changes and contact

We may update this policy from time to time. The effective date at the top of this page reflects the most recent revision. The App also contains a copy at Settings → About BetaSuite → Privacy Policy; if the two ever differ, this website version is the most recent.

Questions, requests, or complaints about this policy or your data: use the contact form on our support page, or the in-app form at Settings → Help & Feedback → Contact Us.

If you are not satisfied with our response, you have the right to lodge a complaint with the data-protection authority in your country of residence.