Privacy

Skool Copilot · Recovery details supplement October 29, 2026

Skool Copilot helps you manage your Skool communities. This is a short explanation of our privacy practices; the base privacy notice, workspace terms and privacy supplement and separate optional diagnostics supplement provide the details. For the account workspace service, the workspace supplement replaces earlier statements that general CRM remains only on the device and Plan syncing is optional.

What we collect and why

Account and access: your Copilot email, account details, Skool user ID, membership and plan status, accepted agreements and security records. Copilot has its own login and never asks for your Skool password.
Your workspace: supported member/contact details and community relationships, notes, tags, stages, saved content, authored drafts, schedule and automation content/history, events, activity and financial observations, planning records, selected preferences and finished media you add or capture through enabled features. After the disclosed agreement and account/identity checks, Copilot automatically saves these records and eligible finished media with your account using Supabase and keeps a working copy in Chrome. Current builds limit new media sync and scheduling to 100 MB per file (100 MiB); larger files remain on the device for supported immediate use and are not restored by these builds on another device or after local storage is cleared. Oversized copies saved by earlier builds may remain on the server under the existing retention and deletion rules.
Cloud features: the Skool session, content, recipients, community and payment-status information, settings and activity records needed for scheduling, monitoring, Auto DMs and Payment Recovery. Recovery can check recent replies to avoid unwanted follow-ups; it does not keep a conversation archive.
Recovery details: choosing Load details, Refresh or an unloaded Conversation tab uses the existing Supabase service and Skool connection to read the selected member’s masked card summary, available billing details and recent messages for display. Card details and conversation text remain in memory and are not saved to the workspace. These manual reads can work while automatic Recovery is off; they do not start follow-ups or send messages. A reviewed and confirmed inline reply stops that verified case’s follow-ups before entering the encrypted scheduled-DM queue. Read the Recovery details supplement.
Planning: supported tasks, goals, results and focus records are included in the account workspace. Earlier optional Plan-sync notices remain available for older supported clients; their optional-service wording does not describe the current workspace service.

Copilot uses your signed-in Skool session to check your own community membership directly. It retains the result and verification time, not the session or page content from this check. The verified community owner may also supply the current member IDs, roles, tiers and active status, including members without Copilot accounts; that list excludes names, email addresses, notes and messages.

Optional automatic failure diagnostics

This separate feature requires its own choice in Settings on each installation. Read the Diagnostics disclosure (diagnostics-v2) before enabling it. This supplement applies only to that optional feature; existing account and Cloud notices remain available at their original versions.

When you separately enable Automatic failure diagnostics on an installation, Skool Copilot sends limited technical summaries of unexpected failures to its Supabase backend. With a separate diagnostics-v2 choice, this also includes file-size limits that prevent syncing or scheduling. Authorized support uses this evidence to investigate problems and decide whether limits need adjustment. Earlier diagnostics-v1 acceptance remains limited to unexpected failures; it does not enable file-limit reports. Successful activity is not recorded by this feature, and receiving a diagnostic does not automatically start AI analysis.

Summaries are associated with your Copilot account and installation. They contain random event or operation IDs, existing Cloud job IDs when available, feature/stage/error codes, first/latest occurrence times and repetition counts, extension build/browser major version, a bounded sequence of technical stages, and small numeric or boolean context such as HTTP status. File-limit reports contain a fixed reason, the affected action and a broad size range; they exclude exact file sizes, filenames, media identifiers, paths and content. Records can indicate discarded evidence or incomplete job correlation. Diagnostic records exclude message contents, text you type, screenshots, page HTML, browsing history, cookies, passwords, access tokens, raw exception messages and raw request/response bodies. Existing account and installation proofs authenticate requests but their secret values are not retained in diagnostic records.

The service stores access-controlled technical metadata; this is not end-to-end encryption. Authorized backend processes and support operators can access it. Other browser accounts cannot read it through the diagnostics service. This feature does not add a general session recorder, collect successful activity, investigate Skool activity automatically, or send information to an AI service.

The first failure starts an approximately 15-minute collection window. Reports normally become available within 15–30 minutes while online, authenticated and the service is available; sleeping browsers, offline devices, unavailable authentication and outages can delay uploads. Repeated failures are combined and pending batches are bounded. There is no daily reporting quota.

Pending local summaries are limited to 100 records and 128 KiB and expire after seven days; local expiry is processed when the extension next handles diagnostics. Server summaries expire 30 days after first receipt and are removed through bounded maintenance, so physical cleanup may occur later. Diagnostics are excluded from workspace backups, Plan sync and cross-device restore. Finite storage and expiry can discard evidence, and some failures leave no diagnostic.

