Cookie Policy

Effective date: 2026-11-07

This Cookie Policy explains how Intrect uses cookies and similar technologies on the ArtifactNet dashboard (app.intrect.io) and demo pages.

1. What Are Cookies?

Cookies are small text files stored on your device when you visit a website. They allow the site to remember your actions and preferences over time.

2. Cookies We Use

2.1 Strictly necessary (no consent required)

NamePurposeDuration
sessionFastAPI session middleware (login state)Session
intrect_sessionHttpOnly session cookie for signed-in requests (Secure; SameSite=Lax; Domain=.intrect.io)24 hours
Google OAuth stateCSRF protection during login flow15 minutes

2.2 Functional

NamePurposeDuration
themeDashboard light/dark mode preference1 year
localeLanguage preference1 year

2.3 Analytics

The website, dashboard and demo pages load Google Analytics 4 through Google Tag Manager using Google Consent Mode in its advanced form. If you visit from the European Economic Area, the United Kingdom or Switzerland, analytics and advertising measurement stay off until you allow them, and a consent banner asks you. Everywhere else analytics and advertising measurement (Google and Meta) are on by default, no banner is shown, and you can turn each of them off at any time under Privacy choices; a Global Privacy Control signal from your browser is honoured as an opt-out of advertising measurement. The region is read from the country Cloudflare attaches to your request, and is checked again on each visit, so a regional default never applies inside those three areas; the country itself is not stored. Until that answer arrives (normally well under two seconds) Google applies the same regional rule using its own location estimate, and if it does not arrive everything stays off and the banner asks you. In this policy, "analytics consent" (and likewise Google or Meta advertising measurement consent) means that the purpose is on for you: by your own choice, or by the regional default until you turn it off. Where a purpose is on by default we record that default with your pseudonymous consent key, marked as a regional default rather than your choice; any choice you make replaces it. While analytics is off, analytics storage is denied: Google receives cookieless pings (page and event, with your browser's IP address and user agent as for any request) without setting or reading analytics cookies or identifiers, and uses them only in aggregate. Only while analytics is on does Analytics set Google's analytics cookies (_ga, _ga_<id>) on your device, typically for up to two years. In the European Economic Area, the United Kingdom and Switzerland advertising storage, ad user data and ad personalisation are denied by default; advertising storage and ad user data are enabled only by a separate Google advertising measurement choice, and ad personalisation remains denied there. Elsewhere all three follow Google advertising measurement: on by default, and off when you turn it off or your browser sends a Global Privacy Control signal. Measurement is linked across intrect.io, app.intrect.io, demo.intrect.io and try.intrect.io so one visit is not counted several times.

Intrect also sets intrect_attribution_v1, a first-party cookie, for up to 90 days. In the European Economic Area, the United Kingdom and Switzerland it is set only with analytics consent and deleted when you turn analytics off. Everywhere else it is kept even when analytics is off, including after "Reject all", so that signups and purchases can be attributed to the visit that led to them. It contains no Google Analytics identifier. It stores an anonymous attribution identifier, the first and most recent Intrect landing path, referrer hostname, bounded campaign labels and the kind (not the value) of an advertising click identifier. It lets a checkout or successful installer download retain the visit that led to it after you move between Intrect subdomains. The download log receives only the anonymous attribution identifier, not the cookie's campaign fields. It does not store full referrer URLs, email addresses, filenames or payment details.

If you create an account while that cookie is kept, the bounded acquisition snapshot is copied to that account record, and with analytics consent so are the current Google Analytics client/session identifiers, so we can measure signup, first use and purchase as one funnel. The account copy is kept until you delete the account; later visits do not overwrite its original signup attribution.

When an Intrect payment completes (an ArtifactNet plan or top-up, plug-in licence, or Clean Audio top-up), and analytics consent is verified, Intrect also sends Google Analytics a server-confirmed purchase measurement and delivery marker, refund measurement and marker for each approved Paddle refund adjustment, and bounded adjustment, transaction and subscription lifecycle markers. These contain the Paddle transaction/event/adjustment identifiers, product category, status, currency, amount, tax and the bounded analytics/attribution identifiers above. They contain no email address, card data or raw Paddle payload. Without analytics consent every completed payment and approved refund is still recorded in Google Analytics, as an anonymous sale record so that revenue reporting is complete: the Paddle transaction/adjustment identifier, product category, currency, amount, tax, payment time and the checkout surface, under an identifier derived from the transaction itself. It carries no Google Analytics client or session identifier, no attribution, campaign, trial or device identifier, and is not used for advertising measurement; lifecycle markers are not sent without consent. Each retry record is kept for no more than 400 days, whether delivery succeeds or fails.

Intrect's sales ledger also keeps, with each completed payment, the bounded labels the checkout carried: checkout kind, product or plan, the page element that opened it and the price identifier; and, when present, the anonymous attribution identifier, first and most recent landing path, referrer hostname, campaign labels and click-identifier type, and (only if analytics was on) the Google Analytics client/session identifiers. It holds no email address, click-identifier value, search term or full URL. This copy is kept with the payment record for as long as we keep payment records for refunds, tax and accounting (typically 5–10 years depending on jurisdiction).

Plug-in milestones are sent to Google Analytics only when measurement consent is verified. Connecting a downloaded plug-in to a web visit additionally requires the optional browser linking flow. A download click is not treated as a trial activation. We do not infer a web visitor from an IP address or device fingerprint.

Cloudflare Web Analytics runs on the same pages. It is cookieless: it measures page views and performance without storing anything on your device and without identifying you across sites.

Aggregate API metrics are collected server-side via Prometheus in addition, and those do not involve client cookies.

2.4 Advertising

Google advertising measurement and Meta advertising measurement are independent of each other, of analytics and of email marketing. In the European Economic Area, the United Kingdom and Switzerland they are off until you allow them. Everywhere else they are on by default, and you can turn either off at any time under Privacy choices; a Global Privacy Control signal from your browser turns both off. Turning them off does not prevent listening, previews, downloads or checkout. Outside those three areas Google ad personalisation follows Google advertising measurement; inside them it stays denied.

With Google advertising measurement consent, intrect_google_click_v1 retains an existing Google click identifier for up to 90 days. Verified purchases may be sent to Google with product, value, original currency and event time, without email or email hash. With Meta advertising measurement consent, Meta Pixel may set _fbp and _fbc, and permitted actions may be sent to Meta. Verified purchases use server delivery and may include normalized, hashed checkout email and available browser/click identifiers. We do not send phone numbers, addresses, uploaded audio, filenames or authentication parameters.

Paddle payment and refund records remain in our internal accounting records regardless of measurement choices. Absence from advertising reports does not mean that a payment did not occur. We do not retroactively send historical purchases when you later opt in or when a regional default turns a purpose on.

3. Third-Party Cookies

When you authenticate via Google OAuth, Google may set cookies on accounts.google.com. Google Analytics, loaded through Google Tag Manager from www.googletagmanager.com, sets the analytics cookies described in 2.3. These Google services are governed by Google's Privacy Policy.

4. Managing Cookies

Use Privacy settings to allow all, reject all or choose each measurement purpose separately. The necessary intrect_measurement_v1 cookie remembers the choice, version and time for up to 180 days across Intrect subdomains; outside the strict regions it can instead hold the regional analytics default, marked as such, until you choose. A tab-session flag (intrect_measurement_strict, deleted when the tab closes) remembers that a visit came from a strict region so the check is not repeated. A new purpose requires a new choice. Withdrawal stops future browser and server measurement and cancels unsent events. Previously transmitted data is not erased by cookie withdrawal; contact privacy@intrect.io to request deletion, including data already disclosed to measurement providers.

You can also control or delete cookies through your browser settings. Disabling necessary cookies will prevent you from logging in.

5. Changes

If we add new cookies, we will update this Policy and announce changes on the dashboard.