Skool Copilot — Terms and membership

Membership billing and refunds

The extension is free to install. Access to tools depends on your Skool Copilot community membership tier. Membership payments and subscription management are handled through Skool.

We do not offer voluntary refunds, except where required by applicable law. Cancel your subscription in Skool to stop future renewals. Cancellation does not itself refund previous payments.

This policy does not limit any statutory withdrawal, refund or other consumer rights that cannot legally be excluded, or any rights under the terms that applied to your purchase. Contact copilot@avinolabs.com about a billing issue or a statutory rights request.

Membership policy published October 3, 2026. The v5 product access terms below include direct membership verification. Earlier versioned agreements remain available at their original links.

Version ID: skool-copilot-terms-v5
Prepared October 3, 2026. Applies when this exact version is presented and accepted.

Skool Copilot is an independent browser extension. It is not affiliated with, sponsored by, or endorsed by Skool. This agreement includes the service connection needed for supported scheduled tasks. Each task and automation still requires its own configuration.

Publisher: Amirthan Puvaneswaran trading as Avino Labs, Finnish sole trader, Business ID 3383759-5. Privacy/support contact: copilot@avinolabs.com. Contact address: c/o Amirthan Puvaneswaran, Vapaa-ajanmaa 3 A 20, 33540 Tampere, Finland. Public policy: https://avinolabs.com/products/skool-copilot/privacy. Effective date: when this exact version is presented and accepted.

1. Account and acceptance

These terms govern the build that presents them. Selecting “Accept and continue” records your acceptance of this exact Terms, Privacy Notice and Local Data Disclosure bundle. Earlier acceptance records remain unchanged. Your Skool Copilot email and password are separate from Skool; the emails do not need to match. Use an email you control and protect your password and browser profile.

2. Community membership and access

Product access is based on your bound Skool identity's membership in the official Skool Copilot community, identified by its stable internal group ID. A membership or role in another community does not grant access. Changing the official community's URL does not change which group qualifies. Moving to a different group requires a reviewed migration and fresh membership evidence.

The backend decides access from a direct, server-verified check of your own membership or a newer complete owner-proved current membership list. Basic members choose one available Stable tool; Premium members choose up to three; VIP includes available Stable and Beta tools. Replacing saved choices has a 30-day server-controlled cooldown. Canonical community Owners/Admins and the verified product operator retain their defined administrative access. Features may be disabled or changed; a tier label is not a permanent promise of a particular feature.

After current consent and installation setup, the account is bound to one opaque Skool user ID. A page-observed ID alone is not a claim that Skool authenticated the person to our backend. Supported identity proof can establish a stronger verified binding. Another Skool login locks the local workspace rather than relabelling or merging its data. Do not share, transfer, resell or use an account to give another Skool identity access.

3. Access verification

After email confirmation, account agreement and Skool identity binding, Skool Copilot automatically checks your own membership directly with Skool. The trusted extension sends the allowed auth_token and, when present, aws-waf-token, browser User-Agent and capture/expiry metadata over HTTPS to our fixed Supabase backend. The backend reads the official community page and, for older membership formats, one exact self membership-product endpoint. It accepts only your matching authenticated Skool identity, the configured community, an approved membership and a recognized role/tier. It does not require the community owner to be online.

This verification uses the session and provider responses transiently. It stores only your opaque identity/community scope, result, role/tier and verification/attempt timestamps, with short coordination identifiers. It does not retain the session, page content, payment details or a roster from this check. Account deletion removes this account-linked proof. Eligible Cloud tools separately use the encrypted service connection described below.

Successful automatic membership checks are normally reused for 30 minutes while the extension is in use. Check again requests a fresh check, subject to a short anti-repeat limit. Temporary failures grant no new access and allow retry. Existing verified access has a bounded active period of 36 hours and a restricted grace period up to 72 hours; a newer completed owner-list check or direct self check can reduce or end access sooner. Provider availability and session expiry can interrupt verification.

4. Local workspace and connected service

The CRM/workspace remains local. For eligible scheduling and automation tools, accepting this agreement instructs Skool Copilot to establish and renew the service connection automatically when your matching signed-in Skool account is available. Trusted background code transfers the narrowly scoped Skool session to our backend over HTTPS and retains it encrypted with server-managed keys so tasks you authorize can run while your computer is off. This is not end-to-end encryption; authorized backend code and key holders can decrypt the session. The Privacy Notice and Data Disclosure explain credentials, recipients and retention. No separate connection switch or permission is needed. This preparation does not schedule a post, send a message, enable an automation, connect a community or enable Plan sync. Their existing deliberate controls and permissions remain. You are responsible for record accuracy and backups; clearing browser data, uninstalling or device loss can remove unbacked-up local data.

Skool Copilot has retired AI-provider features and Auto-Like. Historical notices, consent IDs and backup identifiers may retain the earlier product name to keep previous records accurate. They do not provide an alias that grants access through the old Copilot community.

5. Your responsibilities and third parties

Use the extension only for communities and information you are authorized to manage.
Comply with applicable law, member notices, consent requirements and Skool's terms and platform rules.
Review recipients, content, dates and destinations before external actions. Do not use the extension for spam, harassment, deception, unauthorized monitoring or unlawful profiling.
Keep appropriate human review over scheduling, messaging, Recovery and enabled automation.

The extension uses Supabase for account/access and the connected service and separately enabled workflows, interacts with Skool for supported functions, and uses the explicitly disclosed media/GIF destinations when requested. These services have their own terms and privacy practices. We cannot guarantee their availability or decisions.

6. Changes, interruptions and responsibility

Browser and platform changes, source restrictions, expired sessions, safety limits and unavailable services can interrupt features or delivery. Review queue and outcome reports rather than assuming an action occurred. No delivery time, platform compatibility, revenue result or membership benefit is guaranteed. To the extent permitted by applicable law, the extension is provided as available without warranties. Nothing in these terms excludes rights or liability that applicable law does not permit to be excluded.

Material changes are presented in new versioned notices when appropriate. The extension never silently rewrites the document behind a recorded acceptance. You can stop use, disable optional services, export supported local data and use the account-deletion controls.