CIPHERCELL

HOW IT WORKS · FAQ

Trigz →The full product explanation →
PANEL 01UNFOLD A PANEL →

What happens if you stop paying

Nothing silent: a reminder runs 10 days before expiry; escalating notices run through a 30-day grace window in which late renewal is always accepted, right up to the end. Only after that window (never while a payment investigation is open) does the device wipe itself, according to the expiry it already holds. The service purges its own records in step: nothing that could re-correlate the device to a past customer survives on either end.

MomentWhat fires
Expiry − 10 daysReminder notice
Expiry → +30 daysEscalating notices; late renewal always accepted
Day +30Lapse wipe; two-sided purge; device returns to bare state via re-provisioning
Per GLOSSARY: Grace window, Lapse wipe, Device deadline · ADR 0005: a hold may delay service-side lapse and purge past this window; the device is never told of holds.
02What wipes exist

What wipes exist, and who can trigger them

The duress credential is chosen and known by you alone: never stored, never seen by any operator. Entering it at any unlock prompt wipes the device and every installed eSIM immediately and uninterruptibly.

The dead-man's switch: 72 hours without an unlock (your default, set at provisioning) arms the same catastrophic wipe. An airplane-mode-mimicking quick-settings tile arms it under observation without touching your radios.

The lapse wipe: the announced, published expiry wipe from panel 01.

Three triggers, all independent of the service. Update pulls can never touch the security spine, and the security spine is never part of billing enforcement.

Per GLOSSARY: Duress wipe, Dead-man's switch, Lapse wipe
03Billing disputes

Can a billing dispute wipe my device

No: never. No subscriber-facing channel and no billing state can trigger a wipe. Only the published expiry schedule (panel 01), your own duress triggers, and the compulsion paths produce wipes. Billing disputes are an operator conversation, not a device action. Payment ambiguity itself raises a hold and tells you: it suspends what the service does, never what your device will do, and the device is never told of holds at all.

Per GLOSSARY: Lapse wipe (ADR 0005); published wipe lifecycle policy
04Where anonymity breaks

Where anonymity can break

The service holds no identity: no names, no emails, no account concept: only hashes, enforced by tests. The operator, at any instant, could not tell you who a customer is. What no setting fixes:

The handoff itself: ordering and physical handover tie a device to a person; Monero pricing, no paperwork and an ephemeral paper credential reduce the tie without erasing it. The mobile network: your carrier knows your identifiers and tower location every time the radio speaks; privacy protects traffic, not the fact of connection. Behavior: carrying this phone beside a personal phone or reusing patterns can deanonymize a person. Upstream services: the VPN operator sees tunnel metadata, messaging servers see ciphertext and timing. Compulsion: duress and timer paths destroy data; they do not promise perpetual anonymity.

The Security Promise, published as the product's own document, per EFF Surveillance Self-Defense framing
05Support without an account

Support without an account

Support is a chat over SimpleX, the no-identifier messenger, linked by pasting your own opaque credential from the status page. The chatbot quotes the onboarding help verbatim, delivers automated billing notices, takes one-click extra-data requests, and escalates to an operator inbox when a human is needed.

Operators work under pseudonymous operator IDs with hardware-key authentication: a compromise of the service can't reveal the people running it, and they never had your name to give.

Per GLOSSARY: Support chatbot, Operator ID
06Renewal and grace

How renewal and the grace window work

Renewal is a Monero invoice from the Tor-only status page: quote and QR, valid for 60 minutes. A reminder arrives 10 days before expiry, then escalating notices through the grace window. Late renewal is always accepted within the 30-day grace window: a renewed subscription never wipes, and expiry is computed from the clock, so what you pay against can't desync from what the device acts on.

The opening six-month term is AUD 800; every renewal term AUD 1,200; the supply sheet behind it is on the product page. If your device is ever lost to a wipe, a re-provisioning pass (costs plus a modest labor margin) returns it to service; the subscription is never destroyed.

Per GLOSSARY: Renewal invoice, Term, Re-provisioning
07The warrant canary

What the warrant canary says

Every 30 days, CipherCell publishes a dated operator statement: no warrant or compulsion of the listed kinds has reached us, signed air-gapped with Ed25519 (a vendored, dependency-free RFC 8032 implementation pinned to the RFC's test vectors) so the signature can be produced nowhere near a network machine. If a canary is missing or stale, treat it as answered; the product's transparency is a cadence, not a slogan.

Per GLOSSARY: Warrant canary (30-day cadence)