Cookie Policy
Last updated
1. This website does not use cookies
TRUSTLINE DIGITAL ASSET LTD ("Trustline", "we", "us", "our") does not place cookies on your device when you visit https://www.trustline.id. No cookie is written, nothing is put in local or session storage, no pixel or tracking script is loaded, and no attempt is made to identify your device by its characteristics. We use no analytics, advertising or social media tools.
Nothing is stored on or read from your device, so there is nothing for you to consent to and you will not see a cookie banner.
One page is an exception, and only if you use it: section 1A describes the scheduling tool on the pricing page.
1A. The scheduling tool on the pricing page
The pricing page at /pricing ends with a calendar so that you can book a call. That calendar is provided by Cal.com, Inc. and appears inside the page.
It loads only if you reach it. The page has three steps and the calendar is the last one. Reading the pricing page, or filling in the first two steps and stopping, loads nothing from Cal.com and stores nothing. Cal.com is contacted only once you ask to choose a time.
What happens when it does load. Your browser fetches the calendar from Cal.com and displays it. Cal.com receives your IP address and browser details as part of that request, and stores what it needs on your device to run the booking and to remember your place in it. Cal.com is our processor for this and is bound by a written contract.
What we pass to it. The name, work email, company and scope answers you typed in the first two steps, so that you do not type them twice. Those answers are held in the page while you work through it. We do not write them to your device and, until you book, they are not sent anywhere.
Consent. Loading the calendar and storing what it needs is strictly necessary to provide the booking you have asked for at that moment, so it does not require consent. It is not analytics and it is not advertising. If you do not want it, do not open the last step: write to contact@trustline.id and we will arrange a time by email.
2. Server access logs
Our hosting provider records, in its access logs, your IP address, your browser's user agent string, the page requested, the time, the response code and the referring page. That is a record kept by the server, not something stored on your device, and it is an unavoidable part of how the web works.
We process it on the basis of our legitimate interests in keeping the website available and secure and in detecting abuse. It is not used to profile you or for marketing. Retention is set out in section 7 of our Privacy Policy.
Cal.com keeps equivalent logs of its own for the scheduling tool described in section 1A.
3. Other Trustline applications
This policy describes trustline.id and www.trustline.id, which store nothing at all. Trustline's other applications run on subdomains, are built and deployed separately, and differ from one another, so each is set out below. None of them uses cookies either, and none carries analytics, advertising, heatmap or session-recording tools.
Everything listed here is either strictly necessary to provide a service you asked for, or a preference you set yourself. Neither requires consent, which is why those applications give you this notice rather than a banner.
We are non-custodial. Most of these applications are interfaces to smart contracts on public blockchains. We do not hold your private keys, take custody of your assets, or keep a copy of the private information held in your wallet. Where such an interface keeps anything on your device, it is your wallet connection state, so that your wallet stays connected between pages.
3.1 auth.trustline.id — the authentication screen
This screen is designed to be embedded in the page of the company whose service you are using, at the moment you approve a transaction. It is not meant to be visited on its own, and it is excluded from search engines for that reason.
It stores your sign-in session, through Google's Firebase SDK, and nothing else. The session identifier that ties your approval to the right transaction arrives in the address of the page and is held in memory for the length of your visit; it is never written to your device. The screen re-checks your sign-in after one minute, so a stored session is short-lived in practice.
Because the screen runs inside someone else's page, your browser keeps anything it stores in a compartment separate from the site you are visiting. Neither can read the other's. We place nothing on your device through the site hosting us, and that site remains responsible for its own cookies and its own banner.
3.2 onboarding.trustline.id — the onboarding portal
Used by our customers' developers to configure their security rules. It stores your sign-in session, your email address so a half-finished setup can be resumed, which wallet you connected and which wallet extension you chose, and whether you picked light or dark mode.
3.3 dev.trustline.id — the developer documentation
Reference material, with no sign-in and no forms. It stores whether you picked light or dark mode, and nothing else.
3.4 The full list
| Name | Application | Type | What it is for | How long |
|---|---|---|---|---|
firebase:authUser:* | Authentication, onboarding | IndexedDB, or local storage where IndexedDB is unavailable | Keeps you signed in while you complete the flow. Set by Google's Firebase SDK. | Until you sign out. The authentication screen also re-checks your sign-in after one minute. |
trustlineEmail | Onboarding | Local storage | Lets you pick a half-finished setup back up where you left it. | Until you sign out or reset the wizard, or you clear your browser storage. |
walletConnected | Onboarding | Local storage | Records that you connected a wallet, so the page can reconnect it. | Until you disconnect. |
walletProvider | Onboarding | Local storage | Remembers which wallet extension you chose. | Until you disconnect. |
theme-mode | Onboarding, documentation | Local storage | Remembers the light or dark setting you picked. | Until you clear your browser storage. |
Signing out clears the sign-in entries and the stored email address. Everything else goes when you clear site data for that subdomain in your browser. Nothing on this list is needed once you have finished; removing it only means being asked to sign in again, or to reconnect your wallet, next time.
Google, through Firebase Authentication, is the only third party that stores anything on your device through any of our applications, and only to keep your sign-in session. Fonts, images and scripts on all four surfaces are served from our own domains, so no content delivery network sees your visit.
What each application collects, as opposed to what it stores on your device, is set out in section 3A of our Privacy Policy.
4. If this changes
If we later use cookies or similar technologies here, we will update this page and the date at the top before the change goes live, list what is used and why, and where consent is required, show a banner that blocks the technology until you give it and lets you withdraw it as easily.
Until this page says otherwise, nothing on this website is stored on your device apart from the scheduling tool in section 1A, and that only if you open it.
5. Do Not Track
Because this website does no tracking, a "Do Not Track" or "Global Privacy Control" signal has nothing to switch off. We honour it by default. The scheduling tool in section 1A is there to make a booking you asked for, not to track you.
6. Contact
Questions, or something on this website that this policy does not describe: privacy@trustline.id, or TRUSTLINE DIGITAL ASSET LTD, The Barn, c/o Integral Associates Limited, Rear of 3-5 Church Street, Ampthill, Bedford, England, MK45 2PJ, United Kingdom.
You may also complain to the Information Commissioner's Office. Its details are in section 14 of our Privacy Policy.