Privacy Policy — Browser Extensions

Last updated: October 26, 2026
Developer: Hirme Labs
Website: https://www.hirme.org/
Privacy contact: info@hirme.org

1. Scope

This Privacy Policy explains how Hirme Labs ("Hirme Labs," "we," "us," or "our") handles information through the following browser extensions (collectively, the "Extensions"):

• Gemini Chat Exporter — exports conversations from Google Gemini and Google Search AI Mode.
• Claude Chat Exporter — exports conversations from Claude.
• ChatGPT Chat Exporter / GPT Chat Report — exports conversations from ChatGPT.
• Grok Chat Exporter — exports conversations from Grok.
• Copilot Chat Exporter — exports conversations from Microsoft Copilot.

The Extensions are independent tools developed by Hirme Labs. They are not official products of, or endorsed by, Google, Anthropic, OpenAI, xAI, or Microsoft. This policy applies to the Extensions' functionality, not to the independent privacy practices of the AI platforms or to unrelated services on the Hirme Labs website.

2. What the Extensions do

The Extensions help you turn supported AI conversations into PDF and Markdown (.md) files. Depending on the platform and conversation, an export may include questions and answers, images, attachments or attachment references, tables, links, code, mathematical expressions, and diagrams. You can also choose report and interface settings, such as document name, theme, page size, margins, orientation, and scale.

The Extensions access information on their respective supported AI websites for this user-facing export purpose. In certain supported modes, especially temporary or private conversations, an Extension may observe relevant page requests, responses, or streaming messages while the supported site is in use so that those messages are available if you choose to export. This processing may begin before you click the export button. The Extensions are not designed to monitor unrelated browsing activity.

3. Information processed

To provide the features above, the Extensions may process:

1. Conversation and website content: prompts, replies, conversation titles, message order, hyperlinks, rendered page elements, tables, code, mathematical content, diagrams, and image or attachment data needed for the report. Conversations can contain personal or sensitive information that you or the AI service included in them.
2. Conversation identifiers and technical metadata: conversation or project IDs, share links, resource URLs, request/response metadata, and temporary-session identifiers necessary to find and reconstruct the correct content.
3. Authentication and session information, where required: the Extensions can rely on your existing signed-in browser session. Certain platform integrations may read or use access tokens, anti-forgery (CSRF) values, session identifiers, or existing authenticated requests to retrieve the conversation or its protected media. These values are used for the relevant provider requests, not to create an account with Hirme Labs.
4. Your settings: choices such as light/dark/system theme, document title and filename, page formatting, scale, and whether supported diagrams are rendered as images or kept as code.
5. Files you choose to save: the report generated in your browser, which may include the conversation data described above.
6. Support communications: if you contact us voluntarily, we may receive the contact details and information you decide to include, such as an email address, problem description, or diagnostic attachments.

The Extensions do not require you to provide a separate Hirme Labs account to export conversations.

4. How information is used

Information is used to:

• identify and retrieve the conversation you want to export;
• reconstruct the message sequence, including supported streaming or temporary chats;
• retrieve conversation-linked media where necessary;
• format, render, and generate PDF or Markdown files;
• remember your export and appearance preferences; and
• investigate support requests that you voluntarily send to us.

We do not use conversation content for targeted advertising, data brokerage, profiling, creditworthiness assessments, or training Hirme Labs AI models.

5. Local processing, storage, and retention

Report generation is primarily performed in your browser. Based on the reviewed versions of the Extensions, the export workflow does not automatically upload the full contents of your conversations to servers operated by Hirme Labs.

The Extensions may use different kinds of browser storage:

• Chrome extension local storage: keeps configuration and appearance preferences until you change or clear them, uninstall the Extension, or the browser removes the data.
• Page session storage or in-memory caches: in certain Extensions, may hold temporarily captured conversation messages or metadata, particularly for temporary/private chats. These may persist for the life of the page or browser session, or until cleared by Extension logic or browser data controls. The exact lifetime can vary with the provider and Extension version.
• Downloaded reports: remain in the location selected by your browser or operating system until you delete them. Hirme Labs cannot delete documents stored on your device.

Some versions may produce diagnostic messages in the browser's developer console; these may include conversation information. Such local console output is not automatically sent to Hirme Labs. Review and remove sensitive information before sharing browser logs or screenshots with anyone.

6. Network requests and third parties

