Cookie Policy

This Cookie Policy explains how Pay Engineers (“we”, “us”, “our”) uses cookies and similar technologies on our public website, intelligent configurator, processor-order flows, Stripe Connect workspace landing pages, authorizations & compliance resources, client portal, document exchanges, support tools, blog and related online services (together, the “Platform”).

It should be read together with our Privacy Policy (personal data processing) and Terms of Service (use of the Platform). Where this policy describes optional cookies, those technologies only run after you give consent through our cookie banner — except for strictly necessary cookies required to operate the site securely.

Cookies are small text files placed on your browser or device when you visit a website. They can be “session” cookies (deleted when you close the browser) or “persistent” cookies (kept until they expire or you delete them).

We may also use similar technologies that store or read information on your device for comparable purposes, such as local storage, session storage, or pixels embedded in pages or emails. In this policy, “cookies” includes those similar technologies unless we say otherwise.

As a B2B payment-infrastructure platform, we use cookies primarily to keep authenticated areas secure, remember your consent choices, maintain sessions across multi-step wizards (configurator, orders, compliance), and — only if you opt in — understand product usage and campaign performance.

We do not use cookies to sell your personal data. Optional analytics and marketing categories are off by default until you Accept all or enable them in Customise.

On your first visit (or after we raise the consent policy version), a banner offers three choices:

• Accept all — enables necessary cookies plus preferences, analytics and marketing.
• Reject non-essential — keeps only necessary cookies; optional categories stay off.
• Customise — open the preferences panel and toggle each optional category individually.

Necessary cookies cannot be disabled because the Platform would not function securely without them. You can reopen preferences anytime via “Cookie settings” in the footer, the floating cookie control, or the button on this page.

Necessary cookies are required for security, authentication, load balancing, CSRF protection, session continuity and remembering your cookie consent decision. They are set whether or not you accept optional categories.

• Consent record — cookie name pe_cookie_consent (and related local storage key pe_cookie_consent_v1) stores your category choices and policy version for up to 365 days, or until you clear site data / update preferences.
• Session & auth — Laravel session cookies keep you logged in to the client portal, admin area and multi-step flows (configurator, processor orders, compliance wizard).
• Security — tokens that protect forms against cross-site request forgery and help detect abusive traffic.
• Operational cookies required for core features such as document uploads, ticket replies or invoice payment redirects while you remain in an active session.

Preference cookies remember interface choices that make the Platform easier to use — for example language, region, display or UI settings — when we enable those features. They are off by default and only set if you opt in.

Refusing preferences does not block access to the public site or the essential client portal; you may simply need to re-select certain choices more often.

Analytics cookies help us understand how visitors and clients use Pay Engineers: which public pages or resources are useful, where wizards are abandoned, and where performance can improve. We prefer aggregated metrics where possible.

These cookies are off until you consent. They are not used to build advertising profiles for sale. If no analytics provider is active in a given environment, enabling the category simply authorises future measurement tools we may connect under the same consent.

Marketing cookies measure campaign effectiveness (for example whether a visitor reached the Stripe workspace, services catalogue or contact form from a campaign) and, where applicable, support more relevant communications.

They are off by default. We do not sell marketing cookie data to third parties. Newsletter subscription is separate: joining the newsletter uses the consent checkbox on the form and is governed by the Privacy Policy, not solely by marketing cookies.

Some features set functional identifiers that fall under the necessary or preference logic depending on context:

• Blog engagement — a long-lived blog_like_token may be used so like actions remain consistent across visits without requiring an account.
• Stripe workspace — entering Stripe management may rely on a short-lived workspace session established after the in-product consent dialog; that session is operational and not a marketing tracker.
• Configurator & orders — progress through multi-step wizards depends on authenticated session cookies and server-side draft storage, not on optional marketing cookies.

Most cookies we set are first-party (placed by the Pay Engineers domain you are visiting). If we embed third-party content (for example payment provider checkout frames, Stripe-hosted flows, or optional analytics scripts), those providers may set their own cookies under their policies when you interact with them.

When you leave our Platform for Stripe or a payment gateway, their terms and cookie notices apply to processing on their domains. Our Stripe Connect workspace is a convenience layer; it does not replace Stripe’s own disclosures.

Your consent preferences are stored for up to 365 days (see config max age), or until you clear them or change them in Cookie settings. If we materially change cookie categories or purposes, we bump the consent version so you are asked to confirm again.

Individual cookie lifetimes vary: session cookies expire when the browser closes; persistent cookies expire according to their purpose (consent up to one year; feature tokens such as blog like tokens may last longer).

In addition to our banner, most browsers let you block or delete cookies via their settings. Blocking all cookies — including necessary ones — may prevent login, multi-step wizards, secure form submission or payment flows from working.

You can also use private/incognito windows, clear site data for our domain, or browser extensions that limit trackers. Those tools are outside our control; our banner remains the primary way to manage optional Pay Engineers categories.

Cookie consent is one lawful basis for optional technologies. Broader rights over personal data (access, erasure, objection, etc.) are described in the Privacy Policy. Exercising those rights can be done via the Contact page.

Related documents: Privacy Policy, Terms of Service, and the Contact / Complaints channels for service questions.

We may update this Cookie Policy when our Platform, vendors or legal requirements change. The “Last updated” date will be revised accordingly. Significant changes to categories or purposes will be reflected in a new consent version and a fresh banner prompt.

Use the “Manage cookie settings” button at the bottom of this page (or Cookie settings in the site footer) to Accept all, Reject non-essential, or Customise categories at any time. Refusing optional cookies will not remove access to the public site or core authenticated features of Pay Engineers.