Legal
Cookie Policy
How baxpay.com and BaxPay applications use cookies, SDKs, and similar technologies, and how you control them.
Please read carefully.
These documents describe how BAXPAY SARL operates BaxPay during open beta. They are written for transparency and GDPR accountability. They are not personal legal advice and are not a substitute for counsel-approved contracts. If anything here conflicts with a signed agreement between you and BaxPay, the signed agreement prevails for that relationship. For questions: [email protected] (privacy) or [email protected] (general).
Effective date: 18 July 2026 · Last updated: 3 November 2026
Marketing site defaults
baxpay.com is primarily a static marketing site. We do not run advertising pixels or non-essential third-party trackers by default. Fonts are self-hosted. Optional analytics run only if you opt in via the cookie dialog and we enable a privacy-preserving analytics tool.
How our systems work
You can verify network requests in your browser’s developer tools. Use “Cookie settings” in the dialog (or clear site data) to reset your choice.
1. What are cookies?
Cookies are small text files stored on your device. Similar technologies include localStorage, sessionStorage, SDKs, and pixels. Some are essential for security and basic function; others are optional.
2. Legal framework
In the EU/EEA, storing or accessing information on your device is governed by ePrivacy rules (including the French implementation) and the GDPR. Strictly necessary technologies do not require consent. Optional analytics require prior consent. You can withdraw consent at any time.
3. Cookies on baxpay.com (marketing)
How our systems work
| Name / storage | Type | Purpose | Duration |
|---|---|---|---|
| baxpay-cookie-consent | Necessary (localStorage / cookie) | Stores your cookie preferences so we do not re-prompt every visit | Up to 12 months |
| Locale path (/en/, /fr/, …) | Necessary (URL) | Language selection via URL — not a cookie | N/A |
| Optional analytics (if enabled) | Analytics | Aggregate traffic measurement — only if you opt in | Per tool policy (max 13 months typical) |
4. Cookies and SDKs in BaxPay applications
Signed-in applications (personal, business/freelancer, SoftPOS, admin, APIs) and BaxPay POS necessarily use authentication, security, and (where disclosed) diagnostic technologies:
These are primarily strictly necessary for a requested service. We do not use advertising cookies in the core payment apps.
On BaxPay POS terminals, Google Firebase SDKs may store or access device identifiers and diagnostic data as described in Privacy Policy §15. SoftPOS apps may use platform push/notification and NFC-related OS services required for acceptance.
- Session / refresh tokens (httpOnly cookies where used) — authenticate you securely.
- CSRF / double-submit tokens — protect state-changing requests.
- Security and fraud signals — device/session binding proportionate to risk.
- Preference storage — language, UI mode, cookie consent echo.
- Firebase Crashlytics / Performance on POS — crash and performance diagnostics (no cardholder or biometric data).
- Firebase Analytics on POS — optional, off by default, merchant toggle in Settings.
- Marketing email measurement — a 1×1 image and redirected links in marketing emails only, if you consented; see Privacy Policy §16.
5. How to manage cookies
Use the cookie dialog on baxpay.com (“Customize” / “Necessary only” / “Accept all”). Clear cookies and site data in your browser to reset. Blocking all cookies may break login. On POS, use Settings → Privacy & diagnostics for Analytics.