Effective date: 29.10.26
Extension owner: Artur Joldasbayev
Contact for questions: artmenist@gmail.com

Privacy Policy
for the “Tissent” Extension
This Privacy Policy describes what data the Tissent extension processes, what purposes the data is used for, where it is stored, and how it is protected.

1. About Tissent
Tissent (formerly Ticket Assistant Manager) is a Google Chrome extension and related editor designed to help customer-support agents work with tickets and customer-service platforms. Its features include template and trigger matching, text insertion and translation, ticket archiving, notes, tasks, knowledge articles, decision flows, clipboard tools, and optional AI assistance.

This policy explains what information Tissent can access or process, why it is used, when information is stored locally or in cloud services, and when information may be sent to external providers. The data processed depends on the websites, workspaces, permissions, settings, and features the user chooses to use.

Important: Support tickets and account-management pages may contain personal, financial, licensing, or otherwise confidential customer information. Users should use Tissent only where they are authorized to access and process that information, including through any connected AI or translation provider.

2. Information Tissent May Process
Depending on the settings and usage scenario, the extension may process the following categories of data:

2.1. Ticket and website content
When Tissent is used on a supported or explicitly authorized website, it may read information needed for the active feature, such as:
  • ticket subjects, messages, conversation history, internal notes, message authors, and timestamps;
  • customer names, email addresses, ticket IDs, URLs, tags, custom fields, and attachment names or other visible ticket metadata;
  • text selected or picked from a page, and content extracted from user-configured page elements;
  • support-administration information displayed on relevant pages, which may include purchases, subscriptions, transaction references, payment amounts, product names, license or activation keys, and download links;
  • the current page's URL and navigation information, to recognize supported platforms, detect ticket changes, or operate the relevant page helper.
Depending on the feature, Tissent may process the active ticket automatically (for example, to match triggers or translate ticket text when automatic translation is enabled) or in response to the user's actions (for example, archiving a ticket or selecting text for an AI tool). Tissent is not intended to create a general browsing-history database.

2.2. User accounts and authentication
For registration, sign-in, authorization, access control, and synchronization, Tissent may process an agent's email address, user ID, authentication/session tokens, account role, activation status, and registration-related information. Certain restricted features also check the email domain of the agent currently signed in to a supported helpdesk.

2.3. User-created work data
Tissent may process templates and rich-text content, template images, folders, keywords, triggers, manual intent rules, decision flows, links, imported knowledge articles, notes, tasks, schedules, reminders, ticket counters, workspace preferences, saved prompts, AI memories or skills, and other settings. Personal and team content may be synchronized when the corresponding cloud workspace is used.

2.4. Ticket archives and case context
When a user imports or archives tickets, Tissent may retain ticket messages, customer and agent details, ticket fields, dates, links, attachments metadata, annotations, and other information included in the archive. Case-workflow features may also save selected ticket messages, account or purchase information, diagnostic facts, and progress for individual tickets.
Ticket archives are stored locally in the active extension interface. Archiving or exporting a ticket is distinct from sending that ticket to an AI provider; however, the user can choose to include archived or current ticket information in a model request.

2.5. Clipboard information
Tissent can write text, formatted templates, and images to the clipboard to carry out a user's copy or insertion action. Clipboard-history monitoring is optional and disabled by default. If the user enables it and grants Chrome's clipboard-read permission, Tissent may read and retain copied text in a local clipboard history, subject to the configured history limit, retention, and deletion controls. This may include sensitive text copied from applications outside Tissent.

2.6. Local images, files, and attachments
If the user connects an image folder, Tissent stores a reference to the selected folder and reads its image files on demand for browsing, previewing, or copying. Connecting the folder does not, by itself, upload its images to Firebase or an AI provider. Image content inserted into a template may later become part of a template export or cloud-synchronized template.
Files, images, or text that the user explicitly attaches to an AI request may be processed by the selected model provider or configured endpoint. Files exported or downloaded by the user are saved outside Tissent's managed extension storage.

2.7. AI requests and technical information
Depending on the selected tools, Tissent may process prompts, conversation messages, answers, attached files, selected ticket context, model settings, provider API keys, AI chat history, request identifiers, and usage information. For diagnostics and troubleshooting, the extension may also store error information, timestamps, feature status, synchronization state, and technical logs, particularly when logging is enabled.


