Effective date: September 4, 2026 Provider: HONG PHUOC PHU · 85 Tran Xuan Soan, Phuong Tan Thuan, Ho Chi Minh City, Viet Nam · [email protected]
This Policy applies to JSONIC POS users across all plans. Free, Basic, Advanced and add-ons follow the same core privacy principles.
Depending on enabled features, JSONIC may process Jsofy Account and membership data; store/location information; products/services, SKU/barcode and inventory; orders, merchant-recorded payments, returns/refunds and audit logs; staff and roles; merchant-entered customer/buyer data; seller tax/e-invoice profile and merchant-selected tax classifications; e-invoice/provider status; server-period revenue summaries; security/device/sync/error logs; entitlement/subscription information; uploaded files/media; and integration credentials/tokens when required for an enabled feature.
For sensitive compliance actions such as tax-classification changes, Tax Corrections and e-invoice void/correction/issuance, JSONIC may retain compliance-audit records including Jsofy Account/user ID, tenant, role, timestamp, action, reason, necessary before/after data, IP address and user-agent/device metadata.
JSONIC does not need to receive or store card numbers/CVV for Google Play/App Store transactions. The Store processes the payment method and provides transaction evidence/status required for entitlement verification.
Data is used to provide POS/Cloud services, authentication/authorization, synchronization/backup, canonical transaction records, tax/e-invoice assistance requested by users, security/fraud prevention, billing/entitlement, support, incident investigation, legal compliance and reliability improvements.
JSONIC’s internal Control Plane is designed for service metadata, plans/entitlements, quotas, Help CMS and system operations. It does not provide Admin functionality to overwrite Merchant orders, revenue, inventory, tax classifications, Tax Corrections or e-invoice legal data. Automated technical transformations such as formatting, field mapping, policy-defined rounding, snapshot/canonicalization and provider-payload construction are technical processing only and do not make JSONIC the decision-maker for the Merchant’s business truth or tax obligation.
Tax/e-invoice data is processed to perform customer-requested functions; JSONIC does not use a merchant's classifications to independently determine the merchant's tax liability. The Merchant controls its business/legal truth; the Owner is the sole authority in JSONIC to confirm or change legal/tax/e-invoice configuration. Managers/staff may enter operational facts generated during sales within their role, but may not independently override legal configuration. JSONIC Support/Engineering/Admin does not enter, choose, confirm or edit Merchant legal/tax/e-invoice data on the Merchant’s behalf.
For merchant business data, the merchant may determine the processing purpose and JSONIC may process data on the merchant's instructions to provide the service. For JSONIC account, security, billing, fraud-prevention, essential telemetry and JSONIC legal-obligation data, JSONIC may determine processing purposes/means as permitted by applicable law.
JSONIC processes data only where an appropriate legal basis applies, such as service performance, consent where required, legal obligations or appropriate legitimate interests. JSONIC seeks to minimize data by purpose and role; staff devices should receive only the data slice needed for their permissions.
When a merchant connects a supported e-invoice provider, JSONIC may transmit required seller/buyer, item/service, quantity, price, tax-classification and total information according to the merchant's action/configuration.
Provider credentials are protected within JSONIC-controlled systems using appropriate safeguards and should not be embedded as public APK secrets. An e-invoice provider processes data under its own terms/privacy rules for the provider service it supplies.
In the current flow, JSONIC may display merchant-configured QR/bank-transfer information and record a manual user confirmation that funds were checked. JSONIC does not use Bank Hook, does not read banking-app notifications, SMS or bank statements/accounts, and does not automatically confirm bank transactions.
External payment speakers/devices purchased by merchants are not connected to JSONIC in this flow, and JSONIC does not collect their notification/audio content.
JSONIC does not sell merchant business data to advertisers. Data may be shared with infrastructure, e-invoice, Store, email/support or other processors as necessary to provide requested functions, using reasonable minimization and applicable agreements/law.
JSONIC may also disclose data where there is a valid legal basis/request from a competent authority or, to the extent permitted by law, to protect rights/security, prevent fraud/unlawful conduct and protect JSONIC/Jsofy/users/partners. Disclosure is limited to the applicable purpose/basis and does not authorize JSONIC to alter or impersonate the Merchant.
JSONIC uses safeguards such as HTTPS, tenant isolation, Jsofy/Firebase authentication, server-side authorization, appropriate secret encryption, rate limiting, idempotency/audit and other controls appropriate to the deployment. No system is perfectly secure; users must protect accounts, devices and credentials under their control.
Retention depends on data type, plan, contract and legal requirements. A UI visible-history limit does not necessarily mean canonical/tax records have been deleted. Certain data may be retained for e-invoice/accounting obligations, security, fraud prevention or disputes. Tax Corrections and compliance-audit records may be append-only in normal operations to preserve historical integrity; where needed for a legal hold, fraud/security investigation, dispute or valid authority requirement, JSONIC may preserve logs, audit trails, login history, security events, transactions and necessary technical evidence; an edit/deletion request does not necessarily require erasing those logs while JSONIC has a valid legal, contractual or security basis to retain them.
When no lawful basis remains, data is deleted or anonymized under applicable procedures. Users may request account deletion, subject to lawful retention exceptions.
Depending on applicable law, individuals may have rights to notice, access, correction, consent withdrawal, deletion/restriction and other rights. For customer/staff data collected by a merchant, the merchant will often be the primary contact and JSONIC assists according to its role, contract and law.
JSONIC requests device permissions only for user-enabled functions, such as camera for barcode capture and media/file access for uploads. JSONIC does not require Android Notification Access to read bank notifications for the current payment flow.
Where infrastructure/providers process data outside the user's country, JSONIC applies mechanisms required by applicable law and the actual deployment model. Vietnam personal-data/cross-border obligations must be reviewed against then-current law.
JSONIC POS is business-management software and is not designed for children to independently create commercial accounts. Store/ToS age settings will reflect applicable requirements.
JSONIC maintains an incident contact at [email protected]. JSONIC will investigate and contain personal-data incidents, coordinate with merchants/providers, and make legally required notifications where applicable.
At registration or after material changes, JSONIC may require acceptance of current Terms/Privacy versions and retain evidence of version, time, account, tenant and source. General acceptance does not replace separate consent where law requires one for a specific processing purpose.
Material changes will be communicated reasonably and may require in-app re-consent.
[email protected] · https://jsofy.com