Privacy Policy
Version v1 · Effective September 13, 2026
This document is written and maintained in English, which is the authoritative version. The Filipino translation available on this page is provided to help you understand this policy and is not a separate, independently binding version — if the English and Filipino text ever appear to conflict, the English text governs.
This Privacy Policy describes what information AuraZet Commerce collects, how we use it, and the systems and processors involved, so you can make an informed decision about using the Service.
1. Account and authentication data
When you create a Commerce account, we collect your name, email address, phone number (optional), and password. Authentication is handled by Supabase Auth; we never store your password in plain text — it is hashed by our authentication provider.
2. Merchant and store data
We collect the business information you provide during onboarding and ongoing use: your store's name, type, location, product catalog, pricing, inventory levels, and similar operational details you or your staff enter to run your store in Commerce.
3. Staff and account-role data
If you add staff members, we store the name, role (owner, manager, staff, or a coach-equivalent role where applicable), and a securely hashed PIN for each staff profile you create — never the PIN itself in readable form.
4. Point-of-sale, inventory, and sales data
We store the transactional and operational records Commerce is built around: sales, line items, payment method used, stock receiving and adjustments, shift records, and corrections/voids/refunds — kept as an append-oriented history rather than silently overwritten, so your own audit trail stays intact.
5. Device and sync metadata
To support offline-first selling and device recovery, we store metadata about devices registered to your store (a device identifier and name you choose) and synchronization state needed to reconcile sales recorded offline once connectivity returns. We do not use this metadata to track your location.
13. Social-verification evidence
If you participate in Early Access social-share verification, we store the public URL of the post you submit and its review status, so AuraZet (or, where reliably supported, an automated check) can confirm the share. We do not request or store your social media login credentials.