Skool Extensions ("the Extension") is committed to protecting your privacy. This policy explains what data the Extension processes, what runs locally in your browser, and what is sent to our backend for server-side features such as Cloud Sync, Group Chat, Workflow Builder, Video AI and the AI Chatbot.

Data Controller

Flowdesk GmbH — Händelstr. 15, 14513 Teltow, Germany. Contact via the Skool Extensions community (skool.com/skool-extensions) or the imprint details below.

This Website (skool-extensions.com)

This website sets no cookies and uses no analytics, tracking or advertising services. Fonts, scripts and styles are delivered from our own server, so visiting the site loads nothing from third parties. Unless stated otherwise, the legal basis is our legitimate interest in operating the website securely and answering your questions (Art. 6(1)(f) GDPR).

• Hosting and server log files — the website and the blog are hosted by ALL-INKL.COM – Neue Medien Münnich, Hauptstraße 68, 02742 Friedersdorf, Germany, which processes the data on our behalf (Art. 28 GDPR). With every request the server automatically records browser type and version, operating system, referrer URL, host name of the accessing computer, time of the request and IP address in log files. These data are used only for stable and secure operation and are not combined with other data sources.
• Storage in your browser — a plain visit stores nothing on your device. Only if you choose a language yourself is that choice saved in localStorage. While you use the chat widget, the conversation is kept in sessionStorage and is removed when you close the tab.
• Chat widget — when you send a message, its text, a random session ID and your language are passed via our web server to our backend at api.skool-extensions.com (Hetzner Online GmbH, Germany) and answered by an AI model from OpenAI (USA) on the basis of our product documentation. Your IP address is not passed on; our web server keeps it only as a hash for one minute to limit the number of requests. Answers are cached for three days without any reference to you; questions the chat could not answer are stored for 90 days so that we can improve the documentation. Please do not enter any personal data in the chat.
• Deletion request — the form on the "Delete your data" page sends your Skool handle, e-mail address, the requested scope and your note via our backend by e-mail to our support mailbox. The website itself stores nothing.

Data Processed

• Settings & Preferences — stored locally in your browser (localStorage, chrome.storage.local/sync). Used to remember your feature toggles, bookmarks, tags, templates and UI state.
• Cloud Sync Data — if you enable Cloud Sync, your settings are end-to-end encrypted in the browser before being transmitted to our backend. Only you hold the encryption key (passphrase). The server stores only ciphertext.
• Chatbot Messages — if you use the AI Chatbot in a whitelisted community, your messages are sent to our backend (n8n webhook → OpenAI) for processing. Messages are associated with a session ID, not your personal identity. Token usage is logged per user for fair-use limiting.
• Browser Notifications — permission is requested only when you enable notification features. No notification content is sent to external servers.
• Account Identifiers — when you use any server-side feature (Group Chat, Cloud Sync, Workflow Builder, Video AI, CRM …), your public Skool user ID, display name and avatar URL are stored in our backend as your account record. The Extension never sends your password or Skool credentials — your Skool login is verified through the public Skool API. The one exception is signing in to the Web App with email and password, which runs through our server (see "Mobile App and Web App").

Default Permissions

• "storage" — Save your settings and bookmarks locally and across Chrome/Firefox profiles.
• "notifications" — Show browser notifications for DMs, events, and group chats.
• "sidePanel" — Lets you open the toolkit panels in your browser's side panel next to skool.com.
• "alarms" — Schedule periodic checks for event reminders and notifications.
• "host_permissions" (skool.com, www.skool.com, api.skool-extensions.com, assets.skool.com) — Run the toolkit on skool.com, read the address of your Skool tab for the side panel, communicate with our backend (chatbot, cloud sync, group chat, workflows) and fetch Skool community assets such as cover images.

Optional Permissions (granted on demand)

The following permissions are NOT granted on install. The Extension requests them only when you opt into a feature that requires them, and you can revoke them anytime in your browser's extension settings.

