Privacy Policy
Last updated: 10 November 2026
Looking for how SkoolKit works rather than the legal text? Read the FAQ. It covers connecting more than one community, whether we need your Skool password, and how billing works.
SkoolKit ("SkoolKit", "we", "us") is a Chrome extension and service that gives Skool community owners tools to run communities they own or administer. It is operated by Sentient Mind Ltd. SkoolKit is an independent product and is not affiliated with, endorsed by, or produced by Skool.
This policy explains what data SkoolKit collects, why, how it is used and shared, how long it is kept, and your choices. Our handling of data received through the Chrome Web Store complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
What SkoolKit does
SkoolKit automates community management for Skool communities you own or administer. Every permission and every piece of data below exists to serve these tools:
- Post Scheduler: schedules and automatically publishes posts (including polls, media, and an email-all-members option) to your community at the time you choose.
- Payment Recovery: periodically reads your community's member list (roughly every 15 minutes) to detect members whose payment has failed, and sends them recovery messages by DM from your account, following a sequence you control.
- Auto DMs: sends DMs from your account when a member triggers an event you have configured, such as joining, commenting, liking a post, reaching a new level, or changing tier, including multi-step sequences, reply detection, and per-tier or per-level message variants.
- Churn Hero: reads the same member list to detect members who have cancelled, sends them save messages by DM from your account on a sequence you control, and asks one short exit-survey question shortly before their access ends.
- Member Lens: shows you roster and engagement views of your own community, including members you mark as favorites.
- Member Tags: lets you put your own private labels on members of your community (for example "Coaching client"), one at a time or in bulk, filter your other SkoolKit tools by them, and have your own Inbox rules and Auto DMs apply or act on them. Tags are stored in your SkoolKit account, are never shown to the member, and are never sent to Skool. They are shown beside names on Skool's pages in your own browser only, never to anyone else, and you can switch that off in the tool's settings.
- Alerts: tells you, by a banner, a sound, a desktop notification or an email as you choose for each event, when something you picked happens in a community you connected (see About alerts below).
- Skoolmarks: saves a post or a comment you choose to keep, from any Skool community you are a member of, into your own private folders, with your own note.
- Classroom Organiser: copies and moves classroom pages and folders between classrooms in your own community, from your browser, and only when you press Apply. A move copies the page and then hides the original as a draft; it never deletes your content.
What we collect and why
- Account email and password (at sign-in): to create and authenticate your SkoolKit account. Sent over HTTPS to our authentication provider; your password is never stored by the extension.
- Your Skool session for a community you admin, connected as you open it once you are signed in to SkoolKit (or by pressing Connect in the extension popup): so our servers can act on your behalf (publish your scheduled posts, read your member list, and send and read the DMs your tools produce) while your browser is closed. Stored encrypted at rest and readable only by the server processes that act for you.
- The posts you schedule: title, body, media references, time, and target community, so we can create the post at the scheduled time.
- Your community's member roster: for communities you connect, we read the member list that Skool shows you as the owner. This includes member names, Skool ids, join dates, membership tier, and activity in your community (posts, comments, likes) where a tool you enabled needs it. If Payment Recovery is enabled, it also includes the billing metadata Skool shows you as owner: whether a member's payment has declined, renewal and removal dates, and the card brand and last four digits Skool displays. We never receive full card numbers; Skool does not expose them.
- DM threads between you and members your tools contact: read so automations can detect a member's reply and stop, hand the conversation back to you, or branch as you configured. The messages our tools send on your behalf are stored as an audit log.
- Posts, comments, and likes in your community: read to evaluate the triggers you configured (for example, "DM anyone who comments GUIDE on this post").
- Cancellations and exit-survey replies: if Churn Hero is enabled, the fact that a member cancelled, the dates around it, and the reason they give when asked, stored so you can read it in your dashboard.
- Your Skool membership status: your Skool user id and the list of Skool communities you belong to, used only to verify you have an active SkoolKit membership (see below).
- Posts and comments you save with Skoolmarks: only when you press save, and only the item you saved: its words as Skool shows them to you (the title or an excerpt), the author's public Skool name, handle, avatar and Skool id, when it was posted, its link, the community it is in, and your own folder and note. Kept in your SkoolKit account so your saved list reads without asking Skool again, private to you, never shown to the author or sent to Skool, and deleted when you remove the mark.
- Voice notes you record: not stored by us at all. Recorded in the extension, a voice note is captured and encoded inside your browser and uploaded directly to Skool's own file storage using your own Skool session, exactly as if you had attached a file in Skool; SkoolKit's servers never receive that audio. Recorded on a SkoolKit voice-note link (when an AI app you connected asks for one), the recording passes through SkoolKit's server on its way to Skool and is not kept: we hold only the Skool file id and its length.
- Images and files you pick on an attachment link (Connect to AI, when your AI app asks for attachments for a post, a DM or a reply): not stored by us. Each file passes through SkoolKit's server on its way to Skool's own file storage, using your own Skool session, exactly as if you had attached it in SkoolKit's Scheduler; we keep only what any scheduled post keeps: Skool's file id, and its link (images) or its name (files).
- “Keep me signed in on this device”, if you tick it on a SkoolKit link page (voice-note and attachment links): kept on your device only, in that browser's storage for skoolkit.tools, used only by those link pages, and removed when you press Forget this device or sign in as someone else. Nothing extra is stored on our servers.
We do not collect your general web-browsing history. The extension only runs on skool.com pages, and only reads your Skool session for a community once you are signed in to SkoolKit and open a community your Skool account administers (or press Connect in the popup). Communities you merely belong to are never connected: the extension checks that you are an admin first.
Automated actions taken on your behalf
Payment Recovery and Auto DMs send messages from your Skool account, as you, according to rules and message templates you configure and can edit or switch off at any time. Sends are rate-limited, paced, avoid members' night hours, and stop when a member replies so you can take over the conversation. You are the sender of these messages; SkoolKit is the tool that sends them on your instruction.
Your members' data
The member, billing, and message data described above is your community's data: it is the same information Skool already shows you as the community's owner or administrator. SkoolKit reads and processes it only on your instruction, to run the tools you have enabled for that community. We do not use it for any other purpose, and we do not contact your members except through the automations you configure. You are responsible for using these tools in line with Skool's terms and the laws that apply to you and your members.
About alerts
If you switch on Alerts, SkoolKit keeps a short log (30 days) of the events you asked to hear about in your own communities, such as a member joining, levelling up, cancelling, a payment failing or a reply arriving, with the member's public Skool name and handle, so it can show you a feed of them and deliver each one the way you chose. For a call recording, it also keeps Skool's own download link to your recording (Skool expires it after 14 days), so the alert and its email can offer Download. A banner and a sound are shown and played by your own browser. A desktop notification is shown by Chrome only if you grant the notifications permission when you switch that channel on. An alert email goes to your SkoolKit sign-in address, or to an address you enter, and nowhere else. Nothing about your members is sent to any third party.
About webhooks
If you switch on Webhooks and add a webhook, SkoolKit sends the events you picked (for example a member joining, a payment failing, a cancel, a member leaving) to the URL you entered, and only there, as you directed. Each event carries what that event is about: the member's Skool name, handle and profile link, their tier and level, their email address and lifetime value where Skool shows them to you as an admin, their answers to your community's membership questions where Skool shows them to you (the same answers you see on the member's card, including anything they typed, such as an email address), and details of the event itself (such as the last four digits of a declined card, as Skool shows them). If you use Connect to AI, the event for an AI app's action carries the app's name and the same one-line summary SkoolKit shows you (never a member's words). The receiving service (Make, Zapier, n8n, GoHighLevel, your own app or any other) is chosen and controlled by you, and what it does with the data is governed by your agreement with it. Every request is signed so your app can check it came from SkoolKit. We keep a 30-day log of each delivery (what was sent, when, and what your URL answered) so you can see it and send it again. Deleting a webhook stops all sending to it at once.
About the microphone
The microphone is used onlywhile you are actively recording a voice note, and only after you grant permission in a SkoolKit window. We ask from our own window rather than from inside skool.com, so the permission belongs to SkoolKit and is never granted to Skool's own page code on your behalf. Recording stops and the microphone is released the moment you stop or cancel. The extension never holds an open microphone in the background, and never records unless you press record.
Note that, like every attachment on Skool, an uploaded voice note is served by Skool from a public link with no expiry. That is Skool's storage behaviour and it applies equally to any image or file you attach through Skool itself.
How membership is verified
SkoolKit requires membership of the SkoolKit community on Skool. To check this, the service uses your own Skool session to read the list of communities you belong to, and grants access if the SkoolKit community is among them. The check is performed only for your own account.
How we use your data (Limited Use)
Our use of information received from SkoolKit adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Specifically:
- We use your data only to provide and improve the tools described above.
- We do not sell your data or your members' data, and do not transfer it to third parties except the sub-processors that operate our service, a destination you set up yourself and direct us to send to (a webhook URL you enter), to comply with law, or to protect against fraud, abuse, or security threats.
- We do not use or transfer your data for advertising, or to determine creditworthiness or for lending purposes.
- We do not allow humans to read your session data or your DM threads except with your explicit consent, where necessary for security or abuse investigation, or where required by law.
Who we share it with
We use Supabase (database, authentication, and serverless functions) to store your account, encrypted sessions, scheduled posts, member and billing metadata, automation state, and send logs, and to run the service. We do not share your data with advertisers, data brokers, or any other third parties. If you add a webhook, the events you picked go to the URL you entered, as described above. When a tool acts (publishing a post, sending a DM), its content is sent to Skool at that moment in order to perform the action, the same as if you did it yourself.
Data retention and deletion
Your scheduled posts, connections, member data, and automation history are kept while your account is active. You can revoke any connected community at any time from the extension, which immediately deletes the stored session for that community. You may request deletion of your account and associated data by contacting us; we will delete it within a reasonable period, except where we must retain limited records to comply with law.
Your choices and rights
Communities you admin are connected as you open them, after you sign in to SkoolKit; the sign-in screen says so, and what is stored, before you press Sign in. Every connected community is listed in the extension popup. Nothing is sent on your behalf until you set an automation up, and every automation can be paused or deleted. You can disconnect at any time, and you may request access to, correction of, or deletion of your personal data. To exercise these rights, contact us at the address below.
Security
All data is transmitted over HTTPS. Connected Skool session material is encrypted at rest, the encryption key is held separately, and access is restricted so that your session and your community's data are never exposed to other SkoolKit users (enforced by database row-level security).
Children
SkoolKit is intended for community owners and is not directed to children under 16. We do not knowingly collect personal data from children.
Changes to this policy
We may update this policy from time to time. Material changes will be reflected here with an updated "Last updated" date, and where required we will seek your consent.
Contact
Questions or data requests: privacy@skoolkit.tools · Sentient Mind Ltd.