Privacy Policy

Your portfolio is encrypted on your device before synchronisation. We cannot read its contents.

Last updated: 8 November 2026

The short version

Your holdings, purchase lots, commodity purchases, watchlist and saved backtests are encrypted on your iPhone with a key that never leaves your device. Raqib stores only the encrypted result and cannot read it. Your account details are stored normally, because we need them to sign you in. Two things are deliberately outside that encryption — price alerts and push notifications — and the sections below say exactly what each involves.

What we store, and whether we can read it

  • Your portfolio — holdings, share counts, purchase prices and dates, commodity purchases, watchlist and saved backtests — is encrypted on your device. We store only the encrypted result and cannot read it. Neither can the Raqib team, our hosting provider, or anyone who obtained a copy of our data.
  • Portfolio value, gains, dividend estimates, projections and backtests are calculated on your device and are never sent to us.
  • Imported statements — CSV, Excel, PDF, photo or scan — are processed entirely on your device. The original file, its filename and its extracted text are never uploaded and never stored on our servers.
  • Your account — your username, your email address and a hash of your password — is stored so we can sign you in and send verification codes. This is not end-to-end encrypted, because we need your email address to deliver those codes.
  • A device identifier — a random value the app generates on your iPhone and keeps in the device keychain. It is sent with your requests so that we can keep you signed in, recognise a device you have already verified, and end a session. It is not Apple’s advertising identifier, we never share it, and it is removed when you delete your account.
  • Price alerts, if you create any — the company and the target price you chose, in readable form. The alert has to be evaluated on our server so that it can reach you while the app is closed, and a condition cannot be checked without being read. The alert row holds nothing else: no share count, no cost, no portfolio value, and nothing about whether you own the company at all. Deleting an alert deletes that row.
  • A push-notification token, if you allow notifications — the token Apple issues for your device, the platform, and the language you chose, so a notification can be delivered and written in your language.
  • A record that you accepted the in-app terms — which version, in which language, from which app build, and when. Raqib asks for this agreement before the app opens, and keeps the record so it can show you what you agreed to.
  • Optional details, if you choose to give them — a first and last name, a date of birth, and a phone number. Every one of them is optional: the app works exactly the same without them, and you can clear any of them at any time from the account screen. Unlike your portfolio they are stored in readable form, because the point of them is that we can use them. We do not verify your phone number and we do not send you messages on it today.
  • Product-interaction analytics — a fixed list of non-financial events, such as completing sign-up, verifying your email, signing in, or saving your encrypted portfolio. These records cannot contain your holdings, tickers, amounts, watchlist or imported content; that restriction is enforced in code, not by policy alone. They are stored against a pseudonym rather than your account name, but we hold the key that produces that pseudonym, so we treat this data as linked to you rather than claiming it is anonymous.

Why we use each item, and how long we keep it

  • Your username and email address are used to run the app itself: to create and sign in to your account, to send verification codes, to reset a password, and to greet you by name. We keep them for as long as your account exists, and they are removed when you delete it.
  • Your encrypted portfolio is used only to synchronise it between your own devices and to restore it when you sign in again. We keep it for as long as your account exists, and it is removed when you delete it.
  • The device identifier is used to run the app securely: to keep a session alive, to recognise a device you have already verified, and to end a session. Sessions end after 30 minutes without use. The identifier is removed when you delete your account.
  • Price alerts are used only to check the delayed price against your target and to send you that one notification. They are kept until you delete the alert or your account.
  • The push token is used only to deliver the notifications you turned on. It is removed when you delete your account.
  • Product-interaction analytics are used only to understand how Raqib is used in aggregate — how many people signed up, how many are active, which app versions are in use. Detailed records are deleted after 35 days; only aggregate counts remain after that.
  • None of it is used for advertising, for building a profile of you, or for tracking you across other companies’ apps or websites, and none of it is sold or shared for those purposes.

Who else is involved

  • Apple, for notification delivery and App Store services. A price-alert notification is written on our server and delivered by Apple, so its text — which names the company and the price — passes through Apple’s systems, on Apple’s infrastructure outside Kuwait, like every iOS notification. Portfolio notifications work differently and deliberately: the server sends an empty signal, your device reads its own decrypted portfolio, and your device writes the notification. Our server never learns what it said.
  • TradingView, whose chart is embedded in the app. Opening the Advanced chart on a company page, or the index card when Raqib has no index history of its own, connects your device to TradingView directly, so TradingView receives your device’s network address the way visiting any website would. Raqib keeps that chart in a browser view that retains nothing after you close it, and reads no value out of it. It is the only third-party code the app runs.
  • Yahoo Finance and the news publisher are contacted by our servers, not by your phone. Your device never sends anything to them.
  • When you choose a password, we check it against the Have I Been Pwned breached-password service using only a short fragment of a one-way hash of it — the password itself is never sent, and nothing about you is.
  • Our servers are operated for us by a cloud hosting provider outside Kuwait, and this website is served by Cloudflare (see below).

