Akrux privacy policy

Data the product processes

• Account data such as email, optional display name, locale and authentication-provider identifiers.
• Business profile fields such as name, category, website, city, market, aliases and competitors.
• Generated prompts, provider answers, citations, extracted entities, scan status, cost metadata and calculated report metrics.
• Contact-request fields voluntarily submitted through the Book a call form.

Why it is processed

The data is used to authenticate accounts, research the submitted business, run requested scans, build reports, enforce quotas, send transactional messages, respond to requests and protect provider budgets. AI prompts and public business context are sent to the configured model provider to perform a scan.

Public and private separation

Marketing pages, methodology, documentation, sitemap and llms.txt are public. Account routes, APIs, business profiles, prompts tied to accounts, raw answers, competitors and reports are excluded from public indexes and protected by authorization checks. Robots rules supplement access control; they are not used as the security boundary.

Cookies, retention and requests

Akrux uses an HTTP-only session cookie after authentication and local browser storage for language and pending form preferences. A production retention schedule, legal operator identity, jurisdiction-specific rights process and privacy contact are not configured in this repository. The product owner must supply them before relying on this page as a complete jurisdictional notice.

Public measurement analytics

Public-page analytics, when enabled, stores aggregate date, page, language, event and coarse referral category. It does not store a raw referrer, user email, page contents or claim that normal visits are verified crawler traffic.