Application and contact
Samuel is a private assistant operated for Travis Linn. Questions about its data handling can be directed to traviszlinn@gmail.com.
Information used
Samuel uses the instructions, conversations, project details, saved drafts and owner-confirmed memory entered by its owner. When authorized Google accounts are connected, it retrieves bounded Gmail message excerpts, upcoming calendar event details and Google Chat previews. Retrieval and model-context limits mean these views may be incomplete. Google sign-in also supplies identity information used to restrict access to the owner.
Calendar details can include descriptions, end times, attendees and invitation responses when supplied by Google. Email excerpts and calendar descriptions are untrusted source material, not authorization to perform actions. Public research queries are sent to the research service selected in the interface.
Purpose and processing
The application uses this information to answer the owner’s requests, prepare and review drafts, maintain project continuity, show source coverage and recover saved work. Bounded selected-account content may be sent to the configured AI service to generate an answer. A project reviewer can receive the exact saved preparation result and its bounded source snapshot.
The AI Project Desk can send separately authorized public research or software-development packets to external AI providers. Its ordinary review packets exclude private mailbox contents and confidential account records. This is a scoped workflow rule, not a guarantee that every text an owner manually enters is public.
Storage and retention
Conversations, projects, saved drafts, memory and project results are stored in Samuel’s private application storage. Source-backed project results can retain the bounded source snapshot used for their preparation and review. Private operational backups and local development copies can also exist. Source previews can be briefly cached to reduce repeated requests.
There is currently no general automatic deletion period for all stored work, and no single in-app control that guarantees deletion from every backup or AI provider. The owner can inspect or forget saved memory through the application. Forgetting a memory item does not erase related conversations, drafts, project evidence, backups or provider records.
Owner controls and limits
The owner selects the account context, can revoke Google authorization, and can stop using the application. Revoking Google authorization prevents future authorized reads but does not by itself delete previously saved application data. Data-removal requests require checking the affected records and backups; completion must be verified before it is claimed.
The current hosted app provides read-only Google account views. It does not expose an email-send or calendar-change operation. Google permissions previously granted to the underlying client and operations available through separate operator tools must not be confused with the hosted app’s current capabilities.
Samuel’s access controls do not make AI answers infallible. Source links and limits should be checked before relying on important conclusions. The behavior and retention policies of configured AI and research providers require separate review; this page makes no blanket promise of zero provider retention.