Aisogen- Privacy Policy

Aisogen — AI Social Engagement Assistant  •  Last updated: August 27, 2026

See also: Terms and Conditions | Aisogen Product Page

1. Overview

Aisogen ("the Extension", "we", "our") is a browser extension, available for both Chrome and Firefox, that reads a caption from a social media post you ("you", "your") are viewing and generates an AI-written reply using an AI provider you choose and connect with your own API key. It runs as a side panel in Chrome, or as a sidebar in Firefox — the same functionality either way, just docked using each browser's own UI.

Aisogen has no backend server. It does not operate any servers that receive, store, or process your data. Everything the Extension does happens either (a) locally inside your browser, or (b) as a direct request from your browser to the AI provider you selected. This policy explains exactly what data is touched, where it goes, and how you can control or delete it — noting any differences between the Chrome and Firefox versions where they exist.

2. Information We Do Not Collect

We (the developer) do not collect, receive, or have access to any of the following, ever:

• No account or sign-up — the Extension does not require or create any user account.
• No analytics or telemetry — the Extension contains no analytics SDKs, crash reporters, or usage-tracking scripts.
• No advertising — the Extension shows no ads and does not share data with advertising networks.
• No sale of data — we do not sell, rent, or trade any data, because we never receive any in the first place.
• No remote code execution — all code shipped in the Extension is reviewable in the package itself.

3. Information Stored Locally On Your Device

The Extension stores the following data using the browser's built-in local extension storage (chrome.storage.local in Chrome, browser.storage.local in Firefox) and the browser's IndexedDB. None of this is transmitted to us — it stays on your device unless you choose to export or copy it yourself.

3.1 API Keys & Provider Settings

In the Settings page, you may enter API keys, base URLs, and model lists for any of the supported providers (OpenAI, Deepseek, Gemini, Groq, OpenRouter, Anthropic, Perplexity, HuggingFace, or a custom endpoint you define). These are saved locally under the providers key.

3.2 Prompt, Tone, and Preset Configuration

Your custom prompt text, selected tone, selected output type, preset-prompt categories, and tone categories (including any you add, rename, or delete) are saved locally so they persist between sessions (presetPrompts, toneCategories, activeProvider, activeModel, activeTone keys).

3.3 Local Reply History (Back / Next)

Every time you generate a reply, an entry containing the caption, source URL, system prompt, custom prompt, tone, output type, generated reply, provider, and model is appended to a local, capped history list (last 20 entries, first-in-first-out) stored under the history key. This powers the "Back" and "Next" buttons in the side panel/sidebar. Entries beyond the 20th are automatically discarded — not sent anywhere.

3.4 Log Entries (IndexedDB)

Unless you check "Don't save a log" in Settings, every generated reply is recorded as an entry in a local, uncapped IndexedDB database (AisogenDB) on your device — the same behavior in both Chrome and Firefox. Entries are kept indefinitely until you delete them yourself. Each entry contains: Date, Time, Source URL, Caption, System Prompt, Additional Prompt, Tone, Output Type, generated Output, Provider, and Model.

This data is never uploaded anywhere by the Extension. You can browse it at any time through the built-in "Log Files" viewer, grouped by month, and export any month as a downloadable CSV file on demand using "Save a Copy" — this creates an ordinary file in your Downloads folder, separate from the log itself.

4. Information Read From Web Pages

The Extension reads page content in two different ways, depending on the site:

4.1 Supported Platforms (Instagram, Facebook, Threads, TikTok, LinkedIn, Reddit, X/Twitter)

