I’m one of the trusted contacts for my boyfriend, who uses Opal to block distracting apps. Right now, if he needs a bypass, we have two options: physically be there to enter the PIN ourselves, or tell him the PIN remotely - but the second option means he now knows that PIN permanently, until one of us manually resets it to something new he doesn’t know. Neither option is great: one requires us to be physically present, the other quietly defeats the whole point of a trusted-contact system.
Feature request: support TOTP (the same rotating 6-digit code standard used by Google Authenticator, Authy, etc.) as an alternative unlock method. My boyfriend (the user) would generate a secret key in Opal once, and my his brother and I would each load it into our own authenticator app. When he needs a bypass, we could read him the current live code remotely - but since it expires in seconds, he only gets access for that one instance. He never learns anything reusable, so we can help remotely without ever handing him a permanent key.
I saw this was raised before as a general “send a generated password to a contact” idea, but TOTP would solve that more cleanly, since nothing has to be manually reset between uses.
Alternative is Opal auto generating the codes that are auto sent to one of his shared contacts if he triggers it.