Cookie Policy

Cookies are small text files that a website stores on your device so it can recognize your browser on later visits. Similar technologies — such as local storage, session storage, and server-set tokens — serve the same purpose and are covered by this Policy wherever we refer to “cookies.”

A cookie is a session cookie if your browser deletes it when you close it, or a persistent cookie if it survives until it expires or you clear it. A cookie is first-party if ERPat sets it, or third-party if a provider we use sets it in the course of delivering a feature you have enabled.

We do not use advertising, retargeting, or cross-site tracking cookies.

When you sign in, we set a session cookie that identifies your authenticated session. It lets you move between pages without re-entering your credentials, and it expires when you sign out, when the session times out, or when you close your browser, depending on your configuration. Deleting this cookie signs you out.

Where your organization enables one-time passwords or email verification, short-lived tokens may also be stored to complete that flow. These are discarded once verification succeeds or expires.

The Service issues a per-session token used to verify that form submissions and API requests genuinely originate from your session rather than a malicious site. This is a strictly necessary security measure described in Section 11 of our Privacy Policy and cannot be disabled without breaking the Service.

We store your appearance/theme setting and similar interface preferences so the Service looks the way you left it. These cookies hold only your choice — not your identity — and clearing them simply returns the interface to its defaults.

We may use limited analytics to understand and improve how the Service is used, in line with Section 7 of our Privacy Policy. Analytics data is used in aggregate — page and feature usage, timestamps, browser and device type, and approximate location derived from IP — and is not used to make decisions about individuals.

Where analytics is not strictly necessary and consent is required in your jurisdiction (for example, under the ePrivacy rules that accompany the GDPR), we will seek that consent before setting the relevant cookies. See our GDPR Compliance statement for how consent is handled for EU, EEA, and UK visitors.

Enabling an integration — such as email, SMS, payment, cloud storage, or an external authentication provider — may allow that provider to set its own cookies as needed to deliver the feature. Those cookies are governed by the third party’s own policies, which we do not control. This mirrors Section 11 of our Terms of Service.

You can view, block, and delete cookies through your browser settings. Every major browser lets you clear cookies for a specific site, block third-party cookies, or refuse cookies entirely, and most offer a private or incognito mode that discards them when the window closes.

Disabling strictly necessary cookies will prevent you from signing in and may stop the Service from functioning properly. Disabling preference cookies will reset your interface choices on each visit. Clearing cookies does not delete the records stored in your ERPat account.

We may update this Cookie Policy to reflect changes in the technologies we use or in legal requirements. We will revise the “Last Updated” date above and, for material changes, provide reasonable notice. Questions about cookies, or a request to exercise your rights, can be sent to: