LoginFlip Privacy Policy

Data processed on your device

To save and switch website login states, LoginFlip processes applicable cookies, localStorage for the current full website origin, the active tab URL, account names, and website aliases. This data may include sensitive credentials capable of signing in to an account.

LoginFlip has no service account, developer server, cloud sync, telemetry, advertising, or third-party analytics SDK. Account data is not uploaded, sold, or shared with the developer or third parties. Websites still receive their own applicable cookies when Chrome opens or refreshes them; LoginFlip is not an anonymity tool.

Why permissions are required

cookies: capture, clear, and restore applicable regular and current same-site partitioned cookies.
storage: keep accounts, preferences, workflow state, and limited recovery data locally. LoginFlip does not use storage.sync.
tabs: identify the current website, associate tabs, open websites, reload pages, and activate linked tabs.
scripting: read and restore localStorage on an accessible page after checking its origin.
http://*/* and https://*/*: support ordinary websites selected by the user and their applicable parent-domain cookies. LoginFlip does not automatically capture every visited website.

Storage, retention, backup, and deletion

Saved accounts, names, aliases, and preferences remain in Chrome extension local storage until the user deletes them or uninstalls LoginFlip. At most one previous snapshot per account and one failed-switch recovery record are retained and cleaned after 24 hours on a later initialization or write. Temporary workflows and tab associations use session storage and may disappear earlier.

Incognito and regular cookie stores are separate, but an account explicitly saved from an incognito window remains in extension local storage after the window closes. Exported backups are downloaded to a location chosen by the user. Encrypted backups are recommended; the passphrase is used locally for that operation and is not stored or uploaded. A plain JSON backup may contain usable login credentials.

Users can delete one account, all accounts for a website, previous snapshots, or failure-recovery data from LoginFlip. Deleting local data does not sign out or revoke the server-side account; use the website’s own security controls when revocation is required.

Publisher, compliance, and contact

Publisher: qingtan (individual developer, non-trader). Privacy contact: xinning000@gmail.com.

LoginFlip’s use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. LoginFlip does not sell user data or use it for advertising, credit decisions, or purposes unrelated to its single purpose, and it does not transfer login snapshots to third parties or developer-operated servers.

本机处理的数据

LoginFlip 为保存和切换网站登录状态，在使用相关功能时读取适用网站的 Cookie、当前完整网站地址的 localStorage、标签页 URL，以及用户填写的账号名称与网站别名。这些内容可能含有足以直接登录账号的敏感凭据。

当前版本没有自有服务器、不使用遥测、不集成第三方分析 SDK、不出售或向开发者上传账号数据。扩展代码不主动发送分析或同步请求。打开、刷新网站时，浏览器仍按该网站的规则联网并发送适用 Cookie；这不是匿名浏览工具。

权限用途

cookies：读取、清除和恢复适用网站的 Cookie，包括普通 Cookie、无痕 Cookie Store，以及当前顶层网站同站上下文的分区 Cookie。
storage：在本机保存账号、设置、流程与有限恢复数据；不使用 storage.sync。
tabs：识别网站、关联标签页、打开网站、刷新和切换标签页。
scripting：在核对网页 origin 后读取和恢复 localStorage。
http://*/* 与 https://*/*：支持用户选定的普通网站及其适用父域 Cookie。该权限不意味着自动保存所有访问网站。

保存期限、备份与删除

当前账号快照、名称、别名与设置保存在 Chrome 扩展本地存储中，直到用户删除或卸载。每个账号最多保留一份上一快照，切换失败恢复记录最多一份；这些记录会在 24 小时后于后续初始化或写入时清理。临时流程和标签关联使用会话存储，可能更早消失。

普通窗口与无痕窗口的 Cookie Store 相互独立，但用户在无痕窗口主动保存的账号仍保留在扩展本地存储中。导出备份保存到用户选择的位置。推荐使用加密备份；口令只在本机本次操作中使用，不保存、不上传。明文 JSON 可能含有可直接登录的凭据。

用户可以在 LoginFlip 中删除单个账号、网站全部账号、上一快照或失败恢复数据。删除本地数据不等于退出网站或撤销服务端会话；需要撤销时请使用网站自身的安全功能。

发布者、合规与联系

发布者：qingtan（个人开发者，非交易者）。隐私联系邮箱：xinning000@gmail.com。

LoginFlip 对从 Chrome API 获得的信息的使用符合 Chrome Web Store User Data Policy，包括 Limited Use 要求。LoginFlip 不出售用户数据，不将其用于广告、信用评估或与扩展单一用途无关的目的，也不向第三方或开发者服务器传输登录快照。