Privacy Policy

TimeComments Chrome Extension is developed and maintained by:
Bojan Mirić
Contact email: bo.miric@gmail.com
Country: Serbia

SHORT VERSION:
(1) Email address is being used to grant access to privileged resources contained in the paid version.
(2) There is no recording of YouTube watch history per user.
(3) Bookmarks, saved comments are stored locally and may be synchronized with the Extensions backend.
(4) AI chat history is stored locally and can be deleted by the user.
(5) When you add AI provider details (API Keys), chat messages go directly to the selected provider, not via the Extensions backend.
END OF SHORT VERSION.

Privacy while browsing the internet is important.
Privacy while browsing the internet AND using chrome extensions: double that.

The Purpose of this Privacy Policy is to go into specific details about how the features of the Product described in Chrome Web Store as "TimeComments" Chrome Extension are being delivered (In further text referred to as "The Extension"). That is, what exactly the code is doing on behalf of the user, in terms of any topic that may cause privacy related concerns.

The email address associated with the user’s Chrome profile is obtained through Chrome’s identity system and is used solely for identification and access control. Upon installation and first use, this email address may be securely transmitted to the Backend in order to generate a unique internal user ID. "The Backend" referes to the Google's App Engine, on which the backend of this project is running. If you are not logged in (in Chrome Web Browser), the email address will be sent when you log in. The Backend generates and responds with an ID, stored locally and used instead of the email address to represent the user in every subsequent request. This ID is a unique collection of numbers, letters and special characters without any inherent meaning. The ID and its associated email are used primarily to authorize the use of privileged resources that are associated exclusively with the paid version of the Product. It is also used to prevent abuse of the free resources. Email may be used to communicate major changes in the product, like new features and important bug fixes. The email address is not sold, shared with third parties, or used for advertising purposes.

The Extension is active only when the user begins watching a video on YouTube.
When the user arrives on a new video page, it picks up single piece of information: video id, and along with the, above mentioned, user id sends a request for the comments that contain timestamps.
When the payload is received, it modifies the page in minimal way necessary to complete its mission.

While delivering on a features promised in Extension's Store description, locally the Extension, reads only from the YouTube page what is minimally necessary to complete its task.
Now, the main takeaway of this Privacy Policy:
The Extension does not collect and/or record any information about the user's YouTube watch history. Neither locally, nor at the Extension Backend side of the TimeComments Project.

The Backend may generate aggregated statistics about how the Extensions features are used across all users. These statistics do not include individual watch history and cannot identify a specific user.

Bookmarks, saved comments, and related caption excerpts are stored locally and may be synchronized with the Extensions backend.

AI chat sends the users prompt and selected context—such as bookmarks, captions, and conversation history-to the chosen AI provider. That providers privacy policy applies.

User-provided API keys are stored only in the browser and sent directly to the selected AI provider, not to the Extensions backend.

AI chat history is stored locally and can be deleted by the user.

The Extension does not sell personal information. Information is shared with third-party AI providers only when the user chooses to use those services.
No reports or analytics are sent to any third party.

If no activity associated with a user account is detected for 30 consecutive days, the associated backend data may be scheduled for deletion.

Users may request access to or deletion of their associated backend data at any time by contacting the email listed in this Privacy Policy.