Cookie Policy
Every cookie and storage entry pental.io sets, what it does, and how long it lasts. No advertising or analytics script runs on this site.
This policy covers pental.io and the Pental application. It lists everything we set, in full, rather than describing categories in the abstract.
No advertising cookies, no analytics cookies, no cross-site tracking, no data sold or shared with data brokers, and no consent banner, because nothing we set requires consent under PECR.
What we set on pental.io
| Name | Type | Purpose | Duration |
|---|---|---|---|
pental_theme | Local storage | Remembers whether you chose light or dark, so the site does not flash the wrong theme on your next visit. | Until cleared |
pental_currency | Session storage | Remembers the currency pricing was shown in during your visit. | Until the tab closes |
pental_signup_plan, pental_signup_billing, pental_signup_currency | Session storage | Keeps the plan you chose while you sign up, including through Google or Microsoft sign-in, which leaves the page. | Until the sign-up finishes or the tab closes |
_GRECAPTCHA | Cookie, set by Google | Abuse protection on the forms that carry it: contact, demo booking and sign-in. Set only on a page with one of those forms. | Up to 6 months |
Links from adverts and campaigns
If you arrive from an advert or a campaign link, the parameters on that link (such as utm_campaign, gclid or li_fat_id) stay in the page address as you move around the site. Nothing is written to your device to do this. If you create an account or send an enquiry, the campaign is saved with it. If the link came from a Google or LinkedIn advert, our server tells that platform about the sign-up; nothing is sent from your browser. The Privacy Policy has the detail, including how to opt out.
What the application sets when you sign in
These are strictly necessary: without them a signed-in session cannot exist. They are stored in your browser, on the domain of the portal you are using.
| Name | Purpose | Duration |
|---|---|---|
pental_token | Your session token, presented on each request to your own database. | Session, subject to your firm's timeout policy |
pental_email, pental_role | Identifies the signed-in account and the role it holds, so the interface renders the right thing. | Same as the session |
pental_exp | Session expiry timestamp, used to end a stale session client-side. | Same as the session |
pental_mfa_verified | When the second factor was last proved, which data access is gated on. | Same as the session |
Cookies on a customer's portal
If you are using a portal operated by a testing firm, that firm is responsible for its own domain and any cookie notice on it. The entries the Platform sets there are the strictly necessary session entries above. Firms can add their own tooling to their portal, and where they do, that is their arrangement to disclose.
Managing them
You can clear cookies and site storage in your browser at any time. Clearing the session entries signs you out; clearing the theme entry means the site falls back to your operating system preference. Nothing here can be disabled selectively because nothing here is optional tracking.
Changes
If we add anything, this table is updated before it ships, and the date at the top changes with it.
Pental Limited, 167-169 Great Portland Street, 5th Floor, London, W1W 5PF. Registered in England and Wales, company number 17172077.
Questions about this document go to hello@pental.io. We answer them ourselves.