What we do not do

  • We do not have a master key, a support key, or any other back door to your portfolio.
  • We do not sell your personal data, and we do not share it with anyone for advertising.
  • The Raqib team cannot view your portfolio, its value, your watchlist or your imported documents. What we can look up about you is your account details — your username, your email address, when you joined, when your account was last active, and, when a support request needs it, the optional details you chose to give us — and that limit is built into how Raqib works, not only a rule we follow.
  • We do not include third-party advertising, analytics software or tracking software in the app. The embedded TradingView chart is third-party code and is described above.

Recovery — please read this part

Because your portfolio is encrypted with a key only you hold, if you lose every device you use Raqib on and your recovery code, your encrypted portfolio cannot be recovered by anyone, including us. Keep your recovery code somewhere safe and offline.

There is no Raqib master key, and no way for the Raqib team to recover your portfolio. Support cannot unlock it, because Raqib never has the key. Resetting your account password does not affect your encryption key or your portfolio.

Analytics and retention

  • Analytics events are limited to a fixed list of generic, non-financial facts, such as “the app was opened” or “an import succeeded”.
  • Where we count how many distinct people were active, we use a pseudonym made from your account identifier with a secret key, rather than the identifier itself. Because we hold that key, we do not claim the data is anonymous. We treat it as linked to you.
  • Detailed event records are deleted after 35 days. What remains after that is aggregate counts only.
  • Where we show a breakdown internally, groups smaller than 20 people are withheld so a small group cannot be identified.

How we protect it

  • Your portfolio is encrypted on your device with AES-256-GCM before any of it is sent, using a key derived on your device that we never receive.
  • Everything the app sends travels over HTTPS, and the app additionally pins the certificate authority that issues our server’s certificate, so a certificate installed on a phone by someone else cannot read the connection.
  • Your password is never stored in readable form. We keep only a scrypt hash of it, with parameters chosen against current OWASP guidance, and we refuse passwords that appear in known breaches or on common-password lists.
  • Sign-in tokens are stored as hashes rather than in readable form, sessions expire after 30 minutes without use, and the device identifier lets us require a fresh verification code on a device we have not seen before.
  • On your phone, the app can be locked behind Face ID or Touch ID, covers its contents in the app switcher, copies your recovery code with the narrowest clipboard settings iOS offers, and refuses to run on a jailbroken device.
  • Access is limited by how Raqib is built, not only by policy: nothing the Raqib team uses can reach an encrypted portfolio, a password, a recovery code or an encryption key, and account details are available only as described above.

This website

Everything above is about the Raqib app. This website is separate, and it is not silent: serving any page leaves a technical trace, and we would rather describe it than imply there is none.

  • This site is hosted on Cloudflare Pages. To serve and protect it, Cloudflare processes limited technical information on our behalf — your IP address, request metadata such as the page requested, the time, your browser and device type and an approximate location derived from the IP address, together with security logs used to block abuse. We use this only to keep the site available and defend it; we do not use it to build a profile of you, and we do not combine it with your Raqib account.
  • The site sets no cookies, runs no analytics, embeds no advertising or tracking software, and loads nothing from any third-party origin. It stores no settings or identifiers in your browser: choosing a language simply opens that language’s pages. The site sends nothing to us.
  • If you write to one of our published addresses, we receive and process your message, your email address and whatever you choose to include, for the sole purpose of answering you. Email reaches us through Cloudflare Email Routing and our mail provider. We keep correspondence only for as long as the enquiry and any follow-up need it.
  • Please do not email us screenshots of your holdings or your account password. We do not need them, and an email is not encrypted the way your portfolio is.

Deleting your account

You can delete your account from inside the app at any time: open Settings from the menu button at the top of the Overview tab, scroll to the Account section and choose “Delete account”. You confirm with your password and a verification code we email you. Step-by-step instructions, including how to export a copy first, are on the Delete Account page.

  • Deletion is immediate, not scheduled. Your account record — your username, your email address and any optional details you gave us — your encrypted portfolio, your recovery information, your price alerts, your registered devices and your sessions are removed together, at the same moment.
  • The record that a deletion happened is kept without your identity attached, so we can account for the event without retaining who it was.
  • Pseudonymous analytics events age out on their normal 35-day schedule. Aggregate counts that were already tallied — for example that one account was deleted on a given day — do not identify you and are not removed.
  • Notifications already delivered to your phone are yours to remove, and backups are overwritten on their normal cycle rather than instantly.
  • If you have lost access to your device and cannot delete the account yourself, write to us from the email address on the account and we will close it for you. We will never ask you for your password or your recovery code.

Honest limits

  • A device that has been compromised — by malware, or by tampering with the operating system — could read your portfolio while it is decrypted on that device. Our guarantee is that our servers and the Raqib team cannot read it, not that a compromised phone is immune.
  • Your username and email address are stored in readable form, because sign-in and verification codes require them. So are the optional details above, if you gave them, and any price alerts you create.
  • Anyone with access to our systems can see that an account exists, that it has an encrypted portfolio, roughly how large that encrypted block is, and when it last changed — but never what it contains.
  • We describe our own security work honestly. We do not hold a security certification and we have not been independently audited.

Contacting us about privacy

Privacy enquiries

privacy@myraqib.com

Questions about this policy, or a request concerning your data.

General support

support@myraqib.com

Help with the app or your account.