Cookies notice NativeActions · Version 2026-09-26 Cookies and similar storage help a website remember a session or complete a payment. This notice explains what NativeActions currently uses, when it is used and how you can control it. 1. What this notice covers This notice covers nativeactions.com and its www website, operated by Zabura s.r.o., Company ID 28303881, Cejl 40/107, Zábrdovice, 60200 Brno, Czech Republic. Contact support@nativeactions.com for questions. “Cookies” here includes similar storage or access on your browser or device where the same rules apply. Necessary storage is used to provide a service you request, such as signing in or paying, and to keep that service secure. We do not enable advertising, cross-site marketing or optional audience-measurement cookies on the current website. 2. Account session cookies Signing in creates first-party Supabase session cookies, named sb-stzdizplrwmqxmhhcmyy-auth-token, sometimes divided into numbered chunks such as .0 and .1. These hold authentication-session material so our server can recognize your signed-in requests. They are protected with HttpOnly and, on the HTTPS website, Secure and SameSite settings. The configured maximum browser lifetime is up to 400 days and the cookie can be refreshed when the session changes. Server-side expiry, revocation or signing out can end access earlier. Email or OAuth verification may also use a short-lived code-verifier cookie with the same project prefix. These cookies are not used for advertising. 3. Payment and fraud-prevention technologies When you choose to proceed to payment, the checkout loads Stripe’s payment interface. Stripe receives information needed to display supported payment methods, validate and complete a transaction and help prevent fraud. This can include browser/device information, network information and payment-session identifiers. Stripe can set cookies such as __stripe_mid (typically up to one year) and __stripe_sid (typically around 30 minutes), and use additional cookies or storage associated with the selected payment method, authentication challenge or fraud-prevention service. Exact names and lifetimes can vary with Stripe’s implementation and the payment method. These technologies are used for the payment service and its security. We do not use information from them to build our own advertising audiences. Read Stripe’s current notice for its full list and its independent purposes. If a future integration introduces non-essential purposes on our site, those purposes must be separately controlled before use. Stripe Cookies Policy: https://stripe.com/legal/cookies-policy Stripe Privacy Policy: https://stripe.com/privacy 4. Other technical processing Ordinary web delivery creates server requests and browser caches even when no persistent cookie is set. Vercel and other delivery providers may apply strictly necessary security or challenge mechanisms when protecting a request. The website does not use a preference cookie merely to remember acceptance of this notice. The desktop app stores settings and protected activation material locally. These are separate from website cookies. They support the installed app’s settings, device identity and offline authorization; uninstall and device-removal behavior is described in the app and help center. 5. Your controls You can delete or block cookies in your browser, use a separate browser profile, or sign out to end the current account session. Blocking necessary session cookies can prevent sign-in, and blocking payment-provider technologies can prevent a payment from completing. Browsing public product and help pages does not require an account. Because the current site does not enable optional advertising or analytics cookies, it does not ask you to accept such purposes through an “accept all” banner. If optional purposes are introduced, we will provide a genuine prior choice, with a way to reject them and withdraw that choice as easily as it was given. The Privacy notice explains the controller, recipients, legal bases, retention and your data-protection rights. Technical consent exemptions do not remove the other requirements of data-protection law. Privacy notice: https://www.nativeactions.com/privacy 6. Keeping this notice current We review this inventory when authentication, checkout or hosting integrations change. This version describes the implementation identified by the date above. Report an unexpected cookie or tracker to support@nativeactions.com with its name and the page where it appeared; do not send authentication-cookie values or payment secrets.