yinian

Privacy Policy

Updated: October 16, 2026

yinian is independently developed and operated by an individual. This policy explains how this website, yinian accounts, cloud AI services, AI services used with your own API key, and optional Google Workspace connections handle your information. To contact the developer, ask about how your information is handled, or request account deletion, email support@yinian.ai.

Sign-in and accounts

Email sign-in requires your email address and a one-time verification code; code emails are sent through Resend. Google sign-in requests only basic profile and email permissions, used to confirm your identity and to create or link a yinian account. It does not authorize yinian to read your Gmail messages, contacts or Google Drive files. Google sign-in is handled on Google's own pages, and yinian never receives your Google password.

The server stores your account identifier, your encrypted email address and Google identity identifier, and the digests needed for verification. To prevent abuse of verification codes, it also processes a digest of the source IP address, request times, verification status and email delivery receipts. Verification codes are valid for 5 minutes; a code expiring does not mean the related security records are deleted immediately.

Sign-in sessions last at most 30 days and are not renewed automatically; signing out revokes the session. The desktop app stores sign-in credentials encrypted using the operating system's secure storage. Short-lived cookies required by Google are used to verify the sign-in flow. This website sets no advertising cookies; for visit statistics, see "Website and service providers" below.

Information when you use AI

When you use yinian's cloud models, the messages, context and any file contents you choose to submit for a request pass through the yinian server and are sent to the relevant model provider for processing. The main model provider is currently DeepSeek. Native search sends the queries needed to complete a search to the model provider's search service. Please submit only material you have the right to process.

You can also enter your own DeepSeek, Anthropic (Claude) or OpenAI (GPT) API key in the app and choose which one answers your conversations. Requests then go directly from the desktop app to the provider you chose, without passing through yinian's servers; the key stays on your computer only and is never uploaded to yinian. The daily digest, memory organizing described below, and background work such as conversation titles, reply suggestions and automatic approval review also go to that same provider and use its models. Web search is done by that provider's search service, which receives the search query; web pages are fetched directly by your computer, and what is read is then passed to the provider. These requests are processed and billed under your account terms with that provider; yinian does not record their usage or receive their content.

The daily digest, remembering after each reply and organizing memories while idle are on by default: while the app is running, after a reply, at the set time or when your computer is idle, recent tasks, calendar events yinian is allowed to read, to-dos and what you have said in yinian are sent to your selected model to be organized, using your model quota or your own API usage. You can turn them off at any time in the app's Settings > Assistant.

Where the corresponding feature is available and you enable and use it: Jev browser acceleration sends the task, relevant page information and the form contents you provide to TypeSafe; meeting transcription sends the selected recording or live-captured audio to Alibaba Cloud Model Studio (Bailian) / Tingwu; speech recognition, synthesis and voice conversation send the current audio, the text to be synthesized and the necessary conversation context to StepFun. Recordings may contain the voices of you or other participants, so use them only with the necessary consent. Dynamic thinking effort currently uses a self-provided TypeSafe API key and sends only the current input text to TypeSafe for assessment, never attachments or full history.

Stored locally does not mean never transmitted: when you ask the AI to analyze files, images, web pages or other material, that content may become part of a model request. Cloud features that are not yet available are not enabled by this policy.

The yinian cloud ledger records request identifiers, models, input and output usage, cache usage, credits and processing status, for billing, troubleshooting and abuse prevention; billing does not depend on storing full conversation text. yinian does not sell your personal information and does not use Google sign-in data for advertising. Please also read each model provider's privacy policy for how it retains or uses input.

Google Workspace connections

Google Workspace connections in yinian require separate authorization from signing in to yinian with Google. The Google consent screen displays the app name yinian. Calendar, mail, file search, and document and spreadsheet reading and writing are integrated and have been tested in controlled environments. The brand is verified, but data-access verification remains under Google review and the connection is not available to general users. Integration or brand verification does not mean data access, data protection, complete deletion or security assessment has been approved; these release conditions still need to be completed.

Data accessed and purposes

yinian processes data only after you choose to connect Google, grant the relevant permissions and select the corresponding purpose. Google lists the permissions actually requested, which you can decline; additional permissions require your consent again. An enabled daily briefing may also read calendar events allowed for that purpose and the unread-message metadata needed when generating the briefing. Signing in once does not enable every purpose.

Workspace connections do not synchronize your entire mailbox or Drive, enable background monitoring or advertising analysis, or access additional contacts by default.

AI processing and third-party transfers

When you ask AI to summarize messages, analyze files or work with your schedule, the content needed for the task may become part of a model request. With yinian's cloud models, requests pass through yinian's gateway hosted on Alibaba Cloud in Hong Kong to the model provider; the current cloud model provider is DeepSeek. With your own API key, the Workspace content needed for the task goes directly from the desktop app to the provider you chose (DeepSeek, Anthropic or OpenAI) and is processed under that provider's terms; Anthropic's and OpenAI's current API terms state that data submitted through the API is not used to train their models by default, and OpenAI may keep request records for up to 30 days to prevent abuse. These services may process data in their service regions. Before Workspace connections become available, the app will explain the actual providers, data transfers and purposes and obtain your consent. Google authorization alone does not authorize undisclosed third-party uses.

