Privacy Policy

1. Information we collect

Account information

When you sign up for Rudow, we collect your name, email address, and password (stored as a salted hash, never in plain text). If you join an organization, we store your membership and role within that organization.

Billing information

Subscription payments are processed by Stripe. We do not store your full payment card details — Stripe handles that under its own PCI-compliant infrastructure. We retain billing metadata (plan tier, subscription status, invoice history) necessary to administer your account.

Customer log data

When you (or your application, via our SDKs or ingest API) send log entries to Rudow, we store: the log message, severity level, source label, timestamp, and any structured attributes you attach. You control what goes into these fields — see §3 for your responsibilities around what you send us.

Usage data

We collect operational data about how you use the Service itself — dashboard page views, feature usage, API/MCP request counts (used for plan quota enforcement), and error logs generated by our own systems.

API keys and MCP keys

We store a cryptographic hash of each ingest API key and MCP key you create, plus metadata (name, creation date, last-used date, which projects it's scoped to). We do not store the plaintext key after it's shown to you once at creation.

2. How we use information

We use the information above to:

• Operate, maintain, and provide the Service (storing and displaying your logs and metrics, enforcing plan limits, authenticating requests).
• Power AI-assisted features — see §4, AI features and third-party model providers.
• Process payments and manage subscriptions via Stripe.
• Send transactional email (e.g. password resets, usage-threshold notices) via our email provider, Resend.
• Monitor, secure, and improve the Service, including detecting abuse of the ingest API, MCP server, or dashboard.
• Communicate with you about your account, billing, or changes to the Service.

We do not sell your personal information or your customers' log data.

3. Customer log data

If you send log data to Rudow (via an SDK, the ingest API, or otherwise), you are responsible for what that data contains. Log messages and attributes can inadvertently include personal data about your own end users (e.g. email addresses, IP addresses) if your application logs them. You should:

• Avoid logging sensitive data you don't need for debugging (e.g. full payment card numbers, passwords, government ID numbers, health information) unless you have an independent legal basis and appropriate safeguards for doing so.
• Ensure your own privacy policy and any applicable data processing agreements with your end users cover sending their data to a third-party logging provider like Rudow.

We process log data solely to provide the Service to you (storage, search, dashboards, AI-assisted analysis you initiate) and do not use it for our own independent purposes, such as training general-purpose models on your data.

4. AI features and third-party model providers

Rudow includes AI-assisted features — a chat assistant, “AI insights,” and semantic log search — that send relevant log/metric data to a third-party large language model provider to generate a response. Depending on configuration, this may be Anthropic, OpenAI, or DeepSeek. Semantic search additionally generates vector embeddings of your log content via one of these providers' embedding APIs.

Data sent to these providers is limited to what's needed to answer the specific query or generate the specific embedding (e.g. the logs matched by your search, or the metrics relevant to your question) — not your entire log history in bulk. These providers process this data under their own terms and, where applicable, data processing agreements; we do not control their retention policies beyond what those agreements specify.

If you connect Rudow to your own AI tools via our MCP server, log and metric data flows to whatever AI client you've configured (e.g. Claude Desktop, Cursor) under your own control — that data flow is governed by your relationship with that client/provider, not by us.

5. Sub-processors

We use the following categories of third-party service providers to operate Rudow:

6. Data retention

We retain account information for as long as your account is active, plus a reasonable period afterward for legal and operational purposes. Log data is retained according to your plan's retention window; you can delete a project (and its logs) at any time from the dashboard. Billing records are retained as required by applicable tax and accounting law.

7. Data security

We use industry-standard measures to protect your data, including hashed credentials, scoped API keys, encrypted transport (TLS) for all API and dashboard traffic, and access controls limiting which projects a given key or user can reach. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security.

8. Your rights

Depending on your jurisdiction, you may have rights to access, correct, export, or delete your personal information, and to object to or restrict certain processing. To exercise these rights, contact us at info@rudow.ai. If you are an end user of one of our Customers (not a Rudow account holder yourself), please direct your request to that Customer first, as they control the data.

9. Children's privacy

The Service is not directed at children under 16, and we do not knowingly collect personal information from them.

10. International data transfers

We and our sub-processors may process data in countries other than your own. Where required, we rely on appropriate safeguards (such as standard contractual clauses) for such transfers.

11. Changes to this policy

We may update this Privacy Policy from time to time. We'll post the updated version here with a new effective date, and, for material changes, provide additional notice (e.g. via email or an in-dashboard notice).

12. Contact us

Questions about this policy? Contact us at info@rudow.ai.