Privacy Policy

Floosi is a personal finance assistant on WhatsApp and on the web that helps you follow your spending from bank statements you upload yourself. This policy explains what we process, why, who we share it with, and how you control it.

1. Data controller

The data controller for the purposes of Jordanian Personal Data Protection Law No. 24 of 2023 is:

2. What we process

• Identity and contact: your WhatsApp number or the email address you register with, a display name if there is one, and the date and version of the terms you accepted when you signed up.
• Documents you upload: the PDF, Excel or CSV statements you send yourself.
• Extracted transaction data: dates, amounts, currencies, descriptions, categories, balances and account names.
• Recordings of your voice: if you send a voice note to the bot or use the microphone in the web app. The recording is turned into text and then dropped; we never write it to disk and keep no copy, and what is saved is the text alone, as part of your conversation history.
• What you enter: budgets, savings goals, debts, loans, folders, people and category corrections.
• Subscription data: your plan, trial dates and usage history. We do not process your card details — they are entered into our payment provider's own secure fields and never reach us. When you buy a plan we also collect the name and billing address the provider requires, and we keep a record of each payment: our reference, the plan, the amount, the currency and the date.
• Operational data: limited technical logs for security and fault diagnosis, holding as little personal data as possible.

3. Legal basis and purpose

We process your data on the basis of your explicit consent when you begin using the Service, and on the necessity of performing the contract between us under the Terms & Conditions. The purposes are limited to: reading your statements and categorising your transactions; answering your financial questions; producing budgets, reports and financial statements; managing your subscription; and protecting the Service from abuse.

4. Encryption — and why we cannot read your data

Your financial data is stored in a separate database belonging to you alone. Encryption is required: before you can use the app or the bot you set a passphrase, and your database is encrypted at rest with AES-256-GCM using a key derived from it. We hold neither the passphrase nor the key, and the data is decrypted only during your active session, so the company's staff and operators cannot read the contents of your financial data.

That requirement has a price, and we say it plainly: the passphrase is yours alone, so if you forget it we cannot recover your data — not a policy we chose, but a consequence of not holding the key. You acknowledge this when you create your account.

An account created before encryption became required (26 August 2026) and not used since stays as it was until its owner returns, when setting a passphrase is the first thing shown.

Your account record — logins, plan, trial dates and language — is kept separately from that and is encrypted at rest with a key the Service manages. A third database holds currency exchange rates only, and no personal data.

5. Who we share with, and transfers outside Jordan

We share only what is necessary, with providers acting as processors on our behalf under contractual obligations:

• Parseur Pte. Ltd. (Singapore) — the PDF statements you upload are sent there for automated extraction. Those files are transferred to its servers and are subject to its own retention policy. Spreadsheets never reach it — XLSX and CSV files are read on our own server and never leave it.
• OpenRouter, Inc. (United States) — limited transaction data is sent there to generate answers, summaries and automatic categorisation. OpenRouter does not run the model itself; it routes the request to one of the companies that do. If you send a voice note or use the microphone in the web app, the recording of your voice takes the same route to be turned into text, and the text is then handled exactly as a typed message.
  
  Our account is set so that OpenRouter may only use companies that operate under Zero Data Retention: they do not store what we send and do not use it to train models. That setting is a refusal, not a preference. A company that does not operate that way is rejected before the request reaches it, so a request that cannot be served on those terms fails rather than being served by someone who would keep it. The condition covers speech-to-text as well as text.
  
  The models are open-weights builds running on the serving company's own hardware — today DeepSeek V4 Pro for answers and categorisation and Whisper for speech — so your data does not reach DeepSeek, OpenAI or any other laboratory that published those weights. If a model we have pinned is withdrawn or refused, the request moves to another open-weights model we pinned in advance, under the same condition; we never move a request to a model or a company we have not named to ourselves first.