The Limited Use requirements below apply both to yinian cloud models and to your own API key: Workspace data and derived content must not be transferred to services that use it to train general-purpose models. Google passwords, access tokens and refresh tokens are not sent to model providers, and website analytics does not receive Workspace content. Provider data-use, retention and deletion rules, and the product's actual data protection and deletion capabilities, still require verification before release. Using your own key does not remove these requirements.

Limited Use and human access

yinian's use and transfer of information obtained through Google APIs, including derived data, complies with the Google API Services User Data Policyand the Google Workspace user data and developer policy, including the Limited Use requirements.

This data is used only for the clearly presented Workspace features you authorize. It is not sold or used for advertising, credit assessment, lending decisions, or training, fine-tuning or improving general-purpose AI or machine-learning models. Humans do not routinely read it. Limited human access is permitted only with your explicit agreement to view specific data, for necessary security investigations, or to meet legal obligations. Service providers must follow the same restrictions.

Retention, disconnection and deletion

The desktop app already encrypts authorization credentials using the operating system's secure storage, and Google API communication uses encrypted connections. Google credentials are not synchronized to yinian's cloud by default. Credential encryption does not mean that every copy of Workspace content is encrypted. Read content and summaries may remain in local conversations, tasks, history retrieval, memory or exported files; enabled features such as automatic memory may retain related derived content. Protection, retention and complete deletion of original content and derived copies still require release acceptance.

You can disconnect a Google account in the app's connection management to stop further access through yinian and remove the corresponding locally stored authorization credentials. You can also revoke yinian access in your Google Account third-party connections settings. The app reports when remote revocation is unconfirmed. Disconnection or revocation does not delete original messages, files or events in Google or automatically erase existing local records, exported files or content already processed by model providers. Archiving a conversation or removing it from a list is not content deletion.

To access, correct or delete Google Workspace data and copies held by yinian, contact the email address on this page. Identify the connected account and the data concerned; do not send passwords, verification codes or tokens. After verifying ownership, we will explain the deletion that can actually be completed, requests needed to processors, and any minimal records that must temporarily remain for legal or security reasons. We will explain the actual boundaries for backups, exports or third-party retention. We do not currently promise one-click removal of every copy or immediate complete deletion. General account-record retention rules do not authorize additional retention purposes for Workspace data.

Voluntary feedback and diagnostics

You can submit feedback without signing in or while using your own API key. Only after you send it will your description, app version, operating system, CPU architecture and any diagnostic data you explicitly select and preview be sent to the yinian dashboard. Account submissions are associated with your current yinian account. Full conversations, audio, screenshots, files and local logs are not attached automatically, and existing local statistics are not uploaded retrospectively.

Feedback text is retained for 90 days from the first submission, each diagnostic version for 30 days, and receipts and access records for 180 days. Content is encrypted and available only to authorized maintenance staff. Use the receipt saved on your device to check status or request deletion of cloud content in all versions. Removing the local receipt does not delete cloud content. Existing encrypted backups are not rewritten immediately; confirmed deletions and expiry are applied before restoring them. Deletion records containing only random feedback and operation IDs and the deletion time are stored separately on the US server for as long as historical backups are retained. They contain no feedback text.

Website and service providers

The website uses Cloudflare for domain and network proxy services, with the origin server in the United States; accounts and the cloud gateway run on Alibaba Cloud servers in Hong Kong. Network services may process IP addresses, browser information, request paths and security logs. Email, authentication and model services may process necessary data in the regions where they operate, so related information may be transferred across borders.

This website uses Google Analytics to measure visits, such as the pages viewed, referral source, device and browser type, and approximate location, in order to understand how the site is used. Google Analytics sets analytics cookies for this purpose; they are not used for advertising. You can block or clear cookies in your browser, or install the Google Analytics opt-out browser add-on.

Retention, access and deletion

Account information is kept for as long as the account exists; billing and security records are kept as needed to run the service, handle disputes and meet applicable law. The current trial does not yet offer self-service account deletion and has no uniform automatic deletion schedule. You can contact the developer to request access, correction or deletion; ownership of the account will be verified first, and any records that must be kept will be explained along with the reason.

Service backups are encrypted and access-restricted. Deleting online data does not immediately remove earlier backups; if a backup is restored, confirmed deletion requests are applied again so that a deleted account is not brought back into use. Closing your account is separate from deleting files on your computer; you manage local data on your own device.

Policy updates

When the purposes of processing, service providers or account rules change materially, this page and its date will be updated, and where appropriate you will be notified in the app or by other reasonable means. Processing that requires separate consent will happen only after consent is obtained.