AI Power Progress iA
Trust

Privacy

AI Power Progress iA is designed to run locally. We keep storage local-first, keep analytics minimal, and make optional external calls explicit.

Ask AI Status Catalog

What we store locally

AI runs (metadata)

We store bounded previews of prompts and responses (redacted + truncated), plus timing, model, and source metadata.

Purpose: debugging + evals + reliability, without storing full transcripts by default.

Widget analytics (optional)

If you consent, we store metadata-only events (opens, asks, errors) plus basic performance metrics (Web Vitals) to improve Android speed — without chat transcripts.

Consent is required. You can decline and the site still works.

Shorts/video metrics (optional)

If you consent, we store basic watch metrics for video posts (views + completions) to help creators iterate.

We store aggregated counts and short-lived dedupe keys (per-day) to reduce spam/double-counting.

Caches

Local caches may include web search cache, offline library indexes, and media metadata caches.

Purpose: speed + reliability (especially with multiple workers).

Optional external requests

Brave Search (web grounding)

When enabled, the app sends queries to Brave Search to retrieve current sources. Web snippets are treated as untrusted text.

Controlled by web mode (off/auto/on) in the Ask AI UI and widget.

Linked resources

Resource pages link to external sites. Opening them is your choice and happens in your browser.

Fonts & UI assets

The site uses system font stacks by default and serves UI assets from this origin.

No third-party font CDN requests.

Control & deletion

Analytics consent

On first visit you can allow or decline analytics (which also enables opt-in performance telemetry). You can manage consent below or clear the browser’s localStorage to reset it.

Key: ppia_consent_analytics (stored in localStorage).

Referral & campaign attribution

If you submit a Services Desk request, we may store allowlisted attribution fields (ref/UTM + landing page host/path) to measure what content/partners drive requests.

Keys: ppia_attribution_v1, ppia_attrib_optout (localStorage) and ppia_ref (cookie).

Local data location

App state is stored under ${PPIA_DATA_DIR:-./data}. For large state, set PPIA_DATA_DIR to a mount like /mnt/pp_data/ppia/data.

See Status for storage visibility.

Analytics & performance telemetry (controls)

If you opt in, we store metadata-only analytics and performance telemetry (Web Vitals) locally. We do not store chat transcripts and we do not use third‑party trackers.

Referral & campaign attribution (controls)

We only store a small allowlist of fields (ref / UTM tags + landing host/path). We do not store full querystrings or referrer URLs. This helps improve the business funnel without third‑party trackers.