Aparok
PricingBlogLog inStart free trial

Privacy

Privacy policy

This policy explains what Aparok collects, how it is used, and what product data is stored when teams use audits, prompt monitoring, and assistant traffic analytics.

What we collect

Aparok stores workspace details, domains, crawl results, report data, prompt watchlists, prompt-run observations, and assistant-attributed traffic events sent by the installed snippet.

Snippet events can include URL, referrer, session identifier, conversion metadata, and rendered page metadata such as title, canonical URL, headings, and text length.

How data is used

Product data is used to generate audits, reports, executive summaries, prompt visibility analysis, and AI traffic insights. We also use configuration and access data to secure accounts and enforce workspace boundaries.

Prompt and model data

When prompt monitoring is enabled, Aparok sends configured prompts and grounded report context to third-party model providers such as OpenAI, Perplexity, or Google Gemini. Do not include secrets, credentials, or regulated data in prompts unless your own compliance review allows it.

Retention and control

Workspaces can delete domains, reports, and prompt sets from the product. Operational logs, analytics records, and provider-side processing may have separate retention windows depending on your deployment and provider settings.

Questions

If you need a customer-facing version of this policy for production, replace this draft with your final legal copy and support contact details before launch.

Back to homepage

Aparok

Measure and improve AI discovery with prompt tracking, citation visibility, and assistant-driven traffic analytics.

ProductOverviewBlogPricingPrivacyTermsStart free trial
PlatformLog inDashboardProfile
CategoryPrompt monitoringAI traffic analyticsLLM readiness audits
© 2026 AparokBuilt for teams that want signal, not vanity dashboards.