• "cookies" — Required by the Workflow Builder (Premium) so the service worker can read your Skool session cookies via chrome.cookies.getAll. Without this permission the Workflow Builder cannot run server-side automations on your behalf. See the next section for full details.
• "host_permissions" for https://*.skool.com/* — Granted together with the "cookies" permission and only used to read cookies belonging to skool.com. The Extension does not inject any code on subdomains.

Workflow Builder & Skool Session Cookies (Premium)

The Workflow Builder is a Premium feature that runs your automations server-side: every 30 seconds our cron polls Skool in your name to check trigger conditions and execute actions (auto-reply, tag members, send DMs, etc.). To act on your behalf, the backend needs your Skool session cookie — including the HttpOnly auth_token, which is not accessible via document.cookie and can only be read via chrome.cookies.getAll. If you agree to pushes for Skool direct messages and notifications in the mobile app or the Web App, our server also uses this cookie for those checks (see "Checking Skool for pushes" below); besides the Workflow Builder, you can also provide it in the Extension settings (Integration → "Skool session for phone notifications").

When you press "Submit cookie" in the Workflow Builder panel, the Extension (1) asks you to grant the optional "cookies" + "*.skool.com" permission, (2) reads all cookies for the skool.com domain via the service worker, (3) sends them over HTTPS to api.skool-extensions.com, where they are encrypted at rest (AES, see wf_cookies.cookie_enc) before being written to the database. The server-side cron decrypts them only in memory to make HTTP requests to Skool.

You stay in control: the Workflow Builder is disabled by default, the cookie permission is requested only on explicit action, and you can wipe the stored cookie at any time from the Workflow Builder settings (the "Delete cookie" button calls DELETE /api/wf/cookie). Revoking the "cookies" permission in your browser settings stops any further reads immediately.

AI DM Analysis (on your device or with your own AI provider)

