隱私權政策

Operator and services

The operator is 臻環科技股份有限公司. Contact izev@zev.city for privacy and deletion requests. This policy covers the ZEV City website, ZevRouter and ZEV LINE AI (ZEV 傑夫), a cloud AI assistant used through LINE. ZevRouter provides model routing and Google account connection services. Google consent screens may identify the application as “ZEV City”.

Information and purposes

We process account and group identifiers, authorized Google identity information, connections and settings; prompts, attachments, work files, responses, memories or summaries and tool results; scheduled tasks, email recipients and delivery status; necessary authorization tokens, synchronization and recovery data; usage, model routes, request identifiers, costs, transactions, support, technical and security records. These support your requested features, continuity, billing, security and service operation. Website infrastructure receives connection information such as IP addresses and browser/request information. Necessary cookies or browser storage support sessions and preferences. This policy page itself has no tracking scripts or collection form.

Payment services handle their payment credentials. The ZevRouter usage ledger records transaction details rather than full card credentials. We do not ask you to give ZEV your Google password. New purposes will be explained separately; merely visiting this policy does not authorize them.

LINE groups

The bot does not automatically obtain unrelated private chats, groups it has not joined, or unseen earlier history. When a group owner enables background-message retention, ordinary group text may be retained even without invoking the bot. Owners should inform participants; an owner's setting is not each participant's individual consent. Group responses are visible to members. Bot conversations and outputs may be included in the owner's workspace backups, including enabled Drive backups. Raw background caches are separate, but quoted content may appear in responses or files. Group membership does not grant access to the owner's personal Google authorization.

Optional Google access

• openid, userinfo.email and userinfo.profile: identify the signed-in Google account, show basic account information and connect it to the correct ZEV account.
• https://www.googleapis.com/auth/drive.file: work with files created or opened by this application, or specifically shared with it by you, for work files, exports and currently enabled synchronization/backups. It does not grant access to every Drive file.
• https://www.googleapis.com/auth/calendar.app.created: create and manage application-created calendars and their events, not read all your private calendars.
• https://www.googleapis.com/auth/gmail.send: separately authorized sending of scheduled task results from your Gmail account, after you enable Email notifications and save recipients. This uses the sender, recipients, subject, result body and delivery status. It does not read, search or delete inbox mail or request full mailbox access. Gmail authorization tokens are used by the backend, not supplied as chat-model prompts. Generated results can contain information from your original task, so choose recipients carefully. Connecting Gmail does not itself enable Email notifications.

Permissions and the relevant settings must be active. You can disable Email notifications, disconnect Google in ZEV settings or revoke access in Google third-party connections. This stops future authorization-dependent access; it does not log you out of Google or automatically delete previous mail, files or backups.

Limits on Google data use

Google-authorized data and derived content are limited to the visible features you use. We do not use this data for sale of data lists, advertising audiences, credit decisions or training general-purpose AI models across users. Generating an answer for your request is distinct from general model training. Transfers are limited to necessary, consented features, security or applicable legal requirements; authorization is not permission for arbitrary resale or publication. Human reading is limited to specifically consented assistance, necessary security matters, legal requirements or appropriately de-identified aggregate operations. These limits are based on the Google API Services User Data Policy and Workspace Limited Use requirements; they are not a claim that Google has approved the app or that every third party provides zero retention.

Sharing, international processing and safeguards

Necessary inputs go to the selected model and routing providers, and to tools such as search. Available model families may include Google Gemini, OpenAI GPT, DeepSeek, Qwen and GLM. Attachment or image services can differ from the main chat model. LINE delivers messages, Google Cloud provides hosting and recovery storage, Cloudflare provides website/network/security services, and payment services handle their payment flows. Necessary disclosures may also occur for security or legal duties. This does not mean we sell your conversations.

Processing may take place in Taiwan and other provider locations, including the United States, rather than only in Taiwan. Third-party handling depends on the applicable service and arrangements; we do not promise universal zero retention. We use encrypted transmission, account/workspace isolation and authentication/access restrictions. Privileged operators may technically access stored content: this is not end-to-end encryption that excludes the operator. Processing is limited by work necessity, not casual browsing of private content. Optional hosted-browser features process page displays and login state separately from Google API authorization, without taking over your personal device.

Retention and deletion

Group background caches use both configured time and message-count limits (currently 1–720 hours and 10–5,000 messages). Disabling retention clears that cache; LINE unsend events handle matching background text and attachment references. These are not universal retention periods. AI history, memories and work files persist for continuity and retrieving results, without a single automatic expiry across all data. You may request deletion or account closure. Authorization records support connected functions; disconnected or revoked access is not used for future access.

Recovery backups, Drive versions, exports, usage/security and transaction records have separate purposes and retention mechanisms. Main-data deletion is not simultaneous erasure of all backup copies. We explain the scope, available deletion actions, recovery limitations and any justified retention when handling requests. Previously generated answers or memories may not disappear when a source message is unsent. Copies held by group participants, recipients or in your external accounts may require separate action and are not fully under our control.

Your choices and requests

You may adjust models and group retention, disable notifications, revoke Google access, stop using the service or request access, a copy, correction, cessation of processing or deletion. A feature may stop working if required information or permission is withdrawn. Email izev@zev.city with “Privacy / data request”, the service, account information needed for verification, relevant dates and requested scope. We verify your authority with necessary information, then explain available actions and an estimated timeline. Do not send passwords, verification codes, API keys or private authorization links. We explain any limitations involving others' data, required retention or third-party copies. Possession of a link alone is not sufficient to disclose private account data.

Updates

We date changes here and explain material changes through appropriate service notices or other available channels, requesting consent where required. Reading this page does not change settings, enable email or grant Google permissions. Earlier Beta data-processing notes deferred the operator and public contact details; the details in this policy now apply.