Legal

Implementation & Integration

Last updated: 13 July 2026

This page is the single, authoritative guide to what you (the customer) do on your side to deploy FAIND. FAIND has two moving parts: a hosted, AI-optimized Knowledge Graph (a static mirror of your existing public pages, served from a subdomain via CDN) and a one-line JavaScript snippet that runs on your own site. Deployment is a DNS change plus a script tag — no site migration, no redesign, no content rewrites. Below we cover DNS, the snippet (including a Google Tag Manager variant), optional crawler settings, the consent and privacy treatment (including a ready-to-paste privacy blurb), and how to verify the install. For what the snippet does and the data flow, see Snippet Documentation; for the privacy detail, see Snippet Data Statement; for the data processing agreement, see Data Processing Agreement.

1) Overview & prerequisites

To go live you complete two independent steps, in either order:

Publish the Knowledge Graph subdomain (DNS): either point a subdomain of your own domain at FAIND with a CNAME record, or use a subdomain that FAIND provides with no DNS change at all.
Install the snippet: add one <script async> tag to your site's <head>, either directly in your template or via a tag manager.

You will need: access to your DNS provider (for the CNAME option), the ability to edit your site's <head> (or admin access to a tag manager), and the domain ID and token from your FAIND dashboard. Both values are shown on the install screen in the App at app.getfaind.com. In the placeholders below, DOMAIN_ID and TOKEN stand for those values.

2) DNS — the Knowledge Graph subdomain (CNAME)

The Knowledge Graph is a static mirror of your public pages, served over a CDN. It lives at a dedicated subdomain so AI crawlers have a clean, machine-readable source to retrieve. You have two options:

Option A — your own subdomain (recommended, on-brand): when you add your domain in the FAIND app, we provide the exact CNAME target (a hostname under getfaind.com) to point your chosen subdomain (e.g. kg.yourdomain.com) at. Create a CNAME record for that subdomain pointing at the target shown for your domain in the FAIND dashboard.
- Record type: CNAME
- Host / name: the subdomain you chose (e.g. kg)
- Value / target: the exact CNAME target shown for your domain in the FAIND app (a hostname under getfaind.com)
- TTL: your provider's default is fine (e.g. 3600s)
- Proxy / cloud: if your DNS provider offers a proxy toggle (e.g. Cloudflare's orange cloud), set the record to DNS-only so FAIND can provision and serve TLS for the subdomain
Option B — FAIND-hosted subdomain (no DNS change): if you prefer not to touch DNS, FAIND serves your Knowledge Graph at the subdomain FAIND provides. Nothing is required on your side; the address is shown in the dashboard, and you can switch to your own subdomain later.

Note: the CNAME points a subdomain at FAIND; it does not affect your main website, your MX (email) records, or your existing DNS for the apex domain. TLS for the subdomain is provisioned by FAIND. Propagation can take anywhere from a few minutes to 24 hours depending on your provider.

3) The one-line snippet

Add the following tag inside the <head> of every page you want covered — ideally in your global site template so it appears site-wide. It is a single small script, loaded async so it never blocks rendering:

<script async src="https://app.getfaind.com/geo/snippet.js.php?d=DOMAIN_ID&t=TOKEN"></script>

Placement: in <head>. The snippet defers its work until after the page has loaded, so it does not compete with your content for load time.
Replace: DOMAIN_ID and TOKEN with the values from your dashboard. If the pair is invalid, the snippet logs a console warning and does nothing else (no-op) — it will not error out your page.
Load impact: non-blocking and async. Under a strict Content-Security-Policy it fails closed — the rest of your page is unaffected. See Snippet Documentation for the full behavior.

4) Google Tag Manager variant

If you deploy scripts through Google Tag Manager (or a similar tag manager) rather than editing your template directly, create a Custom HTML tag containing the one-line async script and set it to fire on All Pages:

Tag type: Custom HTML.

HTML: paste the same tag:

<script async src="https://app.getfaind.com/geo/snippet.js.php?d=DOMAIN_ID&t=TOKEN"></script>

Trigger: All Pages (or the subset of pages you want covered).
Consent settings: because the snippet stores nothing on and reads nothing from the visitor's device (see section 6), it does not require consent to fire. If you run GTM Consent Mode, you may treat this tag as not requiring additional consent / strictly necessary, consistent with your own Consent Mode configuration.

5) Optional: robots.txt & AI crawlers

For maximum benefit, make sure crawlers can reach the material FAIND relies on:

Don't block the Knowledge Graph subdomain: the subdomain from section 2 is meant to be crawled by AI and search engines. The Knowledge Graph subdomain ships with a permissive robots.txt that allows major AI and search crawlers, so no action is needed there.
Don't block AI crawlers on your main site (optional): on your main site, ensure your robots.txt does not disallow the AI crawler user-agents you want to reach the pages you want represented (e.g. GPTBot, ClaudeBot, Google-Extended, PerplexityBot). This is your editorial choice and outside FAIND's control.

