Skip to main content
Chrome extension

tSM DIS Ticket Capture Privacy Policy

This policy explains how the tSM DIS Ticket Capture extension handles information when you capture browser content and create tickets in tSM DIS.

Last updated: 29 August 2026

1. Scope and controller

This policy applies to the tSM DIS Ticket Capture Chrome extension (the “Extension”). The Extension has one purpose: to help authorized users create tSM DIS tickets from browser content, including optional screenshots, screen recordings, annotations and source links.

The controller is DataLite, spol. s r.o., Štěpánská 631/51, 110 00 Prague 1, Czech Republic, company ID 25106325 (“DataLite”, “we”, “us”). Privacy questions can be sent to info@datalite.cz.

2. Information the Extension handles

InformationHow and why it is usedStorage
DIS account information
Creator email and DIS API key		Connects the Extension to DIS, identifies the ticket creator and authorizes the requested DIS operations.Saved in Chrome extension local storage in the user’s browser profile. A short-lived DIS access token is kept in memory only.
DIS directory and catalogue data
User names, emails, codes, IDs and status; projects, ticket types and priorities		Loaded from DIS so the user can select an active assignee and valid ticket values.Used in the active Extension session; not sent to a separate Extension backend.
Ticket content
Title, rich-text description, assignee, project, type, priority, versions and environment		Used only to validate and create the ticket requested by the user.Kept in the editor until submitted; after submission it is retained in DIS.
Page and media content
Selected source URLs and titles, screenshots, uploaded images or videos, screen recordings and annotations		Added to a ticket only when the user captures, uploads or includes the content. Screen video is recorded without audio.Draft media is processed locally in the browser. Submitted media is stored in DIS as a private ticket attachment.
Preferences
Theme, defaults, environments, shortcuts, sidebar state, annotation settings and dictation language		Remembers the user’s Extension configuration.Saved in Chrome extension local storage.

The Extension does not passively monitor browsing history. It reads the current page title or URL and captures visible content only after a user invokes a capture function. Each captured source URL has its own inclusion control, and the default can be changed in Settings.

3. Where information goes

tSM DIS

Account requests, directory lookups, ticket data and submitted attachments are transmitted over HTTPS to the configured tSM DIS server. The default server is tsm-dis.datalite.cloud.

Microsoft Teams

If the user chooses “Share to Teams”, the Extension opens a Microsoft Teams deep link containing the selected recipient email, ticket title and link, and optionally the description. Microsoft then handles that information under its own terms and privacy policy. Nothing is shared to Teams without this user action.

Browser speech service

Dictation is optional and uses the speech-recognition service supplied by the browser. Depending on the browser, microphone audio may be processed by the browser vendor’s online service. The Extension does not retain or send raw dictation audio to DataLite; it receives the resulting transcript for insertion into the draft.

The Extension does not sell user data, use it for advertising, use it to determine creditworthiness, or send Extension usage telemetry to a separate analytics or advertising service. We disclose information only as described above, when required by law, or when necessary to investigate security or abuse with appropriate safeguards.

4. Why Chrome permissions are needed

  • Active tab: reads the active page title and URL and captures the visible page after the user starts the Extension.
  • Scripting and optional site access: displays the user-controlled area-selection overlay on a page. Optional access is requested only when needed for capture on that site; it is not used for background tracking.
  • Storage: keeps the DIS connection settings and user preferences listed above, plus a temporary capture draft for the active session.
  • Access to the configured DIS host: signs in, loads valid ticket data, creates tickets and uploads attachments through the DIS API.
  • Screen and microphone selection: is initiated only by the user for optional video capture or dictation and remains subject to the browser’s permission UI.

5. Retention, security and deletion

  • Local settings, including the API key, remain in the Chrome profile until the user changes or clears them, clears the Extension’s site data, or uninstalls the Extension.
  • A capture draft is held only for the active editor/browser session unless it is submitted to DIS. Closing the editor without creating a ticket does not upload the draft to DIS.
  • Created tickets and attachments are retained and deleted according to the retention, access-control and audit rules of the organization operating the configured DIS system.

Data sent by the Extension is transmitted using HTTPS. Authentication information is used only for the requested DIS operations and is not included in ticket content or shared with Microsoft Teams. Users should protect their Chrome profile and revoke a DIS API key if they believe it has been exposed.

6. Your choices and rights

The user controls whether to:

  • include each captured source URL in a ticket;
  • capture, upload, annotate, insert or remove media before submission;
  • start screen recording or dictation;
  • create the ticket in DIS; and
  • open a pre-filled share in Microsoft Teams.

Subject to applicable law, individuals may request access, correction, restriction or deletion of their personal data, object to processing, request portability, or lodge a complaint with the Czech Office for Personal Data Protection. Contact info@datalite.cz to exercise these rights.

7. Chrome Web Store Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

8. Changes to this policy

We may update this policy when the Extension’s functionality, data handling or legal requirements change. The current version and its update date will always be published on this page.