Privacy Policy
Effective date: April 3, 2026 | Last updated: October 10, 2026 | Version: 2026-10-10-diagnostics
This Privacy Policy describes how 2D Data Solutions LLC collects, uses, shares, and protects information when merchants use Taply Retail POS.
Information we collect
| Data type | Examples | Purpose |
|---|---|---|
| Account and contact information | Merchant name, email address, store email, phone number | Authentication, account management, support, and store setup |
| Business information | Store name, address, city, state, country, tax settings, logo | Receipts, reporting, tax configuration, and store profile |
| Staff and customer records | Names, roles, PIN hashes, customer email or phone, visit history | Access control, CRM, receipts, loyalty, and reporting |
| Transaction and purchase history | Orders, items, totals, discounts, tips, refunds, payment method labels | Point-of-sale operation, analytics, accounting, and tax reports |
| Payment metadata | Stripe or Square account IDs, payment intent IDs, payment method metadata | Electronic payment processing and reconciliation |
| Approximate location | Store city and state suggested during setup | Optional setup auto-fill |
| Precise location | Device location used by Stripe Terminal on Android Tap to Pay devices | Card-present payment security, fraud prevention, and Terminal availability |
| Selected photos | Store logo chosen from the merchant's photo library | Store branding on receipts and inside the app |
| Nearby device information | Receipt printer or supported card reader connection state | Printer and payment-device connectivity |
| Crash reports | Stack traces, error messages, app version, operating system version | Debugging and service reliability |
| Performance diagnostics | App hangs and other crash-related diagnostic information | Performance monitoring and stability improvement |
Approximate location is requested only when a merchant chooses the setup auto-fill action. It is used to suggest store city and state and is not stored as latitude or longitude. Manual address entry remains available.
Precise location is requested on Android only when a merchant uses Stripe Terminal features such as Android Tap to Pay. Stripe requires device location to enable card-present payments, reduce fraud, and minimize disputes. Taply Retail POS does not store continuous location history.
We use Sentry for crash reporting and app-hang diagnostics. Session Replay, screenshots, sampled performance tracing, and default personally identifiable information collection are disabled. Sentry is not used to track users across apps or websites.
Information we do not collect
- Full credit or debit card numbers, CVV, or card PAN.
- Bank account numbers inside Taply Retail POS.
- Social Security numbers inside Taply Retail POS.
- Biometric data. Face ID and Touch ID are processed on device by the operating system.
- Continuous location history.
- Advertising identifiers for cross-app tracking.
How we use information
- Operate the POS, receipts, product catalog, orders, staff, inventory, and reports.
- Authenticate accounts and authorize store access.
- Sync merchant data between devices when cloud sync is enabled.
- Process electronic payments through PCI-compliant payment providers.
- Provide support, security, fraud prevention, and legal compliance.
How information is shared
We do not sell personal information or share it for cross-company targeted advertising. We share information only as needed with service providers:
- Supabase for authentication, database, storage, and sync.
- Stripe and Square for merchant onboarding, payment processing, card-present payment security, and fraud prevention.
- Sentry for crash reports and performance diagnostics. Session Replay is disabled.
- Law enforcement or regulators only when required by law.
Storage and security
- Data is encrypted in transit using HTTPS/TLS.
- Cloud data is stored in Supabase/PostgreSQL with encryption at rest.
- Local POS cache uses app-private JSON files for offline operation.
- Sign-out, account deletion, and invalid cached sessions clear local POS cache files.
- Staff PINs are salted and hashed, not stored as plain text.
- Payment card details are handled by payment providers and are not stored by Taply Retail POS.
Your rights and account deletion
Merchants can access and correct store data inside the app. Account deletion is available in Settings, then Legal & Privacy, then Account Deletion. Users may also request deletion at taplypos.com/retail/delete-account.
Some records may be retained only where required for security, fraud prevention, disputes, tax, accounting, or other legal obligations.
U.S. privacy choices and children
The Taply Privacy Policy also explains our U.S. practices, state privacy rights, identity verification, appeals and retention. For a customer or employee record, contact the merchant controlling that record or email Taply to help route your request. You can request access, correction, deletion or a copy where applicable; legal exceptions may apply.
Taply does not offer services directed to children under 13. If you believe a child has provided information through the service, contact support so we can investigate and take appropriate action with the merchant. This is separate from age verification for regulated purchases.
This document does not use optional website measurement. The marketing website has separate privacy settings. Clearing the app or deleting local data does not cancel a subscription.
Contact
For privacy questions, data requests, or complaints, email support@taplypos.com.