When you start this function, the unanswered part of the unread direct messages you select is analysed to suggest tasks. By default this happens on your own device with the AI model built into Chrome, and nothing leaves your browser. If you choose OpenAI or Mistral AI in the settings, the message text (with the sender's name replaced) is sent directly from your browser to that provider using your own API key; this processing is governed by your contract with the provider, and we receive neither the messages nor your key. The key is stored only on your device. Only the tasks you confirm are saved to your Kanban board.

Server-Side Features (Backend Storage)

Some features require server-side storage to work across devices and users. The following data is stored on api.skool-extensions.com only when you actively use the corresponding feature:

• Group Chat — the content of messages you send in Extension group chats (text as well as links to images, files and recordings) is end-to-end encrypted in your browser or on your device and stored on our backend only as ciphertext. Images, files, voice and video messages are uploaded to Skool, not to our server; these files are not end-to-end encrypted, and anyone with the link can open them. Stored unencrypted on our backend: group name and logo link, members, sender and time of each message, reactions, read status, whether you have muted the group (a yes/no value) and notices such as when someone joins or leaves. You can delete your own messages individually, which removes their content from our backend; if the group creator deletes the group, all of its messages are removed.
• Member CRM / Tags / Sales Pipeline — notes, tags, pipeline stages and activity history that you add to Skool members are stored under your account. They are visible only to you (and your admin teammates if you share them).
• Video AI — when you request a transcript or AI summary for a course lesson, the audio is processed, and the resulting transcript, chapters and summary are cached on our backend so that you and other admins of the same course do not pay for the same transcription twice. Original video files are not stored.
• Workflow Logs — every workflow execution writes a log entry (rule, trigger, action, status). Logs are automatically deleted after 30 days.
• Login Log (admin-only) — if you enable the Login Log feature as a community admin, visit timestamps of your members (one row per admin, member, community, day) are stored under your account. Disabling the feature stops further logging; existing entries can be cleared from the admin panel.
• Error Reports — when a critical error occurs, the Extension may send an error report (error code and message, stack trace, skool.com page path, technical diagnostic details, extension version, browser) to our backend so we can fix it; instead of your Skool account it carries a random installation ID. On unexpected errors, the mobile app and the Web App send an error report to our backend: error code, error message, stack trace, the path opened in the app without parameters, app version, operating system and its major version (mobile app) or browser identifier (Web App), and instead of your Skool account a random ID created once for this app installation (mobile app) or in this browser (Web App); the backend adds the IP address. If the error closes the mobile app before the report has been sent, it is sent the next time the app starts. Reports from the mobile app and the Web App contain no message content, tokens, cookies or passwords. IP addresses are nulled after 24 hours; error reports are deleted after 90 days.
• MCP / OAuth Tokens (Claude Connector) — if you connect the Extension to Claude via the MCP connector, short-lived OAuth tokens (access: 1h, refresh: 30d) are stored as SHA-256 hashes and tied to your account.
• Push relay of the Extension — if you have turned on pushes for community events or event reminders in the mobile app or the Web App, the Extension reports what it detects anyway to our backend: community events (kind, community, the member's name and handle, time, for a tier change the old and the new tier, and an event key that contains the member's Skool ID for member events) and upcoming events of the next 14 days (title, start, community). Review text and star ratings are never sent. If you turn a kind off, the Extension learns about it with a delay; anything it still sends until then is discarded by our server without being stored. Upcoming events are kept until they start and deleted 7 days later at the latest; community events are deleted together with the delivery records after 7 days at the latest; the event keys used to filter out duplicate notifications are stored only as a hash and deleted after 7 days.
• Translation cache — when you translate posts, comments or About pages, the translation is stored on our backend under a hash of the original text, so the same text does not have to be translated again. The original text is not stored. Entries are deleted 180 days after their last use. Translations in chats are never stored.
• Extension badge — to mark members who also use the Extension, the Extension sends the Skool IDs and handles of the members shown on the page to our backend in batches. The backend only compares them with its list of accounts and stores nothing.
• Community data for Skool Finder — the Extension sends details of the communities you belong to (name, owner, description, landing page text, member and post counts) and, for communities you run, their discovery ranking and keywords to our backend. This data feeds our community directory Skool Finder (skool-finder.com), which shows publicly available information about Skool communities.
• Leaderboards — if you join the cross-community leaderboard, your display name, avatar, profile handle, activity counts (7, 30 and 365 days) and your top communities are stored and shown to other Extension users; leaving it deletes your entry. If you turn on the affiliate leaderboard as a community owner, the names, handles, avatars, referral counts and commission amounts of your affiliates are stored; depending on your setting, only you or also your members can see them.
• Calendar subscription and calendar feed — if you subscribe to community calendars or publish a calendar feed, the events (title, time, description and links as provided by Skool, community name) are stored on our backend so your calendar app can load them. Removing the subscription deletes them.
• Workflow credentials and integrations — access data you enter for workflow actions (for example SMTP server and password, Pushover token) is stored encrypted (AES-256-GCM). Connected accounts (Google, LinkedIn, Microsoft) are stored as OAuth tokens. When a workflow sends an email, the recipient's address, the subject and the text go to the mail server you configured. You can delete credentials and connections at any time in the Workflow Builder.
• Account registration — every registration of the Extension with our backend is logged with the random installation ID and your IP address so that we can detect misuse. These entries are deleted after 30 days.

Mobile App and Web App

The Skool Extensions mobile app (iOS/Android) and the Web App at app.skool-extensions.com use our backend at api.skool-extensions.com. The following data is processed:

• Pairing with the Extension (QR code) — the Extension shows a short-lived code that can be redeemed only once. Redeeming it creates a separate app token (our server stores only its hash), which you can revoke individually in the Extension settings. If the Extension has already sent your Skool session cookie to our server, pairing also passes this cookie to your device.
• API Token — alternatively, you can paste a personal API token from the Extension settings. If a session consists only of a token (pasted, or pairing without a cookie), our backend accesses Skool with the Skool session cookie the Extension stored encrypted on our server (see Workflow Builder).
• Signing in with Skool credentials in the mobile app — email and password go directly from your device to Skool and never reach our server. Beforehand, our server only provides an anti-bot token; afterwards it checks the session issued by Skool (account and plan) without storing the cookie, and creates your account record if none exists yet. Exception: if you agree to pushes for Skool direct messages and notifications (see below), the app stores the session cookie of this sign-in encrypted on our server.
• Signing in with Skool credentials in the Web App — a browser cannot sign in to Skool directly. Email and password are therefore sent via HTTPS to our server, which performs the sign-in at Skool and returns the session cookie to your browser. The credentials are used only for this request and are neither stored nor logged. Sign-in attempts are limited per IP address. Our server does not keep the session cookie either, unless you agree to pushes for Skool direct messages and notifications (see below); it is then stored encrypted on our server.
• What runs through our backend in the Web App — a browser cannot query Skool directly, so the Web App loads feed, chats, notifications and communities through our REST API, which queries Skool with your Skool session. Voice and video messages you record are uploaded to our backend, which passes them straight on to Skool without storing the file. The mobile app reads directly from Skool when a Skool session is stored on the device (otherwise also through our backend) and uploads recordings directly to Skool.
• Camera and Microphone — used only to scan the pairing QR code and to record the voice and video messages you send. Scanning stores or transmits no images.
• Photos and Calendar — the mobile app opens your photo library only when you choose a photo or video to send in a chat; the selection runs through the system picker, and photos are re-encoded before upload so that embedded metadata such as the location is removed. The device calendar is used only when you add a Skool event to it: the app writes that one event and reads nothing else. Neither photos nor calendar entries reach our servers.
• Storage in the mobile app — the session (app token and/or Skool session cookie), the cached profile, the key derived from your sync password, the block list, unread counters, the feed selection, the random ID for error reports and — once you turn on push notifications — the push device ID, the device secret (used to sign the device off; after you sign out it is kept only until that has been done) and the push status of this device (e.g. a hash of the push token and the time of the last registration) are kept in the iOS Keychain or Android Keystore (expo-secure-store); if an error closes the app, its error report is also kept there until it has been sent. If the app has stored its Skool session on our server for push checks, a marker of it is kept there as well (only a hash and the time); signing out removes it.
• Storage in the Web App — the same data is kept in your browser's localStorage: session (app token and/or Skool session cookie), cached profile, the key cache for Group Chat and Cloud Sync data, block list, unread counters, feed selection and the random ID for error reports. With push notifications turned on, the same push data (device ID, device secret and push status) is stored there as well; the Web Push subscription itself is held by your browser and ends when you sign out, turn push off or withdraw the notification permission. Signing out removes the session, profile and counters; you can remove the rest by clearing the site data for app.skool-extensions.com. If the Web App has stored its Skool session for push checks, a marker of it (only a hash and the time) is kept in localStorage as well; signing out removes it.
• Group Chat — messages are end-to-end encrypted on your device or in your browser; our server only sees ciphertext. Your sync password never leaves the device; only the key derived from it is stored. Reporting a message opens a pre-filled email to our support with group and message ID, group and sender name and your reason — without the message text. Blocked senders are stored and hidden only locally.
• Push Notifications — optional and off until you turn them on in the mobile app or the Web App; you can turn them off again at any time in the push settings or in your device or browser settings. Pushes are available for group chats, Skool direct messages, Skool notifications, event reminders and community events of the Extension (new member, tier change, card declined, new review); you turn on each kind separately, and only group chats are on by default (how our server learns about them: see "Checking Skool for pushes" below and "Push relay of the Extension" above). Once turned on, our server stores, linked to your account, your device's push token or, in the Web App, your browser's Web Push subscription (endpoint address and keys) in encrypted form, together with the platform, the app version or browser family, the language, timestamps (such as registration and last use), your push settings and the hash of a device secret used to sign the device off. Whether you have muted a group chat is stored on our server as a yes/no value — also when you mute it in the Extension — so that no pushes are sent for that group. Recipients: notifications for the mobile app are handed to Expo (650 Industries, Inc., USA), which passes them on to the Apple Push Notification service or Google Firebase Cloud Messaging; Web Push goes to the push service of your browser vendor (e.g. Google, Mozilla, Apple or Microsoft). A push contains the sender's name, the group or community name and the kind of event — never the message text. Event reminders also show the title of the event, tier changes the old and the new tier. Web Push content is encrypted so that the push service cannot read it; pushes to the mobile app are only encrypted in transit, so Expo, Apple and Google can see the title and text of the notification. Deletion: when you sign out, turn push off or remove the device, or when the push service reports that the device can no longer be reached, the device receives no further pushes and its entry is deleted — at the latest after 60 days without use. Delivery records (they never contain message text) are deleted after 7 days at the latest.
• Checking Skool for pushes (Skool direct messages and notifications) — only if you explicitly agree in the mobile app or the Web App (with Premium, VIP or a trial) does our server check Skool, using your Skool session, for new direct messages and notifications: about once a minute, less often once none of your devices with push turned on has opened the app for more than a day, and not at all after 14 days without use, until you open the app again. These are automated requests to Skool in your name; the app points this out before you agree. For this, our server stores only markers (times and IDs of the most recently seen message and notification, and the status of the check), no content; a push names the sender and the context, never the text. The session used is the one the Extension provides (see Workflow Builder) or — only if you signed in to the app or the Web App with your Skool credentials and agree — the session cookie of that sign-in, stored encrypted on our server; your email and password are never stored. If you withdraw your consent in the push settings, the checks stop immediately and the markers and the cookie stored by the app are deleted; signing out of the app deletes the cookie of that session. A cookie provided by the Extension stays; it belongs to the Workflow Builder, where you can delete it.
• Logs — write requests to our REST API (e.g. sending a message or recording through our backend) are logged with time, account, request path, status and IP address; these entries are deleted after 90 days. Requests to our REST API made with an app or API token are additionally logged per token (method, path, status); these entries are deleted after 30 days. Sign-in, pairing and anti-bot token requests are limited per IP address; for this, the backend stores the IP address with a timestamp and deletes these entries after 30 days.
• No Tracking — the mobile app and the Web App contain no analytics, tracking or advertising SDKs. Error reports from the mobile app and the Web App are described above under "Error Reports".

Third-Party Services

The Extension communicates with our own backend at api.skool-extensions.com (Chrome and Firefox use the same endpoint) and with Skool itself (skool.com / assets.skool.com). No data is shared with third-party analytics, advertising or tracking services. A few features connect directly from your browser to a third party: translation sends the text to be translated to Google Translate (translate.googleapis.com), and the spell check sends your draft to LanguageTool (api.languagetool.org) — both only after you have agreed on first use; the GIF picker sends your search term to Giphy. Server-side, the AI Chatbot, Video AI, the cloud voices for reading aloud, the AI texts in the Workflow Builder and the About page analysis forward the content you submit to OpenAI for processing. Only if you turn on push notifications in the mobile app or the Web App are notifications delivered through Expo (650 Industries, Inc., USA) and from there through the Apple Push Notification service or Google Firebase Cloud Messaging or, for Web Push, through the push service of your browser vendor (e.g. Google, Mozilla, Apple or Microsoft); they never contain message text (details in the section Mobile App and Web App above). Only if you choose it for AI DM analysis, the Extension connects directly to OpenAI or Mistral AI with your own API key.

Data Retention

Local data persists until you uninstall the Extension or clear browser data. Cloud Sync data can be deleted at any time from the settings panel. Chatbot session data is automatically purged after 24 hours. Workflow logs are kept for 30 days. Workflow cookies are stored until you delete them, the cookie becomes invalid on Skool, or you delete your account. Group Chat messages persist until you delete them or the group creator deletes the group.

Your Rights

You can delete Extension data at any time. Local data: uninstall the Extension or clear site data for skool.com. Cloud Sync: "Delete Cloud Data" button in settings. Workflow cookie: "Delete cookie" button in the Workflow Builder. To have your account deleted, send a request via the Skool Extensions community. Under the EU GDPR you also have the right to access, rectify, restrict and port your data, and to lodge a complaint with a supervisory authority.

Request deletion of your data →

Changes

We may update this policy when new features are added or when data processing changes. The latest version is always available on this page; significant changes are announced in the release notes.