Privacy

The Try it runner and the signature generator accept your clientId, clientSecret and a workspace access token so they can sign a request the way your own server would.

Those values are held in your browser's sessionStorage, scoped to the tab you are in. Closing the tab discards them. They are not sent to this documentation site, and no server here stores them — the signature is computed in your browser and the request goes directly from your browser to the COUNT API.

A request you send from Try it is a real API request against whichever environment you selected. It is subject to the same logging on COUNT's side as a request from your own integration, and a write really writes.

Your theme choice, your preferred code-sample language, and whether you have dismissed the integration tour prompt are kept in your browser's local storage so the site behaves consistently between visits. The splash animation records that it has played in session storage. None of this leaves your browser.

This site loads one third-party script: the Crisp chat widget (client.crisp.chat), which powers the in-page documentation assistant. If you open it, what you type goes to Crisp so it can answer. The widget loads whether or not you open it.

There is no analytics, advertising, or tracking script on this site. Pages are served as static files.

When your integration calls the Partner API, you are handling accounting data belonging to a COUNT customer who authorized you. Your obligations for that data are set by your agreement with COUNT and with that customer, not by this page. The partner programme covers what the review asks about data handling, and a workspace owner can revoke your access at any time from inside COUNT.

COUNT's security posture, subprocessors and compliance documentation are published at trust.getcount.com. To report a vulnerability, or for any question this page does not answer, see Contact.