|
| 1 | +# Privacy Policy |
| 2 | + |
| 3 | +*Last updated: January 2026* |
| 4 | + |
| 5 | +## 1. Introduction |
| 6 | + |
| 7 | +PoSPro is a decentralized, secure Point of Sale (PoS) solution developed by **REChain Network Solutions** using Flutter, Dart, and related open-source technologies. |
| 8 | + |
| 9 | +This Privacy Policy explains how data is processed, stored, and protected when using PoSPro software, including client applications, self-hosted backends, and optional integrations. |
| 10 | + |
| 11 | +PoSPro follows the principles of **privacy by design**, **data minimization**, and **operator control**. |
| 12 | + |
| 13 | +## 2. Scope of This Policy |
| 14 | + |
| 15 | +This Privacy Policy applies to: |
| 16 | + |
| 17 | +* PoSPro client applications (mobile, desktop, terminal) |
| 18 | +* Self-hosted PoSPro servers or nodes |
| 19 | +* Open-source repositories under REChain Network Solutions related to PoSPro |
| 20 | + |
| 21 | +This policy does **not** apply to third-party services, payment providers, banking systems, or fiscal operators that may be integrated by merchants or operators. |
| 22 | + |
| 23 | +## 3. Key Privacy Principles |
| 24 | + |
| 25 | +* **No mandatory central server**: PoSPro can be deployed in fully self-hosted or decentralized environments. |
| 26 | +* **Merchant-controlled data**: Transaction and customer data remain under the control of the merchant or system operator. |
| 27 | +* **Minimal data collection**: Only data strictly necessary for transaction processing is handled. |
| 28 | +* **Transparency**: PoSPro source code is publicly available for audit. |
| 29 | + |
| 30 | +## 4. Data We Do Not Collect |
| 31 | + |
| 32 | +By default, REChain Network Solutions does **not** collect: |
| 33 | + |
| 34 | +* Customer personal identification data |
| 35 | +* Payment card numbers or CVV codes |
| 36 | +* Biometric data |
| 37 | +* Advertising or tracking identifiers |
| 38 | +* Behavioral analytics for marketing purposes |
| 39 | + |
| 40 | +## 5. Data That May Be Processed |
| 41 | + |
| 42 | +Depending on configuration and applicable law, PoSPro **may process**: |
| 43 | + |
| 44 | +* Transaction metadata (amounts, timestamps, order identifiers) |
| 45 | +* Product or service information |
| 46 | +* Tax or fiscal data required by local regulation |
| 47 | +* Technical logs required for system reliability and security |
| 48 | + |
| 49 | +Sensitive payment data is processed only by **external certified payment providers**, not by PoSPro itself. |
| 50 | + |
| 51 | +## 6. Payments and Third-Party Services |
| 52 | + |
| 53 | +PoSPro may integrate with: |
| 54 | + |
| 55 | +* Banks and acquiring services |
| 56 | +* Payment gateways |
| 57 | +* Fiscal data operators (OFD) |
| 58 | +* Accounting or ERP systems |
| 59 | + |
| 60 | +These services operate under their own privacy policies. PoSPro does not control or assume responsibility for third-party data handling. |
| 61 | + |
| 62 | +## 7. Data Storage and Retention |
| 63 | + |
| 64 | +* Data is stored locally, on merchant-controlled servers, or within infrastructure chosen by the operator |
| 65 | +* Retention periods are defined by merchant policy and applicable law |
| 66 | +* REChain Network Solutions does not have automatic access to merchant data |
| 67 | + |
| 68 | +## 8. Security Measures |
| 69 | + |
| 70 | +PoSPro implements security best practices, including: |
| 71 | + |
| 72 | +* Encrypted communication channels |
| 73 | +* Role-based access control |
| 74 | +* Optional cryptographic signing and verification |
| 75 | +* Open-source security review |
| 76 | + |
| 77 | +Despite these measures, no system can guarantee absolute security. |
| 78 | + |
| 79 | +## 9. Operator and Merchant Responsibilities |
| 80 | + |
| 81 | +Merchants and system operators are responsible for: |
| 82 | + |
| 83 | +* Compliance with local data protection laws (GDPR, 152-ФЗ, PCI DSS where applicable) |
| 84 | +* Secure configuration and operation of PoSPro deployments |
| 85 | +* Obtaining customer consent where required |
| 86 | + |
| 87 | +## 10. Children’s Privacy |
| 88 | + |
| 89 | +PoSPro is not intended for use by children and does not knowingly collect data related to minors. |
| 90 | + |
| 91 | +## 11. International Use |
| 92 | + |
| 93 | +PoSPro may be used globally. Data processing locations depend on where the merchant or operator deploys the system. |
| 94 | + |
| 95 | +Users are responsible for ensuring compliance with local regulations. |
| 96 | + |
| 97 | +## 12. Changes to This Policy |
| 98 | + |
| 99 | +This Privacy Policy may be updated as PoSPro evolves. |
| 100 | + |
| 101 | +* Updates will be published via the GitHub repository |
| 102 | +* Continued use of the software indicates acceptance of the revised policy |
| 103 | + |
| 104 | +## 13. Contact Information |
| 105 | + |
| 106 | +For project-related inquiries: |
| 107 | + |
| 108 | +* GitHub: [https://github.com/REChain-Network-Solutions](https://github.com/REChain-Network-Solutions) |
| 109 | + |
| 110 | +For data-related questions, contact the relevant merchant or system operator. |
| 111 | + |
| 112 | +--- |
| 113 | + |
| 114 | +**PoSPro** is built for secure commerce — with privacy and control remaining in the hands of businesses. |
0 commit comments