English
Operator and scope
This policy describes the Google Play version of Screen Translate, package com.newtranslate.google, operated by 上海煜饶网络科技有限公司.
Office contact address: 上海市浦东新区南汇新城镇环湖西二路888号C楼, China. Contact: hnzmdlcw@163.com.
The current Google Play app does not provide an in-app account registration or sign-in service. Buying a product through Google Play does not create an account with us. Features, engines and processing may vary by app version, configuration, language and access rights.
Screen content, OCR and translation
You decide when to start screen capture and approve Android's screen-sharing prompt. The screen may show information from other apps. Select the content you want translated and use Stop when finished. Some protected screens cannot be captured.
Google ML Kit OCR recognizes screen images on the device. Its diagnostic and usage telemetry is separate from image recognition. Online translation sends text you provide or text recognized from the screen, together with language and request settings, to the configured translation service. Requests may pass through translation infrastructure operated for the app and a configured fallback provider; the displayed engine name alone does not identify every intermediate processor.
Cloud OCR options, when selected and available, send the chosen image or screenshot for recognition. These integrations include Youdao, Alibaba Cloud Qwen and Zhipu. Their use depends on configuration and access rights. Selecting device-side OCR does not itself upload the image to cloud OCR, but translating its recognized text online still sends that text off the device. Some device-side language features may download models.
For example, the currently configured DeepSeek model route uses OpenRouter as an intermediary. The configured Qwen cloud-OCR route uses Alibaba Cloud's China (Beijing) service. Other engine routes can pass through infrastructure operated for the app; configuration and fallback routes may change. China-region cloud processing follows its applicable product and account terms; international-product retention rules are not a blanket deadline for the China-region OCR route.
Online options currently include engines or models branded Baidu, Google, DeepSeek, Gemini, ChatGPT, Hunyuan, Qwen and Zhipu, together with self-hosted Youdao and DeepL options. An engine/model label does not mean a direct connection to the brand owner; configured intermediaries and fallback services may be involved. These services process requests under their applicable service and privacy terms, and their processing and retention rules vary.
If you choose read-aloud playback, speech can use an available device-side voice or an online speech route. The online route sends the text to be spoken and its language to Google over HTTPS to obtain audio; this playback feature does not record microphone audio. Device-side OCR therefore does not mean that every read-aloud request stays on the device.
Local history, cache, copying and sharing
The app can save original and translated text, languages, engine, time and favorite status in a database on your device. Full-screen and selected-area results can be saved; automatic capture and subtitle modes do not save a new history record for every frame. You can delete individual history records in the app.
When history exceeds 5,000 records, the app removes non-favorite records outside the newest 5,000 records; older favorites can remain. This is a record-count rule, not a 90-day expiry. Translation results may also be cached locally. Clear translation cache clears the app's translation cache, separately from history and other SDK or server data.
Copying places text on the system clipboard. If you choose to share, the receiving app or service can handle the copy under its own practices. For large text, the app creates a text file in private cache and grants temporary access to the sharing target you choose. Old export files more than 24 hours old are considered for deletion when another export is made; there is no guarantee of removal at an exact 24-hour deadline. Deleting local history does not recall shared copies or delete information already processed by online services.
Configuration, diagnostics and security
The app requests configuration from its HTTPS bootstrap service using the application ID, app version and a randomly generated installation ID stored on the device. This configuration request does not contain the screenshot or translation text. The installation ID persists across launches; it is not an in-app account. The service uses installation identifiers and IP addresses for configuration delivery, rate limiting, abuse prevention and troubleshooting, and records related request metadata such as version, time, path, response status and duration.
We use Firebase Analytics, Crashlytics and App Check/Play Integrity to analyze use and technical failures and protect services. Depending on the SDK and event, information may include installation/app-instance identifiers, device and app information, usage events, error or crash details and purchase/subscription events. Custom app events can include a message, channel, app version, app signature/package and an existing user identifier where available. No real name, telephone number or payment-card number is required by the current app's own registration or purchase interface.
Our Google Analytics account currently enables data sharing for Google products and services, modeling contributions and business insights, technical support and business recommendations. Google can access or use relevant data for those enabled purposes, including improving its own products and services, account support and business advice. Google describes modeling/business-insight contributions as aggregated and de-identified; that description does not mean every Analytics record or other sharing is anonymized. Google Analytics data sharing. Under this setting and applicable terms, Google's stated uses also include detecting invalid Google Ads traffic and building broad models to improve ads relevance. Google excludes data with ads personalization disabled for the relevant event, user property or region from that personalization use. Uses of shared Analytics data.
The app does not currently provide a dedicated switch that disables all Crashlytics collection. Advertising privacy choices do not by themselves disable every Analytics, crash or installation-identifier path. SDK/provider policies and actual property settings govern their separate retention and processing.
The app uses HTTPS for bootstrap configuration and translation SDK connections. We use platform and service-provider safeguards to protect information in transit and restrict access. No transmission or storage system can guarantee complete protection. Advertising and recognition services describe their own safeguards in the provider information linked below.
Advertising and privacy choices
The app uses Google Mobile Ads and mediation integrations for AppLovin, ironSource/LevelPlay, Liftoff/Vungle and Pangle. Actual availability depends on configuration, consent and region. Advertising services can process identifiers, IP-derived approximate location, app/ad interactions and technical diagnostic/performance signals for advertising, measurement and fraud prevention, and may share data under their applicable terms.
Where available, the app's privacy options let you review advertising choices. Android also provides advertising-ID controls. These controls do not necessarily remove every installation identifier or stop all non-advertising diagnostics. The app checks whether ads may be requested before initializing/requesting its advertising flows; absence of a consent form alone does not mean that all data processing has stopped.
Purchases and rewarded ads
Google Play handles payments. The app receives product, purchase-state, purchase-token and entitlement information to recognize and acknowledge purchases. Analytics may record product, price and purchase/subscription events. The app does not receive your payment-card number from the Google Play payment interface. Google Play and Analytics process their own records under their applicable terms.
If a rewarded ad completes successfully, the app can update local translation-use allowances and frequency information. Advertising partners separately process the ad request and interaction. This policy does not promise that viewing an ad always produces a reward; errors and availability vary.
Retention, deletion and contact
Our Google Analytics property currently has 2 months of event-data retention and 14 months of user-level data retention. Reset user data on new activity is enabled: a new event can restart the user-identifier retention clock, so an active user's identifier may be retained longer. This reset applies to user-level data. These settings do not limit standard aggregated reports and are not a single 14-month deadline for all app data. Google Analytics data retention.
Local history, cache and exported files follow the rules described above. Online services process request content to provide translations and recognition. Operational records can include request time, language/engine, status, duration, request identifiers and text counts/lengths for usage measurement, diagnostics and security. Records are handled according to the service involved and its operational and legal requirements; provider and backup records follow their applicable retention and deletion policies. Local deletion does not automatically send a deletion request to every online service. Firebase states that Crashlytics keeps crash traces and associated identifiers for 90 days before beginning removal from live and backup systems; this is a Crashlytics-specific rule, not a deadline for the whole app. Firebase retention.
You may email hnzmdlcw@163.com to ask about personal information or request deletion. We may need information reasonably necessary to verify the request and identify records. We respond within 10 working days after identity verification; that is a response period, not a promise that all third-party or backup copies are erased within that time. To minimize disclosure, do not send unrelated screenshots, payment credentials or sensitive screen content with an initial request.
Provider information and applicable service terms include:
- Firebase, Google Analytics, Google Mobile Ads and ML Kit.
- OpenRouter privacy.
- Youdao AI privacy.
- Alibaba Cloud China Model Studio privacy information; international Model Studio privacy notice and data-retention rules; the applicable product, region and account/workspace terms determine which rule applies.
- BigModel/Zhipu platform privacy policy and user agreement. Those terms permit lawful use of anonymized data for model development; we do not describe every provider as excluding every form of training.
- AppLovin privacy, ironSource data disclosure, Liftoff Monetize data disclosure and Pangle data disclosure.
These references explain the corresponding services and do not mean every integration is used on every request.
This policy is effective from 17 October 2026. We update it when the app's practices materially change.
中文
运营主体与范围
本政策适用于上海煜饶网络科技有限公司运营的Google Play版Screen Translate（包名 com.newtranslate.google）。办公联系地址：上海市浦东新区南汇新城镇环湖西二路888号C楼；邮箱：hnzmdlcw@163.com。
当前Google Play版本不提供应用内注册或登录；Google Play购买不等于向我们注册账户。功能、识别/翻译引擎及处理路径会随版本、配置、语言和使用权限变化。
截图、OCR与翻译内容
您决定何时启动屏幕捕获，并通过Android屏幕共享授权。画面可能包含其他应用的信息，请选择希望翻译的内容，使用后点击Stop停止；部分受保护画面无法捕获。
Google ML Kit OCR在设备上识别画面，其诊断/使用遥测与图像识别是不同路径。在线翻译会向当前配置的翻译服务发送您提供或从画面识别的文字，以及语言和请求设置。请求可能经过为应用提供的中转服务及配置的回退提供方；界面显示的引擎名称不一定识别每个中间处理方。
选择可用的云OCR时，会发送所选图片或截图进行识别。代码集成包括有道、阿里云Qwen与智谱，实际使用取决于配置和权限。使用设备端OCR本身不代表向云OCR上传图片，但继续在线翻译所识别的文字，仍会将文字发送到设备外。设备端语言功能也可能下载模型。
例如，当前配置的DeepSeek模型路线通过OpenRouter中转；配置中的Qwen云OCR使用阿里云中国（北京）地域服务。其他引擎还可能经过为应用提供的基础设施，配置与回退路线可能变化。中国地域云处理遵循相应产品和账号条款，不能把国际产品的保留规则作为该中国地域OCR路线的统一期限。
当前在线选项包括标为百度、Google、DeepSeek、Gemini、ChatGPT、混元、Qwen、智谱的引擎/模型，以及自建有道和DeepL选项。标签不等于直接连接该品牌运营方，请求还可能经过配置的中转和回退服务；各方依适用服务与隐私条款处理，不同服务的处理和保留规则各异。
主动使用朗读时，可使用可用的设备端语音或在线语音路线；在线路线通过HTTPS向Google发送待朗读文字和语言以获取音频。该播放功能不会录制麦克风声音，本地OCR不等于每次朗读也全在本机。
本地历史、缓存、复制与分享
应用可在本机数据库保存原文、译文、源/目标语言、引擎、时间与收藏状态。全屏和选区结果可保存，自动/字幕模式不按每帧新增历史。您可在应用中删除单条记录。
记录超过5000条时，应用清理最近5000条以外的非收藏记录；较早的收藏可继续保留。这是条数规则，不是90天到期。翻译结果还可能缓存在本机；“Clear translation cache”清理应用翻译缓存，与历史、其他SDK和服务端数据分别处理。
复制会将文字放入系统剪贴板。您主动分享时，接收应用/服务会按其自身规则处理副本。大文本会先写入应用私有缓存，通过FileProvider临时授权给您选择的接收方；在下一次导出时，程序尝试删除超过24小时的旧导出文件，不承诺精确24小时定时删除。删除本机历史不会撤回分享副本，也不会自动删除在线服务已处理的数据。
配置、诊断与安全
应用通过HTTPS向bootstrap配置服务发送应用标识、版本和本机保存的随机安装标识；该配置请求不包含截图或翻译正文。安装标识跨启动保存，不是应用登录账号。服务使用安装标识和IP地址提供配置、限流、防滥用和排障，并记录版本、请求时间/路径、响应状态、耗时等关联请求信息。
应用使用Firebase Analytics、Crashlytics及App Check/Play Integrity分析使用和技术故障、保护服务。依SDK和事件而异，可能涉及安装/应用实例标识、设备和应用信息、使用事件、错误/崩溃及购买订阅事件。自定义事件可包含message、渠道、版本、应用签名/包名及可用的既有userId；当前应用自己的注册或支付界面不要求真实姓名、手机号或银行卡号。
我们的Google Analytics账号当前开启Google产品和服务、建模贡献与业务洞察、技术支持和业务建议四项数据共享。Google可按适用条款为这些用途访问或使用相关数据，包括改进其自身产品和服务、提供账号支持及业务建议。建模贡献与业务洞察按Google说明使用汇总、去标识化贡献；这不代表所有Analytics记录或其他共享均已匿名化。Google Analytics共享说明。在此共享设置及适用条款下，Google说明的用途还包括识别Google Ads无效流量，以及建立广泛模型以改善广告相关性。对于相关事件、用户属性或地域已禁用广告个性化的数据，Google不将其用于该广告个性化用途。共享Analytics数据的用途。
当前没有可关闭全部Crashlytics收集的独立开关；广告隐私选择也不等于关闭所有Analytics、崩溃和安装标识路径。各服务的保留和处理规则应结合其政策及真实属性配置。
应用对bootstrap配置及翻译SDK连接使用HTTPS，并采用平台和服务商提供的保护措施限制信息访问、保护传输。任何传输或存储系统均不能保证绝对安全；广告和识别服务各自的措施可查下列服务商说明。
广告与隐私选择
应用使用Google Mobile Ads，并集成AppLovin、ironSource/LevelPlay、Liftoff/Vungle、Pangle中介。实际可用性由配置、同意状态与地区决定。广告服务可能为投放、衡量、反作弊处理标识符、IP推导的大致位置、应用/广告交互及技术诊断/性能信号，并按适用条款共享数据。
在适用时，您可通过应用隐私选项查看广告选择；Android也提供广告标识符控制。这些选择不一定移除全部安装标识或停止非广告诊断。应用在初始化/请求相应广告流程前检查是否允许请求；没有出现同意表单本身不证明所有处理均已停止。
购买与奖励广告
付款由Google Play处理，应用接收产品、购买状态、购买token及权益信息，以识别和确认购买。Analytics也可能记录产品、价格和购买/订阅事件；应用不会从Play支付界面收到银行卡号。Play及Analytics依各自适用条款处理相应记录。
奖励广告成功回调后，应用可更新本地翻译使用次数和频控信息；广告合作方另行处理请求及交互。可用性和错误各异，本政策不承诺每次观看必然获得奖励。
保留、删除与联系
当前Google Analytics配置为事件数据保留2个月、用户级数据保留14个月。“有新活动时重置用户数据”已开启，新事件可重新开始用户标识的保留计时，因此活跃用户的标识可能保留更久。重置仅适用于用户级数据。这些设置不限制标准汇总报表，也不代表整个应用所有数据统一在14个月内删除。Google Analytics保留说明。
本机历史、缓存及导出文件遵循上述规则。在线服务处理请求内容以提供翻译和识别；运行记录可包括请求时间、语言/引擎、状态、耗时、请求标识及文本条数/长度，用于使用量统计、故障诊断和安全。相应记录按具体服务的运行与法律要求处理，服务商及备份记录遵循其适用的保留与删除政策。删除本机数据不会自动向所有在线服务提交删除请求。Firebase说明Crashlytics堆栈及关联标识保留90天后开始从在线与备份系统移除；这只是Crashlytics范围的规则，不是整个应用的数据删除期限。Firebase保留说明。
您可通过 hnzmdlcw@163.com 咨询个人信息或请求删除；我们可能需要合理必要的信息以验证请求、定位记录。我们会在身份验证后 10个工作日内回复；这是回复期限，不等于所有第三方和备份均在该期限内删除。首次联系请勿附无关截图、支付凭据或敏感屏幕内容。
服务商说明可参阅英文正文中的Firebase、Analytics、GMA、ML Kit链接及当前配置的OCR/翻译、中介政策。本政策自2026年10月17日起生效；数据处理实践发生实质变化时更新政策。