SwiftPay Privacy Policy
Last updated: July 22, 2026
Plain English: Card numbers, balances, transaction history, staff accounts, and reports remain on the merchant’s device. SwiftPay’s separate licensing service receives only the information needed to start a trial, activate a license, and verify continued software access.
Store Records Kept on the Merchant Device
SwiftPay stores the store profile, staff accounts, card numbers, balances, transactions, audit records, receipt settings, agreement acceptance, and backup date in the browser database on the merchant’s device. These records are not sent to the SwiftPay licensing database.
Licensing Information
To prevent repeated free trials, a store provides and verifies a business email address. The licensing provider processes that email and sends the verification code; SwiftPay’s licensing database stores a protected one-way identity hash used to enforce one trial per verified email. When starting a trial, activating, or periodically refreshing a license, the application also sends an Install ID, installation credential, application version, and licensing request. The service stores a protected hash of the installation credential together with trial or license status and relevant dates. The hosting and licensing providers may process ordinary connection information, such as an IP address and request logs, for delivery, reliability, and security.
No Transaction Backend
SwiftPay does not upload card numbers, balances, issue or redemption transactions, staff accounts, receipts, backups, or reports to the licensing service. The licensing service does not provide SwiftPay with remote access to the merchant’s device ledger.
Camera Permission
Camera access is requested only after the user chooses to scan. Camera frames are processed in the browser to read a barcode and are not intentionally recorded or uploaded by SwiftPay.
PINs, Backups, and Device Access
Cardholder PINs are stored as salted password-derived hashes, not readable PINs. SwiftPay backup files are encrypted using the backup password selected by the merchant. New backups also include a separate Recovery Kit that can unlock that backup if its password is forgotten. SwiftPay does not receive or retain either credential and cannot recreate a lost password or Recovery Kit. SwiftPay signs users out whenever the application reloads; however, local browser roles cannot protect records from someone who controls the device operating system, browser profile, developer tools, or IndexedDB. The merchant must use a store-controlled account or kiosk profile, block unauthorized administrative access, and protect staff passwords, unused card numbers, PIN handoffs, printed recovery records, backup files, and Recovery Kits.
Data-Loss Warning
Clearing browser storage, resetting or losing the device, changing browser profiles, or uninstalling the app may permanently remove local records unless a recent backup exists. Save a backup at least weekly and before device, browser, or installation changes.
Contact
For privacy questions, call SwiftPay Support at 470-886-0066.