paaikari privacy policy

This policy describes current data handling for paaikari’s Bangladesh retailer wholesale catalog, ordering, support, Android, and web experiences. For questions, privacy requests, or an account deletion request, contact [email protected].

You can read this public policy and start a deletion request without signing in, reinstalling the Android app, or using a commerce endpoint.

For account and security, we handle a shop or business name, contact name, registered mobile number, full shop address, a protected password credential record, and SMS activation or password-recovery challenges. paaikari does not display your password. A verified email uniquely linked to one account can use the same password for sign-in and receive order receipts; phone-based password recovery remains unchanged. The first sign-in step shows the next step based on whether a phone or email is registered.

Commerce records can include product lines, quantities, prices, discounts, VAT, shipping, a delivery address, referral or coupon selections, payment/refund status, order events, and support messages or item-linked support photos. New checkout is COD-only; historical commercial records may contain applicable payment/refund facts.

Optional store photos supplied during onboarding and photos supplied with support are private uploads, not public catalog images. During store setup, if you consent to using location, an optional shop pin may be recorded once to match and support your shop Area; subsequent activity GPS never modifies this shop location. While signed in with already-granted permission, only your latest foreground activity position is observed and visible only to Admin (no movement history is kept, and there is no background tracking). If permission is denied or location is unavailable, old observations are cleared once an observation reaches the server (no instant remote guarantees). Background location, contact-book access, and unselected tracking are not required.

Web uses a secure HttpOnly session cookie and Android uses protected session storage to maintain sign-in. If you opt in to Android push, a device push token and account/session binding may be stored for order, delivery, support, refund, or category-access updates.

• To create accounts, sign users in with a phone or uniquely linked verified email and password, verify signup, recover passwords by phone, and revoke sessions.
• To provide the permitted catalog, category access, cart, COD checkout, delivery, receipts, and order history.
• To handle support requests and replies, optional private photos, store onboarding, shop location pin, foreground presence observation, and rewards/referral/coupon terms.
• To send a commercial receipt PDF at order placement and delivery when a verified notification email exists; no buyer email is sent for COD collection.
• To send actionable Android push updates when you opt in. Lock-screen previews are not intended to expose full personal details.

paaikari uses OVHcloud for production application hosting (app/API, worker, and storefront) and Supabase for managed PostgreSQL. Public catalog media is stored in Cloudflare R2-compatible S3 storage; private uploads are served through authenticated private-file paths.

Signup and account-phone recovery SMS use the configured Muthofun integration; the current transport follows the Muthobarta API pattern. When verified invoice email is enabled, messages are sent from [email protected] through the TLS SMTP transport at smtp.larksuite.com with Reply-To [email protected]. Opted-in Android push uses Google Firebase Cloud Messaging.

When an Admin explicitly clicks to view a shop or activity location in the Admin dashboard, OpenStreetMap map tiles load and coordinate transfer occurs; there is no automatic map sharing. Providers receive only the service data needed for their role. paaikari does not sell personal or sensitive data. paaikari cannot promise immediate erasure or a fixed duration for a provider’s own logs, abuse-prevention records, or backup copies; the same applies to existing database backups.

Account, order, delivery, support, store-photo, and notification data are not public catalog data. Backend authorization, category access, authenticated API transport, and private-file authorization limit access by active account; Admin or authorized Operations Staff may access data in private operational workflows.

Web sessions use secure HttpOnly cookies and Android credentials use protected platform storage. The configured transports use HTTPS/TLS. No system can promise zero risk of unauthorized access or disclosure.

When you request account deletion, identity is verified first. After an approved deletion is completed, identity, credentials, saved addresses, shop and foreground location data, account requests, support conversations, and private uploads are removed from active application data. Buyer/recipient contacts, delivery or billing addresses, and identifying free text or transaction references are also removed from retained orders.

Anonymized commerce facts such as product/variant description, quantity, unit, price, discount, VAT, shipping fee, payment/refund amount and status, stock movement, and operational timestamps may be retained so commercial records, reconciliation, and historical receipts remain accurate. They are not retained in a form intended to reconstruct the deleted account or sign in again.

An unresolved fulfillment, refund, or other financial obligation does not cancel an order or change stock, and final erasure may not complete immediately while that obligation is being settled. Support will explain the necessary steps; this policy does not promise an unsupported fixed completion time.

This policy describes deletion behavior for the active application database and private storage. Existing backup copies and external SMS/provider records follow separately managed procedures; paaikari does not claim their immediate deletion or a specific retention duration.