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.