6) Consent & privacy — what you do (and don't) need

This is the section most compliance teams ask about. The short version:

No cookies. The snippet sets no cookies. (A stray session cookie that used to appear was removed in July 2026.)
No device storage. The snippet writes nothing to and reads nothing from the visitor's device — no cookies, no localStorage, no sessionStorage, no IndexedDB, and no fingerprinting.
No user-entered data. It reads your page's own public content to detect changes. It never reads form fields or input values.

Consent banner: because the snippet stores nothing on and reads nothing from the visitor's terminal equipment, §25 TDDDG (the German ePrivacy/cookie provision) is not triggered — so you do not need to add a FAIND category to your consent banner. If your consent tool requires every third-party script to be listed anyway, classify FAIND as "strictly necessary / technical" rather than "marketing" or "analytics," consistent with your specific consent-management setup.

What this does not cover: the posture above is about the snippet on your site only. It is separate from any cookies that FAIND's own website (getfaind.com) may set on visitors who come to us — most notably a first-party lead/visitor-journey cookie (faind_vid) used on FAIND's marketing pages. That cookie is not set by the snippet and never runs on your site. On FAIND's own site, faind_vid is set only after consent via FAIND's own cookie banner (the choice is shared across getfaind.com), as described in FAIND's Privacy Policy. None of that affects your visitors, who only ever encounter the storage-free snippet. Data retention for the snippet's signals is covered in FAIND's Snippet Data Statement.

Privacy policy: although no consent is required, you should reference FAIND in your own privacy policy for transparency. The transient technical request metadata the snippet transmits (the page URL/path, with arbitrary and personal-data query parameters stripped in the browser before sending; technical content signals used only to detect changes; and, inherently to any HTTP request, the visitor's IP and User-Agent, which are used only to distinguish bots from humans and are not stored raw) is processed on the basis of legitimate interest (Art. 6(1)(f) GDPR) and, for our relationship as your processor, under the data processing agreement (Art. 28 GDPR / Data Processing Agreement). No visitor identifier is created or stored. A ready-to-paste blurb is in the next section.

7) Copy-paste privacy policy blurb

Drop the following short paragraph into your website's privacy policy (adapt names/links to your house style). It describes the FAIND snippet and Knowledge Graph processing, the controller/processor relationship, and the fact that no cookies or device storage are used:

AI visibility (FAIND). We use FAIND, a service provided by leif ventures UG (haftungsbeschränkt), Karl-Marx-Str. 250, 12057 Berlin, Germany, to make our public web content better readable by AI systems and to measure AI-driven visits (in aggregate). A one-line script from FAIND runs on our pages. It sets no cookies and stores or reads nothing on your device (no cookies, no local storage, no fingerprinting). It reads only our own public page content (such as the main text, title and headings) to detect changes, and it transmits transient technical metadata about the page to FAIND's servers in the EU. Like any web request, this involves your IP address and browser User-Agent; FAIND uses these only to distinguish automated crawlers from human visitors and does not store them in raw form, does not build a visitor profile, and does not track you across sites. FAIND acts as our processor under a data processing agreement (Art. 28 GDPR); the processing rests on our legitimate interest in AI visibility (Art. 6(1)(f) GDPR). For details of what the FAIND snippet does, including how long the snippet's signals are retained, see FAIND's snippet privacy notice at https://www.getfaind.com/snippet-privacy.html.

We recommend having your own DPO or counsel confirm this wording fits your policy and jurisdiction before publishing.

8) Verification

To confirm the install is detected and working:

In the FAIND dashboard: the install screen at app.getfaind.com shows snippet status and flips to "detected" once your pages start reporting, typically within a few minutes of the first page load.
In your browser: load a page with the snippet, open developer tools, and check:
- Network: the snippet loads with HTTP 200.
- Console: no FAIND warning. An invalid domain ID/token produces a single console.warn and the snippet no-ops — that indicates the wrong d=/t= values.
Knowledge Graph subdomain: open your CNAME subdomain (or the subdomain FAIND provides) in a browser and confirm it serves your mirrored content over HTTPS.

9) Support

If detection doesn't complete, re-check that (a) the d= and t= values match your dashboard, (b) the tag is in <head> and not blocked by a Content-Security-Policy, and (c) the CNAME has propagated. For anything else, contact us at privacy@getfaind.com.

See also: Snippet Documentation (what the snippet does), Snippet Data Statement (snippet privacy detail), and Data Processing Agreement (data processing agreement).

Controller / provider: leif ventures UG (haftungsbeschränkt), Karl-Marx-Str. 250, 12057 Berlin, Germany · Email: privacy@getfaind.com