3. How Information Is Used
Information is used to provide and maintain customer-support assistance, including:
  • identifying the current ticket and matching templates, triggers, keywords, and intents;
  • inserting or copying prepared replies and preserving their formatting;
  • translating or editing text and generating AI-assisted responses when a relevant feature is used;
  • storing and searching user-selected ticket archives, notes, articles, and other work materials;
  • operating decision flows, case context, links, reminders, and ticket counters;
  • authenticating users, enforcing access permissions, and synchronizing personal or team workspaces;
  • performing backups, imports, exports, troubleshooting, and security or reliability checks.
Tissent does not sell customer or agent information, and it does not use information obtained through the extension for personalized advertising or marketing by data brokers. Tissent’s use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

4. Where Information Is Stored

4.1. Local storage in the browser
Tissent uses Chrome extension storage, IndexedDB, and in some cases browser local storage to retain settings and work data. Locally held information may include templates and cached cloud content, notes, tasks, clipboard history, ticket archives, case sessions, prompts, model settings, API keys, diagnostics, and references to user-selected image folders. Some browser-stored secrets are not separately encrypted by Tissent; access to the browser profile and device should therefore be protected.
A local-only mode is available for supported workflows without access to Tissent cloud workspaces. Choosing local-only mode does not by itself guarantee that an external website, translation feature, or user-configured model endpoint will never receive data; those operations depend on which functions are used and enabled.

4.2. Firebase cloud services
Tissent uses Google Firebase services, including Authentication, Firestore, Storage, and Cloud Functions. Depending on the workspace and feature, Firebase may hold agent accounts, roles and status, team and personal templates, flows, links, articles, knowledge content and associated images, synchronization metadata, versions, and server-side operational records.
When authenticated OpenAI chat is used, Tissent's backend also stores the relevant chat, request, message, context, and usage state. A user's OpenAI API key for this authenticated service is stored in a server-only record; it is not returned to the browser as a readable key by the key-management feature.
Data placed in a team workspace may be available to other authorized members of that team. Content labels such as “public” or “private” within a shared Articles workspace should not be treated as independent access controls for the entire cloud document.

4.3. Backups and exports
The user can export or import Tissent backup files, tickets, templates, notes, or other content. Backup files may contain substantive customer-support and work data. Clipboard history is included in the global backup only if the user selects that option. The backup mechanism is designed to exclude stored API keys and authentication secrets, but exported work content can still be confidential. Users are responsible for choosing a safe location and recipients for exported files.

5. External Services and Data Transfers

External services receive data only when required for a feature that is used or enabled. The information sent depends on the feature and may include customer-support content. The main integrations are:

Service

When it is used

Information that may be transferred

Google Firebase

Account registration/sign-in, authentication, cloud storage, synchronization, and backend functions

Account details, workspace content, service requests, and operational data as described above

OpenAI

When an authenticated OpenAI AI feature is selected

Prompts, user-selected or configured ticket/case context, conversation content, and supported attachments, via Tissent's Firebase backend

Google Translate (translate.googleapis.com)

When automatic, hover, or manually requested Google translation is enabled or used

Text to be translated, which may include ticket messages

Google Gemini API

When a Gemini-powered text or translation tool is selected

Text, prompts, and relevant request content sent using a user-supplied API key

TypeSafe / JEV

When JEV questions, decision assistance, or optional semantic template ranking is requested/enabled

Anonymized selected ticket text, case context, questions, and/or template-related content needed for the request

Ollama or a user-configured OpenAI-compatible endpoint

When a local-model or custom-endpoint feature is selected

The prompt, enabled context sources, and user-attached content directly to the configured endpoint; an endpoint outside the user's device may be operated by a third party


