Security
Your portfolio is encrypted on your iPhone. We hold the unreadable result; you hold the key.
Last updated: 8 November 2026
In one sentence
Raqib encrypts your portfolio on your device with a key that never leaves it, so our servers store data we are not able to read.
How the encryption works
- When you set up your portfolio, your iPhone generates a 256-bit encryption key and stores it in the device keychain. It is marked device-only and non-syncable, so it is not copied to iCloud and not restored onto another device from a backup.
- Your holdings, purchase lots, commodity purchases, watchlist and saved backtests are gathered into one structure and encrypted with AES-256-GCM before anything is sent.
- What reaches our servers is a single block of unreadable bytes per account, plus a counter used to stop two devices overwriting each other.
- Every decryption is authenticated. If a stored block were altered by even one bit, your app would reject it rather than show you something wrong.
- Portfolio value, gains, dividend estimates, projections and backtests are computed on your device from your own records, using decimal arithmetic rather than floating point, and are never transmitted.
Your recovery code
- Because the key lives on your device, a new device needs a way in. That way is a recovery code your iPhone generates — 25 characters, machine-generated, never chosen by you and never seen by us.
- Your device uses that code to wrap a copy of your encryption key. We store only the wrapped bytes and the public parameters needed to unwrap them; without the code they cannot be unwrapped, including by us.
- Synchronisation is not switched on until you have been shown the code and typed it back, so a portfolio is never quietly protected by something you did not save. On a first device you may postpone this step, and the app reminds you until it is done.
- After you confirm it, the code is never shown again unless you deliberately generate a new one, which requires unlocking your device with Face ID, Touch ID or your passcode.
The consequence, stated plainly
If you lose every device you use Raqib on and your recovery code, nobody can recover your encrypted portfolio — including us. Your account still works and you can start again, but the old data stays unreadable. There is no master key we are choosing not to use; there is no master key at all.
What the Raqib team can and cannot access
What we can see
- Your username and email address, because signing you in and sending verification codes requires them, along with your account’s status and when it was last active.
- That an account exists, that it has an encrypted portfolio, roughly how large that block is, and when it last changed.
- Any price alerts you created — the company and the target price — and the push token that lets Apple deliver a notification to your phone.
- Aggregate, non-financial usage counts, and service health, such as uptime, response times and market-data status.
What we cannot see
- Your holdings, share counts, purchase prices, dates or cost basis.
- Your portfolio’s value, your gains or losses, your dividend estimates, projections or backtests.
- Your watchlist, your commodity purchases or what your portfolio notifications said.
- Any statement you imported — not the file, not its name, not the text read from it.
These limits are built into how Raqib works, not only into rules we follow. When the Raqib team looks up an account, it sees account details and nothing else: the email address, the username, when the account was created, whether its email is verified, its status and when it was last active. Nothing available to the team can reach your holdings, your portfolio’s value, your watchlist, the contents of your encrypted portfolio, your password, your recovery code or any encryption key.
On your phone
- App lock: you can require Face ID or Touch ID to open Raqib. It is off until you turn it on, and turning it off again needs the same device authentication.
- Face ID sign-in: if you choose Remember me, your email and password are kept in the device keychain behind the biometry you enrolled, so a later sign-in needs your face rather than your typing. It is switched off automatically if your enrolled biometry changes.
- The connection to our servers is pinned to the certificate authority that issues our certificate, in addition to the usual HTTPS checks.
- The app covers its contents in the app switcher, and copies your recovery code with the narrowest clipboard settings iOS offers: the item expires, is not shared with other apps, and is not sent to your other devices.
- The app refuses to run on a jailbroken device, because such a device could read the portfolio while it is decrypted.
- Your device keeps an encrypted copy of your portfolio so the app works without a connection. Edits made offline are saved immediately and synchronised when you are back online.
- If you edit on two devices before they sync, your device decrypts both versions locally and asks what to keep, defaulting to keeping everything from both. Our servers never merge anything, because they cannot read either version.
- Signing out removes the encryption key from that device. Another phone needs your recovery code.
How we check that this is true
These are not just design intentions. Our automated tests encrypt a portfolio containing unique marker values, store it the way the real app does, and then search for those markers everywhere on our side where they could leak — stored data, logs and the contents of every network request. The tests fail if a marker is found anywhere.
We describe our own engineering work here. Raqib holds no security certification and has not been independently audited, and we do not claim otherwise.
Security in brief
Your portfolio is encrypted on your iPhone before it is synced, so Raqib cannot read it.
Your recovery code is the only way to restore your portfolio on a new iPhone. Raqib cannot recover it for you, so keep it somewhere safe and never share it.
When you sign in on a new device, we email you a 6 digit code to confirm it is you.
Reporting a security concern
If you believe you have found a vulnerability, please write to us with enough detail to reproduce it, and give us a reasonable opportunity to fix it before publishing. We will confirm that we received your report.