Privacy Policy

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.
• Member Lens: shows you roster and engagement views of your own community.

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 choose to connect: 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").
• 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).

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 after you explicitly click Connect.

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.

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, 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. 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

Connecting a community requires an explicit click and shows what will be stored beforehand. Each tool is off until you enable it, 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.