This Privacy Policy explains how VelocityPOS (a Point of Sale app built with Flutter and Firebase) collects, uses, stores, and shares information when you use the app.
VelocityPOS (“we”, “our”, “us”) is a Point of Sale (POS) application that helps retailers manage sales, inventory, customers, receipts, and reports. The app supports offline use with local storage and may synchronize data to the cloud (for example, using Firebase services).
Note: This document is a general privacy policy template tailored to VelocityPOS features. You should review it with a legal professional and ensure it matches your exact implementation (what you collect, where you store it, and which third-party services you enable).
This policy applies to anyone who installs or uses VelocityPOS, including:
When you sign in to VelocityPOS, we may collect or process:
VelocityPOS is a POS system, so it may store data that you (or your staff) enter, including:
Depending on your configuration and enabled features, the app may collect:
VelocityPOS may display product images by loading them from image URLs entered in the app. The app may request those URLs over the internet to display the images. If you use receipt sharing (WhatsApp/Email/SMS) or export features (PDF/CSV/Excel), the app may generate files and store them on your device.
We use information to:
If your users are in regions where privacy laws require a legal basis (e.g., GDPR), you may rely on one or more of the following:
We do not sell personal information. We may share data only in the following cases:
VelocityPOS may use third-party services to operate, such as:
These providers process data on our behalf to deliver the app’s features, subject to their own terms and security measures.
We may disclose information if required by law, regulation, legal process, or enforceable governmental request, or when we believe disclosure is necessary to protect the rights, property, or safety of users, the public, or our service.
If your business uses multiple staff accounts, admins and managers may be able to view operational data based on role permissions (for example, sales history, customer records, inventory).
VelocityPOS supports offline operation by storing data locally on your device (for example, using SQLite). This may include your products, customers, sales, and settings.
If cloud sync is enabled, the app synchronizes your business data to the cloud so it can be restored on new devices and kept consistent across devices. Sync typically happens when an internet connection is available.
We use reasonable administrative, technical, and organizational measures designed to protect data, such as:
We keep data for as long as needed to provide the service and for legitimate business purposes such as accounting, auditing, dispute resolution, and compliance with legal requirements.
VelocityPOS allows businesses to view, edit, and delete many types of business data (products, customers, sales) depending on user role permissions.
Data deletion may be possible through in-app tools. If your app uses cloud sync, deletion may also remove records from cloud storage (depending on implementation). Some records may be retained where required by law.
VelocityPOS is primarily a utility/business app. If you add marketing communications in the future, you should provide opt-out mechanisms.
VelocityPOS is not intended for children under 13 (or the minimum age required by local law) and we do not knowingly collect personal information from children. If you believe a child has provided personal data, contact us to request deletion.
If you use cloud services (such as Firebase), your data may be processed in countries other than where you live. These transfers may be necessary to provide the app. Where required, we rely on appropriate safeguards provided by the service provider.
The app may include integrations or actions that involve third parties, for example:
Third-party services have their own privacy policies. We recommend reviewing them.
We may update this Privacy Policy from time to time. We will update the “Last updated” date at the top. Material changes may be communicated through the app or release notes.
If you have questions, requests, or complaints about privacy, contact:
This table helps you (and reviewers) understand what POS data may exist in the app. Adjust to match your code.
| Category | Examples | Purpose | Where stored |
|---|---|---|---|
| Authentication | Email, Google Sign-In profile info, session tokens | Account creation, login, security, role access | Auth provider (e.g., Firebase Auth) + device session storage |
| Products | Name, SKU/barcode, pricing, tax, stock, category, image URL | Inventory and billing | Local DB (offline) and optional cloud sync |
| Customers | Name, phone, email, address, notes, loyalty points | CRM, loyalty, receipts, analytics | Local DB and optional cloud sync |
| Sales | Invoices, items, totals, taxes, discounts, payment method, timestamps | Billing, reporting, accounting | Local DB and optional cloud sync |
| Receipts & exports | PDF receipts, CSV/Excel reports | Sharing, printing, recordkeeping | Device storage; may be shared through third-party apps |
| Diagnostics (optional) | Crash logs, performance metrics | App stability and improvement | Analytics/crash provider if enabled |
If you don’t use analytics/crash tools, remove that row to keep the policy accurate.