Check-in
Checking in means saying "I'm fine" after a protest. It stops the reminders, then sharing for pending sessions.
When to check in
As soon as you are safe after the protest. Two places are possible: your account, or the field phone itself.
From the account
From any device signed in to your account. If a check-in is expected, signing in takes you straight to the Check-in screen, before any other screen. The Check-in link also remains available in the account menu.
- Enter your 6-digit code.
- Confirm. The screen shows "Checking…" for about one second.
- "Check-in recorded. Automatic sharing is off." Continue opens the dashboard.
With a wrong code: "Wrong code. Try again." After 5 attempts within a quarter of an hour, you have to wait.
A check-in from the account covers every pending session.
From the field phone
The phone that filmed is often the only device at hand. On its recording screen, in the settings panel, Check-in opens the same entry; the Check in from this phone link is also offered on the end screen. Same delay, same message, and the same 5 attempts per quarter of an hour, counted together with the account's.
Two differences from the account:
- The normal code checks in only this phone's session. The account's other sessions stay pending.
- The phone holds no key. On a duress code, it cannot prepare new accesses: only the contacts ticked when the session was created (standby access) receive the sharing. The other effects of the duress code are the same as from the account. The decoy account makes no sense on the phone, which displays nothing.
The phone stays write-only: it receives nothing back that would let it read or list anything.
The trade-off
A phone seized while unlocked is also a place where someone can demand your code. With the normal code, that person stops the session's automatic sharing. This is exactly the situation the duress code is for: enter it, the screen will show nothing different. The codes stay in your head, never on the phone.
Under duress
If someone forces you to check in, enter the duress code. The screen behaves exactly as it does with the normal code: same delay, same message. What it triggers in addition is described in Security and codes.
What checking in does not do
- It does not change the lock.
- It does not undo sharing that has already happened. If the reminders have already gone as far as sharing with contacts, they keep access; you can remove it from the session.
- It has no effect on sessions set to Immediate sharing: they are shared on receipt, by choice.
Forgotten code
You can change it from your account, in Security and codes. Both codes have to be set again together.
In the log
The check-in is recorded in the log of each session concerned: "Check-in done, automatic sharing disabled.", with its origin, account or phone. This entry is the same for both codes. The effects of the duress code (sharing with contacts, lock raised to 30 days) are recorded too: someone who later views your real account can see them.