Privacy policy
Information you share
Our contact form asks for your name, email, company, team size, a short description of what you do, and why you are interested in Mirrors. Please do not include passwords, API keys, customer records, or other confidential material in the form.
When you use the product, we store account information and the agent configurations, corrections, conversation traces, analysis results, and audit data you submit or generate through the service. Submitted traces can include messages, model inputs and outputs, tool arguments and results, and any prompts or other agent context you choose to send. We also store account access, subscription, and turn-usage records.
How we use it
We use your submission to understand your request and follow up about your demo request or product questions. Your message is available to authorized Mirrors team members in our team inbox. We may keep notes about our conversation and the replies we send.
We use product data to operate the service, analyze recurring agent failures, let you write and manage corrections, secure accounts, provide support, and calculate usage and billing.
Services that process submissions
Vercel hosts this website and its contact endpoint. Supabase stores submissions and manages team authentication. Resend handles email notifications and replies. Submissions are sent to devs@mirrors.dev so the founders can respond.
Services that process product data
Vercel hosts the signed-in app. Supabase provides account authentication and stores product metadata. Amazon Web Services runs the API and stores submitted content and operational logs. Agent37 runs analysis workers, and ClickHouse stores an analysis index.
Model-backed analysis and embeddings send relevant agent content through Vercel AI Gateway to model providers, including OpenAI. Depending on the analysis job, its content can also be processed by TypeSafe.
Stripe processes payment and billing information through its checkout and customer portal. Mirrors stores Stripe customer and subscription identifiers, subscription status, and turn-usage records. Usage reports to Stripe contain the customer identifier, turn counts, event identifiers, and timestamps; they do not contain conversation content.
Website analytics and reliability
We use PostHog for page visits, interactions, scroll and click patterns, website performance, and session replay. Replay helps us understand how visitors use the public website. It records the public page layout and interactions while masking form inputs and displayed contact details. Request and response bodies, headers, and console contents are excluded. URL queries and fragments are removed from telemetry, except the campaign labels on links we share (utm_source, utm_medium, utm_campaign, utm_term, and utm_content). We also record the domain of the site that linked you here, but not the page. We keep this with your visit’s analytics. If you book a demo, we also pass the campaign labels to Cal.com, our scheduling provider, so we can see which link brought you here. Analytics requests reach PostHog through our own domain.
Analytics and replay are enabled by default for eligible visits. PostHog uses cookies and local storage to recognize the same anonymous browser across page visits. We do not identify website visitors in PostHog. PostHog respects the browser’s Do Not Track setting and previously saved analytics opt-outs.
We use Sentry for website errors and performance traces, and for generic contact delivery failure codes. It receives page timing and diagnostic information, not contact field contents or message text. Sentry session replay is disabled; session replay is provided by PostHog only.
Product analytics and reliability
In the signed-in product, PostHog provides usage analytics and masked session replay, and Sentry provides error and performance monitoring. These tools can associate events with your account ID and email. Replay masks form inputs and account text; sensitive content panels are excluded. We do not collect request bodies, authentication credentials, or console contents through these tools. Existing analytics opt-outs are respected.
Website visitors
We use Letter (lettervisit.com) to measure visits to this site, including from AI assistants, and to identify the companies and business contacts who visit, for our sales and marketing. It uses your IP address, cookies and the pages you view, matched to professional profiles. Visitors in the EU, UK and Switzerland are identified only if they accept cookies. You can opt out at lettervisit.com/opt-out or by turning on Global Privacy Control in your browser.
Security and access
The team inbox requires sign-in and explicit team access. Contact-form field contents and message bodies are not included in analytics events. To limit automated submissions, the contact endpoint uses a short-lived rate-limit record derived from a network address.
Your questions and requests
To ask about access, correction, retention, or deletion of information you shared through the website or product, email devs@mirrors.dev.