Privacy

coExploro is operated by a sole proprietor registered in Ukraine. The same individual acts as the data controller for the purposes of GDPR and equivalent privacy laws. For any privacy question, data subject access request, or erasure request, contact legal@coexploro.com.

coExploro processes account information, submitted URLs, screenshots captured from those URLs, analysis records, share-link state, waitlist submissions, answers to the optional question on how a visitor found coExploro, the campaign tags of the first link a new account came from, and operational logs needed to run the service. When paid checkout is enabled, payment, checkout, subscription, tax, refund, and customer-service records are processed by Paddle as Merchant of Record/payment provider.

Requests to the coExploro MCP server at api.coexploro.com/mcp need no account. We keep operational logs for them and count each request: the count records the request type, the tool name, the client family the client reports (for a tool call, read from the user agent the request carries), whether a tool call succeeded, returned an error from the tool, or was refused, and, when a corpus lookup finds no teardown, a fixed "not found" label. It never records the tool arguments or the rest of the answer. The AI transparency page describes this count.

We do not sell analysis data. We do not train AI models on user submissions or generated outputs.

The active AI model providers are Google, Anthropic, and OpenAI. They process prompts, outputs, and screenshots as needed for extraction, persona analysis, synthesis, and fallback routing.

More detail about model roles, limitations, and human oversight is in the AI transparency page.

Active infrastructure processors include Railway for application hosting and databases, Cloudflare R2 for storage, Browserbase for browser capture when configured, Langfuse Cloud for observability when configured, Resend for transactional email when email keys are configured, Paddle for paid checkout when billing checkout is enabled, PostHog for cookieless product analytics (page views with time on page and scroll depth, and the feature events we name) when an analytics key is configured, including masked session replay where replay is enabled for a visit (your browser sends this analytics data through our own web server, which passes your IP address on to PostHog for coarse geolocation), and Brandfetch for company-name or domain to website and logo resolution in URL autocomplete (for a pasted URL, only the hostname is sent) when external suggestions are enabled.

On the wait screen of a teardown run without an account, a visitor may give an email address. It is used once, to send one email with the link to that teardown when the run finishes or stops. The address is deleted once that email is sent or can no longer be sent, and at the latest 7 days after it was given.

The visitor's email contains fixed text and the teardown link only: never the analysed site's name or any text from the teardown, because anyone can type any address into the field.

A verified account owner who starts a teardown from the form or by upload gets one email with the link when it finishes or stops while they are away and not watching it, sent to the account address. The owner's email contains the analysed site's host and the link. Both run emails are sent through Resend.

While a teardown runs, we may ask how you found coExploro. Your answer is kept with that teardown and with the account that claims it. We also note the campaign tags (utm_source, utm_medium, utm_campaign) of the first link you opened coExploro from. Your browser keeps this note for up to 90 days, and we save the tags to your account when you create one. Analytics events also carry these tags.

Data subject access, correction, deletion, and portability requests can be sent to support@coexploro.com. Requests are handled manually while automated account deletion is not yet available.

Paddle processes payment, checkout, subscription, tax, refund, and customer-service records only when paid checkout is enabled and a user starts or completes Paddle-managed checkout.

When paid checkout is disabled for an environment, account, or plan, no Paddle checkout or payment data is sent from coExploro for that attempted purchase path.