Recovery details

Document ID: recovery-details-v1 · October 29, 2026

This supplement describes the member details you choose to load in Payment Recovery. It adds to the existing privacy and scheduling notices; it does not replace earlier accepted documents or enable Recovery, sending or a new account permission.

Details you choose to view

Choosing Load details, Refresh or an unloaded Conversation tab asks Copilot's Supabase service to read the selected member's billing details and a bounded recent Skool conversation using your existing encrypted Skool connection. The service checks the signed-in account, community ownership and exact member before returning private details to you. Loading these details can work while automatic Recovery is off or no active follow-up case exists; it does not start or restart follow-ups.

The billing display can include the plan price and currency, payment-failure date, access deadline and member time zone. From the latest available membership invoice, only the card brand and last four digits, invoice date and open/paid status are returned. Conversation reads use an existing conversation with the verified participants. They return recent readable message text, direction and times, not a complete conversation archive. Copilot does not create a conversation to read it. Missing or incomplete details are shown as unavailable or partial.

Temporary processing

Invoice responses and conversation text are processed in server memory. Returned card and conversation details remain only in the extension view's memory for the selected member and account; changing that selection or account clears the details. Switching between Activity and Conversation or returning to the payment list can retain the same selection in memory. These details are not written to Copilot's database, workspace sync, backups or diagnostics. A small price and follow-up-status summary can remain in memory for up to five minutes to keep the payment list consistent. Existing saved membership observations, Recovery cases and revenue summaries retain their separate purposes and retention rules.

Requests use HTTPS between the extension, Supabase and Skool. The existing service connection is encrypted with server-managed keys, not end-to-end encryption. Supabase processes the request to provide these details; they are not sent to an AI provider. Skool retains its own source records under its policies. Privacy and support requests can be sent to copilot@avinolabs.com.

Replies and follow-ups

Reading details does not send a message. Where an inline reply is available, you write it, review it and confirm the queue action. Copilot stops that verified case's automatic follow-ups before putting the reply in the existing encrypted scheduled-DM queue. Queued does not mean delivered. The queued message and delivery history follow the scheduling service's existing retention rules. An unqueued draft remains in view memory and is discarded when the selected member or account changes, or the extension view is unloaded. Where no verified active case exists, the interface instead offers the member in People for a native reply.

Stopping or resuming follow-ups is a separate deliberate action. Resume is available only for an eligible retained case stopped by its owner, continues at the next unsent message and rechecks billing, reply evidence and access. It does not replay confirmed messages or revive purged history. Automatic reply checks remain separate from this on-demand detail display.

Earlier versioned notices remain historical evidence of their stated practices and accepted versions. This document clarifies the additional owner-requested detail reads and reviewed replies; it does not record a new acceptance on your behalf.