Privacy Policy

Terradium is created by Kugie and operated by PT. Semesta Solusi Digital. Terradium helps you write content built to be cited by AI engines, measures where you appear across AI answers (ChatGPT, Perplexity, Google AI Overviews, and Gemini), and — through the Embed SDK — helps you understand which of your visitors arrived from an AI answer.

For personal information about your own account, Terradium acts as a data controller. For data we process on your behalf — including the visitor events collected by the Embed SDK that you install on your website — you are the controller and Terradium acts as a data processor. The Data Processing Addendum at /dpa governs that relationship.

We collect the following categories of personal information:

• Account identity. When you sign in, our authentication provider (Clerk) supplies your name and email address. We keep a mirrored copy to scope your data to your account. If you choose Sign in with Google, Google shares your name, email address, and profile picture with Clerk so we can create and secure your account. We use this only to sign you in — we do not access your Gmail, Calendar, Drive, contacts, or any other Google data.
• Search Console data. If you connect Google Search Console, we read your performance data (queries, pages, clicks, impressions, CTR, position, and AI-surface impressions) for the properties you authorize, to power your dashboards. You can disconnect at any time.
• Project content and AI-visibility data. The projects, articles, keywords, and prompt-sampling runs you create, and the resulting metrics (appearance rate, citation share, share-of-voice, average position).
• Embed SDK visitor events. When you install our embed on your site, it sends us visitor events on your behalf. By default this is non-PII traffic-source data — see section 3.
• Audit events and usage data. A timeline of actions taken in your account, plus standard server logs (such as request metadata) used to operate and secure the Service. Source IP addresses seen by the embed endpoint are anonymized server-side and not stored in raw form.

When you add the Terradium embed to a website you operate, it collects a small set of non-PII signals about how a visitor arrived, so you can attribute traffic to AI answers. By default it collects:

• Referrer & traffic source, including an AI-referral classification (e.g. ChatGPT, Perplexity, Gemini, Google AI Overviews) derived from the referrer.
• UTM parameters and gclid present on the landing URL, and the entry path (e.g. /pricing).
• Optional survey responses — only if you enable the visitor survey, and only the answer the visitor chooses (e.g. “How did you find us? → ChatGPT”).

No PII by default. The embed does not set advertising cookies, does not fingerprint visitors, and does not collect names, emails, or precise location. The visitor's IP address is used only transiently to derive coarse signals and is anonymized server-side — we do not store raw IPs.

Consent mode. The embed respects a consent posture you configure. When consent is required and has not been granted, the embed stays in a no-op / minimal mode and does not send attribution events. As the operator of your site, you are responsible for obtaining any consent your jurisdiction requires from your visitors.

For the embed's visitor events, you are the controller and Terradium is the processor. The Data Processing Addendum describes our obligations, sub-processors, and the retention and deletion rules for this data.

• To generate, plan, and publish your content, and to serve it through the public content API.
• To sample AI engines and report where and how often your content is cited.
• To attribute, in aggregate, which visitors to your site arrived from an AI answer.
• To authenticate you, secure the Service, prevent abuse, and provide support.

We do not sell your personal information, and we do not use the content or visitor data you load into the Service for advertising. Information we receive from Sign in with Google is used solely to authenticate you and operate your account, and is never used for advertising.

To run the Service, we share the minimum personal information needed with the following sub-processors:

• Clerk — authentication (name, email). Clerk also brokers third-party sign-in, including Google for "Sign in with Google."
• OpenRouter and the underlying model providers — content generation and prompt-sampling. We pass the prompts and context needed to produce or evaluate content.
• Google — Search Console data access for properties you connect.
• Cloudflare R2 — object storage for generated featured images.
• Polar — subscription billing and the customer portal.
• Resend — transactional and notification email.
• Slack — optional notification delivery, if you connect it.

A current sub-processor list also appears in our DPA. We may also disclose information if required by law, to enforce our terms, or to protect the rights, property, or safety of Terradium, our users, or others.

• Every record is scoped to your account and isolated from other tenants at the database level.
• Sensitive credentials — such as API keys, webhook secrets, and connected-integration tokens — are encrypted at rest using AES-256-GCM.
• The embed ingestion endpoint anonymizes source IP addresses server-side and never stores raw IPs.
• API and embed requests are authenticated, and the embed endpoint is rate-limited.
• Our infrastructure is self-hosted on Coolify (see the DPA for data location).

No method of transmission or storage is completely secure, but we work to protect your information using appropriate technical and organizational measures.

We retain your account and content data for as long as your account is active. Embed visitor events are retained for a limited window to power attribution reporting and are then deleted or aggregated; the specific retention period and deletion path for visitor_events data are set out in the DPA. When you close your account, or on a valid deletion request, we delete or anonymize the associated personal information within a reasonable period, except where we must retain it to comply with legal obligations or resolve disputes.

Depending on where you live, you may have the right to access, correct, export, or delete your personal information, and to object to or restrict certain processing. You can manage much of your data directly in the dashboard, or contact us to make a request. If your data was collected by a customer using Terradium's embed (for example, as a visitor to their website), we will refer your request to that customer as the controller of that data.

Terradium and its sub-processors may process information in countries other than your own. We take steps to ensure such transfers are subject to appropriate safeguards.

The dashboard uses cookies and similar technologies that are necessary to keep you signed in and to operate the Service, and product analytics to improve it. The Embed SDK does not set advertising cookies on your visitors and operates in a no-PII-by-default mode as described in section 3.

We may update this Privacy Policy from time to time. When we make material changes, we will update the "Last updated" date above and, where appropriate, notify you.

For privacy questions or to exercise your rights, contact us at legal@kugie.app.