Souqna
Privacy Policy
What the current service stores, what other people can see, and which account controls are available.
Draft version · 25 October 2026 · No effective date assigned
1. Information stored by the service
The service stores account email and authentication records; profile display name, preferred language and membership date; and optional profile fields such as avatar URL, biography, phone, seller type and selected location when provided. Not all stored profile fields currently have a self-service editing screen. It also stores listing text, photos, category/location, price and condition, listing status and view counts; favorites; saved-search names and criteria; conversation membership, messages and read markers; reviews; reports and relevant evidence; notifications, read status and notification preferences; and moderation status, reasons and audit history. Ordinary registration does not ask for identity documents. There is no platform checkout or payment-card collection workflow.
2. Why information is used
Information supports sign-in, account access, publishing and finding listings, member messaging, favorites and saved searches, conversation-based reviews, in-app alerts, moderation and abuse prevention. Selected locations are supplied by members, not automatically obtained through GPS. The saved-search alert system compares stored criteria with newly public listings; sellers cannot see who saved a search or its match ledger. Moderation records support enforcement and the history of administrative actions. Email notification choices are stored, but marketplace email notification delivery has not been activated. Authentication-related email is distinct from marketplace alerts; this draft does not promise successful delivery of either.
3. Public and private visibility
Active visible listings and photos, seller display names, membership dates, seller type, active listing counts and published reviews may be viewed without signing in. Public reviews include the reviewer’s display name, rating, comment and date. Do not put contact details, identification documents or other sensitive information in public listing text or photos. Account email, password credentials, stored phone fields, saved searches, favorites and notification feeds are not exposed by the public seller profile. Messages are accessible to conversation participants; authorized report review can expose relevant scoped message evidence. Reporters see their own limited report status, not internal notes or other people’s reports. Authorized account administrators can access account email and relevant operational records. This is access control, not a promise of end-to-end encryption or absolute confidentiality.
4. Browser storage and service providers
The application uses browser storage for the selected language and authentication session. Essential service infrastructure handles hosting, account authentication, database records and photo storage through Lovable Cloud. Google sign-in, when chosen, involves Google’s authentication service and account information returned for sign-in. The interface also loads fonts from Google’s font service, which receives the associated network requests. Service requests and error diagnostics can be processed by hosting and operational tooling; a verified inventory of providers, technical log fields, hosting countries, log retention and international-transfer arrangements still requires owner confirmation. This draft makes no claim of “no tracking,” data residency or compliance certification, and does not establish an advertising or analytics consent system.
6. Retention and deletion limits
There is no approved comprehensive retention schedule or automatic account-deletion workflow. Account and activity records remain stored unless removed through applicable existing operations or an authorized process. Pausing, expiry, marking sold, moderation removal or account suspension changes visibility or permissions; it does not erase conversation history and all related records. My listings offers deletion of an owned listing and its photos; that is not whole-account erasure, and associated conversations can remain without the listing. Administrative audit history is append-only. Cached or previously downloaded public content, provider logs and backups are not subject to an established deletion deadline in this draft. The owner must approve record-specific retention, backup handling, legal holds and deletion procedures; no immediate or universal erasure is promised.
7. Current controls and privacy requests
You can switch language, sign out, manage your listings, remove favorites, open/rename/delete saved searches, mark notifications as read and change supported notification preferences. Important in-app account/moderation notices remain enabled. Stored email choices do not mean alerts are being emailed. The current Account page does not provide self-service account deletion, a personal-data export or editing for every profile field. A verified privacy/deletion-request contact and an identity-safe request process have not yet been published and must be supplied by the owner. Do not use public listings or messages to unrelated sellers for privacy requests, and do not send passwords. Applicable access, correction, objection or erasure rights, verification steps and response periods need local legal review; this draft does not invent a deadline or guarantee that every request can be fulfilled.
8. Approval and country-specific review
The owner must identify the responsible legal operator and contact, confirm actual providers and processing locations, choose a retention schedule and request-handling procedure, and obtain country-specific review of lawful grounds, required notices, minors, cookies/browser storage, international transfers and statutory rights. No GDPR or other statutory compliance claim, governing jurisdiction or legally approved privacy promise is made. The English and Arabic drafts both require owner approval and reconciliation before an effective date is set.