Cookie Policy
Last updated: October 17, 2026
This Cookie Policy explains how Arct Technology LLC ("Arct Cloud", "we", "us", "our") uses cookies and similar technologies on arct.cloud, the console at console.arct.cloud (the "Console"), docs.arct.cloud, our API and related subdomains (together, the "Platform"). It lists each cookie, what it does, how long it lasts and how you control it.
Our Privacy Policy describes the personal data these tools collect, our legal bases, who receives the data, transfers outside your country, how long we keep the data and your rights. Our Subprocessors page names the providers that process data for us and where they do so.
This policy does not cover websites and applications that our customers run on Arct Cloud servers. Their operators set their own cookies and are responsible for them.
1. Cookies and similar technologies
A cookie is a small text file that a website stores in your browser. The website, or a provider whose code runs on it, can read the cookie on later visits. We also use:
- Local storage: data a website keeps in your browser until you delete it.
- Session storage: data a website keeps in your browser until you close the tab.
- Tags: code from a provider such as Google that runs in your browser and sends information to that provider. We load Google tags through Google Tag Manager.
First-party cookies are set by the Platform. Third-party cookies are set by another provider, such as Google or Stripe. Some providers also set cookies on their own domains when their code runs on our pages, and pages a provider hosts, such as Google sign-in or the Cryptomus payment page, set that provider's cookies. Their own cookie policies cover those cookies.
Where a provider collects data through its code on our pages, our responsibility is limited to that collection and its transmission to the provider. We do not control how a third-party provider reads its cookies or what it does with the data after it receives it, and we are not responsible for its practices. The provider's own privacy and cookie policies govern them. Please read those policies before you accept the related category.
Console pages load an icon font, and the card payment form loads a text font, from Google Fonts. When the page opens, your browser requests the font files from Google, which receives your IP address, browser details and the address of the site that requested the font. Google Fonts stores nothing in your browser for this, so it has no row in section 4. The Privacy Policy lists Google as a recipient of this data.
In this policy, "cookies" includes these similar technologies unless we say otherwise.
2. How we ask for consent
On arct.cloud, visitors in every country are asked for consent before optional analytics or advertising tags load. The Console applies the same saved choice to its own cookies and tags.
- On your first visit, a banner lets you accept all categories, reject all of them, or choose by category. The reject option sits on the same screen as the accept option, at the same size.
- Until you choose, we use only strictly necessary cookies. Arct Cloud analytics sets no cookies and stores nothing in your browser, so it runs without consent (section 5).
- Non-essential cookies and tags load only after you accept their category.
- You can change or withdraw your consent at any time through the Cookie preferences link at the foot of every page on arct.cloud, or through Cookie preferences in the Console account menu.
- Withdrawal applies from the moment you make it. It does not affect the use of cookies before that moment. To remove cookies already stored, delete them in your browser as described in section 8.
- You can use the Platform and order servers without accepting any non-essential category. Features in a category you reject do not load. Support through the ticket system stays available.
We store your choice in the consent cookie listed in section 4. The choice applies to the browser and device on which you made it. If you delete your cookies, the banner asks again.
The documentation site at docs.arct.cloud is hosted by Mintlify and does not show our consent banner. When you visit it, Mintlify stores the analytics identifiers and display choices listed in section 4 and records the pages you view. You can remove them by clearing your browser's site data for docs.arct.cloud, as described in section 8.
Where the GDPR, the UK GDPR or a similar law applies, your consent is our legal basis for functional, analytics, and advertising and measurement cookies. Strictly necessary cookies do not need consent. We use them to provide the Platform and the Account you sign up for, and in our legitimate interest in keeping it secure.
3. Categories
Strictly necessary
These cookies are required for the Platform to work. They sign you in to the Console, keep your session secure, support payments, block automated abuse, remember your cookie choices and remember display choices you make on the documentation site. They are always on. If you block them in your browser, signing in and paying will not work.
When you sign up or sign in to the Console, we set the sign-in, session and security cookies and storage listed in section 4 without asking for consent, because your Account and the core Console features need them.
Functional
These cookies remember choices that make the Platform easier to use, such as an order preference carried through sign-in. They also run the support chat in the Console where it is offered. They load only with your consent.
Analytics
These cookies show us how visitors use the Platform, for example which pages they open and where a visit started. We use the results to improve the Platform. They load only with your consent, except Mintlify's analytics storage on the documentation site, which section 2 describes. With this category, Arct Cloud analytics also records the first page of your visit and whether you visited before, as described in section 5.
Advertising and measurement
These cookies and tags measure whether our Google Ads campaigns and referral links lead to sign-ups and purchases. They record ad click identifiers, campaign tags and referral codes, and report conversions to Google Ads. They load only with your consent.
4. Cookies and storage we use
The table lists the cookies and similar technologies used on the Platform. A duration is the longest time an item stays in your browser unless you delete it earlier. Third-party providers may change the names, number or duration of the cookies they set without notice to us. Their own policies give the current details.
| Name | Provider | Purpose | Category | Duration |
|---|---|---|---|---|
arct_consent | Arct Cloud (arct.cloud and Console) | Stores your cookie choices so we can apply them on each page. | Strictly necessary | 180 days; the banner asks again after the choice expires |
__session (large sessions are split into __session__0, __session__1 and so on) | Auth0 (Okta), on the Console | Keeps you signed in to the Console. | Strictly necessary | Ends after 30 minutes without activity, and no later than 4 hours after sign-in |
__txn_<state> | Auth0 (Okta), on the Console | Links a sign-in request to its response and protects the sign-in against forgery. | Strictly necessary | Up to 1 hour; deleted when sign-in completes |
auth0, did and related Auth0 cookies | Auth0 (Okta), on the sign-in page Auth0 hosts for us | Keep your session on the sign-in page and help detect suspicious sign-in attempts. | Strictly necessary | Set by Auth0 under the session settings of our Auth0 account |
__stripe_mid | Stripe, on the Console | Helps Stripe detect and prevent fraud during card payments. | Strictly necessary | 1 year |
__stripe_sid | Stripe, on the Console | Helps Stripe detect and prevent fraud during card payments. | Strictly necessary | 30 minutes |
__cf_bm | Cloudflare | Tells human visitors apart from automated traffic to protect the Platform from abuse. | Strictly necessary | 30 minutes |
Cloudflare Turnstile | Cloudflare, on the contact, sales and abuse report forms | Checks that the contact, sales and abuse report forms are sent by a person. | Strictly necessary | Set by Cloudflare |
login_event_sent (session storage) | Arct Cloud (Console) | Makes sure each sign-in is written to your account activity log once. | Strictly necessary | Until you close the browser tab |
support:attachment-error:<ticket ID> (session storage) | Arct Cloud (Console) | Shows an attachment upload error on the ticket page after you open a ticket. | Strictly necessary | Deleted once shown, or when you close the browser tab |
arct_order_pref | Arct Cloud (Console) | Carries the location and tier you picked on arct.cloud through sign-in, so the order page opens with them selected. | Functional | 7 days |
arct:count:<list> (local storage) | Arct Cloud (Console) | Remembers how many rows each Console list showed, so the loading placeholder matches. | Functional | Until you clear site data |
intercom-id-<app ID>, intercom-device-id-<app ID> | Intercom, on the Console | Run the support chat and keep your conversation history across visits. | Functional | 9 months |
intercom-session-<app ID> | Intercom, on the Console | Keeps your chat session open while you use the Console. | Functional | 1 week |
isDarkMode (local storage) | Mintlify, on docs.arct.cloud | Remembers the light or dark theme you choose on the documentation site. | Strictly necessary | Until you clear site data |
bannerDismissed (local storage) | Mintlify, on docs.arct.cloud | Remembers that you closed a notice banner on the documentation site. | Strictly necessary | Until you clear site data |
_ga | Google (Google Analytics 4) | Distinguishes browsers so we can count visitors and measure how the Platform is used. | Analytics | 2 years |
_ga_<ID> | Google (Google Analytics 4) | Keeps the current Google Analytics session. <ID> is our Google Analytics property ID. | Analytics | 2 years |
arct_first_seen (local storage) | Arct Cloud (arct.cloud) | Records the date of your first visit so analytics can tell new visitors from returning ones. | Analytics | Until you clear site data |
arct_landing (session storage) | Arct Cloud (arct.cloud) | Records the first page you opened in this tab so analytics can see where a visit started. | Analytics | Until you close the browser tab |
ph_<project key>_posthog | PostHog, on the Console | Product analytics: measures how Console features are used. PostHog keeps a copy in local storage. | Analytics | 1 year |
mintlify_anonymous_id (local storage) | Mintlify, on docs.arct.cloud | A random identifier that lets Mintlify count page views and returning visitors on the documentation site. | Analytics | Until you clear site data |
mintlify_session_id (session storage) | Mintlify, on docs.arct.cloud | Groups the documentation pages you view in one visit. | Analytics | Until you close the tab |
_gcl_au | Google (Google Ads) | Links a Google ad you saw or clicked to a later sign-up or purchase, so we can measure our campaigns. | Advertising and measurement | 90 days |
_gcl_aw | Google (Google Ads) | Stores the click identifier of a Google ad you clicked. | Advertising and measurement | 90 days |
arct_attr | Arct Cloud (arct.cloud and Console) | Stores the campaign tags (UTM parameters) and ad click identifiers (Google gclid, gbraid and wbraid, and Meta fbclid) from the link that brought you to us, so a later sign-up or order can be credited to that campaign. | Advertising and measurement | 90 days |
arct_aff | Arct Cloud (arct.cloud and Console) | Stores the referral code from a referral link so the referrer can be credited when you sign up. | Advertising and measurement | 30 days |
arct_ref | Arct Cloud (Console) | Stores a signed link from our Discord referral program so the referral can be credited when you sign up. | Advertising and measurement | 30 days |
arct_signed_up | Arct Cloud (set by the Console for arct.cloud and Console) | Records that this browser has already reported a sign-up, so the sign-up conversion is counted once. | Advertising and measurement | 2 years |
arct_purchase_reported:<order ID> (local storage) | Arct Cloud (Console) | Records that a crypto order was already reported to our analytics and advertising tools, so the purchase is counted once. | Advertising and measurement | Until you clear site data |
5. Arct Cloud analytics
We count visits with Arct Cloud analytics, a service we host ourselves at i.arct.cloud. It sets no cookies and stores nothing in your browser, so it runs for every visitor on arct.cloud and in the Console without asking for consent.
It records the address of each page you open, including any campaign tags (UTM parameters) in the link, the referring site and actions such as sign-up and purchase. We remove ad click identifiers and referral codes from page addresses unless you accept advertising and measurement cookies. If you accept analytics cookies, we also add the first page of your visit (arct_landing) and whether you visited before (arct_first_seen). If you accept advertising and measurement cookies, we add the campaign tags, ad click identifiers and referral code stored in arct_attr and arct_aff. After you sign in to the Console, we link your analytics activity to your account.
6. Google tags and Consent Mode
We use Google Analytics 4 and Google Ads on arct.cloud and in the Console. Both load through Google Tag Manager.
We use Google Consent Mode. Before any Google tag runs, we set its four consent signals to denied for every visitor: analytics_storage, ad_storage, ad_user_data and ad_personalization. A signal changes to granted only after you accept the matching category. Analytics controls analytics_storage. Advertising and measurement controls ad_storage and ad_user_data. ad_personalization remains denied. The shared Google container loads only when both analytics and advertising measurement are allowed, so it does not send cookieless Google pings before those choices. Accepting analytics alone keeps the Google container blocked.
If you accept advertising and measurement cookies, we copy the Google click identifiers stored in arct_attr to your account when you sign up or sign in, and to each order you place. For each paid order, we send Google Ads the click identifier, the order value, the currency and the time of payment as an offline conversion, so Google can report which ads led to purchases.
If you accept analytics cookies, we store the Google Analytics identifier from your _ga cookie with your account when you place an order. Our servers use it to send purchase events to Google Analytics. After you sign in, the Console also sends Google Analytics your account identifier as a user ID. If you withdraw analytics or advertising consent, we delete the stored Google Analytics identifier or click identifiers from your account the next time you open the Console. Our Privacy Policy describes this processing and how long we keep the data.
Google processes Google Analytics data for us as our service provider. Google also processes advertising data for its own purposes under its advertising privacy terms. The applicable roles depend on the product and processing operation. Google explains its use of this data at policies.google.com/technologies/partner-sites.
7. Global Privacy Control and Do Not Track
If your browser sends a Global Privacy Control (GPC) signal, we treat it as a refusal of advertising and measurement cookies in that browser. We do not load those cookies and tags while the signal is present, and that category cannot be enabled through Cookie preferences while the signal remains active.
We do not act on Do Not Track browser signals. Use Cookie preferences or GPC to set your choices.
8. Controlling cookies in your browser
Cookie preferences is the main way to control cookies on the Platform. You can also use your browser:
- Most browsers let you block cookies, delete them, or delete all site data for a domain. Deleting site data for arct.cloud and console.arct.cloud also removes the local and session storage listed in section 4.
- Private or incognito windows delete their cookies and storage when you close them.
- The help pages of Chrome, Firefox, Safari and Edge describe the steps for each browser.
- Browser settings apply only to the browser and device on which you change them. Set them on each browser and device you use.
- Blocking cookies may not stop tags or other technologies that do not rely on cookies.
If you block or delete cookies, we cannot guarantee that the Platform will work as intended, and some features may not be available. If you block strictly necessary cookies, you cannot sign in to the Console or pay for an order. Browser settings and third-party cookie tools are provided by their makers, and we are not responsible for how they work.
Google also offers its own controls:
- Google Analytics opt-out browser add-on: tools.google.com/dlpage/gaoptout
- My Ad Center, for your Google ad settings: myadcenter.google.com
9. Changes to this policy
We may update this policy at any time, for example when we add, remove or change a cookie or similar technology, or when the law changes. The date at the top of this page shows when we last changed it. Unless we state a later date, an updated policy takes effect when we post it. Before we use cookies for a new purpose, or let a new third party use the data for its own purposes, we ask for your consent again where the law requires it. Please check this page from time to time.
10. Contact
For questions about this policy or our use of cookies, email [email protected]. The Privacy Policy explains how to exercise your rights over the personal data that cookies collect.