Cheatly Privacy Policy

Last updated: May 2025

Overview

Cheatly is a Chrome extension that uses AI vision to answer questions visible on your screen. Your privacy is important to us. This policy explains what data the extension accesses, how it is used, and what is stored.

Data Collection

Cheatly does not collect, transmit, or store any personal information on our servers. The extension has no backend server and no analytics.

Data Processed Locally

• OpenAI API Key — You provide your own API key, which is stored locally in Chrome's chrome.storage.local. It never leaves your browser except when sent directly to the OpenAI API.
• Extension Settings — Display mode and model preferences are stored locally in chrome.storage.local.

Data Sent to Third Parties

• OpenAI API — When you double-click a question, a screenshot of the currently visible tab is captured and sent to the OpenAI API (api.openai.com) along with your API key for processing. This is the only external network request the extension makes.
• No data is sent to any other third party. There are no analytics, tracking pixels, or advertising services.

Screenshots

Screenshots are captured on-demand only (when you double-click). They are sent directly to the OpenAI API and are not saved to disk, uploaded to any server we control, or retained after the API response is received.

Permissions

• activeTab — Required to capture a screenshot of the current tab when you double-click.
• storage — Required to save your API key and preferences locally.
• scripting — Required to inject the content script that listens for double-click events.
• host_permissions (<all_urls>) — Required so the content script can run on any webpage where you might have a question.

Data Retention

All data is stored locally in your browser. Uninstalling the extension removes all stored data. No data is retained on any external server controlled by Cheatly.

Children's Privacy

This extension is not directed at children under 13. We do not knowingly collect data from children.

Changes to This Policy

We may update this policy from time to time. Changes will be reflected in the "Last updated" date above.

Contact

If you have questions about this privacy policy, please open an issue on our GitHub repository.