GlossAI Legal & Trust Repository

Screen Privacy Disclosures

Complete disclosures regarding when, why, and how GlossAI accesses screen information.

Effective / Last Updated: October 31, 2026•Canonical: glossai.app
Review Notice: This document contains legal placeholders (highlighted in badge tags) that require your final operational confirmation or legal counsel sign-off before official publication.

1. Why GlossAI Uses Screen Access

GlossAI helps users understand and interact with information displayed on their computers without constantly switching applications. Certain features may require access to selected screen content. Examples include explaining highlighted paragraphs, solving selected mathematical problems, summarizing document text, understanding presentation content, and answering questions about user-submitted screen content.

2. When Screen Content Is Accessed

Screen content is accessed when a user activates a feature that requires it and the necessary operating-system permissions are available. Depending on the operating system and feature, this may include selected or highlighted text, images or screenshots explicitly submitted by the user, and other visual information required by an activated feature. The exact information accessed depends on the feature and permissions granted.

3. What Happens to Your Screen Content?

A typical request may involve the following steps:

  1. User activation: you activate GlossAI using a desktop shortcut or another supported interaction.
  2. Content selection: you select, highlight, or submit the information you want analyzed.
  3. Content processing: GlossAI obtains the content required for the requested operation.
  4. AI transmission: relevant content may be transmitted to GlossAI's backend and third-party AI providers to generate a response.
  5. AI response: the response is displayed through GlossAI's interface.
  6. Conversation handling: depending on settings and enabled features, the request and response may be stored in conversation history.

4. What GlossAI Does Not Need

Installing GlossAI does not, by itself, mean every document, application, or screen is continuously transmitted to AI providers. The intended interaction model is user-initiated assistance rather than unrestricted collection of screen content. The application should not collect screen information unrelated to the requested functionality. Verify actual capture triggers and background behavior before publishing this statement.

5. Background Operation

GlossAI may run in the background to support keyboard shortcuts and desktop functionality. Background operation does not automatically mean screen content is continuously captured or transmitted. Screen-related processing should occur only when the corresponding feature is activated and authorized. Confirm this behavior in both macOS and Windows builds.

6. Sensitive Information

Your screen may contain passwords and authentication codes; banking and payment information; private messages; personal documents; business and university records; and confidential work materials. Do not submit sensitive information unless you have a legitimate reason and authorization to do so.

7. Third-Party AI Processing

GlossAI may use OpenRouter and selected AI model providers to process requests. When screen content is required to answer a request, relevant content may be shared with these providers. Their data processing and retention policies may differ. Users should review relevant third-party privacy policies when using AI-powered screen features.

8. User Control

Users can manage screen-related permissions through their operating system. Users may disable screen-related permissions, stop using screen-reading features, close GlossAI, remove operating-system permissions, delete eligible saved conversation history, and request account and personal data deletion. Revoking permissions may prevent some features from working.

9. University and Workplace Environments

Users accessing university, workplace, or enterprise systems must follow applicable institutional policies. GlossAI should not be used to process confidential institutional information without appropriate authorization. Institutions may establish additional restrictions through their agreements with GlossAI.

10. Our Privacy Commitment

GlossAI aims to make screen-based AI assistance transparent and user-controlled. We will continue to improve the application to minimize unnecessary screen access, protect transmitted information, and provide clear permission controls.

11. Contact

GlossAI
For questions about screen access or privacy: [PRIVACY EMAIL](e.g. privacy@glossai.app)

Publication Checklist — Complete Before Launch

The following items are placeholders or verification tasks. Do not publish the documents until the relevant items have been completed.

1
Replace [PRIVACY EMAIL], [LEGAL CONTACT EMAIL], and [SECURITY EMAIL] with monitored addresses.
2
Identify the legal owner or registered entity and add the correct business address where appropriate.
3
Choose and obtain legal review of the governing-law jurisdiction and dispute-resolution wording.
4
Verify actual screen capture triggers, background behavior, operating-system permissions, and whether screenshots or text are captured.
5
Map all data flows: desktop app → GlossAI backend → OpenRouter → selected model provider.
6
Verify each AI provider's retention, logging, and model-training terms for the exact account/API configuration used.
7
Document actual retention periods for account data, conversations, diagnostics, security logs, and backups.
8
Verify encryption in transit and at rest, database access policies/RLS, token storage, backups, and administrative access.
9
Establish and test account deletion, data access, correction, and privacy-request workflows.
10
Review Qatar's applicable privacy law and any other laws relevant to target users and international data transfers.
11
Have qualified counsel review the final documents before publication.
© 2026 GlossAI. All rights reserved.