Version 1.0.1 · Last updated: 26 October 2026
This Privacy Policy explains how RELZ ("RELZ", "we", "us", "our"), a service operating in the Hashemite Kingdom of Jordan, collects, uses, shares, keeps and protects your information when you use the RELZ applications, website and services (the "Platform"). Please read this Policy alongside our Terms of Service. This Policy explains our processing; it does not treat your use of the Platform as consent to every optional use of your information. Where consent is required, we ask for it separately.
RELZ is a technology platform operating in Jordan that helps customers discover and use independent stores ("mini-apps") through one account, with cash payment. Each mini-app is run by an independent business ("Vendor"), which is the seller. Orders may be delivered by a delivery company selected and contracted by the Vendor where that option is actually available. RELZ decides how personal data is used to operate its Platform and is responsible for that processing. Vendors and delivery companies are responsible for their own processing of the information they receive to fulfil an order. For any privacy question, or to exercise your rights, contact us at teamrelzapp@gmail.com.
| Category | Examples |
|---|---|
| Account information | Name, username, email address, phone number, preferred language and profile photo. Passwords are handled by our authentication provider and stored only in hashed form. |
| Optional profile details | Gender, a short biography, city and other profile details, only if you add them. Date of birth is optional. If you enter it while signing up, it is used only on your device to check that you are at least 18 and is not sent to us; if you add it to your profile, we store it with your profile. |
| Location & addresses | Your delivery addresses and the map pin/coordinates you set. Precise device location is used only with your permission, to show nearby stores and set delivery locations. |
| Orders & activity | Orders and invoices, cart contents, RELZ Credit and rewards, price offers, reviews, favourites, follows, the mini-apps you install or open, products you view, searches you make in the app, and in-app messages. |
| Return requests & reports | If you send a return request: the order and items concerned, your reason for each item, your explanation, any photos you choose to add, the outcome you ask for, and the request's history. If the store records a refund: the method, amount, date, reference and any proof photo the store adds, and whether you confirm receiving it. If you report an unresolved issue to RELZ: your note and the request and store conversation it concerns. |
| Support | Support tickets and messages, and any screenshot you choose to attach. |
| Content you create | Photos, videos and reels, reviews, comments, and messages you upload or send. Uploading these uses your device camera, microphone, and photo library — only when you choose to add content, and only with your permission. |
| Contacts (optional) | If you use "find friends" and grant permission, the app reads the phone numbers in your device contacts and, on your device, turns each eligible number into a protected matching value (a one-way hash of its last eight digits). Only those values are sent, and only to find existing RELZ users with matching numbers. We do not upload or store your address book, we do not store the matching values, and we never contact anyone on your behalf. You can decline this and still use the app. |
| Payment (customers) | Customer checkout on RELZ is cash-based. We currently do not collect customer card numbers or customer bank-account details. We keep order amounts, fees and each order's cash-payment status for your history and for accounting, and the refund records stores enter for return requests. RELZ does not hold, send or receive refunds. |
| Business users | For people who run a mini-app or delivery company: the owner's or representative's name, email and phone number, and whether they were verified; the merchant application, store and support details, pickup location and working hours; licence, tax-registration and identity documents uploaded for verification, and the result of RELZ's review. |
| Payouts & settlements (business users) | Payout information the business provides, such as the CliQ type, CliQ alias or mobile number, recipient name, bank name and, where provided, the account holder and account number; changes to those details; payout destinations, transfer references, payout confirmations, payment-not-received disputes and their evidence, and the related accounting records (commissions, fees, deductions and settlements). |
| Legal & consent records | Which version of these Terms and this Privacy Policy you accepted, when, in which language and in which app; the version of each mini-app's policy accepted with an order; and, for business users, the merchant agreement and responsibility statement versions they accepted. |
| Device & usage | Device type, operating system, app version, language, identifiers, push-notification tokens, and in-app analytics events about how the Platform is used. |
| Diagnostics | Crash and error reports. A report may include your user ID and email address, device and app details, technical logs and the context of the error; in the customer app it may also include a screenshot of the screen at the moment of the error. |
Account and order details are needed when you choose to register or place an order, and business and payout details are needed to sell on RELZ and receive payouts. Location permission, access to contacts, camera, microphone or photos, optional profile details and marketing choices are optional as described above. We aim to collect only information needed for each purpose.
We process information needed to provide the account and services you request, to meet legal obligations, and to protect the Platform and its users where the law permits. We ask for separate consent for optional features or marketing where required, and you may withdraw that consent without losing access to unrelated core services.
To fulfil your order we share the details necessary to complete it — such as your name, delivery address/location, phone number, and order contents — with the Vendor you order from and, only when delivery is arranged, with the delivery company assigned to that order. No delivery company receives your details while delivery is only being simulated for testing. We share what each recipient needs for its part of the order, not information merely because you browse a mini-app. Vendors and delivery companies are independent businesses and are responsible, as separate controllers, for their own use of the data they receive. This does not reduce RELZ's own responsibility for the processing RELZ carries out.
When you send a return request, we share it — including your explanation, any photos you add and the request's history — with the Vendor that sold the item. The Vendor reviews and responds to it under its published policy and applicable law, and arranges any refund, replacement or repair; it sees the refund records it enters and whether you confirm them. If you report an unresolved issue to RELZ, authorised RELZ staff review the request, your conversation with that store and the related records to check the Vendor's compliance with our platform standards. RELZ does not decide the return or handle the refund.
We do not sell your personal information. We share limited data with providers that help us run the Platform, under their terms and only for the purposes below:
| Provider | Purpose | Location |
|---|---|---|
| Supabase | Database, authentication, file storage and server functions. | European Union — Frankfurt, Germany. |
| Resend | Sending authentication, verification, password-reset and other transactional account emails. | European Union — Ireland. |
| Google (Firebase) | Firebase Cloud Messaging for push notifications, and Firebase Analytics for app usage analytics. | Google's servers, including in the United States. |
| Apple (Apple Push Notification service) | Delivering push notifications to iPhone and iPad. | Apple's servers, including in the United States. |
| Google Maps | Displaying maps and selecting delivery/store locations. | Google's servers, including in the United States. |
| Sentry | Detecting and diagnosing app crashes and errors. | The United States or the European Union, depending on the region of our Sentry account; contact us and we will tell you which. |
| Cloudflare | Hosting the RELZ website and these policy pages. | Cloudflare's global network. |
Our providers operate outside Jordan, so your information is stored and processed in other countries: in Germany and Ireland in the European Union (Supabase, Resend), in the United States (Google Firebase, Google Maps, Apple's push service, and possibly Sentry), and on Cloudflare's global network for the website. Such transfers remain subject to applicable Jordanian data-protection requirements. We limit the information shared to what is needed for the stated purpose and can explain the relevant recipient and location when you contact us.
With your permission, we send notifications about orders, deliveries, and — if you opt in — offers and promotions. On iPhone, notifications pass through Apple's push service; on all devices they are sent through Google Firebase. You can turn notifications off at any time in your device settings or in the app, and opt out of marketing while still receiving essential service messages.
We keep information only while it is needed for the purpose for which it was collected, using the criteria below. We do not keep data for a fixed number of years unless the law requires a specific period for a record; where it does, we keep that record for that period.
| Information | How long we keep it |
|---|---|
| Account and profile (including optional date of birth, gender and biography) | While your account is open. Deleted when you delete your account, including your profile photos. |
| Orders, invoices and cash-payment status | Kept as transaction records after the order ends, for as long as accounting, tax and other legal obligations or a valid legal claim require. When you delete your account they are kept without your name, addresses, contact details or order notes. |
| Chats and messages | While your account is open; deleted when you delete your account, including images you sent in chat. |
| Return requests, refund records and refund evidence | Kept with the related order for the same period as the order, because they are part of the Vendor's and RELZ's transaction records. On account deletion they are detached from you and any open request is closed. |
| Reports to RELZ and support tickets | While your account is open, and for as long as needed to resolve the matter and any related account action; deleted when you delete your account, including attached screenshots. |
| Content you upload (reviews, photos, videos, comments) | Until you delete it or your account, or until we remove it for breaching our Terms. |
| Push-notification tokens | Until you sign out of that device, the token is replaced or no longer valid, or you delete your account. |
| Contact-matching values | Used only to answer the matching request and not stored. |
| Analytics | Kept by Google Firebase Analytics for the retention period set in our analytics settings, no longer than 14 months. |
| Diagnostics | Kept by Sentry for a limited period set by our Sentry plan, after which they are deleted. |
| Business owner identity, merchant application and verification documents | While the business uses RELZ, and afterwards for as long as needed to meet legal and regulatory obligations or for a valid legal claim. |
| Payout information, payouts, confirmations and financial disputes | Payout details while the business uses RELZ; payouts, transfer references, confirmations, disputes and the related accounting records for as long as accounting, tax and other legal obligations or a valid legal claim require. |
| Legal and consent records | While your account is open, as evidence of what you accepted; deleted with your account, except the policy version accepted with an order, which stays with that order. |
If you ask, we will explain the retention period and reason applicable to a particular category of your data.
To exercise any right, use the in-app Delete Account option where available or email teamrelzapp@gmail.com. If an in-app deletion cannot be completed, contact us at that address so we can handle the request. We will respond within 15 working days, subject to any applicable legal exception. If you believe your data rights have not been respected, you may raise a complaint with Jordan's Personal Data Protection Directorate at the Ministry of Digital Economy and Entrepreneurship after contacting us.
We use industry-standard measures to protect your information, including encryption in transit and secure, access-controlled storage. No method of transmission or storage is completely secure, but we work hard to protect your data and to notify you where the law requires.
RELZ is intended for users aged 18 and over and is not directed to children. Users confirm that they are at least 18 when they create an account or accept our Terms; giving a date of birth is optional, so we cannot detect every account that belongs to a child. We do not knowingly collect personal information from children. If you believe a child has provided us information, contact us and we will delete it.
We may update this Policy from time to time. We will change the version and date above and, for material changes, ask you to review and accept the update in the app. We record the version you accepted, when you accepted it, and the language in which it was shown.
Questions or requests about this Policy or your data:
Email: teamrelzapp@gmail.com