Legal documents are provided in English.
The short version. Ajax AI works without an account. No messages or page content are sent until you accept the in‑product data notice and then ask Ajax AI something (before that, opening Settings may only register the anonymous install token and load your daily usage counters — see 3.2). When you do, we send only what is needed to answer that request — your message and the content you chose to include (the current page, selected text, a file, a link or a screenshot) — to our server and our AI provider. We don't store the content of your conversations on our servers, we don't sell data, we don't show ads, and we ask our AI provider to route only to models that don't train on your data. Your chat history stays in your browser.
1. Who we are
Ajax AI (“Ajax AI”, “we”, “us”) is a browser extension that provides an AI assistant in Chrome's side panel, together with the API service that powers it. Ajax AI is developed and operated by FitzTools (fitztools.com), an independent software developer. For the purposes of data‑protection law, FitzTools is the controller of the limited data described in this policy. You can reach us at egor.besarabm@gmail.com.
2. Scope
This policy covers the Ajax AI extension (side panel, full‑screen view, floating button, selection toolbar and right‑click menu) and the Ajax AI API that the extension uses to generate answers and images. It does not cover the websites you visit, or third‑party services you open from links in answers; those have their own policies.
3. What we process
3.1 Content you choose to send
Ajax AI only processes content when you take an action such as sending a message, clicking a suggestion, using the selection toolbar or the right‑click menu, adding a source, or creating an image. Depending on what you do, a request may include:
| Data | When it is sent | Why |
|---|---|---|
| Your message or prompt, and earlier messages in the same chat | When you send a message | To generate the answer with conversation context |
| Content of the current tab: visible text, page title and URL (for YouTube: title, description and captions; for email pages: the open message) | Only when the “Current” option is on and you send a message, or when you choose an action such as “Summarize this page” or “Translate this page” | To answer questions about the page you are viewing |
| Text you select on a page | When you use the selection toolbar or the Ajax AI right‑click menu | To explain, summarize, translate or rewrite it |
| Files you upload (PDF, text, code, images) | When you add them and send a message | To answer questions about them. PDF text is extracted on your device; only the text is sent. Scanned PDFs without a text layer are sent as a file. |
| Screenshots of an area you select | When you use the screenshot tool and send a message | To answer questions about what is shown |
| Links you add | When you add a link | Our server fetches the public page to read its text |
| Other tabs you add as a source | When you pick a tab and send a message | To answer questions across tabs |
| Web search requests | Only when “Search” is on | To look up current information and show sources |
| Image descriptions | When you use “Create image” | To generate the image |
Because you decide what to include, this content may contain personal information (for example, if you ask about an email or a document that names people). Please don't include sensitive information you don't want processed by an AI service.
3.2 Technical data
- Anonymous install token. On first use the extension receives a random identifier (for example
ins_3f9…) signed by our server. It is not linked to your name, email, Google account or device identifiers. - IP address. Used transiently to deliver the response and to prevent abuse. For daily limits we store only a one‑way keyed hash of the IP address, never the address itself.
- Usage counters. The number of requests per day by type (messages, “Smart” messages, web searches, images) for the install token and the hashed IP.
- Request metadata. The extension version, request time and the selected options (mode, quality, search on/off, reply language).
3.3 Data stored only in your browser
Your chat history (including generated images and attached screenshots), settings, saved prompts and the time you accepted the data notice are stored locally using Chrome storage and IndexedDB. This data is not sent to us and is not synced by us. You can delete it at any time (see section 12).
4. What we don't collect
- We do not collect your browsing history and do not read pages in the background. A page is read only at the moment you ask about it.
- No accounts, passwords, names, email addresses or payment information.
- No advertising identifiers, cookies, analytics or tracking scripts in the extension.
- No precise location, contacts, keystrokes or form data. The floating button and selection toolbar run locally on the page and send nothing until you click an action.
5. How we use data
We use the data above only to provide Ajax AI's single purpose — answering, summarizing, translating, writing and creating images for you — and the operations directly needed for it:
- to generate the response you asked for and return it to your browser;
- to enforce free daily limits and protect the service from abuse, spam and fraud;
- to keep the service secure and working (for example, diagnosing errors from our AI provider without logging the content of your requests).
We do not use your data for advertising, profiling, selling, or to determine creditworthiness. Where the GDPR or UK GDPR applies, we rely on: performance of our service at your request (Art. 6(1)(b)) for processing your requests; our legitimate interest in preventing abuse and keeping the service secure (Art. 6(1)(f)) for usage counters; and your consent given in the extension's data notice.
6. Who receives data
We share data only with service providers that are necessary to run Ajax AI, under terms that limit their use of it:
| Recipient | Role | Data |
|---|---|---|
| OpenRouter, Inc. (United States) | AI gateway that routes requests to model providers and runs web search and PDF parsing | Request content described in 3.1 and request metadata |
| AI model providers selected through OpenRouter (the specific providers may change over time) | Generate text and images | Request content needed to produce the answer |
| Railway Corporation (United States) | Hosting for our API server and database | Request content in transit (not stored), install token, hashed IP and usage counters |
We may also disclose information if required by law or to protect against fraud or abuse, and, in a merger or acquisition, only after obtaining your explicit prior consent. We never sell or rent user data and never transfer it to advertising platforms, data brokers or information resellers.
7. AI processing
- Answers are generated automatically by AI models. No human at Ajax AI reads your requests or answers, except with your explicit consent (for example, if you send us a conversation for support), when necessary for security (such as investigating abuse), or to comply with law.
- We instruct OpenRouter to route requests only to providers that do not use or retain inputs for model training (OpenRouter's “data collection: deny” setting).
- Your content is not used by us to train any AI model.
- Content you include from web pages is treated as data, not instructions; we add safeguards in our prompts, but AI output can still be inaccurate.
8. Browser permissions
- Side panel — shows the assistant next to the page.
- Access to websites (all sites) — lets you use Ajax AI on any site you choose: read the page you ask about, show the optional floating button and selection toolbar, insert text you approve into a field, capture an area you select, and read a PDF you are viewing. Nothing is read until you take an action.
- Scripting — extracts the visible text of the current page when you ask about it.
- Storage — saves settings, saved prompts and chat history locally.
- Context menus — adds “Ajax AI” actions to the right‑click menu.
- Favicon — shows site icons next to sources.
9. Retention
- Request content (messages, page content, files, screenshots, prompts and answers) is processed in memory to produce your response and is not stored in our database or logs. OpenRouter and model providers process it under their terms; with the routing setting in section 7, providers are selected that do not retain it for training.
- Usage counters (install token, hashed IP, date and counts) are deleted after 30 days.
- Install token records are kept while the service is active so your token keeps working; they contain no personal information.
- Local data stays in your browser until you delete it or uninstall the extension.
10. Security
All data between the extension, our server and our providers is transmitted over HTTPS (TLS). The AI provider key is kept only on our server and is never shipped in the extension. Install tokens are cryptographically signed, IP addresses are stored only as keyed hashes, and our hosting provider encrypts data at rest. No method of transmission or storage is completely secure, but we work to protect your data and will notify you as required by law if a breach affects you.
11. International transfers
Our server and providers are located in the United States. If you use Ajax AI from another country, your request is processed in the United States. Where required, transfers rely on appropriate safeguards such as the providers' Standard Contractual Clauses.
12. Your choices and rights
- Control what is sent: turn off “Current” to stop including the page, remove sources before sending, or decline the data notice (“Not now”) — the assistant will not send your messages or page content until you accept.
- Delete local data: Settings → Privacy & data → Delete all chats, delete individual chats from History, or uninstall the extension to remove everything stored locally.
- Turn off page features: disable the floating button or selection toolbar in Settings, or hide the button on a specific site.
- Legal rights: depending on where you live (for example the EEA, UK or California), you may have rights to access, correct, delete, restrict or object to processing of your personal data, to data portability, and to withdraw consent. Because we don't keep conversation content or accounts, we usually hold no data that identifies you; contact us and we'll help with any request, including deleting usage records linked to your install token. You may also complain to your local data protection authority.
- California: we do not sell or share personal information for cross‑context behavioral advertising, and we don't use sensitive personal information to infer characteristics about you.
13. Children
Ajax AI is not directed to children under 13 (or under 16 in the EEA and UK), and we do not knowingly collect personal information from them. If you believe a child has provided personal information through Ajax AI, contact us and we will delete it.
14. Chrome Web Store Limited Use
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Ajax AI uses data only to provide and improve its single, user‑facing purpose described above; transfers happen only as necessary to provide that purpose, to comply with law, to protect against abuse, or in a merger with your prior consent; data is never used or transferred for personalized advertising or creditworthiness; and humans do not read user data except as permitted by that policy.
15. Changes
We'll update this policy when our practices change and revise the effective date above. If a change materially affects how we use data, we will show a notice in the extension and ask for your consent again before the change applies to you.
16. Contact
Questions or requests: egor.besarabm@gmail.com. Please don't email us sensitive information.