Legal · Cookies
Cookie Policy
Pre-incorporation draft. The status note below explains what that means.
This Cookie Policy explains what cookies and similar technologies Talisman uses on the website at talismanproject.org and in the Talisman application, why we use them, and how to control them. It complies with the Privacy and Electronic Communications Regulations 2003 (PECR) regulation 6 and with UK GDPR.
Status. Pre-incorporation draft. The cookie inventory below reflects the current, deliberately-minimal setup. A consent banner will be activated before any non-essential cookies or similar technologies are introduced. Bracketed
[TBC]markers indicate items pending sign-off.
1. What are cookies and similar technologies
A cookie is a small file placed on your device by a website you visit. Cookies are commonly used to make websites work, to remember your preferences, and to gather information about how a site is used. The same rules in PECR regulation 6 apply to other technologies that store information on or read information from your device, including local storage, IndexedDB, service workers, and HTTP-cache directives where they are used to identify users.
Outside the browser context, the Talisman application stores data on your device for offline-first operation. That data is not "cookies" in the strict sense, but the data-protection principles in the Privacy Policy apply to it.
2. The website
The Talisman marketing website at talismanproject.org is currently set up with no analytics cookies, no advertising cookies, and no third-party tracking pixels. The cookies and similar technologies that may be set are:
| Name | Type | Purpose | Lifetime | Consent required under PECR? |
|---|---|---|---|---|
theme (local storage) | Strictly necessary | Remember your colour-theme preference (cyan / dark) so the site renders correctly when you return | Until you clear local storage | No (functionality you have requested) |
| Vercel platform cookies (where served via Vercel) | Strictly necessary | Load-balancing, security, and platform integrity | Session | No (strictly necessary) |
[TBC: any others identified at sign-off] | — | — | — | — |
Strictly-necessary cookies and storage do not require consent under PECR regulation 6(4). They are used only as necessary to provide the service you requested.
If we introduce analytics, behavioural, or any other non-essential cookies in the future, we will:
- Add them to the table above.
- Add a consent banner to the website that asks for your prior, freely-given, specific, informed, and unambiguous consent before any such cookie is set.
- Allow you to withdraw consent as easily as you gave it.
We do not currently use any third-party advertising or behavioural-tracking pixels.
3. The waitlist form
The waitlist sign-up form on the website transmits the email address you submit to our infrastructure. The submitted address is stored in our records on the lawful basis described in the Privacy Policy. The form does not, on its own, set a tracking cookie that follows you elsewhere.
4. The Talisman application
The Talisman iOS application stores data on your device for offline-first operation. The principal categories are:
- Authentication state — secure-storage tokens that keep you logged in.
- Library and listening-time credit balance — locally cached for offline access and immediate-availability features.
- Track and album metadata — locally cached for browsing without a network round-trip.
- Audio caches — for tracks you have unlocked into your Library, lossless FLAC stored locally; for metered listening, time-bounded caches that the application clears on its own schedule.
- Mesh peer state — where you have opted in to mesh participation, ephemeral peer-discovery records.
- Notification preferences and opt-in flags — your in-app choices for what features are on.
- Embedded PRISM database state — the on-device portion of the Talisman storage layer.
This is not "cookies" in the PECR sense, but is documented here to give a single, complete picture of what is stored and where. The Privacy Policy describes the lawful basis for each category and your rights over it.
5. Third-party cookies in checkout flows
When you complete a digital purchase via the Talisman web Airlock, you transition to a Stripe-hosted checkout. Stripe sets its own cookies in that browser context as part of fraud prevention and the payment user experience. Stripe is the controller of those cookies. See Stripe's privacy and cookie information.
When you complete a physical purchase from within the Talisman application, the same Stripe consideration applies in the in-app browser context.
6. Controlling cookies
You can control cookies through your browser settings. Each browser is different; the relevant help pages are:
Restricting cookies may stop parts of the website from working. Strictly-necessary cookies and storage cannot be disabled without affecting the service.
For the application, the in-app settings let you control cache size, mesh participation, notifications, and account log-out. Closing your account erases the local data subject to the retention rules in the Privacy Policy.
7. Updates
We update this Policy when our cookie inventory changes. The "updated" date in the document header reflects the date of the most recent change.
Drafted in pre-incorporation form, 28 April 2026, for review and finalisation by qualified UK counsel.