For TypeSafe/JEV requests, Tissent applies its local personal-information anonymizer before sending relevant content; some operations are skipped if the anonymizer is unavailable. Other export and AI tools may offer an anonymization option. Anonymization is not guaranteed to identify or remove every personal or sensitive detail. The user should review the content and the chosen provider before sending confidential information.
The user may also direct Tissent to fetch a knowledge article from a website or to interact with a configured helpdesk or account platform. Such requests contact the corresponding site as necessary for the selected function.
A Tidio/Lyro integration exists in the code as a disabled experimental feature; it is not available as an active user-facing feature in the documented version. If activated in a future release, the disclosure will need to be updated to describe its data transfers. The current deterministic Tissent Bot technical-manual assistant does not send its question to an AI model, although it can read its knowledge from a permitted Firebase workspace.
External providers process data under their own terms and privacy practices. Tissent does not control the provider's independent retention or processing rules.
6. Access to Websites and Browser Permissions

Tissent is designed for supported helpdesk and support-administration pages, including Usedesk, Freshdesk, and supported Movavi support pages. Users can additionally configure other work-platform domains and, where Chrome permits, local HTML files. For these additional locations, the extension requests the applicable website-access permission before enabling relevant page features.

Depending on the enabled functions, Tissent uses Chrome permissions for page inspection and script injection, tab navigation, local storage, context menus, notifications and scheduling, clipboard writes, and optional clipboard reads. Access to a user-chosen local image folder is requested separately through the browser's file/directory picker.

Tissent does not need to read unrelated webpages in order to maintain a general log of browsing activity. Reading content on a supported or user-authorized page is limited to operating the extension's disclosed functionality.

7. Security and Data Minimization
Tissent uses Firebase authentication and access controls for cloud workspaces, separates local, personal and team data, and uses backend validation and security rules to restrict cloud operations. Template content is sanitized before certain rich-text insertion and clipboard operations. The extension includes tools to remove or replace identifying details before selected exports or third-party AI requests.
Security limitations are important:
  • Local extension data, including certain provider keys and saved content, is protected primarily by the security of the browser profile and device; Tissent does not provide separate application-level encryption for all such information.
  • Tissent's server-side storage of an OpenAI key relies on backend access controls and platform protections; the documented implementation does not add separate application-level encryption to that record.
  • Team members with the relevant permissions can access shared team-workspace data.
  • No anonymization, storage, or transmission method can guarantee absolute confidentiality or security.
Users should avoid including unnecessary personal data or secrets in templates, notes, shared workspaces, archives, backups, and AI prompts.

8. Retention, Deletion, and User Controls
Locally stored information remains available until it is cleared, deleted through Tissent's controls, removed with the extension/browser profile, or subject to a feature-specific retention policy. Clipboard-history retention and maximum-entry controls can be configured. The template-image store also has automatic cleanup for images no longer referenced by saved content. Ticket archives and saved case sessions can be deleted using their respective controls.

Signing out stops access to an authenticated cloud session and clears certain local cloud caches; signing out does not automatically delete the user's Firebase account, cloud documents, server-side AI records, or separately exported files. Removing the extension does not delete copies stored in cloud services, other browser profiles, or backups that the user has created. Server-side versions, operational/audit records, and provider-held information may follow separate retention requirements.

Users can manage available data through Tissent's relevant delete, reset, disconnect, and export controls, or request assistance with data associated with their Tissent account at artmenist@gmail.com. Tissent does not currently publish a single universal fixed retention period for every category of data.

9. Privacy Rights and Requests
Users may contact the extension owner to request information about personal data associated with their account, correction of inaccurate data, deletion where applicable, or deactivation of their account. Requests are handled subject to applicable law, technical limitations, and the rights of other people whose data may appear in shared business records.
For privacy questions or data requests, contact artmenist@gmail.com.

10. Children's Privacy
Tissent is intended for professional customer-support workflows, not for children. It is not designed to solicit personal information directly from children. Customer-support content may nevertheless contain information about individuals of different ages and must be handled in accordance with the user's authorization and applicable rules.

11. Changes to This Policy

This policy may be updated when Tissent's features, integrations, data practices, or applicable requirements change. Material changes to user-data practices should also be clearly disclosed to users through appropriate product or Chrome Web Store notices. The current published policy is available at:
https://ajoldasbayev.tilda.ws/privacy_policy

12. Contact
Artur Joldasbayev
Email: artmenist@gmail.com

This site was made on Tilda — a website builder that helps to create a website without any code
Create a website