Dexly Privacy Policy.

Privacy summary

Dexly is designed so that hosted services handle identity, billing, entitlements, and quota accounting, while browser context and coding workflow inputs stay on the user's machine or in the user's chosen local Codex workflow.

Data stored by Dexly's hosted backend

Dexly's hosted backend may store data needed to operate account and billing features, including:

• identity and account profile fields such as account id, email address, and display name
• authentication and session-handling data needed to keep extension sign-in working
• billing status, entitlements, plan state, and usage quota counters
• usage reservations and usage event records for metered plans
• Stripe customer, subscription, checkout, payment-linked, and event-integrity records needed to enforce billing state

Data that stays local to your device or local workflow

Dexly's hosted backend does not store:

• active page URLs, page titles, or local page-context references captured for a task
• browser page content or full DOM snapshots
• prompts sent through Dexly
• captured screenshots or selected-element images
• local workspace files, folder contents, or absolute local workspace paths
• Codex thread history, transcript content, reasoning output, or local task streams

When you use inspect or capture features, the extension may locally access the active page URL and title, selected DOM snippets, click, drag, hover, focus, and scroll interaction data needed to run inspect and capture flows, and optional screenshots so it can prepare the task for your local coding workflow.

Stripe and Supabase

Supabase powers Dexly's hosted authentication and session flows for extension sign-in.

Stripe handles payment processing, recurring subscription billing, Customer Portal actions, refund processing, and dispute events for Dexly's hosted billing surface.

Dexly uses these providers only for the hosted account, authentication, payment, and subscription parts of the product. Their services are also governed by their own terms and privacy policies.

Extension local storage

The Dexly extension may store local state in chrome.storage.local on your device. That local state can include:

• settings and connection preferences
• workspace presets and local workspace path references
• recent task summaries, including saved page-context references such as page URL metadata, and saved final output summaries used to reopen local history
• cached billing state and auth/session-related state needed by the extension

That local extension state is not the same as Dexly's hosted billing backend storage.

How data is used

• to authenticate users and maintain extension sign-in sessions
• to calculate entitlements, enforce quotas, and reflect billing state in the extension
• to process payments, subscription changes, refunds, and disputes through Stripe
• to support billing operations, fraud prevention, and service integrity

Dexly does not use its hosted backend to build a remote prompt or transcript store for your browser-assisted coding activity.

Privacy questions

For privacy questions or account-related requests connected to Dexly's hosted services, contact support@dexly.example.