On these platforms only, a small script is automatically present on the page (declared in advance in the Extension's manifest, and shown as a permission at install time). It stays passive — it does not read or transmit anything until you click "Get Caption" in the side panel/sidebar.

4.2 Any Other Website

The Extension does not have standing access to any other site. If you click "Get Caption" on a site outside the list above, your browser (Chrome or Firefox) will show you a native permission prompt asking whether to allow the Extension to access that specific website. Only if you approve does the Extension inject the same caption-reading script into that one page, read it, and return the result. If you decline, or close the prompt, nothing is read and nothing changes for that site. This one-time approval applies to that site going forward, so your browser won't show the prompt again there — but the script itself is still only loaded when you click "Get Caption," never automatically just from visiting the page. You can review or revoke the approval at any time via chrome://extensions → Aisogen → Site access (Chrome), or about:addons → Aisogen → Permissions (Firefox).

In both cases, once running on a page, the script reads the currently visible post caption and the page's URL, using the same site-specific logic (Instagram, Facebook, Threads, TikTok, LinkedIn, Reddit, X/Twitter), a generic fallback for other page layouts, and a meta-tag fallback as a last resort.

The content script never makes any network request of its own. It only reads what is already loaded in your browser and passes the extracted caption text and URL back to the side panel/sidebar through the browser's own internal extension messaging (Chrome or Firefox) — a purely local, in-browser handoff.

5. Clipboard Access

The Extension requests the clipboardRead permission, used only in these two places, both of which you trigger manually:

• Paste button — reads your system clipboard text into the Caption box when clicked.
• Capture Text (OCR flow) — after you use Windows' Text Extractor (Win+Shift+T / PowerToys) to copy on-screen text, the side panel/sidebar reads the clipboard automatically the next time its window regains focus, so the captured text appears in the Caption box.

Clipboard content is only ever placed into the Caption box on your screen; it is not logged, stored separately, or transmitted anywhere by this feature itself.

6. Information Sent to Third-Party AI Providers

When you click "GENERATE", the side panel/sidebar sends the caption text, the generated system prompt, and your custom prompt/tone/output-type instructions to the single AI provider you have selected in the Provider dropdown — using the API key and base URL you supplied for that provider in Settings. This request goes directly from your browser to the provider's API server; it does not pass through any server operated by us.

Supported providers and their own privacy policies (each governs how they handle data you send them):

We encourage you to review the policy of whichever provider you use, since the caption text you send may originate from a social media post (potentially containing another person's publicly visible words) and is subject to that provider's own data handling and retention practices.

7. Permissions We Request, and Why

8. Data Retention & Your Controls

• Local history: automatically capped at 20 entries (oldest dropped first). You can also clear the current caption ("Clear Caption") or reply ("Clear Reply") at any time.
• Log entries: uncapped by design so you have a durable record — but entirely under your control. Use "Clear All Logged Entries" in Settings to erase the log outright, or check "Don't save a log" to stop new entries being added (existing entries are left untouched until cleared). See Section 3.4 for details.
• Reset options: Settings includes "Reset to Default" controls for Preset Prompts and Tones, plus a "Don't save a log" checkbox and a "Clear All Logged Entries" button for log storage (see Section 3.4).
• Uninstalling the Extension: removes its local extension storage data and its IndexedDB database from your browser, including all logged entries themselves, since they are stored directly in that database. Any CSV files you've previously exported via "Save a Copy" are unaffected, since those are ordinary files in your Downloads folder, outside the Extension's storage.
• API keys: deleted the same way in both browsers — clear the field in Settings and click "Save All Settings", or uninstall the Extension.

9. Data Security

The Extension follows standard Manifest V3 practices in both browsers: it runs in a sandboxed extension context inaccessible to web pages and other extensions. Custom Provider base URLs are required to use https:// — plain http:// is rejected specifically to avoid sending your API key unencrypted over the network. As noted in Section 3.1, locally stored data (including API keys) is not encrypted at rest, consistent with how most browser extensions store local settings.

10. Children's Privacy

The Extension is not directed at children and is not intended for use by anyone under the age of 13 (or the minimum age required by your jurisdiction). We do not knowingly collect data from children, and given the Extension has no backend, no data is ever collected by us from any user of any age.

11. International Users

Because all Extension data stays on your device (aside from the direct calls you make to your chosen AI provider), there is no cross-border transfer of data performed by us. Any AI provider you connect to may process data in accordance with its own policies and may operate servers in other countries — see Section 6.

12. Changes to This Policy

If this policy changes, we will update the "Last updated" date above and, for material changes, note this in the Extension's release notes on its listing on the Chrome Web Store and/or Mozilla's addons.mozilla.org (AMO), as applicable.

13. Contact Us

Questions about this policy can be sent to: aisogen[at]msmanu.com

Developer / publisher name: Manu M. S