Privacy
Privacy notice
This page covers the AgentOps Monitor site and services at agentopsmonitor.com. What we collect, why, and how to have it deleted.
What we collect
The site loads two third party scripts in your browser. Google Tag Manager loads on the site's public pages, and Google Consent Mode sets its optional storage categories (analytics, advertising, personalisation, functionality) to denied before the container loads, and keeps them denied until you allow them. Cloudflare, which serves the site, adds its Web Analytics script to every page to count page loads and measure load times; Cloudflare states that it uses no cookies. The cookie banner does not control it. When you create an account we store your email address and, if you give them, your name and company; our sign-in provider stores your login. The service runs on providers that process data on our behalf: Railway (hosting), Cloudflare (network, DNS, and the analytics script above), InsForge (database and sign-in), and Stripe (payments for paid plans). The site hosts a first party chat assistant: when you choose to submit a lead through it, we receive the details you provide (email address, company name) together with the conversation transcript, which we store in a dedicated first-party lead store and use to respond to your enquiry. The hosting platform may record standard request logs (IP, user agent, request path, response status) for operational security and abuse detection. The site stores your privacy choice in local browser storage so it can respect that choice on later visits. If you close the chat assistant, one flag in session storage keeps it closed until you close the tab; it holds no personal data and is set without asking for consent. Only if you allow preferences storage does the chat assistant also keep the email address and company you typed into it, in local browser storage.
// Example privacy preference payload
{
"analytics": false,
"marketing": false,
"timestamp": "2026-08-19T00:00:00.000Z"
}How we use the information
Request logs are used to keep the site available, detect malicious traffic, and investigate incidents. Chat lead submissions (email address, company name, and the conversation transcript) are used to respond to your enquiry and are kept until you ask us to delete them. Account details are used to sign you in and to bill a paid plan. None of it is sold, and it is shared only with the providers named above that process it for us.
Cookies and privacy choices
Optional analytics, preference, and marketing technologies remain off unless you allow them. Global Privacy Control signals keep marketing off. Read the Cookie Policy for the current technology inventory, or to update or withdraw consent.
How we store agent run data
When you send us a trace, we store the agent run and its spans, including the input you supply and the output the agent produced. That data commonly contains the full text of your model prompts, model completions, tool arguments, and tool results, so it can contain personal data and secrets such as credentials that appear in your own prompts.
This data is stored in our database in plain text. We add no application-level encryption, and we have not verified whether our database provider encrypts its storage at rest. In transit it is protected by HTTPS. Anyone with direct access to our database, or a backup of it, can read the contents of your prompts and outputs. Access is restricted by tenant: your data is readable only from your own account, and every query is filtered to your account on the server.
Data retention
Agent run and span data is retained indefinitely. There is currently no automated retention or deletion schedule for it, so it accumulates until it is deleted. You can erase it yourself. There is no button for this yet: a signed-in DELETE /api/account request with the JSON body {"confirm": "DELETE_MY_ACCOUNT"} removes every run, span, API key, usage record, and profile row associated with your account. Erasing your account first cancels any active subscription; if that cancellation fails, nothing is deleted and you are asked to try again. The request does not delete your login identity, because our authentication platform offers no application-level way to remove it. Ask us through the contact form and we will complete that final step by hand. Chat and contact-form requests are stored separately and are not removed by this request; ask us to delete them too.
Request log retention follows the hosting platform default. Chat lead submissions are stored in a dedicated first-party lead store (the details you submit plus the conversation transcript, with a submission timestamp) rather than only in hosting logs. Leads are used to respond to your enquiry and are deleted on request; a fixed automated deletion schedule for leads is on our remediation list.
Your rights under GDPR and similar laws
If you are in the European Economic Area, the United Kingdom, California, or another jurisdiction with similar rights, you can request access to or deletion of any personal data we hold about you. That includes agent run and span data, not only request logs and chat lead submissions, because run and span data is the primary data this product stores. Send the request through the contact form and include the email address it concerns (for chat leads, the address you submitted).
Deletion of run and span data is self-service, as described under Data retention above. We do not currently offer a self-service export of your data; ask us through the contact form and we will provide what we hold.
Contact
Privacy questions: use the contact form.
This notice is effective as of October 2026.