Cookie Policy
Version 1.0 · Effective October 15, 2026
This is a translation. In case of any discrepancy, the Portuguese version prevails.
On this page
We use cookies and similar technologies on the website, the dashboard, the app, and the Checkout. Essential and security cookies are always active, because payments cannot be processed securely without them. All others are activated only with your consent, which you may change at any time under "Cookie Preferences."
1. What cookies and similar technologies are
Cookies are small files stored in your browser. Similar technologies include local storage, pixels, SDKs in apps, and device identifiers used to prevent fraud. In this Policy, "cookies" covers all of them.
2. Categories we use
| Category | Purpose | Legal basis | Can you disable it? |
|---|---|---|---|
| Strictly necessary | Maintain the session, login, cart, language, and protection against forged requests | Necessity to provide the service and legitimate interest | No |
| Security and anti-fraud | Identify the device, detect bots and card testing, support 3DS authentication | Fraud prevention and legitimate interest | No, on the Checkout and the dashboard |
| Functional | Remember preferences and enable one-click purchase with a saved card | Consent | Yes |
| Analytics | Measure usage and performance of the SecurityPag website and dashboard | Consent | Yes |
| SecurityPag marketing | Measure campaigns and display SecurityPag ads on other websites | Consent | Yes |
| Seller pixels on the Checkout | Measure the Seller's sales on Meta, Google, TikTok, Pinterest, and tracking tools | Consent, under the Seller's responsibility | Yes |
3. Pixels installed by Sellers
3.1. Sellers may configure third-party pixels on the Checkout and in the Members Area. In such cases, the Seller is the controller and is responsible for informing the Buyer and obtaining the Buyer's consent.
3.2. The Checkout fires marketing pixels only after the Buyer's consent in the cookie notice.
3.3. SecurityPag may block scripts that compromise the security or the PCI DSS compliance of the Checkout. Pixels never have access to card data.
4. Detailed list of cookies
The updated list of cookies in use, with name, provider, category, purpose, and duration, may be consulted under "Cookie Preferences" in the website footer, or requested by e-mail at compliance@securitypag.com.
5. App
The app uses SDKs for authentication, notifications, crash reporting, and, with your consent, usage analytics. Phone permissions, such as the camera for identity verification and notifications, are requested only when necessary and may be revoked in the device settings.
6. How to manage
- Cookie notice: on your first visit you choose to accept, refuse, or customize. The accept and refuse options have equal prominence.
- Preferences: the "Cookie Preferences" link in the footer allows you to change your choice at any time.
- Browser: you may delete or block cookies in your browser settings. Blocking essential or security cookies may prevent login and payments.
- Validity of your choice: we store your choice for up to 12 months and ask again after that period or when new categories are introduced.
7. Visitors outside Brazil
For visitors from the European Union, the European Economic Area, and the United Kingdom, non-essential cookies are activated only with prior consent, in accordance with local electronic privacy laws.
8. Contact and changes
Questions: compliance@securitypag.com. This Policy may be updated; the effective date indicates the current version. More information on data processing is available in the Privacy Policy.
Other Legal Center documents
© 2026 SecurityPag · RGST TECNOLOGIA LTDA · CNPJ 47.993.283/0001-83 · Av. Paulista, 302, Conj. 10, Bela Vista, São Paulo/SP
Questions about these documents: compliance@securitypag.com