Moshtare LP privacy

Updated October 27, 2026. Moshtare LP is provided by Moshtare and operated by AL-SHAHTA AL-SUFLIA TRADING ESTABLISHMENT. For privacy or account support, contact Moshtare.

Merchant account and personal-data deletion requests: Request deletion · طلب حذف البيانات. Requests are reviewed after ownership verification; financial audit records are retained as described on the request page.

Merchant app and Android services

We use PostHog US Cloud for session replay and screen-navigation events in the signed-in merchant web dashboard to understand usability problems and improve support. Dashboard recordings are not masked: they can include page text, entered form values, images, QR codes and canvas content, including merchant and customer names, contact details, notes, balances and loyalty activity displayed in the dashboard. Login, password, verification-code and account-security screens are excluded. Console logs, network request contents and customer-facing pages are not recorded by this integration. PostHog also receives a merchant workspace identifier, program type, navigation events and browser/session metadata. Recordings are retained for 30 days. Replay respects the browser’s Do Not Track preference. Native-only app screens are outside this web integration.

Merchant accounts may be provisioned by an administrator. When self-service registration is available, it asks for the store name, a phone number verified by a code, and a password. Existing email accounts remain supported. We process protected password credentials, verified merchant phone bindings, merchant and workspace identifiers, installation identifiers, session records and security records to authenticate the account, operate its loyalty program and prevent abuse. Authorized merchant users access customer names and contact information where supplied, membership references, balances and loyalty purchase, award and redemption history within their store.

Reward and loyalty-update messages use the selected SMS or WhatsApp channels. The service and its messaging providers process the destination number and complete message, including the loyalty link. During the trial, the merchant’s verified phone appears in the fixed test-message footer and is visible to the recipient. Message snapshots, channel results and credit records support accounting and recovery; provider acceptance does not prove handset delivery. A recipient number alone does not prove ownership of a customer membership.

Forgotten merchant passwords can be reset using a short-lived verification code sent to the account’s current registered phone. The reset changes only that account’s password and ends its previous sessions. Verification is funded by the platform, outside store message credits. If you lose the registered number, contact support for independently verified assistance; a code to a new number alone cannot transfer the account. Recover password · استعادة كلمة المرور.

Public deletion requests accept a contact phone or email. Contact details do not prove account ownership. Support verifies ownership, confirms eligible scope and documents any retained records before manual fulfillment. Your browser saves the original request and a private reference until a matching receipt confirms intake, so an interrupted submission can be recovered without creating a different request.

Phone-only merchants can initiate an authenticated deletion request in Account. Fulfillment requires ownership review; submitting a request does not immediately delete the store or its audit history. Subscription and message-credit inquiries open WhatsApp with the displayed store and quote details; the merchant chooses whether to send them.

Customer-directory searches are sent to our service. Merchant actions, optional notes and store settings are recorded; optional Wallet logos and banner images are uploaded for the store’s card design. Financial and security records are retained for audit, dispute resolution and abuse prevention. Account and other eligible personal data can be requested for deletion through the request page above, subject to ownership verification and stated retention requirements.

Android notification delivery uses Firebase Cloud Messaging and per-installation identifiers. The barcode-scanning SDK includes Google ML Kit, which processes camera frames on the device and collects installation identifiers, device/app information, feature events, error codes and performance metrics for diagnostics and usage analytics. Our service also records connection and reconnection diagnostics. Camera and notification permissions are optional. Fixed branch coordinates entered for nearby Wallet reminders describe the store; the merchant app does not request the phone’s current GPS location.

Hosting, database, image storage, notification and scanning service providers process the information needed for these functions. Data is transferred using HTTPS, and merchant access is restricted to authorized accounts and their workspace. We do not sell loyalty data or use it for cross-app advertising tracking. Essential cookies and local storage support authentication, language and preferences. Local recovery journals retain operation identifiers, request details and account recovery credentials, which may include a recipient phone or verification challenge reference, so an interrupted action can recover its original result. These journals do not store passwords or verification codes. Service providers may process information outside your country.

Stand memberships

Stand membership and loyalty activity are scoped to one merchant. Apple and Google sign-in identifiers are stored as merchant-scoped one-way identifiers; verified provider email addresses are encrypted and saved for balance updates within that merchant, never for identity matching or OTP. A supplied name is saved for recognition and retained when a later sign-in omits it. A contact phone supplied for redemption is unverified and does not authorize access or merge memberships. Phone sign-in, where offered, verifies a separate login identity.

Authorized merchant phones can view the member reference, supplied name, contact details and loyalty history. Merchant award and correction notes appear in the customer history. Stand currently has no customer self-service deletion or contact-edit screen. Financial history is retained as an immutable audit record.

For Google/Apple customers, email balance updates are enabled by default and controlled independently by Moshtare LP master administration. Postal receives the destination email and the store’s balance/progress message for delivery; stored delivery records support status checks and prevent duplicate sends. SMS/WhatsApp receive the phone number and their separate message when enabled. Apple Hide My Email addresses are supported; disabled forwarding prevents email delivery. Email updates never contain OTP codes.

Optional Stand Apple and Google Wallet cards display merchant branding and loyalty balances. Their QR code contains an opaque merchant membership reference used for identification; it is not a login credential. Their return links contain public store context and require the existing authenticated session or sign-in. Stand customer web credentials use Secure HttpOnly cookies; server-side credential hashes expire after 180 days. Wallet device push tokens are encrypted at rest.

POS receipt memberships

Moshtare LP creates a random membership for each store. It does not store your email address, Aqmar account, raw Apple or Google identifier, or a shared cross-store customer identity. Before redemption, you provide a missing contact phone for that store. A name is not required. Authorized merchant users can view these details to handle your redemption. You can edit or delete contact details; transaction and points-ledger records remain for audit.

If you continue with Apple or Google, the identity provider may send standard identity claims. Moshtare LP requests and saves a supplied name for recognition within that store, preserves it when later sign-ins omit it, and discards email addresses. It keeps a one-way identifier cryptographically scoped to the current merchant. A name does not prove ownership or authorize a transaction; unnamed customers can continue using their member reference.

Contact numbers are unverified and never used to merge accounts or grant access. Where SMS sign-in is available, a verification code proves access to a separate phone login identity. The SMS provider receives the destination number and message; delivery records and verification attempts support retries and abuse prevention.

Android browser credentials are random, stored only as hashes on our servers, placed in Secure HttpOnly cookies, and expire after 180 days. Google Wallet cards are optional and contain the points balance, configured point value, merchant branding, and a signed store-membership recovery link. They contain no QR code, barcode, name, email, or phone number.

Apple Wallet device push tokens are encrypted at rest. Transaction records and an immutable points ledger are retained for merchant audit. Deleting a membership revokes credentials and Wallet registrations, detaches retained aggregate transactions, and makes any Google Wallet object inactive. Google may retain that inactive card under expired passes until you remove it manually.