BEAZA
Privacy Policy
How BEAZA processes personal data in the product today. Counsel-approved privacy policy is required before production launch.
LEGAL CONTENT APPROVAL PENDING: This page currently shows an engineering product-practice summary. Counsel-approved Terms/Privacy must be published before production launch. It is not a finalized legal contract.
Who we are
BEAZA operates the public website and related customer/merchant services described in product documentation. Legal entity name, registered address, and data-controller identity are LEGAL REVIEW REQUIRED.
Public contact for privacy and support uses the configured support email shown on the Support page.
Data we process
Depending on how you use BEAZA, we may process:
- Account and profile details such as name, phone, email, preferred language, and optional profile fields
- Authentication-related records needed to sign in (we do not publish password or OTP internals)
- Order, cart, fulfillment, and related merchant/branch interaction history
- Payment method metadata, provider references, and transaction status — not full card PAN/CVV in BEAZA application databases
- Wallet ledger and balance activity
- Loyalty points and stamp/reward activity
- Gift sender/recipient details and messages where gifts are used
- Vehicle details you save or attach to From Car orders (for example make, model, color, plate)
- Location coordinates submitted for From Car arrival events where that feature is used
- Device and push-notification tokens for operational notifications
- Support and privacy-request communications you submit
- Security and operational audit/activity records
- Ordinary web/server logs such as IP address and user agent
Location
From Car arrival flows may receive latitude/longitude when you report arrival or related handover status. Location is used for the arrival/handover experience where enabled. BEAZA does not continuously track customers as a standing product behavior.
Nearby discovery does not currently persist customer GPS traces for ranking in the audited codebase path.
Sharing with participating merchants
Merchants receive information needed to fulfill orders. Presenters expose customer first name and, for From Car, vehicle details for handover. Customer phone is not exposed in the audited merchant order presenters.
Service providers
BEAZA uses provider abstractions for categories such as payments, SMS/OTP, push notifications, email, object storage, and (where configured) gift delivery messaging. Named production vendors are used only when actually configured for an environment. Unselected provider interfaces are not listed here as active processors.
International transfer rules: LEGAL REVIEW REQUIRED.
Purposes
We process data to provide accounts, process and fulfill orders, handle payments and wallet/rewards activity, support From Car handover where enabled, send operational notifications, provide support, prevent fraud/abuse, and keep necessary financial and security records.
We do not claim advertising tracking purposes for the public website in its current configuration.
Lawful bases under specific privacy regimes: LEGAL REVIEW REQUIRED.
Retention and account deletion
You may request account deletion through the BEAZA app privacy flow or by contacting support. Identity verification is required. After processing, account information, saved preferences, devices, and vehicle profiles are anonymized or removed, and the account is soft-deleted/deactivated. Exact coordinates used for live From Car handover are minimized.
Orders, payments, and related financial records may be retained for integrity, fraud prevention, or legal obligations. BEAZA does not promise that every related record disappears immediately or completely.
Specific retention durations: LEGAL REVIEW REQUIRED.
See also the Account Deletion page.
Privacy requests
Supported request types in product workflows include data export, data correction, and account deletion (via app/API and admin processing). Export availability is through the privacy-request workflow, not a public one-click website download.
Children/minors thresholds: LEGAL REVIEW REQUIRED.
Security
BEAZA applies access controls, authentication, sanitization of public CMS HTML, and operational auditing appropriate to the platform. No system can claim that data is completely secure under all circumstances.