Who we are
Hasala (حصّالة) is a private budgeting app for iPhone, made for people in the United Arab Emirates. It is available as an invite-only beta through Apple’s TestFlight.
Hasala is run by Saleh Lootah, an individual based in the United Arab Emirates. He is the controller of the personal data this policy describes. Hasala is not a company. In this policy, “Hasala”, “we” and “us” mean him, as the operator of the app and of hasala.app.
We can be reached by email only; the addresses are under Contact.
This policy covers the Hasala iPhone app (App Store name “Hasala Budgeting”), the website at hasala.app, and the emails we send from no-reply@hasala.app. It describes the beta as it works today.
The short version
- Your bank emails are read on your iPhone. Hasala connects to your Gmail with read-only access. Your iPhone fetches only messages from your banks’ alert addresses. The emails themselves are never sent to our server.
- Your money data is sealed on your iPhone before it syncs. Your transactions, amounts, merchants, categories, budgets, bills and rules are encrypted on your iPhone before they leave it. Our server can’t read them.
- Our server still sees some things. It sees your email address and name, that your account exists, details about your sign-in methods and devices, when you sync and how much sealed data you store, and a keyed hash of your Gmail address with the timing of changes in your mailbox. From that timing it can tell roughly when, and how often, you get bank alerts, though not what they say. We list all of it below.
- No ads, no data sales, no AI services. Hasala sorts transactions on your iPhone. Today, nothing is sent to an AI service. If we ever offer an optional, AI-powered feature, it will be off by default, explained before you turn it on, and you can turn it off at any time. Data from your Gmail will never be used to train AI models (see Limited Use, below).
What stays on your iPhone
Some things never leave your iPhone. Others leave only in sealed form.
Never leaves your iPhone
- Your bank alert emails. Your iPhone downloads them from Gmail, reads them and keeps the details it needs: amount, merchant, date, card, and the Gmail message ID so it can find the email again. The email itself isn’t stored in your Hasala data and isn’t sent to us.
- Your Gmail access token. The token that lets Hasala read your Gmail is kept in your iPhone’s Keychain, on this iPhone only. Our server never receives it.
- Your settings for this iPhone. Examples are notification level, Hide amounts and Face ID lock.
Leaves your iPhone only in sealed form
- Your money data. Your transactions, budget and plan sync between your devices through our server. Before anything in them leaves your iPhone, it is encrypted with keys only your devices hold. This covers transactions, amounts, merchants, categories, notes, budgets, bills, accounts, goals, projects and rules. Our server stores this sealed data and passes it to your other devices. It cannot open it.
- Your encryption keys. The keys that open your data are created on your iPhone and kept in its Keychain, on this iPhone only. They aren’t included in iCloud or computer backups. Our server keeps only sealed copies of them, which your passkey or your recovery phrase opens, so that a new iPhone can unlock your data.
- Your 12-word recovery phrase. It is created on your iPhone. Our server keeps a sealed copy it can’t open, so that you can view the words again in Hasala with your passkey. We email you each time they’re shown. If you sign in with a password only, they can’t be shown again, so keep the copy you wrote down.
How your iPhone stores it
Hasala’s local database on your iPhone is protected by iOS data protection. It can’t be read after a restart until you unlock your iPhone for the first time. It is excluded from iCloud and computer backups. If you restore a backup to a new iPhone, Hasala downloads your sealed data again and unlocks it with your passkey or your recovery phrase.
Anyone who can unlock your iPhone can open Hasala and see your data. Face ID lock hides Hasala until you unlock it. It doesn’t change how your data is encrypted.
What we collect and why
This is everything our server receives or stores about you, and why.
Your account
| What | Why |
|---|---|
| Your email address (verified when you sign up) | To identify your account, let you sign in with a password if you choose one, and send you account emails such as verification and security notices. |
| Your display name | To show your name in the app and to greet you in emails we send you. |
| A random account ID, when your account was created, and its status (active, suspended or deleted) | To run your account. |
How you sign in
| What | Why |
|---|---|
| For each passkey: its ID, its public key, the type of authenticator, whether it is backed up, and when it was last used | To check that it’s you when you sign in with Face ID. A passkey’s private part stays in your passkey manager; we never receive it. |
| If you set a password: a scrambled form of it, never the password itself. Your iPhone scrambles your password with a deliberately slow, salted function before sending it, and our server stores only a further salted hash of that scrambled form. | To let you sign in with email and password. |
| Sealed copies of your account keys: one that only your 12-word recovery phrase can open, one for each passkey that only that passkey can open, plus related public keys | So a new iPhone can unlock your data with your passkey, and so you can get back into your account with your recovery phrase if you lose every device and passkey. |
| A sealed copy of your recovery phrase, which our server can’t open | So you can view your 12 words again in Hasala after confirming with your passkey. We email you each time they’re shown. |
| Sign-in sessions: a one-way hash of each session token, and when it was created, last used and ended | To keep you signed in, and let you sign out on every device. |
| Security actions and when they happened, such as “Gmail connected at 10:02” or “passkey added” | To protect your account and show you security alerts on your other devices. |
A password never unlocks your data. Only a passkey or your 12-word recovery phrase can do that.
Your devices
| What | Why |
|---|---|
| A random ID for each iPhone you add, and when it was added or removed | So your devices can trust each other’s changes, and so you can remove a lost iPhone. |
| Each iPhone’s push token from Apple | To send a silent signal that wakes Hasala on your iPhone when there is new mail or a change to sync. |
Sync
| What | Why |
|---|---|
| Your sealed data | To sync your transactions, budget and plan between your devices. |
| When each device syncs, a rough size for each upload, and how much sealed data you store | To keep sync in order, apply storage limits and stop abuse. |
Your iPhone uploads new transactions soon after a bank alert arrives. So our server, and Cloudflare in front of it, can tell roughly when, and how often, you get bank alerts. They can’t tell what the alerts say.
Gmail connection
| What | Why |
|---|---|
| A keyed hash of your Gmail address (a code made from it with a secret key) | So that when Google tells us your mailbox has changed, we know which iPhone to wake. |
| The timing of changes in your Gmail, such as new mail arriving or mail being read, archived or deleted | To wake Hasala on your iPhone so it can check for new bank alerts. This happens for every change, not only bank alerts. |
| When your Gmail notification setup next needs renewing | To remind your iPhone to renew it so alerts keep arriving. |
Your Gmail address reaches our server in two moments. The first is when you connect Gmail. The second is each time Google notifies us that something in your Gmail has changed. Our server uses the address to find the right account and then discards it. It stores only the keyed hash and never writes the address to its logs. If you also use that address as your Hasala email address, our server already has it, in plain text, as your account address. Because the hash is made from your address, someone holding our secret key could check whether a guessed address matches it.
Your IP address
Our server sees the IP address of each request, passed on by Cloudflare. It uses it briefly in memory to limit abuse, for example too many sign-in attempts. It does not write IP addresses to its logs or database.
Invites
| What | Why |
|---|---|
| A one-way hash of your invite code and of the key in your invite link, a keyed hash of the email address we sent the invite to, and when the invite was created, sent, used, or expired | To make sure only invited people can create an account, and that an invite link opened from your email confirms your address. |
| A short note we write when we create the invite, such as the first name of the person it’s for | To keep track of who we invited. |
30 days after an invite is used, expires or is withdrawn, we forget the note, the keyed hash of the address and the link key. An unused invite is then deleted. A used invite stays linked to your account as “invite used” until you delete your account; when you do, the link to your account goes too.
Your invite. When we invite you, we add your email address to Hasala’s beta on Apple’s TestFlight, and Apple emails you an invitation to install it. We don’t give Apple your name. Apple’s terms apply to your use of TestFlight. TestFlight tells us whether you accepted the invitation and when you install and open the beta. It also sends us crash reports, which don’t include your transactions, and any feedback you send through it. Testers never see each other.
If you’d rather Apple didn’t get your address. Tell us at support@hasala.app before we invite you, and we’ll send you TestFlight’s public join link instead. We switch that link on only while someone is waiting for it, with a limit on how many people can use it. You then join TestFlight with your own Apple Account, and we give Apple nothing about you; TestFlight doesn’t tell us who you are. You still need your Hasala invite to create an account.
When you create your Hasala account, we delete your address from the waitlist; your account keeps its own address and the name you give it. If you leave the list or delete your account, we remove you from the TestFlight beta. If you joined with the public link, we can’t tell you apart from other link testers, so we close your invite or account instead.
Bank requests
If you tell us in the app which bank you use and it isn’t supported yet, we link the request to your account so we can tell you when your bank works with Hasala. It’s deleted with your account.
On our website, you tell us your bank only when you ask for an invite (see The website).
Things you send us
| What | Why |
|---|---|
| Emails you send to our support, privacy or security addresses | To answer you. |
| Feedback and crash reports you send through TestFlight | Apple passes these to us. If you attach a screenshot, it may show your amounts and merchants, so check it before you send. |
The website
Asking for an invite. While sign-ups are handled by email, the invite form on hasala.app doesn’t send anything to us. It opens an email to support@hasala.app in your own email app, with the address and bank you entered, and we receive it only if you send it. We add the address the email comes from, not an address typed into it. We keep that email like any other support email (see How long we keep data) and use it only to add you to the waitlist.
Once the form sends sign-ups to our server, we store your email address, the bank you picked (and the bank name you typed, if you chose “Another bank”), how you reached us (for example, the website’s form), and the dates you asked, confirmed, were invited and joined. We email you a link to confirm the address, and you join the list only once you confirm it. If you don’t confirm it within 7 days, we delete it. A confirmed address stays on the list until you join Hasala or leave the list, and for 180 days at most. We use your address only to send your invite and to tell you when your bank works with Hasala, never for marketing. Every email we send has a link to leave the list, which deletes your address straight away. If you join Hasala, the bank you told us about moves to your account and stays with it until you delete the account. Only we review the list, in an admin tool that is reachable only from our own devices over a private network.
Bot checks. Our forms can use Cloudflare Turnstile to tell people from bots. When it’s switched on, Cloudflare looks at technical details from your browser, including your IP address, to decide; we receive only the answer.
Emails we send. We keep a record of each email we send you: what kind it was, the address, when we sent it and whether it was delivered. We never keep what the email said. These records are deleted after 30 days. If you delete your account, they lose your address straight away and keep only a masked form, such as m•••@example.com, until they’re deleted. The record of the email confirming the deletion loses your address as soon as that email has gone.
Cookies and analytics. The website sets no cookies. It counts visits with Cloudflare Web Analytics, which Cloudflare adds to its pages. Web Analytics uses no cookies or other storage in your browser, doesn’t fingerprint you and doesn’t follow you across other sites. We see only totals, such as visits per page, the sites visitors came from, browser and device types, countries and how fast pages load, never linked to you or to your Hasala account. Invite, freeze and waitlist links are not counted: their addresses carry personal codes, so on those pages (hasala.app/i, /freeze and /waitlist) the website’s security policy doesn’t let Web Analytics run. The Hasala app itself contains no analytics or tracking tools. Elsewhere, the website’s security policy lets it run only its own code and Cloudflare’s analytics script, plus Cloudflare Turnstile’s while bot checks are on. It remembers, in your browser and only for the open tab, that you’ve already seen the opening animation; that never leaves your browser.
What we don’t collect
- Your bank emails, or any other email in your Gmail.
- Your amounts, merchants, categories, budget or plan in readable form.
- Your recovery phrase or encryption keys in readable form, or your Gmail access token.
- Your contacts, location, photos or browsing activity on other sites.
The app contains no advertising, analytics or crash-reporting tools from other companies.
How we use your data
We use your data only to:
- provide Hasala: run your account, sign you in, sync your sealed data and wake your iPhone when new mail arrives;
- keep Hasala secure: stop abuse, investigate security problems and alert you to changes on your account;
- send you emails about your account, such as verification, password, security and beta notices;
- answer your messages;
- understand how the website is used, in totals (see Cookies and analytics); and
- meet our legal obligations.
We don’t sell your data. We don’t use it for advertising. We don’t use it to decide whether you get credit or a loan. We don’t use it to train AI or machine learning models.
Under the UAE Personal Data Protection Law, we rely on these grounds:
- Providing the service you asked for. This covers running your account, sync and push.
- Your consent. This covers connecting Gmail. You give it in Hasala’s Gmail step and on Google’s permission screen, and you can withdraw it at any time.
- Keeping the service secure. We have a legitimate interest in stopping abuse and protecting your account and other users’ accounts.
- Understanding how the website is used. We have a legitimate interest in counting visits to hasala.app, in totals that are never linked to you, to see which pages help people.
- Complying with the law.
Gmail and Google user data
Hasala asks Google for three permissions: openid and email, which give Hasala your Gmail address so it can match the connection to your account, and gmail.readonly, which gives read-only access to your Gmail.
What Hasala does with it
- Your iPhone, not our server, connects to Gmail.
- Your iPhone asks Gmail only for messages from your banks’ alert addresses, so the rest of your inbox is never downloaded. If Gmail’s search also returns an email that only looks like it’s from your bank, Hasala reads just its sender details on your iPhone and then sets it aside.
- From each bank alert, your iPhone keeps the amount, merchant, date and card, plus the Gmail message ID so you can open the original email later. These become transactions, which are encrypted on your iPhone before they sync.
- Hasala can’t send, delete, label or change your email.
- At launch, Hasala reads alerts from Dubai Islamic Bank (DIB) and Emirates NBD.
Limited Use
Hasala’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In practice, for data Hasala receives from your Gmail:
- Used only for features you can see. We use it only to find your bank transactions and show them in Hasala, and to let you open the original alert.
- No transfers, except as allowed. We don’t transfer it to anyone, except when needed to provide those features or to comply with the law. If Hasala were part of a merger, acquisition or sale of assets, we would transfer it only with your explicit consent, asked for first. In practice it isn’t transferred at all. The raw emails stay on your iPhone, and the details drawn from them leave only as sealed data our server can’t open.
- No ads. We never use or transfer it to serve ads, including personalised, retargeted or interest-based ads.
- No sales, no credit decisions. We never sell it, and we never use it to decide whether you get credit or a loan.
- No one reads your email. We don’t read it, and the design keeps it out of our reach. The only exception would be if you explicitly agreed to let us look at a specific email, for example to add support for your bank. Even then, you would choose the email and send it to us yourself.
- No AI training. We don’t use it to develop, improve or train AI or machine learning models. Hasala’s categorisation runs on your iPhone using Apple’s on-device model, and nothing from your Gmail is sent to an AI service.
Keeping and deleting it
- Your Gmail access token is kept in your iPhone’s Keychain, on that iPhone only, and is never sent to our server. When you disconnect Gmail, Hasala revokes it at Google and deletes it from the Keychain.
- Your bank alert emails are never stored by Hasala. Your iPhone reads each one and keeps only the details listed above.
- Those details (amount, merchant, date, card and Gmail message ID) are kept in Hasala’s encrypted database on your iPhone, protected by iOS data protection, and on our server only in sealed form that we can’t open. They stay until you delete them or your account.
- Your Gmail address is kept on our server only as a keyed hash, which is deleted when you disconnect Gmail or delete your account (see Gmail connection).
- Disconnecting Gmail stops Hasala reading your mail. Transactions it has already brought in stay in Hasala until you delete them.
- Deleting your account erases all of it from our server straight away, and from your iPhones. Encrypted backups that still hold sealed copies expire within 30 days.
Google’s verification screen
During the beta, Google shows a warning that it hasn’t verified Hasala. This happens because Google’s verification of apps that read Gmail is not yet complete for Hasala.
Stopping Gmail access
You can disconnect Gmail in Hasala under Profile › Bank alerts. Hasala then revokes its access at Google and stops Google’s new-mail notifications. You can also remove Hasala’s access in your Google Account under Security › Your connections to third-party apps and services. Deleting your Hasala account disconnects Gmail too.
Encryption in plain words
Your transactions, amounts, merchants, categories, budgets, bills and rules are encrypted on your iPhone before they leave it. Our server can’t read them. This is what we mean by end-to-end encrypted: the data is sealed on your iPhone and opened only on your devices, and our server stores and passes along only the sealed copies.
The keys that open your data are created on your iPhone. Your devices hold them, and two things can unlock them on a new device:
- your passkey, which you use with Face ID and which syncs through iCloud Keychain; and
- your 12-word recovery phrase.
Some things are not sealed. Our server needs your email address, your name and the account details listed above to run your account, so it can read them.
Hasala will never ask for your recovery phrase, your password or a code in an email, a notification, a phone call or on a website. Only type them into the Hasala app.
If you lose your recovery phrase and every passkey, your account can’t be recovered. Not even by us.
Notifications
Hasala writes its notifications on your iPhone. Our server only sends a silent signal through Apple to wake the app. It never sends what a notification says.
By default, notifications don’t show amounts or merchants. For example, you’ll see “New transaction” and “Tap to see it in Hasala”. You can turn on Show amounts and merchants in Settings › Notifications. If you do, amounts and merchants may appear on your Lock Screen.
Who else handles your data
We use a small number of service providers. None of them can open your sealed data.
| Provider | What they do | What they can see |
|---|---|---|
| Cloudflare | Network provider in front of our server, and host of the hasala.app website, where it also counts visits for us with Cloudflare Web Analytics. Encryption in transit ends at Cloudflare, which forwards requests to our server. | The requests between the app and our server, including your IP address, your email address and name when they are sent, and the sealed data. If you use a password, it also sees the scrambled form your iPhone sends when you sign in (see our Security page). It also sees what you send through the website’s forms, such as your email address and bank, and, when you visit the website, the pages you open, your IP address and your browser and device type. Web Analytics gives us only totals from these, never linked to you. Cloudflare cannot open the sealed data. |
| Cloudflare Email Service | Delivers the emails we send from no-reply@hasala.app. | Your email address and the content of those emails, such as a verification code. |
| Cloudflare R2 | Stores the off-site copy of our encrypted server backups. | Encrypted backup files only. Cloudflare doesn’t hold the key to open them. |
| Hosts your Gmail and tells our server when your mailbox changes. | Your mail, as it already does, and that you’ve given Hasala read-only access. Google also sees your iPhone’s IP address when it connects to Gmail. | |
| Apple | Distributes the beta through TestFlight and handles your TestFlight invitation, delivers silent push signals, and syncs your passkeys in iCloud Keychain. | When you install and open the beta, crash reports (which don’t include your transactions), any feedback you send, and push timing. For an invite: your email address, unless you asked for the public join link. Testers never see each other. Apple encrypts iCloud Keychain so that Apple itself can’t read your passkeys. Your Hasala database is excluded from iCloud backups. |
Emails you send to our @hasala.app addresses (support@, privacy@ and security@), including invite requests while the website’s form is handled by email, arrive through Cloudflare Email Routing, which forwards them to our email provider (Apple iCloud Mail), where we keep them like any other support email. Apart from that, we don’t use any other service provider that handles your personal data. Invites, our admin tool and, once sign-ups go to our server, the waitlist run on our own server.
Our server
The beta runs on hardware operated by the developer. It sits behind Cloudflare and accepts no connections except through Cloudflare. A small number of trusted people have administrative access to it; because your financial data is end-to-end encrypted on your iPhone, they can’t read it. Like our server, they can see the account details listed in What we collect and why, such as your email address and name.
Encryption of the server’s disks at rest is being added before the public launch.
Where your data is processed
Our server is located in the United Arab Emirates. Cloudflare, Google and Apple operate worldwide, so data they handle may be processed outside the UAE. When personal data leaves the UAE, we rely on the protections in the providers’ own data processing terms and on the cross-border transfer rules of the UAE Personal Data Protection Law.
How long we keep data
| Data | How long |
|---|---|
| Your account, sign-in methods, devices and sealed data | Until you delete your account. They are then erased from our server straight away. |
| Security actions (such as “passkey added”) | 90 days, or until you delete your account if that’s sooner. |
| Encrypted server backups | Made daily and kept for 30 days. After you delete your account, your encrypted data, keys and account details can remain in backups for up to 30 days. |
| Restore records | When you delete your account or leave the waitlist, and after some security changes (such as freezing your account, removing a device or changing your password), our server keeps a short record with a random ID and the time, so that restoring a backup can’t undo the change. These records never hold your email address or name. They are kept for 60 days. |
| Sign-in sessions | A session ends after 30 days without use, or after 90 days at most. Its record is removed 30 days after it ends. |
| Push tokens | Removed when you sign out, remove that iPhone, or delete your account. |
| Gmail connection (keyed hash) | Until you disconnect Gmail, remove the iPhone that reads it, or delete your account. Google may keep sending change notices for up to 7 days after that. We ignore them and store nothing from them. |
| Your old recovery data after you change your recovery phrase | Removed from our server straight away, so the old words stop working with it; may remain in encrypted backups for up to 30 days. Someone who already used the old words keeps what they got with them (see our Security page). |
| Invite records | Unused invites expire after 14 days, unless we set a different expiry. 30 days after an invite is used, expires or is withdrawn, its note, address hash and link key are forgotten, and an unused one is deleted. A used invite stays linked to your account until you delete it. |
| Server logs | Our logs never contain your email address, IP address, tokens or sealed data. They hold technical events and error codes, and your random account ID only when a server error affects your account. They have no fixed period: the oldest entries are removed automatically as the log storage fills up. |
| Admin records | A record of what we do in our admin tool, such as sending an invite, kept for 400 days. It refers to people only by internal IDs, never by email address or name. |
| Support emails | We keep them only as long as we need them to help you, and delete them when you ask. |
| Waitlist sign-up, not confirmed | 7 days. |
| Waitlist sign-up, confirmed | Until you join, leave the list, or 180 days after you confirmed, whichever comes first. |
| Bank requests from the app | Until you delete your account. |
| Email records | 30 days. We never keep what an email said. |
| Data on your iPhone | Until you delete your account or use Remove this iPhone. Signing out keeps your data on the iPhone. Deleting the app removes it from the iPhone. |
Deleting your account
You can delete your account in the app under Profile › Delete your account. You’ll be asked to confirm it’s you. Then:
- Hasala stops Gmail notifications and revokes its Gmail access.
- Our server erases your account, sealed data, keys, sign-in methods, devices and Gmail connection straight away.
- Hasala erases its data on that iPhone. Your other iPhones erase theirs the next time they connect.
- We send you one email to confirm the deletion.
Some things remain for a while afterwards:
- encrypted backups that still contain your data, until they expire within 30 days;
- our records of the emails we sent you, with your address masked, until they’re deleted after 30 days;
- the restore record of the deletion, which holds only your random account ID, for 60 days;
- admin records that refer to you by an internal ID only, for up to 400 days;
- Apple’s TestFlight record of you, until we remove you from the beta (after that, Apple’s own retention applies); and
- Cloudflare’s own records of delivering our emails, under Cloudflare’s retention.
Your passkey stays in your passkey manager until you delete it there, for example in the Passwords app. Step-by-step instructions are on our Support page.
If you can no longer open the app, email privacy@hasala.app from your account’s email address and ask us to delete your account. To make sure the request is really yours, we’ll reply to that address and ask you to confirm before we delete anything. We’ll also delete your waitlist entry, if you still have one.
Security
Security is built into how Hasala works:
- Data is sealed on your iPhone with modern authenticated encryption, and the server refuses data that isn’t sealed.
- Sign-in with Face ID uses passkeys.
- Sensitive actions, such as connecting Gmail, adding a device, viewing your recovery phrase or deleting your account, ask you to confirm it’s you again. With a passkey, that’s Face ID. If you sign in with a password only, it’s your password, entered on an iPhone already added to your account, which also checks your Face ID or passcode.
- Our server accepts connections only through Cloudflare, and its logs exclude email addresses, IP addresses, tokens and sealed data.
- Backups are encrypted, and the key to open them is not kept on the server.
No system is perfectly secure. Our Security page explains the design, its limits and how to report a problem.
Your rights
Under the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021), you have the right to:
- Access. You can ask what personal data we hold about you, why, who we share it with and how long we keep it.
- Portability. You can ask for your data in a structured, machine-readable form.
- Correction. You can ask us to fix data that is wrong or incomplete.
- Erasure. You can ask us to delete your data.
- Restriction. You can ask us to limit how we use your data, for example while a dispute is settled.
- Objection and withdrawal of consent. You can ask us to stop processing your data, and you can withdraw consent, such as Gmail access, at any time.
- Automated decisions. You can object to decisions based only on automated processing that have legal or similarly significant effects on you. Hasala makes no such decisions about you. Categorisation is a suggestion on your own iPhone, and you can change it.
Because we can’t open your data
Because your transactions, budget and plan are sealed, we can’t read them, so we can’t hand them over in readable form. You can export them yourself from the app as a CSV file, under Settings › Export your data. What we can give you on request is the account data listed in What we collect and why.
How to exercise your rights
Email privacy@hasala.app from the email address on your account. We’ll reply as soon as we can, and within the time the law requires. We may ask you to confirm the request in the app, or by replying from that address, so that we know it’s you. We don’t charge for requests.
If you’re not satisfied with our answer, you can complain to the UAE Data Office.
Children
Hasala is for adults. You must be at least 18 to use it. We don’t knowingly collect data from children. If you think a child has created an account, contact us and we’ll delete it.
Changes to this policy
We’ll update this policy when Hasala changes. The date at the top shows when it last changed. If a change materially affects how we use your data, we’ll tell you in the app or by email at least 30 days before it takes effect.
Contact
We can be reached by email only.
- Privacy questions and requests: privacy@hasala.app
- Security reports: security@hasala.app
- Everything else: support@hasala.app, or see our Support page.