Beta terms

1BX Beta — Participation Agreement

Version: beta-tos-2026-10-15.1 · Last updated: 15 October 2026

Applies to: the 1BX closed beta only — the invited testers, the beta builds they install, and the beta surfaces at 1bx.app/get/ and quiet-apps.pages.dev/install/*.

Does not replace: the project’s own legal/TOS.md and legal/PRIVACY.md. Where this document and those disagree about the beta, this one wins for the beta.

This is a written draft, not legal advice. It is written to be accurate about the code — every claim in §3 is checkable against a file or a header — but the wording, retention periods and jurisdictional clauses should be reviewed before you rely on it commercially.

1. What the beta is

You have been invited to test 1BX, a private messaging app that installs under an ordinary-looking name of your choosing (“a cover”). The beta exists so we can find out what breaks on real phones — every check in the project so far has run in a desktop test suite, and none of it has been confirmed on a handset.

Two ways in, and one of them creates no account. You can set up with an email address and password, or with nothing but a name: on the Create account screen, No email? Set up on this device starts a session that lives only on that device. That path asks for no address, sends no signup request, and creates no account anywhere — not with us, not with anyone else. It makes an internal placeholder address ending in @noemail.invalid; .invalid is the TLD RFC 2606 reserves so that it can never resolve, which means it is never a real mailbox and nothing is ever sent to it. Both paths set the same three codes and use the same on-device keys.

By installing or using a beta build you agree to this agreement. If you do not agree, stop here and uninstall — no hard feelings and nothing else is required of you.

2. What “beta” means, stated plainly

  • It has not been confirmed to work on any handset by us. Anything it does on your device is a first observation, not a confirmation.
  • The builds are debug-signed, not release builds.
  • There is no code recovery. If you lose the code you set, the data behind it is gone. There is no reset, no recovery email and no support path that can restore it. Write your code down.
  • A device-only session is not an account. If you set up without an email address, there is nothing anywhere to sign in to, recover, transfer or delete — the session lives on this device only. The address it generates for itself ends in @noemail.invalid, which can never resolve: it is not a mailbox and nothing is sent to it.
  • Messaging works, with limits stated plainly. The relay is a Cloudflare Pages Function on the same host as the app, so a message leaves your device and waits there until the recipient collects it. The body of a message is encrypted on your device, and your private key never leaves it. Two limits matter: the metadata is not private — the relay can see that a message was sent and when, and it must know where to hold it, so who talks to whom is visible to the relay even though it cannot read the contents; and the key you send to is a claim, not a verified fact, because this beta has no built way to confirm that the key handed to you belongs to the person you think it does. A message to someone who is not an app user goes as ordinary email and is not encrypted this way. None of this has been confirmed on a handset by us. Do not rely on the app for anything that matters, and do not delete your only copy of anything important on the strength of it.
  • Data loss is expected. A beta can lose your data, and updates can change or break how it is stored. Keep your own backups.
  • The beta can end at any time. See §9.

3. Monitoring and tracing — the point of this document

The beta is being traced so we can see whether it actually works. This section describes exactly what is measured, what is never measured, and how to opt out. Nothing is measured that this section does not name.

3.1 What is measured in the beta

Cover-install events
When a request reaches the beta’s host, a server-side function running at Cloudflare’s edge records what kind of request it was: opening a cover’s install page (and which cover), opening the cover chooser, fetching the compiled app (app_boot — the strongest evidence available that the app actually launched), reading the install manifest, reading the build record, or sending a message (message_sent — a request that actually left the device for the relay’s send path; a row here means a message was sent). Each record holds the time, the path, the cover, a user-agent string, a coarse country, the Cloudflare edge location and a Cloudflare request id. No IP address is stored.
Where it lives: our own database (Cloudflare D1), install_hits
Ordinary relay traffic
Deliberately not recorded. The relay is a function on this same host, so checking the inbox, syncing the channel and looking up a contact are normal traffic and are not logged by the middleware. If you see no row for them, that is the design, not a fault. (Before 2026-10-13 the host was static and a relay request was recorded as relay_attempt, read as a stale cached bundle; that event no longer exists and that reading is no longer true.)
Where it lives: nothing is stored
Host access logs
The host, Cloudflare, keeps its own ordinary access logs, as any website host does. That is your IP address, a user-agent string and the time. It is outside our code and outside our control.
Where it lives: the host’s own logs
Cover installs, cross-checked
Which cover install link was opened, so we can tell a broken cover from an unused one.
Where it lives: same install_hits table, cover_install rows
Download / transfer events
When a beta file is served to a device, the server records the transfer — this is the same log any download server keeps, and it is the only record that a tester actually got the file.
Where it lives: the serving machine’s log
Crash, error and usage reports, from inside the app
The app posts one JSON body to POST /api/diag. The request is unauthenticated on purpose — a crash before setup is still a crash worth hearing about. The body is exactly: v (the format version, currently 1), kind (crash, error or usage), event (the action that happened), errorType, messageScrubbed, stackScrubbed, appVersion, bundleSha (the build digest), platform, screen, installId, and — for a failed request — endpoint (the path only, never a query string), status (the HTTP status) and tokenAttached (true or false, never the token). installId is a random value kept in sessionStorage that dies when the tab closes — so the honest label stays sessions, not users. The app scrubs the free-text fields before they leave the device, and the endpoint caps lengths and validates the body again.
Where it lives: our own database (Cloudflare D1)
Every error the app shows you is reported
Not only crashes. If the app displays an error — a failed sign-in, a message that would not send, a refused request — that is reported as kind: 'error' with the fields above and nothing more. This replaced a narrower rule that reported only crashes, which meant the errors testers actually saw were the ones we never saw. An error you are shown and the record we keep describe the same event.
Where it lives: our own database (Cloudflare D1), diag
What a crash report deliberately cannot carry
Message contents — plaintext or ciphertext — your codes (real, decoy or kill), any key material, email addresses, handles, your contact list, and who you talk to. There is no field for any of them in the body above, the app strips free text before sending, and the endpoint validates again. See §3.2.
Where it lives: nothing is stored
What you tell us
Anything you send us through the beta feedback form, including your device model and Android version.
Where it lives: our own database + the operator’s mailbox

No cookies, no fingerprinting, no cross-site identifiers, and no third-party analytics. Any in-app tracing uses a value kept in sessionStorage that dies when the tab closes — so the honest label is sessions, not users.

The device-only setup described in §1 sits outside all of this: it sends no signup request, creates no account, and mints no token, so there is no account event for us to record.

3.2 What is never measured

  • The contents of your messages, vault, notes or files.
  • Your codes — the real code, the decoy code or the kill code.
  • Your cryptographic keys, or any key material.
  • Your contact list or who you talk to.
  • Any address from a device-only setup. That path collects no address, and the dead @noemail.invalid address it creates is never a mailbox and is never sent to the relay.
  • Anything in a crash or usage report that is not one of the fields named in §3.1 — including message contents (plaintext or ciphertext), your codes, key material, email addresses, handles, your contact list, or who you talk to. There is no field for any of them, the app scrubs the free text before it sends, and the endpoint caps and validates the body again.
  • Anything outside the beta surfaces listed above.

The app’s core promise is that it leaves no trace on your device. Beta tracing is a temporary, disclosed exception that applies to the beta builds only — it is not part of the shipped product. When a build ships publicly, this section does not apply to it.

3.3 In-app crash, error and usage reporting — what the beta turns on

Crash, error and usage reporting is being switched on for the beta, and this agreement is re-published with a new version string first — before any build turns it on, which is the order §3.3 has always required and §8 repeats. When it is on, the app posts one JSON body to POST /api/diag:

  • v, kind, event, errorType, messageScrubbed, stackScrubbed, appVersion, bundleSha, platform, screen, installId — the exact list in §3.1, and nothing else. A report caused by a failed request also carries endpoint (path only), status and tokenAttached (true or false — never the token itself).
  • kind: 'crash' and kind: 'error' are faults: what broke, where in the code, on which build. An error the app shows you is a fault, and it is reported — a failed sign-in, a message that would not send, a refused request. Not only crashes: an error you are shown and not told about would be the one kind of silence this section exists to rule out.
  • kind: 'usage' says a step happened (for example that the app opened, or that a code was set). It records that it happened, never who did it — installId is a random value in sessionStorage that dies with the tab, so the honest label is sessions, not users.
  • The app scrubs message and stack text before sending, and the endpoint caps lengths and validates the body again.
  • No message content, no code and no key is recorded — §3.2 still holds, and that part never changes.
  • Everything is deleted at the end of the beta (§3.5).
  • You may opt out (§3.4) and the beta still works.

The edge events in §3.1 (cover_install, picker, app_boot, manifest, version_probe, message_sent) are recorded by the host, not by the app, and they carry no identifier of you — there is no IP column by construction. Opting out of in-app reporting does not remove them, because they are a server noticing a request rather than your device telling us anything.

Confirmed live, 2026-10-14. POST https://quiet-apps.pages.dev/api/diag accepts a report and answers {"success":true,"id":N}; GET answers 405 (Allow: POST) and OPTIONS 204. The endpoint scrubs again server-side (mobile/pages-functions/api/[[path]].js): a field matching a PEM header, a 40+ character base64 run, a Bearer token, a JWT, an API-key shape, an email address or an /install/ handle is dropped whole, and the rule that fired is recorded in scrubbed_fields — so a client that failed to scrub still cannot store one.

One limit, stated rather than glossed. The response echoes only success and id, and there is no read route (GET is 405, /api/diag/4 is 404), so the stored NULLs were read from the row itself — the operator’s check — and not confirmed from outside. An independent HTTP check can confirm that a report is accepted and that the scrub rules are in the deployed code; it cannot confirm the value that landed in the column.

3.4 Your controls

  • Opt out of tracing at any time without losing access to the beta. The tracker honours the browser’s Do Not Track signal and an explicit opt-out; an opt-out is permanent on your device. That switch controls the in-app reporting in §3.3. The edge events in §3.1 are recorded by the host when a request arrives and cannot be switched off from the device — they hold no identifier of you, and no IP address is stored.
  • Ask to be excluded before you install — say so and no beta tracing applies to you.
  • We do not need your email address. If you give one, it is stored only alongside the exact version of this agreement you agreed to, and only from a deliberate consent action. The event table has no email column, so counting paths physically cannot store an address.
  • Ask for a copy or deletion of what we hold about you (§7).

3.5 Retention

Host access logs
The host’s ordinary retention, not extended by us for the beta
Edge/install tracing events (install_hits)
Deleted at the end of the beta, and no later than 90 days after it
In-app crash, error and usage reports (POST /api/diag)
Deleted at the end of the beta, and no later than 90 days after it. Read by the operator directly from our own database; not sold, not shared, and not fed to any third-party service.
Feedback you send, including your address
Until you ask us to delete it, or until the beta programme closes

4. What we ask of you

  • Do not share the beta links. The beta is unreleased; the cover mechanism depends on it staying quiet. This is a request, not a legal restriction on what you may say about your own experience.
  • Do not rely on it for anything that matters, and do not put anything in it you cannot afford to lose.
  • Tell us what breaks — including the small things. A failure written down is the useful result. “It did nothing” is a finding. §2’s limits are the reason.
  • Do not attempt to access systems, accounts or data that are not yours, or to overload or probe the beta infrastructure except through the feedback route we provide.

5. Feedback you send us

You keep ownership of anything you write to us. By sending feedback you give us permission to use it, including quoting it, to improve the product — with your name and device details removed unless you ask us to credit you.

6. No warranty, and the limit of our liability

The beta is provided “as is” and “as available”, with no warranties of any kind. To the fullest extent permitted by law, the Developer is not liable for any indirect, incidental, special, consequential or punitive damages, or for any loss of profits, revenue, data, goodwill or other intangible loss, arising from your use of the beta, from unauthorised access to or alteration of your local data, from bugs or interruptions, or from the conduct of any third party. Nothing here limits liability that cannot lawfully be limited.

7. Your rights over your data

You may at any time ask us to give you a copy of, or delete, the personal data we hold about you — in practice that means your email address, the consent record that goes with it, and anything you sent us. Requests go to the address in §10.

Because the anonymous tracing data contains nothing that identifies you, we cannot locate or delete “your” rows — there is no link to you to search by. That is a limitation of the design, not a refusal.

8. Changes to this agreement

The version string and date at the top change whenever the text does. If a change would expand what we collect, we will ask you to agree again rather than assume it — and §3.3 says the same thing. The version you agreed to is recorded with any consent you gave.

9. Term

The beta runs until the Developer ends it. We may close it, change it, or end your participation at any time. When it ends, the tracing data described in §3.5 is deleted, and we will tell you before a build that traces nothing replaces it.

10. Contact and governing law

Sheehan Gillis — sheehangillis@proton.me

Governed by the laws of Canada, with exclusive jurisdiction in the courts of British Columbia.

Appendix — what is actually on today

Recorded so this document cannot drift from the system it describes. Measured 2026-10-11, 2026-10-12 and 2026-10-14 (local time, +08:00) — the device-only row was added just after local midnight, the crash/usage, message_sent and relay rows on 2026-10-14, and the crash/usage state updated the same day once the endpoint was deployed. The version string above follows the document’s own §8 rule; the .1/.2 suffixes mark later revisions issued on the same date, because a date alone cannot distinguish several texts on one day and §8 requires the string to change whenever the text does.

The landing page carries no tracker
✅ 1bx.app serves Content-Security-Policy: default-src 'none'; script-src 'self'. The one script that directive allows is the page’s own background animation, /ocean.js, which makes no network request of any kind; 'self' still refuses every third-party script, and inline script stays refused. Its footer promises “no analytics, no trackers”.
The cover host can carry one if we choose
✅ quiet-apps.pages.dev serves no CSP header
Cover-install tracing is live (§3.1)
✅ measured 2026-10-12: requesting https://quiet-apps.pages.dev/install/weather/ wrote row cover_install cover=weather into install_hits (D1 1bx-beta-hits, 3c5c6569-c97f-4c3a-b904-1c83f63cbaa4), followed by picker, app_boot, manifest and version_probe from the same run. Columns are ts, event, path, cover, ua, country, colo, ray — no IP column exists, by construction.
The tracing adds nothing to the page
✅ it is a Cloudflare Pages Function (mobile/pages-functions/_middleware.js); no script tag, no cookie, no CSP relaxation, nothing on the phone. The site serves the asset first and logs afterwards, so a logging failure cannot break an install.
1bx.app still carries no tracker
✅ unchanged — its CSP is still default-src 'none', its only permitted script is its own request-free /ocean.js, and the functions live only on the covers host
Messaging works, and the relay is on the app’s own host (§2)
✅ measured 2026-10-14 from the wire: the deployed build’s version.json records apiUrl = https://quiet-apps.pages.dev/api — its own origin, no tunnel — and the live bundle contains no trycloudflare URL. https://quiet-apps.pages.dev/health answers 200 (application/json), while /api/messages and /api/channel/sync answer 401 without a token, i.e. the relay routes exist there and are protected rather than missing. ⚠️ Not measured by me: the two-client send/receive round trip; that is the operator’s run. No handset result exists for any of it.
Crash, error and usage reporting (§3.1, §3.3)
✅ Live and accepting reports. Measured 2026-10-14: GET https://quiet-apps.pages.dev/api/diag → 405 (Allow: POST), OPTIONS → 204, and four POSTs of a well-formed report → {"success":true,"id":3} … {"success":true,"id":6}. The endpoint scrubs server-side as well as client-side (mobile/pages-functions/api/[[path]].js): a field matching a PEM header, a 40+ character base64 run, a Bearer token, a JWT, an API-key shape, an email address or an /install/ handle is dropped whole and the rule that fired is recorded in scrubbed_fields. ⚠️ Not confirmed from outside: the response echoes only success and id and there is no read route (GET 405, /api/diag/4 404), so the stored NULLs were read from the row itself — an external HTTP check can confirm acceptance and the deployed scrub rules, but not the value that landed in the column. What this replaces, stated because it was a real gap: until this version, the app reported crashes only — a handled error shown to a tester (a failed sign-in, a refused send) was displayed and then lost, so the failures testers actually met were the ones never recorded. Every error the app shows is now reported.
A relay request is ordinary traffic, not an alarm (§3.1)
✅ measured in source 2026-10-14: mobile/pages-functions/_middleware.js:74 classifies exactly one relay path — /api/receive-email → message_sent — and returns null (unlogged) for every other /api/* path, so an inbox poll or a channel sync is not recorded. The old relay_attempt event, which read normal relay traffic as a stale cached bundle, no longer exists.
Access logs exist for downloads (§3.1)
✅ measured: a request through the beta APK server logged 2026-10-11 15:23:48 206 192.168.100.102 GET /1bx-beta-1.0.0-arm64-debug.apk bytes=100/98867834 ua="ProbePhone/1.0 (Android 13)" — time, remote address, method, path, bytes and user-agent
The feedback route exists
⚠️ unverified today. feedback-worker/README.md says the feedback routes are deployed, but *.workers.dev is unreachable from this machine — DNS resolves it to Facebook/Meta IPs (69.63.190.26), the same router/VPN interference NEXT_STEPS.md:12528 records for 1bx.ai. That is a fault on this machine, not evidence about the Worker.
A device-only setup creates no account, collects no address, and its dead address is never a mailbox
✅ measured in source 2026-10-12: the No email? Set up on this device button in onboarding_screen.dart calls AuthProvider.signupDeviceOnly(), which makes no network call and mints no token (_idToken = null); it sets deviceOnly: true and writes the session to on-device storage. Its placeholder address is device-<timestamp>@noemail.invalid and its local id is local_<timestamp>. RFC 2606 reserves .invalid, so it can never resolve and is never a real mailbox. Not yet confirmed on a handset.