Aspis Cookie Policy
Effective date: 1 October 2026
If you had an account with us before 1 October 2026, this policy applies to you from 1 November 2026. Until then, our previous cookie policy continues to apply to you.
1. About this policy
This policy is issued by Aspis Protocol Ltd, a company registered in England and Wales under company number 15506799. Our registered office is at 167-169 Great Portland Street, 5th Floor, London W1W 5PF, United Kingdom. In this policy, "we" and "us" mean Aspis Protocol Ltd.
It explains the cookies and similar technologies we use on:
- our website, aspis.finance; and
- the Aspis web app at v3.aspis.finance.
Please read it together with our Privacy Policy. That policy explains how we use the personal data these technologies collect, and your rights.
Aspis Copilot, our Telegram bot, does not use cookies. Our Privacy Policy explains how Copilot usage is analysed.
AgentCouncil is our other brand. Its sites (agentcouncil.org and dashboard.agentcouncil.org) have their own AgentCouncil Cookie Policy. Because they are on a different web address, you make your cookie choices for them separately.
2. What cookies and similar technologies are
- Cookies are small text files that a website saves in your browser. The website can read them back on later visits.
- Local storage and session storage are areas of your browser where a website can keep information. Session storage is cleared when you close the tab. Local storage stays until it is deleted.
- IndexedDB is a larger store inside your browser that some tools use to hold data for a short time.
- Tags, pixels and scripts are small pieces of code, from us or from other companies, that run on a page and can send information about your visit to whoever supplied them.
- Session recording (also called session replay) is a tool that records how you use a page, such as where you click and scroll, so that the recording can be replayed later.
A first-party cookie is set by the site you are visiting. A third-party cookie is set by another company's web address. In this policy, "cookies" covers all of these technologies.
The law (the Privacy and Electronic Communications Regulations 2003, or PECR) says we must ask for your consent before we store information on your device or read it from your device, unless an exception applies. We rely on two exceptions: where the storage is strictly necessary to provide a service you have asked for, and where it only remembers a choice you have made about how the site looks or works, such as closing a banner. For everything else, including all analytics and marketing, we ask for your consent.
3. Your choices and how our cookie banner works
Your first visit. On your first visit, a banner asks what you would like. You can choose Reject all, Accept all or Manage settings. All three have equal prominence. "Manage settings" lets you switch analytics and marketing cookies on or off separately.
Nothing optional before you choose. Until you make a choice, we use only strictly necessary cookies. No analytics or marketing tools load. If you do not make a choice, we treat that as a no.
How we remember your choice. We store your choice in a cookie called cc_consent. It records which optional categories you allowed and when you chose. It lasts 6 months, and then we ask you again. We will also ask again if we change the categories of cookies we use. We do not keep a copy of your cookie choice on our servers. If you delete your cookies, or use another browser or device, we will ask you again.
One choice for all Aspis pages. Your choice applies to aspis.finance and all its subdomains, including the web app, so you only need to choose once.
Changing your mind. Select Cookie settings at the bottom of any page to change your choice at any time. It is as easy to withdraw consent as it was to give it. When you switch off analytics or marketing cookies, we delete the cookies and browser storage those tools placed on our own web addresses, including the TILDAUTM cookie and any session recordings stored in your browser that have not yet been sent to Amplitude. We then reload the page so that no optional tool keeps running. Cookies that other companies set on their own web addresses, such as X's, can only be deleted from your browser (see section 11).
Rejecting cookies does not stop you using our sites.
4. The categories we use
| Category | What it is for | Do we need your consent? |
|---|---|---|
| Strictly necessary | Making the sites work and keeping them secure: signing in, connecting your wallet, taking payments, and remembering your cookie choice | No. These are always on |
| Functional | Remembering something you chose or entered while using a feature, such as closing a banner | No. They are set only when you use that feature |
| Analytics | Understanding how people use our sites so that we can improve them, including session recordings and linking your visits with Aspis Copilot | Yes |
| Marketing | Measuring our advertising and which campaigns bring people to us | Yes |
5. Google Consent Mode
We use Google Consent Mode (version 2) to pass your choices to Google's tags.
- Before you choose, our pages tell Google that consent is denied for four things: analytics storage, advertising storage, sending user data to Google for advertising, and personalised advertising. We also switch on Google's ad data redaction.
- Google's analytics and advertising tags do not load at all until you accept the matching category.
- When you make or change a choice, we update these signals. Analytics storage is granted only if you accept analytics cookies. The three advertising signals are granted only if you accept marketing cookies.
- The "functionality" and "security" signals stay on, because they cover only strictly necessary storage.
6. Session recordings
If you accept analytics cookies, Amplitude records every visit you make to aspis.finance and the web app. A recording captures the pages you view, your clicks, scrolling and mouse movements, and what the page showed at the time. We use recordings to find and fix problems and to improve our design. We do not use them for advertising. Only our authorised staff can view them.
What is hidden. Text you type into form fields, including passwords, is masked in your browser before any recording is sent, so we do not see what you typed. Our staff admin screens and any screen that shows an API key are not recorded. Card details are entered in Revolut's secure payment field, which is not recorded.
What may be captured. Other text shown on the page may appear in a recording. For example, this can include your nickname, email address or wallet address on your account page.
Amplitude keeps recordings for up to 90 days, and other analytics events for up to 24 months. If you reject analytics cookies, or later switch them off, no recordings are made.
Some Amplitude settings are managed from our Amplitude account. This means we can adjust them without changing our website. Any change stays within the analytics purpose described here, and it applies only if you have accepted analytics cookies.
7. Linking your website visits with Aspis Copilot
If you accept analytics cookies:
- a small script of ours (bot-analytics.js) adds your Amplitude device ID to links to Aspis Copilot on our pages. If you open Copilot through one of these links, we connect that device ID to your Telegram ID;
- when you connect a wallet in the web app, we send the wallet address and your device ID to our analytics service;
- if you open the web app from a link in Copilot, the link carries your Telegram ID. We keep it briefly in your browser (fromTgId) and record that you came from Copilot.
This lets us understand how people move between our website, the web app and Copilot. Our Privacy Policy explains what we do with the linked data. If you reject analytics cookies, links to Copilot do not carry your device ID, and we do not send your wallet address or Telegram ID to our analytics service from your browser.
8. The cookies and similar technologies we use
The "Where" column shows whether an item is used on the aspis.finance website, in the web app, or on both. Where another company decides how long its own cookies last, the table says "Set by" that company; their privacy or cookie policy gives the details.
8.1 Strictly necessary
| Name | Set by | What it does | Where | How long |
|---|---|---|---|---|
| cc_consent | Aspis (first-party cookie) | Remembers your cookie choices and when you made them | Both, shared across all aspis.finance addresses | 6 months |
| aspis_access_token | Aspis (local storage) | Keeps you signed in | Web app | Until you sign out. The sign-in it holds lasts 15 minutes |
| aspis_refresh_token | Aspis (local storage) | Renews your sign-in without asking for your password again | Web app | Until you sign out. It lasts 7 days and is renewed each time it is used |
| aspis_email_verified_at | Aspis (local storage) | Tells your other open tabs that you have confirmed your email address | Web app | Until you clear your browser storage |
| aspis_disclaimer_ack_v1 | Aspis (local storage) | Remembers that you have seen our important notice, so that it does not appear on every page | Web app | Until you clear your browser storage |
| WALLETCONNECT_CLIENT_ID | Aspis (local storage) | Identifies the WalletConnect connection when you connect a vault on the Swap page | Web app | Until you clear your browser storage |
| Keys beginning @appkit/ or @appkit-wallet/, and WALLETCONNECT_DEEPLINK_CHOICE | Reown (local storage) | Connects your wallet and remembers the connection, the network you chose and wallets you used recently. Caches the balances and names shown in the wallet window, and, if you use an email or social-login wallet, your social username. We have switched off Reown's usage statistics | Web app | Until you disconnect your wallet or clear your browser storage |
| Keys beginning wc@2: and WalletConnect databases | WalletConnect (local storage and IndexedDB) | Keeps your wallet's connection session and pairing | Web app | Until you disconnect your wallet or clear your browser storage |
| Reown embedded wallet | Reown (third party, secure.walletconnect.org) | Runs the email or social-login wallet, if you choose that option | Web app, only if you choose it | Set by Reown; see their policy |
| Google sign-in | Google (third party, accounts.google.com) | Lets you sign in with Google. It loads when a sign-in or sign-up form is shown | Web app | Set by Google; see their policy |
| Telegram login | Telegram (third party, oauth.telegram.org) | Lets you link your Telegram account. It loads when you open your account page while Telegram is not linked | Web app | Set by Telegram; see their policy |
| Revolut checkout | Revolut (third party) | Takes your card payment, runs 3-D Secure checks and helps prevent fraud. It loads when you start a checkout or update your card | Web app | Set by Revolut; see their policy |
| __cf_bm | Cloudflare (first-party cookie) | Helps Cloudflare tell people from automated bots. Used only if Cloudflare's bot protection is switched on for the site | aspis.finance | 30 minutes |
8.2 Functional
These remember something you chose or did while using a feature. They are created only when you use that feature. If you do not want them, you can delete them at any time by clearing your browser's data for our site, and the site will go back to its default display.
| Name | Set by | What it does | Where | How long |
|---|---|---|---|---|
| aspis_verify_banner_dismissed | Aspis (session storage) | Hides the "confirm your email" banner after you close it | Web app | Until you close the tab |
| promo-code | Aspis (local storage) | Remembers a promo code you entered for an Agent-Fund | Web app | 30 days |
8.3 Analytics (only with your consent)
| Name | Set by | What it does | Where | How long |
|---|---|---|---|---|
| _ga | Google Analytics (first-party cookie) | Tells visitors apart, so that we can count visits and see how the sites are used | Both | 2 years |
| _ga_C20YGV6J1M | Google Analytics (first-party cookie) | Keeps track of your visit for our website's analytics | aspis.finance | 2 years |
| _ga_GL3ZS39FYV | Google Analytics (first-party cookie) | Keeps track of your visit for the web app's analytics | Web app | 2 years |
| AMP_489971b161 | Amplitude (first-party cookie) | Holds your Amplitude device ID and details of your current visit | Both | 1 year |
| AMP_MKTG_489971b161 | Amplitude (first-party cookie) | Records how you arrived: the referring site, campaign tags and ad click IDs | Both | 1 year |
| Amplitude storage (entries beginning AMP_ or amp) | Amplitude (local storage and IndexedDB) | Holds events and session recordings until they are sent to Amplitude | Both | Until they are sent, usually during the same visit, or until you switch off analytics cookies |
| browser_id | Aspis (local storage) | A random ID we use for analytics if Amplitude has not loaded | Web app | Until you switch off analytics cookies or clear your browser storage |
| fromTgId | Aspis (session storage) | Carries your Telegram ID from a Copilot link, so that we can record that you came from Copilot (section 7) | Web app | Until it is sent, or until you close the tab |
| bot-analytics.js | Aspis (script) | Adds your Amplitude device ID to links to Aspis Copilot (section 7) | Both | Stores nothing itself |
8.4 Marketing (only with your consent)
The web app uses no marketing cookies. These are used only on aspis.finance.
| Name | Set by | What it does | Where | How long |
|---|---|---|---|---|
| Google Tag Manager (GTM-T6FDDQMS) | Google (script) | Loads our other website tags and passes your choices to them | aspis.finance | Sets no cookies itself |
| X pixel (ppuz5 and pt3s6) | X (script from static.ads-twitter.com) | Records visits and actions, such as clicking a link to Copilot, so that we can measure our adverts on X | aspis.finance | Stores nothing itself |
| _twclid | X (first-party cookie) | Stores the X ad click ID if you arrived from an advert on X | aspis.finance | Set by X; see their policy |
| muc_ads, personalization_id and similar | X (third-party cookies on X's web addresses) | Used by X for advertising, including for its own purposes | aspis.finance | Set by X; see their policy |
| TILDAUTM | Aspis (first-party cookie, set by our form script) | Keeps the campaign tags from the page address, so that any form you submit shows which campaign brought you | aspis.finance | 30 days |
The companies that supply these tools may also use the data for their own purposes. Their privacy policies explain how they do this.
X. X can use the data its pixel collects for its own purposes, such as improving its advertising, under X's Privacy Policy. For collecting this data on our site and sending it to X, we and X are jointly responsible. We are responsible for asking for your consent and for telling you about it, and X is responsible for what it does with the data after that. You can use your data protection rights about this data with us or with X. You can also manage how X uses data for adverts in your X account settings.
9. Forms on aspis.finance
When you submit a form on aspis.finance, the form also sends us the address of the page, including any campaign tags in it. If you have accepted marketing cookies, it also sends the campaign tags kept in the TILDAUTM cookie (section 8.4). It sends no other cookies. The Privacy Policy explains how we use what you submit.
10. Cookies from our old banner
Our previous cookie banner used the cookies t_cookiesConsentGiven, t_cookiesCategories and t_cookiesRejectAll, which lasted 365 days. We no longer set or read them. Your browser may still hold them until they expire, and you can delete them at any time (see section 11).
11. Controlling cookies in your browser
You can also control cookies through your browser settings: you can block them, delete them or be warned before they are set. If you block strictly necessary cookies and storage, signing in, connecting a wallet and paying may not work. These pages explain how to manage cookies in common browsers:
Google offers a browser add-on that stops Google Analytics on every website. The ICO explains more about cookies on its website.
The simplest way to change your choices on our sites is to use Cookie settings at the bottom of any page.
12. Changes to this policy
We will update this policy when we add, remove or change the cookies and similar technologies we use. The date at the top shows when it last changed. If we add a new category of cookies, or use cookies for a new purpose, we will ask for your choice again.
13. Contact us
If you have any questions about this policy or our use of cookies, email info@aspis.finance, or write to Aspis Protocol Ltd, 167-169 Great Portland Street, 5th Floor, London W1W 5PF, United Kingdom.
