Cookies policy
What are cookies?
Cookies are small text files placed on your device when you visit a website. They allow the site to remember information about your visit, for example, that you are logged in, and are widely used to make websites work correctly.
How we use cookies
Cadrify uses only strictly necessary cookies and a small number of functional cookies to improve usability. We do not use advertising, tracking, or third-party analytics cookies. Under UK PECR, these cookies do not generally require consent, so no cookie banner is used. All cookies described in this policy are first-party cookies set by Cadrify.
Cookies we set
| Name | Purpose | Expiry | Type |
|---|---|---|---|
auth_token |
Authenticates you to the platform. Set on login and deleted on logout. Without this cookie you cannot access any authenticated part of Cadrify. | 7 days, or on logout | Strictly necessary |
session |
Stores temporary workflow state required to complete multi-step processes, such as the electoral register import (retaining column-mapping choices across page requests). Also stores referral parameters on public campaign pages. Any stored information is limited to data you have actively entered during the current workflow. | Browser session (deleted when you close your browser tab) | Strictly necessary |
signer_info |
Set on public-facing petition and event pages after you submit a form. Stores your name and email address so that your details are pre-filled server-side the next time you sign a form for the same organisation. Only set after a successful submission; the cookie is read by the server when rendering the form and is not accessible to JavaScript in the browser. | 90 days | Functional / preference |
Cookie attributes
All cookies set by Cadrify share the following security attributes:
- HttpOnly, the cookie cannot be read by JavaScript on the page, reducing the risk of cross-site scripting attacks.
- SameSite=Lax, the cookie is not sent on cross-site requests, reducing the risk of cross-site request forgery.
- Secure, the cookie is only sent over HTTPS, never over plain HTTP.
Browser storage (localStorage)
In addition to cookies, certain parts of the Cadrify platform use your browser’s localStorage to store data on your device. This is not a cookie and is not transmitted to the server automatically; it persists until cleared by the application or by you. Cadrify uses localStorage in the following ways:
- Door-knock field view, door-knock responses and knock results are queued in localStorage as an offline buffer while you are door-knocking without a reliable connection. This data (which may include elector contact details and responses) is synced to the server as soon as a connection is available and then cleared from localStorage. It persists locally only until the sync is acknowledged.
- GOTV round and telling views, similarly, door-knock and telling records are queued locally for offline resilience and cleared once synced.
- Activists table, column widths and layout preferences are saved locally so your view is preserved between visits. This contains no personal data.
localStorage data is accessible only to cadrify.org pages in your browser. No localStorage data is shared with third parties. You can clear localStorage at any time through your browser settings; doing so may cause any unsynced door-knock or GOTV responses to be lost.
Analytics and third-party cookies
Cadrify does not set or load any third-party analytics, advertising, or tracking cookies. We do not use Google Analytics, Meta Pixel, or any similar service on the platform or on this website.
UTM campaign parameters that appear in public campaign page links are stored in the
temporary session cookie (described above) to attribute sign-ups to the correct
campaign source. They are not passed to any third-party tracking service.
Managing and deleting cookies
You can view, block, or delete cookies at any time using your browser settings. The links below take you to guidance for the most common browsers:
Clearing the auth_token cookie will log you out of Cadrify. Clearing
signer_info will remove any pre-filled details on public petition and event
pages.
Changes to this policy
If we add new cookies or browser storage uses we will update this page and revise the “last updated” date above. Where legally required, we will seek consent before introducing any new non-essential cookies.
Contact
Questions about cookies: privacy@cadrify.org.