support
contact
for bug reports, feature requests, or anything else — email okidooki_ag@icloud.com.
expect a reply within 2 business days. we are a small team; please be patient and include:
• your obliv user id (it's fine to share — it's just a public identifier)
• ios version and iphone model
• obliv version (settings → about)
• steps to reproduce the issue
getting started
obliv uses mutual contact exchange. there are no phone numbers, no usernames, no directory to search. two people can only communicate after each has added the other.
step 1 — share your id. open the contacts tab and tap "show my qr" (or copy your user id string). give it to the person you want to talk to, out of band (in person, over another channel).
step 2 — they add you. the other person opens contacts → "scan qr" or "add by id" and adds your identifier.
step 3 — you add them. they share their id with you. you do the same on your side.
step 4 — talk. only once both sides have each other in contacts will messages, calls, and key exchange succeed. if user A sends a message to user B but B has not added A back, the message will not be delivered to B's device — it is dropped at the protocol layer. this is intentional: it prevents spam, unsolicited contact, and enumeration of identifiers.
losing a contact is as simple as removing them. once removed, neither side can reach the other until both re-add.
frequently asked
i forgot my pin. can i recover my account?
no. obliv is designed with zero recovery. after 5 wrong pin attempts the app wipes your identity completely — this is intentional and cannot be overridden. you will need to create a fresh identity and re-share your user id with contacts.
why does obliv not use face id / touch id?
biometric unlock is vulnerable to physical coercion (someone holding your phone up to your face) and to forensic extraction tools. a pin that lives only in your head meets obliv's threat model.
why can't i take a screenshot of my chat?
obliv uses ios's secure display flag on sensitive screens (chats, your qr, your identity reveal). screenshots of those screens come out black. this protects you against malware that takes silent screenshots and against accidental screen recording.
do you see my messages?
no. messages are end-to-end encrypted. ciphertext passes through our infrastructure as an opaque blob. we do not have, and cannot obtain, the keys to decrypt it.
how do i add a contact?
contacts tab → "show my qr" (let the other person scan) or "scan qr" (scan theirs). alternatively "add by id" if you already know their user id string. no phone number exchange.
can i use obliv on multiple devices?
not yet. each identity is tied to the device that generated it. multi-device support is on the roadmap but intentionally deprioritised — it complicates the ratchet and widens the attack surface.
my call won't connect over mobile data.
obliv uses peer-to-peer connections with a relay fallback. if both peers are behind restrictive nats (some carrier networks), the relay is used automatically. if calls consistently fail to connect in normal use, please email support — it almost certainly means a routing issue.
the app is in english but i want polish.
obliv currently ships in english only. additional locales are planned. if you want to help translate, email support.
reporting abuse
because obliv does not store messages and cannot identify users beyond their self-published public key, we have very limited ability to act on abuse reports. for serious threats (credible violence, child sexual abuse material), contact local law enforcement; obliv will cooperate with valid legal process within the limits of what we technically know (public keys + push tokens, nothing else).
security disclosures
found a vulnerability? please email okidooki_ag@icloud.com before public disclosure. we commit to acknowledging within 48 hours and fixing critical issues within 14 days.