Oathmark Support

Contact us

The fastest way to reach us is email. We typically reply within one business day.

• General support: support@oathmark.ai
• Privacy questions or data requests: privacy@oathmark.ai
• Security issues: security@oathmark.ai (see reporting a security issue below)

Mail: Oathmark, 2 S Biscayne Blvd, Suite 2600, Miami, Florida 33131.

Install the Continuous Monitoring extension

The Oathmark Continuous Monitoring extension detects when someone on a device visits a known AI tool (ChatGPT, Claude, Gemini, Copilot, and others) and reports that detection — tool name and timestamp only — to your firm's Oathmark dashboard. It never reads page content, keystrokes, or credentials.

1. Visit the extension's Chrome Web Store listing: Oathmark Continuous Monitoring.
2. Click Add to Chrome (or the equivalent button in Microsoft Edge or Brave) and confirm the install.
3. Click the Oathmark icon in the browser toolbar, then Open settings.
4. Paste the monitoring key from your Oathmark client portal (see below), enter a device label such as "Jane's laptop," then Save settings.

The extension will now report AI-tool usage on this device to your Oathmark dashboard automatically. For deployments across a fleet, see For IT administrators.

Find your monitoring key

Each Oathmark client engagement has a single monitoring key that authenticates the extension to your dashboard. Anyone with the key can register a new device to your dashboard, so treat it like a shared secret.

1. Open your Oathmark client portal at oathmark.ai/intake and sign in with your engagement link.
2. Scroll to the Continuous monitoring section.
3. Click Copy key in the "Your monitoring key" box.

If you need to rotate the key because it may have been exposed, contact support@oathmark.ai and we will regenerate it for your firm.

Uninstall the extension from a device

Go to chrome://extensions (or edge://extensions), find Oathmark Continuous Monitoring, and click Remove. This stops the extension from detecting or reporting anything from that device going forward. It does not clear the device's row from your dashboard — that row stays until removed from the dashboard, since it reflects device history, not the extension's install state.

Remove a device from your dashboard

In your Oathmark client portal (or have your admin do it from the admin panel), find the device under Connected devices and click the × next to it, then confirm. This removes the device from your dashboard and detaches it from past detections in your history — but it does not uninstall or disable the extension on that device. If the extension is still installed and later visits a monitored AI tool again, it will re-register as a "new" device on the dashboard.

To fully retire a device, do both: uninstall the extension from the device and remove its row from the dashboard.

What the extension collects (and what it doesn't)

Continuous Monitoring is deliberately narrow. It collects, per detection:

• The name of the AI tool visited (matched against a configured list of domains).
• A timestamp.
• The device label the user or admin entered during setup (or a browser-and-OS label derived from the User-Agent when none is provided).
• The extension version installed.

It does not collect page content, keystrokes, credentials, session cookies, form data, prompts, responses, screenshots, browsing history outside of the configured AI-tool domain list, or anything from tabs open on other sites. For the full disclosure, see the Privacy Policy (Section 2.10, Continuous Monitoring).

Supported browsers

The extension is a Manifest V3 Chromium extension and is supported in current versions of:

• Google Chrome (desktop)
• Microsoft Edge (desktop)
• Brave (desktop)

Firefox and Safari are not currently supported. For those browsers, tool usage will not be reported to the dashboard; the engagement report will note the limitation.

For IT administrators

For firms deploying the extension across many devices at once, we recommend force-installing it via Google Workspace admin or Chrome Enterprise policy rather than asking each employee to install by hand. The extension's Chrome Web Store item ID is:

fkipggnhgkoobdhflkiglihkbibkbbhm

See Deploying Oathmark for IT administrators for the full step-by-step guide covering Google Workspace admin, Microsoft Edge (Intune / group policy), and pre-configuring the monitoring key so end users don't have to paste it themselves.

Billing & subscriptions

Oathmark uses Stripe for payments and subscriptions.

• Invoices & receipts: issued automatically by Stripe to the billing email on file after each successful payment. If you didn't receive one, check spam or email support@oathmark.ai and we will resend.
• Change payment method or billing email: email support@oathmark.ai and we will send a secure Stripe customer-portal link.
• Cancel a subscription: email support@oathmark.ai from the billing email on file. Insurance Renewal Package subscriptions can be set to non-renewing from your client portal; other subscription cancellations are handled via email.
• Refunds: handled case by case per our Terms of Use.

Portal access & login

Your Oathmark client portal is reachable through the engagement link we sent you when you signed up. If you've lost it:

1. Email support@oathmark.ai from an address on file for your firm.
2. We will re-send the engagement link, or issue a new one if the original has been rotated.

We do not use passwords for the client portal — access is by engagement link. Keep the link confidential; treat it like a shared secret.

Reporting a security issue

If you believe you've found a security vulnerability in the Oathmark website, portal, extension, or API, please report it responsibly.

• Email security@oathmark.ai with a clear description of the issue, the steps to reproduce it, and any proof-of-concept material.
• Please do not publicly disclose the issue until we've had a reasonable opportunity to investigate and remediate.
• We commit to acknowledging your report within two business days and to keeping you informed of remediation progress.

We do not currently run a paid bug-bounty program, but we're happy to publicly credit good-faith researchers when a report leads to a fix.