Poly is a private assistant operated by Sebastian Sogamoso for personal and authorized work use. It is not offered for public registration.
Information accessed and purposes
Once authorized and connected to the runtime, Poly may access Gmail messages, attachments, labels and drafts; Calendar events, attendees and calendar metadata; and Drive files, document contents, comments and metadata. It uses this information to answer the owner’s requests, summarize information, prepare drafts, organize schedules, and manage authorized resources. Access is limited by each account’s granted permissions.
Google API access has been tested, but runtime integration is still being completed. Authorizing an account does not by itself enable unattended actions. Sending an email requires approval for that specific email. Invitation replies, proposed reschedules, Drive deletions and Drive comments require approval.
Processing and service providers
Poly runs on a privately operated Mac mini. Vercel Connect manages OAuth credentials and token exchange. Relevant request context may be sent to OpenAI or Anthropic for model processing. When memory features are enabled, conversation content and information included in those conversations may be stored locally and sent to Supermemory for retrieval in later conversations. Private replies are delivered through Slack. Other cloud model providers may be configured; their processing must be considered before routing Google data to them.
These services process transmitted information under their applicable terms, account settings, and retention policies. Local hosting does not mean all processing stays on the Mac mini. This policy does not promise zero retention or a blanket training exclusion by third-party providers.
Account separation and disclosure
Personal and work accounts have separate authorizations. Combined answers are intended only for the verified owner’s private conversations and must label their sources. Sharing information or performing actions in another connected service is subject to the assistant’s account and approval controls.
Storage, retention and deletion
OAuth credentials are stored through Vercel Connect, with configuration secrets held in 1Password. Local conversation records, cached information and enabled external memory may persist until removed; there is no guaranteed automatic retention period. Revoking access stops future authorized API access but does not automatically erase previously stored conversations, memory or provider logs.
The owner can disconnect access in Google Account settings or Vercel Connect. To request review or deletion of retained information, contact sebastian@sogamo.so. Deletion may require separate removal from local storage, Slack and external memory or model services, subject to their capabilities and retention requirements.
Contact and changes
Questions about this private assistant and its data handling can be directed to Sebastian Sogamoso at sebastian@sogamo.so. This policy should be updated when integrations or data handling change.