Your record. Your sources. Your assistant.
Help with Pref
Contact sam@thesideletter.co for access questions, setup help, corrections, revocation or deletion. Public enrollment is being prepared. The Claude Google connection has been verified for the approved owner; contact support for current availability and other supported assistants.
What to include
Describe the action, approximate time, visible status code and whether you were setting up, reading, correcting or downloading. Include your non-secret client label only if needed. Do not include a key, private record, full error body, source document, signed URL or account identifier in a support email. The operator can arrange an appropriate private follow-up after identity verification. No response or recovery interval is promised.
Connection or setup failure
For the Google route, return to your assistant's connector settings, select Connect and choose the same Google account. First sign-in creates your account; later sign-ins find it again. No service token or OAuth secret belongs in chat. A cancelled or expired connection can be restarted from those settings. If the connection still fails, contact support with the visible message and approximate time.
If your assistant lacks email or portal access, connect that source through its own supported settings. Google sign-in to Pref supplies identity only. If a fresh conversation cannot retrieve your invented test record, do not start a real import.
A 401 can mean missing, wrong, expired or removed access; reconnect through your assistant's settings when the Google route is available. A 403 means the connection lacks permission. A 409 means a saved revision or pending selection changed: reread and make a deliberate correction. A 429 or 503 means a limit or temporary pause; respect the retry guidance and ask for help if it persists. Never discard history to work around a limit.
For an existing operator-managed pilot credential, support handles replacement after verifying your identity. Enter it only through the approved secure capture route.
Source, correction or download gap
Report the exact source/window that was unchecked, blocked or stale. Do not interpret that as no updates. Sign in only in the provider's own supported handoff. Declined source access remains declined.
For a wrong match, ask the assistant to read the saved evidence and correct or retract that reference, preserving history. If the action is missing, ask support; do not create guessed replacement holdings. A CSV must arrive as a usable file, not just a success message. Missing Muse actions and current correction/download UX need acceptance before they are promised.
Remove an assistant
When the Google route is active, open Connected assistants, sign in with the same Google account and select Remove for the affected assistant. That stops its Pref access and renewal; your saved portfolio and history stay in your account. Your other connected assistants retain their own access. Connecting again creates a new connection.
Stop any collection or delivery jobs separately in the assistant. Remove email and portal permissions through those providers when desired. Removing Pref access does not delete copies already held by an assistant or provider.
For existing operator-managed pilot credentials, ask support to revoke the affected client after verifying your identity. Report suspected exposure without sending the credential. Deleting records alone does not revoke access.
Export or delete your record
You may request your own CSV or complete saved-history export through verified authorized access. Complete history can require bounded pages; an incomplete download must not be presented as complete.
After verifying your identity and explicit instruction, the operator uses separate owner deletion authority to remove your tenant's live observations, collection state, document evidence, correction/audit history and delivery state. The ordinary maintenance agent cannot delete the portfolio. Review whether an export is wanted before deletion; never create one automatically.
Client journals, downloaded exports, conversations, provider copies and retained whole-database snapshots have separate retention and deletion. A whole-database copy may include other tenants and requires an exact reviewed deletion process. Other users' live records remain separate. See privacy and retention. Remove remaining assistant connections and revoke legacy credentials to prevent a later save from recreating a deleted record.