Turning collection off clears pending diagnostics and stops future collection and uploads on that device. An in-flight upload may already have reached the service. Off does not remove previously accepted server records or disable another installation. Logout, account changes and local reset clear pending diagnostics. Optional disclosure acceptance remains on the installation record. Account-data access includes diagnostic metadata, and account deletion removes associated diagnostic records.

Diagnostics do not send, retry or reschedule messages, change a delivery outcome, or preserve message contents as a recovery backup. Existing Cloud execution history, encrypted schedule retention and backup controls retain their separate purposes and rules. A missing diagnostic does not establish that an operation succeeded or that a retry is safe.

Your choices

Accepting the account agreement enables membership verification and prepares the Skool connection for eligible Cloud tools. This can let authorized work run while your computer is off. You separately choose the schedules, communities and automations to enable. Automatic workspace saving is part of the current account service after its disclosed agreement and checks; it does not itself authorize sending or replay schedules. Preparing a connection does not itself start monitoring or send messages. Unsynced changes wait on the device and can be lost if local storage disappears before upload; unfinished recordings are not a cloud recovery point.

Where data is stored and shared

Local records and downloaded backups are readable by someone with access to those files or your browser profile. Supabase hosts account, workspace and enabled Cloud services in our Paris project. Ordinary workspace records are access-controlled JSON; finished media and thumbnails use private object storage with account-scoped, short-lived access URLs. Workspace content uses the provider's infrastructure encryption at rest and HTTPS, without an additional application-layer encryption scheme. Separately stored Skool sessions and supported Cloud execution content use server-managed AES-256-GCM. None of these services is end-to-end encrypted: authorized service operators/providers can access content when permitted and necessary for disclosed operation, security or specifically authorized support. SHA-256 media hashes check integrity, not confidentiality.

We use HTTPS. Supabase provides authentication and backend services; Namecheap Private Email delivers account emails. Skool and its media providers, Amazon S3 and Mux, receive authorized content and uploads. GIPHY receives searches when you use its GIF search. These providers may process request metadata, including IP addresses, outside the EU. Exports go to destinations you choose.

Retention and deletion

The browser working copy can disappear when extension storage is cleared or the extension is uninstalled. Successfully synchronized supported content can be retrieved after signing into the same Copilot and matching Skool accounts and meeting the service access requirements; this is not historical rollback or a zero-loss guarantee. Current workspace records remain until deleted or account removal; deletion leaves content-free sync markers. Workspace mutation receipts expire after 30 days, and unreferenced media becomes eligible for cleanup after 24 hours. Account and active service records stay while needed. Completed Cloud content normally becomes eligible for cleanup after seven days, most job history after 90 days, and notification events within 30 days. Active work, limited security records and provider backups have separate retention rules in the full notice. An aggregate recovery-revenue total without stored owner or member identifiers may remain.

Account deletion blocks new workspace access and removes linked live account/Cloud/Plan records, with durable storage cleanup including a delayed sweep after outstanding upload grants expire and retries on failure. Provider recovery copies follow provider retention controls and are not an ordinary workspace history; database backups do not include Storage media bytes. Account deletion does not erase local work, downloaded backups or content already posted to Skool. Signing out, turning off a feature or uninstalling alone does not delete the hosted account. Stop or cancel workflows you no longer want.

Use of your information

Skool Copilot complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. We use data only to provide or improve disclosed features. We do not sell it or use or transfer it for personalized advertising. Transfers are limited to those features, security, legal requirements, or a business transfer with your explicit prior consent. Human access is limited to your consent to specific information, necessary security or legal work, or aggregated and anonymized data for internal operations.

We process necessary service data to fulfil our agreement with you and use legitimate interests for security and membership-access checks. For member data supplied for community work, the community operator determines the purpose and lawful basis as controller or represents that controller, and Avino Labs acts as processor under the workspace processing terms. Account administration and security remain our own controller activities. The agreement is not a lawful basis for every member's data. Operators must give appropriate member notices, honor rights and provide only data they are entitled to process; this service is not designed for special-category or criminal-offence data.

Contact and your rights

Skool Copilot is provided by Amirthan Puvaneswaran trading as Avino Labs, a Finnish sole trader (Business ID 3383759-5), independently of Skool. Email copilot@avinolabs.com to request access, correction, deletion, portability, restriction or objection, or a review of an access decision, including after a subscription ends or an account becomes inaccessible. The account download is bounded JSON with media descriptions, not media files; contact us for a larger or complete-media return. Requests use proportionate verification and a private response route; do not send passwords or Skool cookies. We respond within one month and explain any legally permitted extension within that month. Community members may also contact their operator. You may complain to Finland’s Data Protection Ombudsman.

Base privacy notice and contact details · Current workspace supplement and processing terms · Terms · Data use