PhotoZ Privacy Policy
WORKING DRAFT — PhotoZ is an independent browser extension developed by TSoft to help you browse and manage Google Photos. This policy explains the information PhotoZ accesses, how the extension uses and stores it, and the role of the TSoft authentication service. This document is under final publisher review; backend retention, deletion procedures, and a public privacy contact must be confirmed before publication.
Last reviewed: 2026-10-30
1. Who we are and the scope of this policy
PhotoZ is developed by TSoft and is not affiliated with, sponsored by, or endorsed by Google LLC. The official product website is https://browserextension.tsoftvn.win/photoz/.
This policy describes information processed by the PhotoZ browser extension and its associated TSoft authentication service. Google services operate under their own applicable terms and privacy policies.
2. Information used for PhotoZ sign-in
PhotoZ offers a separate Google sign-in for the PhotoZ application. After you authorize sign-in, it may use your Google Account identifier, email address, display name, and profile picture to identify and display your signed-in account.
The extension sends the Google OAuth authorization code, PKCE code verifier, and redirect URI over HTTPS to https://api.tsoftvn.win/api/auth/google/exchange to complete the authentication exchange. The service can return account information and a PhotoZ session token.
PhotoZ stores its account information and, when issued, its application session token in the browser extension's local storage. This PhotoZ application sign-in is separate from your existing Google Photos browser session.
Information retained on the TSoft authentication backend, relevant service providers, logging practices, and deletion periods still require confirmation before this draft is made final.
3. Google Photos and media information
When you use PhotoZ features, the extension may access media identifiers; file names; image or video types; media dates; sizes and dimensions; thumbnails; media URLs; album data; Favorites and Archive status; Trash records; and media details needed for the selected operations.
PhotoZ accesses Google Photos in the context of your active browser session. Features can scan or refresh library information, load media details, browse albums, manage Favorites and Archive, manage selected items, and resolve media for preview or download.
Some features, including scanning or automatic detail loading, may run after you enable or initiate them in the application. Google Photos content is processed to provide the related PhotoZ features, not to create advertising profiles.
Google Photos data and any Google Photos Picker data are subject to the access permissions and controls provided by Google. Google Photos Picker access uses the read-only Photo Picker scope when that feature is used.
4. Browser cookies and sessions
PhotoZ uses the existing Google Photos browser session to make requests needed to carry out its media-management features. Its cookies permission allows access to Google-related cookies when required for those operations.
The extension source also retains local code for capturing and restoring Google cookie snapshots associated with an earlier multi-profile design. This functionality may be present in existing installations or stored legacy profile data even though the current user interface focuses on one account.
PhotoZ does not require you to enter your Google Account password into the extension. Signing out of PhotoZ does not sign you out of Google Photos in the browser.
5. Local storage, cached metadata, and downloads
PhotoZ uses chrome.storage.local to maintain scanned library records, media metadata, albums, Favorites, Archive, Trash metadata, app settings, and authentication state. Certain legacy profile records may also be stored locally.
PhotoZ may request media content from Google-controlled domains for previews and downloads. Downloaded files are delivered using browser download workflows or other local device operations supported by the extension.
The extension's local storage is not presented as an independently encrypted vault. Security of locally stored information also depends on the browser, device, and operating-system security.
6. How PhotoZ uses information
PhotoZ uses account information to authenticate and display the current user; Google Photos information to show and manage requested media; locally cached data to reduce repeated scanning and improve responsiveness; and settings to provide the chosen application behavior.
Operations such as changing Favorites or Archive status, managing albums, and processing selected media are intended to act on content in the Google Photos account associated with the current browser session.
The extension does not include a feature that automatically uploads your entire Google Photos library to the TSoft authentication endpoint. Whether the server maintains diagnostic logs or other account records must be verified separately.
7. Services involved and sharing
Google services receive requests related to Google authentication, Google Photos operations, Google Photos Picker where used, and media delivery.
TSoft's authentication endpoint at api.tsoftvn.win receives information necessary for the PhotoZ sign-in exchange. TSoft may use infrastructure providers to operate that endpoint, subject to the verified production configuration.
The PhotoZ extension is not designed to sell Google Photos data, share it with data brokers, or use it for targeted advertising. This statement and any commitments for the associated production backend must be approved by the publisher before this draft is finalized.
PhotoZ may need to comply with applicable legal obligations. The exact handling of such requests depends on applicable law and the publisher's practices.
8. Browser permissions
PhotoZ requests storage and unlimitedStorage to maintain local records and settings; cookies to work with the authenticated Google Photos browser session; tabs and scripting to interact with supported Google Photos pages; identity to perform Google sign-in; and clipboardWrite for copy operations initiated by the user.
The extension also requests access to Google Photos, relevant Google media domains, Google Photos Picker, and the TSoft authentication API. These host permissions support requests necessary for the extension's disclosed functionality.
The extension should request only permissions needed by its current functionality. Permissions and remaining legacy code should be reviewed before Chrome Web Store publication.
9. Data retention, Clear Data, and Sign Out
Locally cached media information remains in extension storage until it is cleared, replaced, or otherwise removed by the browser or extension. PhotoZ's Clear Data function clears the media caches for the current profile without deleting the photos or videos in your Google Photos account.
Clear Data does not necessarily remove PhotoZ account sign-in state, application settings, or every legacy profile record. PhotoZ Sign Out removes the active PhotoZ account and application session token from local storage but does not necessarily remove cached media information.
Uninstalling the extension may remove its locally stored extension data according to the browser's behavior. For deletion of account-related data handled by the TSoft backend, contact the publisher using the verified privacy contact shown on this page once provided.
The production backend's data retention periods and the procedure for deleting account data still require verification before publication.
10. Security
PhotoZ uses HTTPS when communicating with the Google and TSoft HTTPS endpoints configured in the extension. Google OAuth sign-in uses PKCE as part of the authorization flow.
Protect your browser profile and device against unauthorized access. No method of electronic transmission or storage can guarantee absolute security.
11. Google user data and Limited Use
PhotoZ accesses Google user data only for the relevant disclosed user-facing features and within the permissions granted for the applicable Google sign-in or Google Photos service.
Any use and transfer of information received from Google APIs must comply with the applicable Google API Services User Data Policy, including its Limited Use requirements, and with the Chrome Web Store User Data Policy. The publisher must verify that the production extension and backend meet those requirements before approving this policy.
12. Children and changes to this policy
PhotoZ is a general-purpose Google Photos management utility and is not designed specifically for children.
We may revise this policy to reflect changes in PhotoZ functionality, services, or applicable requirements. Any published revision will show an updated date on this page. Where required, we will provide notice or obtain consent for materially different processing.