Legal

Privacy Policy

Last updated: July 5, 2026

The short version: your data is hosted in the United States with industry-standard security, access is limited to our own team – no outside contractors – logs are stored in screened form by default, and we never sell your data or train models on it.

1. Scope

This Privacy Policy explains how in/guard/out (“we”, “us”) handles personal data when you visit our website, request demo access, or use the guardrails proxy service, its APIs, and dashboard (together, the “Service”). It should be read together with our Terms of Service.

One distinction matters throughout: data about you (your account, your sign-up details, your usage of the Service) versus data you route through the Service (your applications’ prompts, responses, and tool traffic – “Customer Content”). We treat the second category as yours, and we designed the product to minimize what we ever see of it.

2. What we collect

We collect:

Account and contact data – name, work email, company, and what you tell us in the sign-up or demo-request form.
Service usage data – API keys used, request counts and timestamps, per-stage timings, token counts and cost metering, violation flags, and dashboard activity. This is the operational telemetry the product itself shows you.
Request logs – transcripts of requests and responses processed by the Service, stored in screened form by default: detected PII is replaced with placeholders before logging, and the placeholder-to-value map is held in memory for the single request and never written to the database. Raw logging exists only as an explicit per-account opt-in.
Website analytics – on our public website we use Google Analytics and PostHog to understand how visitors find and use it: pages viewed, referrer, approximate location derived from IP, device and browser type, and interaction events, collected via cookies and similar identifiers. You can block or clear these in your browser, and Google offers an opt-out browser add-on.
Dashboard product analytics – inside the product dashboard we use PostHog to see which features are used and where the UI needs work: screens viewed, buttons clicked, and similar interaction events tied to your account. Product analytics covers your use of the interface – it does not capture the contents of your request logs or other Customer Content.
Website basics – server logs (IP address, user agent, pages requested) and a theme preference stored locally in your browser. We use analytics as described above, but no advertising or retargeting trackers.

3. How we use it

We use this data to:

provide and operate the Service – routing your traffic, running the checks you configure, metering, and showing you your own logs and dashboards;
respond to demo requests and support questions;
secure the Service – detecting abuse, enforcing limits, investigating incidents;
understand how the website and dashboard are used, via the analytics tools described in section 2, and improve the Service using aggregated usage statistics; and
meet legal obligations.

4. What we do not do

We do not sell personal data. We do not use Customer Content to train models. We do not run third-party advertising or share your data with data brokers. We do not use outside contractors to access or process your data: access is limited to our own team, on a need-to-know basis, for operating and supporting the Service.

5. Where data lives and how it is protected

The Service and its data are hosted in the United States with reputable cloud infrastructure providers. We follow industry-standard security practices: encryption of data in transit and at rest, access controls with least-privilege scoping, isolated environments, and audit logging of administrative access.

The product’s own design is part of the security posture: PII is screened into placeholders before requests leave for model providers, logs store the screened form by default, and secrets and screened values are blocked from leaving through agent tool calls. No system is perfectly secure, and we do not promise ours is – but minimizing what is stored, and storing the screened form, limits what any incident could expose.

6. Sharing

We share data only with:

Upstream providers you configure – the model providers, search services, and tools you route traffic to receive the (screened) content needed to serve your requests. Your contracts and their terms govern their processing.
Infrastructure service providers – US-based hosting and email-delivery services that store or transmit data on our systems’ behalf. They provide infrastructure; we do not grant outside parties human access to your data.
Analytics providers – Google (Google Analytics) and PostHog receive the website and dashboard usage data described above and process it for us as service providers. Customer Content is never sent to them.
Legal recipients – if required by law, subpoena, or to protect the rights, safety, or security of the Service, and successors in a merger, acquisition, or asset sale (with notice).

7. Retention

Account data is kept for as long as you have an account and for a reasonable period after closure. Request logs and telemetry are kept per your plan’s retention allowance, then deleted. The PII placeholder map is never persisted at all. You can request deletion of your account and associated data at any time; we will honor it subject to legally required retention.

8. Your rights

Depending on where you live, you may have rights to access, correct, export, or delete personal data we hold about you, and to object to or restrict certain processing. Write to [email protected] and we will respond within a reasonable timeframe. If you are in a jurisdiction with a supervisory authority (for example, the EEA or UK), you also have the right to lodge a complaint with it. Note that the Service is hosted in the United States, and by using it you understand your data is processed there.

For personal data inside Customer Content, your organization – not we – decides why and how it is processed; direct requests about it to the organization that routed it through the Service, and we will assist them.

9. Children

The Service is a business tool, not directed at children, and we do not knowingly collect personal data from anyone under 16. If you believe a child has provided us data, contact us and we will delete it.

10. Changes and contact

We will update this policy as the product and law evolve; material changes will be announced by email or in the dashboard before they take effect, and the current version always lives at this page.

Questions, requests, or concerns: [email protected].