• Resend (Ireland) — verification and password-reset email. It receives your email address and the code sent to it, and nothing else.
• HyperPay — our card payment provider, with Arab Bank as the acquiring bank. When you buy a plan, the payment page and its card fields are served from the provider's own platform, which is hosted outside Jordan: it receives your card details directly, together with your email address, the name and billing address you enter and the amount, under its own privacy policy. We never receive the card number, the expiry or the security code.
• Meta Platforms — WhatsApp — the channel carrying messages between you and the bot, subject to WhatsApp's own terms and privacy policy.
• WafaiCloud (Riyadh, Saudi Arabia) — the servers Floosi and the web app at app.floosi.net run on, and where your database is stored.
• Google LLC (United States) — only if you choose to sign in with Google. We ask Google for your email address and nothing else, and Google learns that you signed in here. Your financial data is never sent to Google, and if you sign in with a password instead, Google receives nothing at all.
• Cloudflare, Inc. (United States) — serves our public website, floosi.net, and sees the ordinary network details of a request for a page there, including your IP address. The web app and the bot do not pass through it, so no statement, transaction or account data reaches it.
• Exchange-rate sources — exchangerate-api.com, the open currency-api dataset and frankfurter.app, used to convert between currencies. We fetch a public table of rates against the US dollar from them. Nothing about you is sent to them — not an amount, not a transaction, not an identifier — and the conversion happens on our own server.

What is never sent to any of them: your encryption passphrase, the keys to your database, and the database file itself — no processor ever receives your complete financial records. What is sent is set out above, processor by processor: the PDF statement to the extraction provider, and the transaction data needed to answer a question to the AI provider.

In the web app the text transcribed from your voice is placed in the message box for you to read, and nothing is sent until you press send. It is a proposal, not a submission: if the transcription is wrong you edit it or delete it, and words you never said never enter your record. Anything you had already typed is kept — the transcript is added to it rather than replacing it.

6. Statement files

The statement file you upload is passed to the extraction provider without being saved as a file on our server; what we keep is the transaction data extracted from it, held as described in clause 4.

The file itself stays with the extraction provider for 90 days and is then deleted. That 90 days is a setting we choose on our own mailbox there, not a schedule it imposes on us — we say so because a policy that hands a processor the responsibility for a setting its customer controls sends the reader to the wrong party to ask. Its own policy says a deleted document leaves its active systems immediately and its backups within 45 days.

7. Retention and deletion

We keep your transaction data for as long as your account exists, because that data is the Service. An account that ends without a plan is deleted by us, on a schedule: an account whose free trial ended without a payment is deleted 32 days after the trial ended, and an account that has ever paid is deleted 90 days after its last paid month ended. That deletion is the same one described below; a plan keeps the data, and deleting it sooner is yours to do at any time. You can delete your account and everything in it at any time, from the web app's settings or by sending the deletion request to the bot; both run the same code, because this product has one deletion path and no second one. On deletion:

• Immediately: your database and its salt, your logins, every active session and the account record itself are removed from live systems. That includes the copies most products forget: if two of your accounts were ever merged, the retired side's database and the snapshot kept to make that merge reversible go too, so no readable duplicate is left anywhere.
• Up to 28 days: a copy of you may remain in a backup taken before the deletion. The Floosi server keeps 7 daily and 4 weekly copies, which then age out on their normal cycle.

Backups are never opened, searched or edited to remove one record; they age out in rotation within the period above, and are only ever used to bring the Service back after a failure. A backup carries exactly the encryption the live file had: if you switched encryption on, the copy is unreadable to us as well; if you did not, the copy is no better protected than the original. We may keep billing records for the period required by Jordanian income and sales tax law.

8. Your rights

Under Personal Data Protection Law No. 24 of 2023 you have the right to:

• access your data and know how it is processed;
• correct or update inaccurate data;
• delete your data — available to you directly, at any time;
• object to or restrict processing;
• withdraw your consent at any time, without affecting the lawfulness of processing before that;
• lodge a complaint.

To exercise any of these, write to info@almaseer.co and we will respond within the period set by law.

9. Complaints

If our response does not satisfy you, you may complain to the Personal Data Protection Unit at the Ministry of Digital Economy and Entrepreneurship, the supervisory authority in the Hashemite Kingdom of Jordan.

10. Security

We apply technical and organisational measures including encryption in transit always, and at rest whenever you have switched it on (clause 4), a separate database per user, administrative server access restricted to a private network, and backups that carry their source's encryption. No system is completely secure, but the design aims to keep the contents of your data unreadable even to the people who run it.

11. Children

The Service is for people aged 18 and over. We do not knowingly collect minors' data, and we delete it if we discover we have.

12. Changes to this policy

We may update this policy. The last-updated date appears at the top of the page, and we will notify you of any material change through the bot or by email before it takes effect.

13. Language

The Arabic version is the legally binding text; this English version is for convenience only.

14. Contact

info@almaseer.co · +962 77 147 7178 · Office 1, 5th floor, Building 150, Wasfi Al-Tal Street, Tla' Al-Ali, Amman, Jordan.