Tamias Duo

Privacy policy

Effective October 24, 2026

Tamias Duo is a personal AI assistant operated by Denis Duvauchelle. This policy explains how the web, macOS, and iOS apps handle information. Contact desduvauchelle@gmail.com with privacy questions or deletion requests.

Information we handle

• Account information: your sign-in identifier, email address, profile information provided by your sign-in service, and app preferences.
• Content you provide: chats, tasks, project information, notes, uploaded files, and voice recordings or transcripts used by voice features.
• Connected-service information: account identifiers, permissions, credentials or authorization tokens, and information retrieved to provide the features you use.
• Operational information: activity records, errors, model usage, token counts, and costs used to operate, troubleshoot, secure, and manage the service.

Google account access

Google sign-in uses your identity and email to sign you in. Connecting a Google service is a separate choice. Depending on what you connect, Tamias can access:

• Gmail: message headers, sender and recipient details, subjects, bodies, labels, and drafts. Gmail permission enables reading, composing, sending, and modifying messages, including archiving. These capabilities support inbox views and assistant email tasks.
• Google Calendar: calendars and events, with permission to create or update calendar information for calendar features and assistant tasks.
• Google Drive: read-only access to file information and content for finding and using files in your tasks.

Only connect accounts you are authorized to use. Permissions shown by Google may be broader than any single action you perform. Connecting an account does not make its contents public or give other Tamias users access to it.

AI processing and service providers

Relevant chats, retrieved email or file content, and task context may be sent to AI services when the assistant uses that information. Voice features send audio or text for transcription or speech generation. Current infrastructure includes Convex for backend storage and processing, Vercel for web hosting and AI Gateway routing, and OpenRouter and the model providers selected by the service or your configuration for AI processing. Providers and models can vary by feature and configuration.

We use these services to deliver the features you request, operate the service, and address security or reliability issues. Provider retention and processing depend on the service and configuration; this policy does not promise zero retention by every AI provider. Tamias does not run a general-purpose model-training pipeline using your connected Google data.

How we use and share information

We use information to provide the assistant and connected features, store your work, authenticate accounts, respond to support requests, maintain security, and monitor usage and reliability. Information is shared with service providers as needed for these purposes, with destinations involved in actions you request (such as email recipients), or when required by law.

We do not sell Google user data or use it for advertising, credit decisions, or unrelated profiling. Tamias Duo’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Human access to connected Google data is limited to your specific consent, necessary security or troubleshooting work, legal requirements, or other uses permitted by that policy.

Storage, security, and retention

Authorization refresh tokens and supported stored connection credentials are encrypted before being saved in the backend. Account access checks limit connections to their owner. Web traffic uses HTTPS. No service can guarantee absolute security.

Inbox views retrieve messages from your mail provider. Content used in assistant conversations, task records, archive display snapshots, files, and related activity may remain stored in Tamias. Account and saved content are retained while needed to provide the service, until you remove supported records or request deletion. Operational records and backups may remain for security, recovery, or legal purposes. We do not promise a fixed automatic deletion period.

Your choices and deletion

Remove a connection from the Connections screen to delete its stored connection record and stop Tamias using that connection. For Google connections, Tamias also attempts to revoke the stored token. You can independently revoke access at Google Account connections. Disconnecting does not automatically erase content already saved in chats, tasks, or other records, and does not delete the original messages or files at Google.

To request deletion of your Tamias account or stored personal data, email desduvauchelle@gmail.com from the account email where possible. We may need to verify ownership before processing your request. You can also ask about access to or correction of your information.

Cookies and international processing

The web app uses authentication cookies and local preferences needed for sign-in and app settings. Our providers may process information in countries other than your own. Applicable privacy rights depend on where you live; contact us to exercise them.

Children and changes

Tamias Duo is not directed to children under 13. Contact us if a child has provided personal information. We will update this page when practices change and seek additional consent where required for a new use of connected Google data.