Cookies, listed one by one.

1. What cookies are, and why we use them

Cookies are small text files that a website stores in your browser. Similar technologies, such as local storage and pixels, work in the same way, and this policy covers them too. We use them to keep this site working, to remember your choices and, if you agree, to understand how the site and our documentation are read.

This policy covers this website, our documentation and the developer dashboard. It does not cover our Partners’ software: if you run payroll inside a Partner’s product, that product’s own cookie policy applies.

2. The categories we use

Strictly necessary. Keep the site secure, keep you signed in to the developer dashboard and remember your cookie choice. They are always on, because the site cannot work without them.

Preferences. Remember the code language you picked in the documentation and whether you closed an announcement. Off until you accept them.

Analytics. Count visits and measure which pages and guides are read, in aggregate. Off until you accept them.

Marketing. We do not use advertising or retargeting cookies on this site.

3. Cookies on this site

payrun_consent (Payrun). Stores your cookie choices. Strictly necessary. Kept for 12 months.

__session (Payrun). Keeps you signed in to the developer dashboard and protects forms against cross-site requests. Strictly necessary. Deleted when you sign out, or after 12 hours.

docs_lang (Payrun). Remembers whether you read code samples in curl, Node or Python. Preferences. Kept for 6 months.

_analytics_id (analytics provider). Distinguishes visitors so they can be counted, only after consent. Analytics. Kept for 13 months.

_analytics_session (analytics provider). Groups page views into one visit, only after consent. Analytics. Kept for 30 minutes.

4. Third parties

Analytics cookies are set by our analytics provider, which processes the data on our behalf and may not use it for its own purposes.

The scheduling tool used to book a demo may set its own strictly necessary cookies when you open it; its cookie policy applies. We do not allow advertising networks to set cookies through this site.

5. Emails and pixels

Service emails, such as notices about API changes, deprecations and incidents, contain no tracking pixels.

Product news emails count opens and clicks only if you asked to receive them, and every one of them has a one-click unsubscribe link.

6. How to manage your choices

When you first visit, you can accept or refuse each optional category. Refusing optional cookies does not limit what you can read or do on the site. To change your choice later, clear this site’s cookies in your browser and choose again.

We treat a Global Privacy Control signal sent by your browser as a refusal of optional cookies. You can also block or delete cookies in your browser settings; if you block strictly necessary cookies, parts of the site, such as the developer dashboard, may stop working.

7. Changes and contact

We update this policy when we add, remove or change a cookie. The date at the top of this page shows the latest version.

Questions about cookies can be sent to privacy@payrun.example (demo address) or through our contact page.