Legal
Cookie Policy
Last updated: September 23, 2026
1. What Are Cookies
Cookies are small text files stored on your device when you visit a website. They let the Service function correctly and improve your experience. This Policy explains which cookies Paymos uses and how to control them. It complements our Privacy Policy.
2. Cookies We Use
| Type | Purpose | Duration | Consent |
|---|---|---|---|
| Essential | Authentication, security, sessions | Session | Not required |
| Functional | Interface settings, language preference | 1 year | Not required |
| Analytics | Usage and performance analysis across the Service | Up to 1 year | Not required |
All three categories rely on our legitimate interest in running and improving the Service. Analytics cookies used to wait for consent; they no longer do, and we no longer ask. Session recording runs in the merchant dashboard only — never on the public site, a payment page or a POS terminal.
3. Managing Cookies
Block or delete cookies through your browser settings. That does not stop analytics: events still reach Amplitude with your IP address, but the paymos_did identifier no longer carries over between visits. The four milestones our servers report (see the Privacy Policy) do not depend on your browser at all. There is no in-product switch: the notice on our website says that we use cookies and links to this page; it does not offer a choice. Disabling essential cookies may stop parts of the Service from working.
4. Third-Party Cookies
We do not use advertising cookies and do not share data with advertising networks. Every event your browser sends reaches Amplitude with your IP address. Amplitude also processes pseudonymous device and session identifiers, page addresses (without the query string or fragment) and titles, referral and campaign data, clicks, form interactions (not the text you enter), page-load speed, and — in the merchant dashboard only — masked session recordings. Payment and POS pages send no title.
We send Amplitude no amounts, fees, or balances; they stay in the Paymos database. In click data we mask API keys, wallet addresses, transaction hashes, and similar long identifiers on every page, and every number on payment and POS pages and in the merchant dashboard. Network request contents are never captured.
Questions: [email protected]