Sqemes – Prompt Templates & AI Enhancement Effective date: July 13, 2026
This privacy policy explains how the Chrome extension Sqemes – Prompt Templates & AI Enhancement collects, uses, stores, and shares user data. It applies only to the Chrome extension and supplements the general Sqemes website privacy policy.
1. Controller
Controller under the GDPR: NeoRebels GmbH Dreiherrnsteinplatz 11 63263 Neu-Isenburg Germany
Contact: ufuk@neorebels.com
2. Purpose of the Extension
The extension connects a user’s Sqemes workspace with supported AI chat platforms. It lets users:
- insert saved Sqemes prompt templates into supported AI chat input fields,
- fill template variables,
- improve user-entered prompt text with AI,
- view recently opened supported AI chats as a private metadata-only link list,
- select the active Sqemes workspace and AI model.
The extension reads content on supported AI platforms only when needed for these user-facing functions. It does not collect full page contents, full browser history, chat messages, AI responses, conversation summaries, or conversation excerpts.
Sqemes Cloud or self-hosted. By default the extension connects to Sqemes Cloud (https://app.sqemes.com). Users who run their own Sqemes deployment can instead point the extension at their self-hosted instance (see Section 3). Users may also add their own sites on which the widget should load, in addition to the supported AI platforms listed below (see Section 8, “Optional host permissions”). The extension only accesses a self-hosted instance or a custom site after the user explicitly adds it and grants access through Chrome’s permission prompt.
3. Connection With a Sqemes Account
The extension does not provide a separate sign-in form. Users sign in to the Sqemes web app and the extension syncs that existing session.
By default the extension is connected to Sqemes Cloud at https://app.sqemes.com. Users who operate their own Sqemes deployment can connect the extension to a self-hosted instance instead: they enter their instance URL in the extension options and grant the extension access to that instance. The extension then reads the instance’s public configuration (its Supabase API URL and publishable key) from the instance and uses it in place of the Cloud values.
Whichever instance is active, the user can choose to sync the existing Sqemes session with the extension. During this sync, the extension may inspect the active instance’s app tab or its auth cookies to find the Supabase session and copy the required session data into chrome.storage.local.
When the extension is connected to a self-hosted instance, the account, session, workspace, prompt-enhancement, and Recent AI Chats data described in this policy is exchanged with that instance’s backend, which is operated by whoever runs the self-hosted deployment — not by NeoRebels GmbH or Supabase, Inc.
4. Data Collected or Processed by the Extension
| Data category | Data collected or processed | How it is collected | How it is used |
|---|---|---|---|
| Account data | Email address, user ID | Synced from the authenticated Sqemes app session and verified through Supabase Auth | Shows the signed-in account and authorizes access to the user’s Sqemes workspace |
| Authentication data | Supabase access token, refresh token, session expiration time | Synced from app.sqemes.com local storage, session storage, or Sqemes auth cookies during user-triggered session sync | Keeps the extension authenticated and refreshes the session |
| Extension settings | Selected workspace ID and name, selected AI model, theme setting, Recent AI Chats preference, recently used prompt IDs | Stored when the user changes extension settings or uses prompt templates | Restores extension preferences and recent prompt shortcuts |
| Workspace data | Available workspaces, prompt templates, assistants, assistant system prompts, and model availability | Fetched from the authenticated Sqemes backend using the user’s session | Displays the user’s Sqemes content in the extension and inserts selected templates into chat input fields |
| Prompt input content | Text currently in the active supported AI chat input field | Read only when the user triggers a template action or AI enhancement | Fills variables, inserts templates, or sends the selected text for AI enhancement |
| Recent AI Chats metadata | Chat platform or custom-site host, page title, URL, chat key, created timestamp, last-seen timestamp, updated timestamp, pinned state | Captured on supported AI chat pages and on user-added custom sites when the user is authenticated and Recent AI Chats is enabled | Shows a private list of recently opened chat links |
The extension does not sell user data. The extension does not use user data for advertising, creditworthiness, lending, unrelated analytics, or profiling.
5. How Data Is Stored
Local browser storage
The extension stores the following data locally on the user’s device using chrome.storage.local:
- Supabase access token,
- Supabase refresh token,
- user ID,
- email address,
- session expiration time,
- selected workspace ID and name,
- selected AI model,
- theme setting,
- Recent AI Chats on/off preference,
- recently used prompt IDs.
This local extension data is not synced with Chrome Sync by the extension. It remains on the device until the user signs out of the extension, removes the extension, clears browser data, or the data is no longer needed.
Sqemes backend storage
Sqemes workspace data, prompt templates, assistants, model settings, and Recent AI Chats metadata are stored in the user’s authenticated Sqemes account through the Sqemes backend on Supabase infrastructure.
Recent AI Chats metadata is limited to up to 100 entries per user. It contains metadata-only links and does not contain chat messages, AI responses, summaries, snippets, or full page content.
6. How Data Is Shared
Sqemes shares user data only as needed to provide the extension’s stated functionality.
| Recipient | Data shared | Purpose |
|---|---|---|
| NeoRebels GmbH / Sqemes backend | Account data, authentication requests, workspace data, prompt templates, assistants, model settings, prompt enhancement requests, Recent AI Chats metadata | Provides authentication, workspace access, prompt template insertion, AI enhancement, and Recent AI Chats |
| Supabase, Inc. | Account data, authentication data, database records, edge-function requests, Recent AI Chats metadata, workspace data | Provides authentication, database, REST API, and edge-function infrastructure for Sqemes |
| AI model providers configured for the workspace | Prompt text submitted by the user for AI enhancement, plus the selected model and required request metadata | Generates the AI-enhanced prompt text requested by the user |
Depending on the model configured in the user’s Sqemes workspace, prompt text submitted for AI enhancement may be processed by one of these AI model providers:
| Provider | Company |
|---|---|
| OpenAI | OpenAI, LLC, USA |
| Anthropic | Anthropic, PBC, USA |
| Google Gemini | Google LLC, USA |
| xAI Grok | xAI Corp, USA |
| DeepSeek | DeepSeek, China |
| Mistral AI | Mistral AI SAS, France |
Only the providers needed for the selected model are involved. Data is not shared with advertising networks, analytics providers, data brokers, credit agencies, or unrelated third parties.
Self-hosted instances. When the extension is connected to a self-hosted Sqemes instance, the account, authentication, workspace, prompt-enhancement, and Recent AI Chats data is sent to that instance’s backend and its configured infrastructure and AI providers, which are operated and controlled by the party running the self-hosted deployment — not by NeoRebels GmbH or Supabase, Inc. The recipients listed above apply when the extension is connected to Sqemes Cloud.
7. AI Enhancement
When the user selects Enhance with AI, the extension sends the prompt text selected or entered by the user to the authenticated Sqemes backend. The Sqemes backend may forward that text to the AI model provider configured for the user’s workspace. The returned enhanced text is sent back to the extension and shown to the user.
The extension does not automatically send entire conversations or AI responses for enhancement. The only chat-page content sent for AI enhancement is the text the user intentionally submits through the extension feature.
8. Chrome Extension Permissions
The extension uses the following Chrome permissions:
storage
Used to store session data and extension settings locally on the user’s device.
scripting
Used on the active Sqemes instance (Sqemes Cloud or a configured self-hosted instance) during “Sync from Sqemes App” to check whether an active session exists and import it when the user requests sync, and to register and run the Sqemes widget on user-added custom sites (see “Optional host permissions” below). It is not used to inject scripts into sites the user has not explicitly added.
tabs
Used to:
- find an already-open tab of the active Sqemes instance (Cloud or self-hosted) for session sync,
- open the active Sqemes instance when the user needs to sign in,
- route the extension keyboard shortcut to the active supported or custom chat tab.
The extension does not use tabs to collect general browsing history.
cookies
Used for the active Sqemes instance (Sqemes Cloud or a configured self-hosted instance) as a fallback during session sync if the app stores the Supabase session in auth cookies. The extension does not read cookies from AI chat platforms, custom sites, or unrelated websites.
Host permissions
The extension has host permissions for:
https://app.sqemes.com/*https://chat.openai.com/*https://chatgpt.com/*https://claude.ai/*https://gemini.google.com/*https://grok.com/*https://chat.deepseek.com/*https://www.perplexity.ai/*
On supported AI chat platforms, the extension uses host access to detect the active chat input field, show the Sqemes widget, read the chat input only for user-triggered actions, write processed text back into the input field, and save metadata-only Recent AI Chat links when enabled.
Optional host permissions
The extension declares optional host access (*://*/*) that is not granted at install and is never used automatically. The extension requests access to a specific origin, one at a time, through Chrome’s permission prompt, only when the user:
- connects the extension to a self-hosted Sqemes instance — access to that instance’s origin(s); or
- adds a custom site on which the widget should load — access to that site’s origin.
On a self-hosted instance or a user-added custom site, the extension uses this access only for the same purposes described above: connecting to the chosen instance, and showing the widget / reading the input field for user-triggered actions / saving metadata-only Recent AI Chat links when enabled. When the user removes a custom site, the extension revokes the corresponding access and unregisters its widget from that site. The extension does not request or use access to sites the user has not explicitly added.
9. Retention and Deletion
Locally stored extension data remains on the user’s device until:
- the user signs out of the extension,
- the user uninstalls the extension,
- the user clears browser data,
- or the data is no longer required for the extension functionality.
Recent AI Chats metadata is stored in the user’s authenticated Sqemes account and is limited to up to 100 entries. Older entries are pruned when the limit is exceeded. Users can disable Recent AI Chats in the extension settings.
Server-side data retention for Sqemes workspace records follows the general Sqemes privacy policy and workspace settings.
10. No Analytics or Advertising Trackers in the Extension
The Chrome extension does not use advertising trackers, analytics scripts, or tracking cookies. It does not collect general browser history and does not create advertising profiles.
11. Chrome Web Store User Data Policy
The extension’s use of data is limited to the extension’s stated purpose and complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
12. User Rights
Where the GDPR applies, users have the right to request access, correction, deletion, restriction of processing, data portability, objection to certain processing, withdrawal of consent where applicable, and complaint to a competent supervisory authority.
Requests can be sent to the contact address above.
13. Changes to This Policy
This privacy policy may be updated when extension features, technical processes, service providers, or legal requirements change. The current version should remain publicly available on the Sqemes website.