1. Introduction

Oplog ("we", "our", "the extension") is a Chrome browser extension that helps users log and replay their AI workflow operations across supported platforms. This Privacy Policy explains what data we collect, how we use it, and the choices you have.

2. Data We Collect

When you activate a logging session, the extension captures the following on supported AI platforms and any websites you explicitly enable:

Data Type	What Is Captured
AI Prompts	The text of prompts you submit to AI platforms
Clipboard Activity	Text you copy from or paste into AI chat pages
File Uploads	File name, size, and type of files you upload to AI platforms. The file itself is uploaded to Cloudinary (see Section 5).
Downloads	File name and URL of assets you download from AI platforms. The file itself is uploaded to Cloudinary (see Section 5).
Session Metadata	Timestamps, platform name (e.g. "claude", "chatgpt"), and a session identifier
Authentication	Your email address and an authentication token, stored locally in your browser

Monitored Sites

The extension has built-in support for these AI platforms:

• claude.ai
• chatgpt.com
• gemini.google.com
• grok.com / grok.x.ai
• imageprompt.org

Additionally, you can explicitly enable recording on any other website via the extension popup. Custom sites are only monitored after you click "Enable on this site" — the extension never automatically records on sites you haven't activated.

3. How We Use Your Data

• Workflow Logging: Events are recorded to create a timeline of your AI interactions within a session.
• Pipeline Generation: Recorded sessions can be converted into reusable step-by-step pipelines via the Oplog web dashboard.
• Asset Previews: Uploaded and downloaded files are stored on Cloudinary so they can be previewed in the timeline and pipelines.

We do not use your data for advertising, analytics profiling, or sale to third parties.

4. Data Storage

Local Browser Storage

The extension stores your authentication token, current session state, list of user-activated custom sites, and a temporary event buffer in chrome.storage.local. This data remains on your device and is cleared when you log out.

Backend Server

Recorded events are transmitted to the backend server you configure during setup. The backend stores sessions and events in a MongoDB database. You retain full control over your backend deployment and its data.

5. Third-Party Services

Cloudinary

Files you upload to or download from AI platforms during a logging session are sent to Cloudinary, a cloud-based media management service, for storage and preview purposes. Cloudinary receives:

• The file content (images, documents, or other assets)
• A generated public identifier for the file

Cloudinary's use of your data is governed by their Privacy Policy. No other third-party services receive your data.

6. Browser Permissions

The extension requests the following Chrome permissions:

Permission	Why It's Needed
storage	Store authentication tokens and buffer events locally
downloads	Detect when you download assets from AI platforms
activeTab	Identify which tab is active and enable dynamic script injection on user-activated custom sites
scripting	Dynamically inject content scripts into user-activated custom sites and extract generated images (e.g. from Gemini) for upload to Cloudinary
Host access	Content scripts auto-inject on built-in AI platforms and api.cloudinary.com. Custom sites are injected on-demand via activeTab + scripting only when you enable them.

7. Your Choices & Controls

• Opt-in recording: Data is only collected when you press "Start Logging". You can stop at any time.
• Custom site control: Recording on non-built-in websites requires you to explicitly click "Enable on this site". You can disable it at any time from the popup.
• Delete sessions: You can delete any recorded session and its events from the Oplog web dashboard.
• Log out: Logging out clears your authentication token and session data from the browser.
• Uninstall: Removing the extension stops all data collection and clears local storage.

8. Data Security

We take reasonable measures to protect your data:

• All communication with the backend server and Cloudinary uses HTTPS encryption.
• API authentication uses JWT (JSON Web Tokens) with expiration.
• Sensitive credentials (e.g. .env files) are never included in source code or repositories.

However, no method of electronic transmission or storage is 100% secure. We cannot guarantee absolute security of your data.

9. Data Retention

Recorded sessions and events are stored on the backend server until you choose to delete them via the web dashboard. Files uploaded to Cloudinary are retained until manually removed. Local browser data is cleared upon logout or extension removal.

10. Children's Privacy

Oplog is not intended for use by individuals under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal data, please contact us so we can take appropriate action.

11. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated effective date. Continued use of the extension after changes constitutes acceptance of the revised policy.

12. Contact

If you have questions or concerns about this Privacy Policy or your data, please contact us at:

Email: gauravkrvbzi@gmail.com
GitHub: github.com/GauravKrv