To retrieve a conversation or its media, an Extension may make requests to the AI service you are already using and to the service's media/CDN domains. Those requests may contain the same account/session context that your browser normally uses for that service. Depending on the content of a conversation, the Extensions may also request media from related external content hosts, such as Google-hosted resources, Microsoft/Bing-hosted resources, YouTube thumbnail hosts, or other image/attachment hosts accessible to the respective Extension.

The principal service providers involved are:

Each provider independently governs the information it receives under its own terms and privacy policy. We do not sell conversation data, disclose it to advertisers or data brokers, or intentionally transmit it to an Hirme Labs analytics or conversation-storage backend as part of the reviewed export workflows.

If you choose a link in the Extension's popup that opens the Hirme Labs website, the resulting website visit is separate from exporting a conversation. Its website-side data handling may differ from the browser Extensions' handling described here.

7. Platform-specific handling

The Extensions share the same export purpose, but their retrieval methods are not identical:

• Gemini: reads supported Gemini/AI Mode conversations and may intercept relevant streaming or request/response content for temporary chats. Temporary conversation entries may be kept in browser session storage.
• Claude: reads supported conversations through Claude pages or authenticated service requests. Temporary-chat capture may use page session storage.
• ChatGPT: may use the existing ChatGPT session, including an access token when necessary, to request conversation data or protected attachments. Temporary-chat content may be cached in page session storage.
• Grok: may use existing Grok session cookies, CSRF values, and anonymous-session identifiers to retrieve supported conversations or reconstruct private chats.
• Copilot: may use existing Microsoft/Copilot access tokens where necessary and may observe Copilot WebSocket messages to reconstruct temporary conversations; related images and attachments may come from supported Microsoft or third-party media hosts.

These methods are used only for the stated export feature and may change as providers update their services. We will update this policy when our handling practices materially change.

8. Permissions and access

Each Extension requests access to the websites, resources, and browser capabilities needed for its supported export workflow. Depending on the Extension, this may include limited host permissions, browser storage, downloading generated documents, or identifying the active tab.

Permission prompts are not a statement that Hirme Labs receives the underlying conversation content. They allow the Extension to perform the actions described in this policy in your browser and through the relevant service.

9. Our data-use commitments

We use information handled by the Extensions only to provide or improve their disclosed, user-facing export function, to maintain their security and reliability, or as required by applicable law. We do not sell user data, transfer it for personalized advertising, or use it for lending or credit decisions.

Our use of information obtained through the Extensions adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. Where Google APIs are involved, the use of information received from Google APIs will also adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

10. Security

The Extensions are designed to work with supported HTTPS services and the browser's existing session. We aim to limit access to the resources necessary for export and to avoid maintaining independent copies of conversations on Hirme Labs servers.

No software or browser storage method can guarantee absolute security. You should keep your browser updated, avoid exporting sensitive conversations on shared devices, protect downloaded files, and avoid sharing session tokens or unredacted debug logs.

11. Your choices and controls

You can:

• choose whether to install, enable, or uninstall an Extension;
• decide whether to generate or share a report;
• change or clear saved Extension preferences through Chrome's controls;
• clear the relevant website's site/session data to remove temporary captures stored by the page, subject to that site's behavior;
• delete downloaded PDF or Markdown files using your device's file manager; and
• contact us about privacy questions or information you have sent directly to our support channel.

We generally cannot access, retrieve, or delete conversation data that remains only in your browser or on your device because it is not held in an Hirme Labs conversation database.

12. Children's privacy

The Extensions are not specifically designed for children. They do not create separate Hirme Labs accounts for children or intentionally seek information about them. Use of each AI platform remains subject to that platform's age restrictions and terms.

13. International users and privacy requests

Depending on your location, applicable privacy laws may provide rights concerning personal data, including rights to request information, correction, or deletion. We will review requests involving personal information that Hirme Labs actually holds, such as information you voluntarily send for support. Because reports and temporary captures are generally stored in your own browser or device, the controls described above are typically the most direct way to manage them.

14. Changes to this policy

We may update this policy when features, supported services, data practices, or legal requirements change. The current version and its revision date will remain available at the URL shown in the Chrome Web Store listing. Material changes to data-handling practices will be disclosed through appropriate product or store notices where required.

15. Contact

For privacy questions or requests relating to these Extensions:

Hirme Labs
Email: info@hirme.org
Website: https://www.hirme.org/

When contacting us, please identify the Extension involved. Do not include passwords, access tokens, or private conversation transcripts unless you have considered the privacy implications and the information is necessary to resolve your request.