Skool Copilot — Product Access Terms

Version ID: skool-copilot-terms-v3
Prepared September 30, 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 notice describes collection, credentials and deletion without enlarging feature authority.

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 normally decides access from a 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

While durable access is pending, an exact currently signed-in canonical Skool document may establish a short-lived, memory-only client lease. The page reduces self-membership evidence to the opaque self ID, group ID, Owner/Admin/Member role and recognized Standard/Premium/VIP tier. An older membership shape may require one exact read-only self membership-product request. Raw page responses, price/payment details and session material are not included in this access proof. The reduced tier, role and source revision go to the authenticated policy endpoint, together with the existing account token, installation proof and bound Skool ID. Policy remains subject to current server authorization and saved tool choices.

A page lease cannot authorize server-hosted records, billing or a durable membership decision. Definitive durable access and consent states take precedence. Missing, conflicting or stale evidence grants nothing. Leases expire and must be proved again after expiry, restart, sign-out, document or identity changes, or a community configuration revision.

For an already entitled account, exact-page role/tier observations may identify a mismatch. They grant nothing. A proven restriction may temporarily limit local features while reconciliation is pending. The authenticated mismatch request sends no observed tier or role; it requests a fresh owner snapshot. This bundle retains the existing demand-only backend behavior and does not authorize a new server verification-hold capability.

The owner-source pipeline performs a lightweight due-check while an eligible already-open owner context is available, ordinarily every five minutes. It reads a complete directory only when due. Mismatch-triggered complete snapshots retain the one-hour limit. Only a valid complete owner-proved snapshot may change ordinary durable membership grants; an ordinary member cannot upload one. Membership removal, role/tier changes, failed or stale verification, expiry, revocation and disabled features can reduce or end access.

4. Local workspace and optional services

The CRM/workspace remains local by default, with the optional transfers described in the Privacy Notice and separate feature disclosures. You are responsible for local record accuracy and for protecting backups. Clearing browser data, uninstalling, device loss or storage failure may permanently remove unbacked-up data. Cloud scheduling, membership monitoring, Recovery and Plan sync retain their separate disclosures, opt-ins and controls. Accepting this bundle does not enable them.

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 separately enabled Cloud services, 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.