Pandus SDK documentation
Limits and retention
How many sites, events and recordings each plan includes, how long data is kept, the live axe sample and what happens when a quota is reached.
Updated:
The SDK is part of the Pro and Agency plans. The limits below are the ones your account uses; prices are on Pricing.
| Plan | Sites with the SDK | Events a month | Recordings a month | Events kept, days | Recordings kept, days | Live axe sample |
|---|---|---|---|---|---|---|
| Pro | 1 | 1,500,000 | 300 | 395 | 30 | 2 % |
| Agency 10 | 10 | 6,000,000 | 1,000 | 395 | 30 | 2 % |
| Agency 25 | 25 | 15,000,000 | 2,500 | 395 | 30 | 2 % |
| Agency 50 | 50 | 30,000,000 | 5,000 | 395 | 30 | 2 % |
How events are counted
- An event is one row of the event reference. One page view is about 15 events.
- Limits are shared by all sites of the team.
- Heatmap points (
hm_click,hm_view) and debug mode do not count. - Server events count like events from the browser.
When a quota is reached
The SDK lowers the sample and then stops collecting analytics and recordings until the next month. Barrier signals are collected until a hard limit and are the last to stop. You get a notice in the dashboard and by e-mail with the option to move to a larger plan.
Retention
Events are kept for the number of days in the table (13 months by default), recordings for 30 days by default. Older data is deleted automatically every night. On Free and with the express report the SDK modules are off; the “Report a barrier” button and the accessibility page stay.
The Pandus SDK and the scanner are automated checks, not a full audit, and not legal advice. The SDK changes nothing on your site and does not determine which visitors use assistive technology.