ExplainMyBigO does not require an account and is intended to operate without collecting personal information from users.

For abuse prevention and rate limiting, our API may process your network address and transform it into a pseudonymous identifier (HMAC/hash) used only for short-lived security counters.

ExplainMyBigO may store data locally in your browser using IndexedDB, such as:

• local analysis history (if you enable/use this feature),
• UI preferences and settings,
• app state required for functionality.

This data remains on your device unless you manually delete it.

ExplainMyBigO is designed so that your prompts, code, and other content you enter are not stored on ExplainMyBigO servers. If the app provides history, it is stored locally on your device.

We do not use your prompts or code for training our own models.

We do not sell your data. ExplainMyBigO is not designed to share your prompts or locally stored content with third parties.

Security-related processing (such as CAPTCHA validation and API abuse prevention) may involve specialized service providers acting on our instructions.

To protect service availability, we apply request throttling and temporary blocks when unusual traffic is detected.

• We do not store raw IP addresses in application-level rate limit keys.
• We use a pseudonymous identifier derived from your network address (HMAC/hash) for security counters.
• Rate-limit counters have short retention windows (for example, minute/day windows and temporary blocks) and automatically expire.

This processing is used solely for security and abuse prevention, not for advertising or behavioral profiling.

Some features may involve third parties:

ExplainMyBigO does not aim to run user tracking. However, some technical analytics may be present due to hosting and delivery infrastructure (see "Third-party services").

If ExplainMyBigO introduces additional, app-level analytics/telemetry in the future (for example, to improve stability, understand feature usage, or diagnose errors), we will update this Privacy Policy accordingly.

ExplainMyBigO does not intentionally use advertising cookies. Hosting or delivery providers may use essential cookies or similar mechanisms for security, rate limiting, and service delivery.

Because app data is stored locally, you can remove it at any time by:

• using an in-app "Clear history / Clear data" option (if available), and/or
• removing the site's storage via your browser settings (site data/storage).

Keeping data local reduces exposure, but no system is perfectly secure. Your security also depends on your device, browser configuration, and installed extensions.

ExplainMyBigO is not intended for children under 13. We do not knowingly collect personal information from children under 13.

We may update this policy over time. The "Last updated" date will reflect the most recent revision.

If you have questions about this Privacy Policy, please contact us using the channel listed on the project's website or repository.