AI Question Solver Privacy Policy

Effective date: June 23, 2026

AI Question Solver is a Chrome extension that helps a user solve and understand a submitted study question. This policy describes the v1 extension and hosted backend.

What Data Is Collected Or Transmitted

AI Question Solver handles only the data needed to answer the question the user submits:

The extension does not collect accounts, login credentials, profiles, sync data, browsing history, contacts, payment data, health data, location, cookies, ad identifiers, or usage analytics.

How Data Is Used

Submitted content is used only to provide the extension's core feature: returning an answer-first explanation for the user's question. The hosted backend receives the submitted text or selected captured image, sends the necessary content onward to the model provider, and streams progress, answer, or error data back to the extension.

AI Question Solver does not sell user data. Submitted content and operational metadata are not used for ads, advertising, marketing, unrelated analytics, tracking, profile building, or unrelated purposes.

What Data Is Shared

Submitted question text, selected captured page-region content, and current-item follow-up transcript may be shared with:

Operational services such as CloudFront, AWS WAF, CloudWatch, and the model provider may process metadata needed for security, reliability, cost monitoring, rate limiting, and request delivery. Application logs are designed not to include question text, captured image content, answer text, explanations, or raw model output.

Retention

AI Question Solver has no persistent server-side store of user content. Question text, captured images, answers, and current-item transcripts are processed in request and are not cached as answer history by the application.

The client carries follow-up context only for the current item. Choosing New question resets that context. The backend does not keep a server-side conversation store.

Operational metadata may be retained by infrastructure and model-provider systems as needed for security, reliability, cost monitoring, and rate limiting, but application logs must not include question text, captured image content, answer text, explanations, or raw model output.

Security

Production requests are transmitted over HTTPS to the hosted backend. Localhost HTTP is used only for development and mocked tests.

The backend uses project-owned model access; no model API key is stored in the extension package. Backend logging is metadata-only by design.

User Choices

The user controls what is submitted. The extension sends typed question text only after the user chooses Solve. It sends captured page-region content only after the user chooses Capture and selects a region.

Changes

This policy may be updated as the extension changes. The Chrome Web Store listing and in-product Privacy link should point to the current published version.