Cloud Scheduling Disclosure

Version ID: cloud-scheduling-v3. Prepared September 30, 2026. Applies only when this exact notice is presented and explicitly accepted.

This connection receipt covers supported Cloud posts, comments and DMs. Automations, membership monitoring and Payment Recovery retain their separate explicit feature choices and scoped controls; this receipt alone enables none of them.

Publisher: Amirthan Puvaneswaran trading as Avino Labs, Business ID 3383759-5. Contact: copilot@avinolabs.com.

When you explicitly connect supported Cloud services, trusted extension background code reads the allowed Skool `auth_token` and, when present, `aws-waf-token` from the exact qualifying tab's cookie store. It sends the bounded cookie header, browser User-Agent and capture/expiry information over HTTPS to the fixed Supabase backend. The backend proves the signed-in Skool account against the immutable account binding and stores an AES-256-GCM encrypted connection with server-managed keys and identity-bound associated data. The WAF value can also support a bounded browser media-upload header.

These credentials can act as your Skool session. This is not end-to-end encryption: authorized backend code and anyone with the necessary backend/key access can decrypt them. The extension does not request or retain your Skool password. Stored-content encryption does not make routing, connection metadata, consent and execution records end-to-end encrypted. Protect your Skool/browser sessions and your account separately.

An explicit identity-conflict “Verify with Skool” proof can transfer the bounded session once for transient server-side identity verification without storing a Cloud connection. That proof does not grant unattended delivery. Ordinary exact-page membership checks use the browser's existing session without reading/forwarding cookies; these two mechanisms must not be conflated.

Delivery and retention

Only separately authorized Cloud scheduling/automation work can execute while the computer is off. Authored content and supported media capabilities are encrypted; exact routing, identity and bounded execution metadata are used only to perform and track the action. Raw media uploads to validated Skool destinations and is not copied into a general Supabase media library.

Terminal full-body/recipient/media payloads normally become eligible for cleanup seven days after terminal outcome; cleanup runs can be delayed. Separately encrypted post titles can remain with terminal job history, which generally has a 90-day cutoff subject to safe cleanup conditions. Active automation definitions and monitoring comparisons remain while required; disabled definitions and terminal cases have their own eligibility/dependency rules. Content-free replay/operation fences can persist for the account lifetime to prevent duplicate actions.

Disconnect clears the primary live session ciphertext and stops connection-dependent work, including cancellation of supported undispatched queue work. It does not recall an in-flight request, delete historical records immediately, delete already published Skool content, or revoke a cookie copied independently. Account deletion cascades ordinary linked records; local files/devices and provider backups/logs are separate boundaries described in the privacy policy. You can also cancel selected work or stop individual supported automations.

Uncertain delivery after irreversible intent is never automatically retried. Review Skool and the outcome before making a new operation. Skool interfaces are undocumented and can change or be restricted. Use only communities/recipients you are authorized to manage. Encryption does not establish another person's lawful basis or replace appropriate community notices.

Privacy Notice v3. Earlier accepted notices and timestamps remain unchanged.