CiteAura
Product
OverviewHow It WorksFeaturesAI visibility audit
Solutions
For brandsFor agencies
Resources
DocsGuidesMethodologySample report
MCP Pricing
Sign In Get Started

Privacy Policy

Effective Date: October 29, 2026 · Version 1.6

Our Core Privacy Commitment: CiteAura never trains AI models on your private data, prompt matrices, or customer audits. All API keys are encrypted with hardware-grade AES-256-GCM and stored exclusively within your isolated tenant workspace.

1. Overview & Scope

CiteAura ("we", "our", or "us") provides a Generative Engine Optimization (GEO) platform that diagnoses, tracks, and verifies brand visibility across artificial intelligence search engines and large language models. This Privacy Policy describes how we collect, use, process, and protect your information when you visit citeaura.com, access the CiteAura web application at citeaura.com/app, or interact with our APIs.

2. Information We Collect

2.1 Account & Workspace Information

When you register for a CiteAura workspace, we collect your email address, organization or team name, role, and hashed password.

2.2 Usage & Approximate Location Information

We use a first-party random visitor identifier to measure visits, registrations, activation, and subscription conversion. When traffic passes through our trusted edge network, we retain the two-letter country code associated with registration or a visit for aggregate geographic reporting. We do not require you to provide a country during registration, and we do not retain a precise location for this purpose.

2.3 Project & Brand Measurement Data

To perform GEO audits and generate engineering tickets, you provide website URLs, target domains, competitor names, and target keyword question sets. This data is stored in tenant-isolated filesystems (Open SSOT) to generate diagnostic reports and deployment assets.

2.4 Bring Your Own Key (BYOK) Model Credentials

If you configure model API keys (e.g. OpenAI, Anthropic, DeepSeek, Google Gemini, Zhipu AI, Moonshot AI, xAI, Perplexity), your credentials are immediately encrypted at rest using AES-256-GCM. Plaintext API keys are never written to logs, never exposed in client-side responses, and only injected temporarily into isolated worker processes during live sampling executions.

2.5 Google Search Console Data

If you choose to connect Google Search Console to a project, we request read-only access (webmasters.readonly). We read the list of Search Console properties your Google account can access and, for the property you select, the search queries with their clicks, impressions, and average position for the last 90 days.

We use this data only to suggest AI sampling questions and to show those Google figures next to AI visibility results inside your tenant workspace. We do not store your Google OAuth credentials: the access token is used during the connection request and then revoked. A query snapshot is kept in the project until you delete it from the question bank or project settings, or the project is deleted. Only the question text you choose to sample is sent to AI model providers; Google figures and account details are not.

We do not use Google user data for advertising, do not sell it, and do not use it to train or improve AI models. CiteAura's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

2.6 Google Analytics 4 Data

If you connect Google Analytics 4 to a project, we request read-only access (analytics.readonly). We read the list of Analytics properties your Google account can access, the web stream address used to match the property, the key event configuration, and the sessions, users, and key events attributed to known AI assistant domains over the last 28 days.

We use this data only to show how much traffic AI assistants send to your site inside your tenant workspace. We do not store your Google OAuth credentials: the access token is used during the connection request and then revoked. The referral snapshot is kept in the project until you delete it in project settings or the project is deleted. We do not use Google user data for advertising, do not sell it, and do not use it to train or improve AI models.

3. How We Use Your Information

We use the collected information strictly for the following purposes:

  • Delivering GEO audit diagnostics, perception gap analyses, and 13 standardized engineering tickets;
  • Executing AI visibility sampling and verification runs across model matrices;
  • Compiling white-label client delivery decks and deployment asset packages (JSON-LD, /llms.txt);
  • Managing billing subscriptions, team role permissions, and usage counters;
  • Providing technical customer support and critical platform notifications.

4. Zero Model Training Guarantee

We believe in absolute data sovereignty for brand teams and marketing consultants. CiteAura will never sell, license, share, or use your proprietary content, prompt archives, audit findings, or custom strategies to train, fine-tune, or evaluate public machine learning models.

5. Data Isolation & Security Architecture

CiteAura enforces strict multi-tenant isolation:

  • Tenant Boundaries: All audit reports, tickets, metrics, and delivery archives are segregated per tenant ID on disk with strict directory traversal prevention.
  • Cryptographic Security: Sensitive credentials are encrypted with AES-256-GCM using isolated tenant keys. Communications are encrypted in transit via TLS 1.3.
  • Role-Based Access Control (RBAC): Tenant workspaces support Owner, Editor, and Viewer permission tiers to prevent unauthorized access.
  • Audit Logging: All security-sensitive operations (key updates, role changes, exports) are recorded in tamper-evident audit event logs.

6. Cookies & Tracking Technologies

We use strictly necessary HTTP-only session cookies to maintain your authenticated login state and CSRF defense headers. We also use a first-party HTTP-only random visitor cookie and short browser storage containing only page paths, source hosts, and campaign labels for aggregate registration and conversion measurement. On public pages, we use Microsoft Clarity for aggregate interaction analytics, heatmaps, and session replay. Clarity may set cookies and local storage and collect interaction data such as clicks, scroll depth, and page activity. Microsoft processes this data under the Microsoft Privacy Statement. We do not use advertising pixels or sell analytics data. You can limit this analytics by using your browser's privacy controls or blocking clarity.ms.

7. Data Retention & Deletion Rights

Under GDPR, CCPA, and global data privacy standards, you have the right to:

  • Access & Export: Export all audit records, JSON snapshots, and delivery packs at any time in open standard formats (JSON/Markdown);
  • Rectification: Update your profile, organization, or project configurations;
  • Permanent Deletion: Request the complete purge of your tenant workspace, encrypted keys, and associated file storage by contacting our privacy team.

8. Contact Us

If you have any questions, privacy concerns, or data subject requests regarding this policy, please contact our Data Protection Team at:

Email: [email protected]
Official Website: https://citeaura.com

CiteAura

Next-gen Generative Engine Optimization (GEO) diagnosis, execution, and delivery.

© 2026 CiteAura
AI SEO toolsAnswer engine optimizationGoogle AI OverviewsPerplexity SEOLLM optimizationAI brand monitoringCompare platforms Docs Guides About Contact Sign In Privacy Policy Terms of Service