Cookie and Device Storage Policy
What the website keeps in your browser, what the app keeps on your device, whether it reaches us, and how to clear it.
1. What this policy covers#
1.1 This policy explains what the Platform stores on your device and reads back from it. These are four different things, and this policy keeps them apart:
- cookies — small text files saved by your browser, used only on the website;
- local storage and session storage — space the browser gives a site to keep small pieces of data;
- app storage on your phone — the app's own storage. It is not a cookie, and no cookie is used inside the app;
- the notification token — an identifier the mobile app registers with us so notifications can reach your device.
1.2 It supplements the Privacy Policy, which governs personal data generally.
1.3 The controller for the technologies described here is FAWRAN LLC, operating under the trade name FAWRAN. Its details are in the Privacy Policy and in the “Operator and contact details” section at the foot of this document.
There is no cookie banner on the Fawran website, because there is nothing on it to consent to. The website sets no advertising cookie and no cross-site tracking cookie. What follows is the complete list of what we actually use.
2. What the website stores in your browser#
2.1 Needed for the service to work#
| Name or type | Where it is kept | Does it reach Fawran? | Purpose | Duration |
|---|---|---|---|---|
fawran_market | Cookie | Yes — sent with each request | Remembers which market you are browsing so the right Items and prices are shown | Persists between visits until deleted |
| Sign-in session data | Browser storage managed by the sign-in provider | Yes — the session token authenticates your requests | Keeps you signed in across pages without entering a new code each time | Until you sign out or the session expires |
| Payment provider identifiers | Set by the payment provider on payment pages | Reaches the payment provider, not us | Fraud detection on the payment and protection of your card | Set by that provider's policy |
| Infrastructure identifiers | Set by the hosting provider | Reaches the hosting provider | Request routing, load balancing and service protection | Short |
This category cannot be switched off from inside the Platform, because it is what makes the service work. You can block it in your browser settings, but doing so will break sign-in, the cart and checkout.
2.2 Kept only on your device, and never sent to us#
| Name | Where it is kept | Purpose | Cleared when |
|---|---|---|---|
cartItems | Local storage | Your cart contents, so a page refresh does not lose them | The cart is emptied, or browser data is cleared |
wishlist | Local storage | Items you saved | You remove them, or browser data is cleared |
recentlyViewed | Local storage | The Items you looked at most recently | Browser data is cleared |
followingVendors | Local storage | Stores you chose to follow | You unfollow, or browser data is cleared |
fawran_search_history | Local storage | Your last ten searches, shown back to you in the search box | You clear an entry or the list, or browser data is cleared |
fawran_language | Local storage | Whether you chose Arabic or English | Browser data is cleared |
None of the six above is uploaded to Fawran or attached to your account. They exist so the interface remembers what you were doing.
2.3 Measuring sponsored placements inside Fawran#
| Name | Where it is kept | Does it reach Fawran? | Purpose | Duration |
|---|---|---|---|---|
fawran_ad_session | Session storage | The identifier is sent with a placement event | Links a sponsored-placement view to a tap and to a resulting Order, so the placement can be billed and measured | Ends when the tab is closed |
2.3.1 These are internal placements. We show Items and offers from within Fawran, and we place no third-party advertising network on the Platform that follows you across other sites.
3. What the mobile app stores on your device#
3.1 The app does not use browser cookies. It uses its own on-device storage instead:
| What is used | Does it reach Fawran? | Purpose | Cleared when |
|---|---|---|---|
| App storage (session) | The session token authenticates your requests | Keeps you signed in | You sign out, or the app's data is cleared |
| App storage (preferences, cart, wishlist, recently viewed, search history, language, market) | No | Remembers what you were doing | The app's data is cleared, or the app is uninstalled |
| Notification token | Yes | Delivering order and shipment notifications to your device | You turn notifications off, sign out, or the account is deactivated |
| Image cache | No | Avoids downloading the same product image twice | The app's cache is cleared |
3.2 The system permissions the app requests — camera, photo library, location, notifications — and the purpose of each are set out in the Privacy Policy and in the app's store listing.
4. How to control it#
4.1 From inside the Platform#
- Language: change it with the language switcher; the stored value updates.
- Market: change it with the market selector.
- Search history: remove a single entry, or clear the whole list, from the search box.
- Cart and wishlist: empty them, and the stored value goes with them.
- Notifications: turn categories on or off in account settings — see the Communications and Marketing Preferences Policy.
4.2 From your browser#
Every modern browser lets you block or delete cookies, clear local storage, and browse in a private window.
Blocking the category in section 2.1 breaks sign-in, the cart and checkout. Clearing local storage loses your unconfirmed cart, your wishlist and your language choice; it does not affect Orders already recorded in your account.
4.3 From your phone#
In your phone's system settings you can turn notifications off and withdraw the camera, photo-library and location permissions. Clearing the app's storage, or uninstalling it, removes everything in section 3.
5. Legal footing#
5.1 The categories in 2.1 and 3.1 are processed in order to provide the service you requested, and there is no separate switch for them because the service cannot run without them.
5.2 The values in 2.2 never leave your device, so no transfer of personal data takes place at all.
5.3 The placement identifier in 2.3 is used to bill and measure placements inside the Platform, on the footing set out in section 4 of the Privacy Policy. You may object to it under Article 4(B)(6) of the Personal Data Protection Law No. (24) of 2023 by writing to the privacy contact address.
5.4 Withdrawing a consent does not make what happened before it unlawful, and it carries no financial or contractual consequence for you, under Article 4(C) of the Law.
6. Other parties that may set identifiers#
| Party | When | Why |
|---|---|---|
| The sign-in, database and storage provider | Throughout your use of the Platform | Running sign-in and storing your account and order data |
| The payment provider | On payment pages only | Fraud detection and securing the payment |
| The maps provider | When the address map opens | Rendering the map and address autocomplete |
| The hosting provider | Throughout the connection | Routing and service protection |
| The notification services | When a notification is delivered to your device | Delivering the notification |
Those providers, and what they process, are set out in section 6 of the Privacy Policy.
7. Durations, and changes to this policy#
7.1 Session values end when the tab is closed or the session expires. Persistent values remain until you delete them or they expire.
7.2 We do not use persistent identifiers for cross-site tracking.
7.3 When a new technology or provider is added, we update the tables above and publish a new version with a number and an effective date, recorded in the policy changelog.
8. Version history#
| Version | Date | What changed |
|---|---|---|
| 1.0 | 26 June 2026 | Initial publication. |
| 2.0 | 26 July 2026 | Generic descriptions replaced with tables naming what the Platform actually uses, its purpose and its duration; a mobile-app section added; an express statement that there are no third-party tracking networks. |
| 2.1 | 26 July 2026 | The controller for the technologies described here identified as FAWRAN LLC, trading as FAWRAN. |
| 2.2 | 28 July 2026 | Rewritten against what the applications actually store. Browser cookies, browser storage and the mobile app's own storage are now kept apart instead of all being called cookies, and each row states plainly whether the value reaches Fawran at all — six of the website's stored values never leave your device. The measurement and analytics category was removed, along with the mobile "measurement identifier" and "advertising identifier" rows, because no such identifier appears in the storage the applications actually use. The notification token is now described where it belongs. A correction of description; no new storage is introduced and the effective date is unchanged. |
Operator and contact details
These details apply to every document in the Legal Center.
- Contracting entity
- FAWRAN LLC
- Trading as
- FAWRAN — فورا
- Operating market
- Marketplace services for customers in The Hashemite Kingdom of Jordan
- Registered Office
- FAWRAN LLC 131 Continental Drive, Suite 305 Newark, Delaware 19713 United States of America
- Legal and privacy contact
- admin@fawra.net
- Customer support
- https://help.fa9ran.com
- Governing law
- the laws of the Hashemite Kingdom of Jordan
- Dispute venue
- the competent courts of Amman
Address of record for the entity in its state of formation. It is not a customer-service address, not a returns address, not a warehouse, and not an address for correspondence about an order. Do not send returns or ordinary customer correspondence there.
For legal notices and privacy requests. For help with an Order, use customer support below.
Support runs through the Help Center and in-app support. Those are our official support channels.
The buyer policies are governed by applicable Jordanian law for our operations in Jordan, and no mandatory Jordanian consumer protection is removed by them.
Related documents
Every category of personal data we process, why, on what legal footing, who receives it and for how long.
Your eight statutory data rights, how to exercise each one, and how we verify it is you.
Which messages we send, which you can switch off, and which you cannot.