What we collect, why we collect it, how long we keep it, and the choices you have. Last updated: October 23, 2026.
This policy covers ziplogger.ai (the marketing website) and app.ziplogger.ai (the ZipLogger service). "ZipLogger", "we", and "us" refer to Fox Real Estate LLC, the operator of the ZipLogger service. Questions about anything on this page: [email protected].
ZipLogger handles two very different categories of data, and treats them differently:
Account data — information about you and your organization: name, email address, organization name, billing status, and the settings you configure. We are the data controller for this.
Customer telemetry — the logs, traces, metrics, and product events your applications send to your workspace. You control what is in this data; we store and process it on your behalf and on your instructions (we act as a processor for it). Do not send us data you are not allowed to share — telemetry payloads are defined entirely by your integration.
When you create an account: your name, email address, organization name, and a password (stored only as a salted PBKDF2 hash — we cannot read it). Signup requires a card check; card details go directly to our payment processor, Stripe, and never touch our servers. We store only Stripe's customer and subscription references.
When you use the service: the telemetry your applications send (logs, traces, metrics, product events), the configuration you create (dashboards, alerts, saved filters, health-check URLs, browser monitors), API keys (stored hashed), and operational records such as sign-in timestamps and audit logs of administrative actions.
When you connect integrations: if you connect a git provider (GitHub or GitLab), we store the access credential encrypted and fetch commit metadata and blame information over the provider's API — we never clone your repository. If you configure AI analysis with your own AI provider key, it is stored encrypted and used only to send analysis requests to the provider you chose. AI features are described in section 4.
When you visit the website: standard analytics as described in section 6.
To provide the service: storing and searching your telemetry, evaluating your alert rules, running the health checks and browser monitors you configure, attributing regressions to commits, and sending you transactional email (invoices, password resets, alert and usage notifications). To bill you, via Stripe. To secure and operate the platform: rate limiting, abuse prevention, and debugging. We do not sell your data, and we do not use your telemetry for advertising or to train AI models.
AI features (incident and Issue investigations, Ask ZipLogger, summaries and natural-language search) run only when your workspace has turned AI on: a workspace admin switches it on in the AI settings, or saves the workspace's own AI provider key. An admin can turn AI off at any time. When AI is on, the workspace chooses the AI provider (Anthropic, OpenAI or Google) and one of two ways to use it:
Your own key. Requests go to the provider under your own account with that provider and are subject to your agreement with it. ZipLogger does not act as the provider's customer for these requests.
ZipLogger's hosted model. Requests go to the provider under ZipLogger's account, so the provider acts as our subprocessor (section 7). This happens only if a workspace admin explicitly allows it for that provider, after reading the in-app disclosure of what is sent; moving it to another provider requires that confirmation again. ZipLogger's hosted keys use each provider's standard commercial API terms; we do not have a zero-data-retention agreement with any of them.
What is sent, from the investigated time window and the workspace's own environment only: incident and Issue fields (title, severity, service, times, description); error and log lines (message, release, trace id, top stack frames); trace and span summaries (operation names, durations, status, database system and statement shape); release, deploy and commit metadata (names, commit hashes, commit messages, authors); host, container, Kubernetes and database monitoring figures (CPU, memory, restarts, connections, slow statement text); real-user monitoring page figures and replay session ids, only if the workspace allows it; and your question, with earlier questions and answers of the same conversation. Never sent: session replay recordings or screenshots, request or response bodies, API keys or ZipLogger credentials, and data of other environments or workspaces.
Removed before anything is sent: passwords, tokens and API keys (including provider, Stripe, GitHub, Slack, Google and ZipLogger keys), Authorization and Cookie headers, private keys, credentials in connection strings and URLs, secret-named environment variables, email addresses, IP addresses, payment card numbers and US social security numbers. Redaction is done by ZipLogger before the request leaves our servers; we never rely on the AI model to remove anything. ZipLogger keeps the resulting investigation report and its evidence references with the incident, and Ask ZipLogger conversations for the period the workspace sets.
If AI is not turned on for a workspace, no telemetry from it is sent to any AI provider.
If you connect an AI assistant to your workspace over MCP (for example Claude or Cursor), the assistant gets read-only access to your workspace's logs, error patterns, traces, service status, and regression analyses — authorized either by OAuth with your explicit consent, or by a workspace API key you create with read access. Whatever the assistant reads is then handled by the assistant under its own provider's terms. You can revoke access at any time by revoking the API key or contacting support.
Telemetry retention follows your plan: up to 3 days (Free), 14 days (Pro), 30 days (Team) or 90 days (Business). Traces that contain an error are kept for the plan's full retention window; error-free traces are kept for up to 30 days, and never longer than the plan's retention. A workspace can shorten any of these itself, and a storage cap it sets can delete the oldest days before the window ends. Expired telemetry is deleted automatically by our retention workers.
Account data is kept while your account is active. When you close your account (or ask us to delete it), we delete your account data and remaining telemetry within 30 days, except for records we are legally required to keep, such as invoices.
The marketing website uses Google Analytics 4 and Microsoft Clarity to understand how the site is used. The application uses Microsoft Clarity for product-usage insight. The application also sets cookies and browser storage strictly needed for signing you in. We run no advertising pixels and no cross-site tracking of our own.
We also use our own product, on this website and inside the application: errors and page events are reported into a ZipLogger workspace we own, and a small sample of visits is recorded as a session replay — the page structure, the cursor, clicks and scrolling — so we can see where our software confuses people. Recordings are kept for 30 days and are never shared or sold.
Inside the application the recorder is deliberately blunt, because those screens show your data: all text is masked, the panels that display logs, events, traces and replays are not recorded at all, and identifiers in page addresses (a user id, a trace id) are replaced before anything is sent. A replay of the application shows which screens were opened and what was clicked — never what they contained.
What a recording never contains: anything typed into a field. Every input value is masked in your browser before anything is sent, and passwords, one-time codes and payment fields are masked unconditionally. The sign-in, sign-up and password-reset pages are not recorded at all. Cookies, browser storage and request headers are never captured. The same guarantees apply to session replay in the product itself, which is off until a workspace turns it on; see the session replay documentation for the full list of what is and is not captured.
We share data with subprocessors only as needed to run the service: Stripe (payments and card verification), Brevo (transactional email), Cloudflare (DNS, CDN, and network security in front of our infrastructure), Google and Microsoft (website/product analytics, section 6), and our hosting provider (servers on which the service runs). Each receives only what its function requires.
Conditional AI subprocessors. Each of the following receives data only from a workspace whose admin has allowed ZipLogger's hosted model with that provider (section 4). It receives the redacted data categories listed in section 4, never the categories listed there as never sent. A workspace using its own provider key is not covered here: that provider then acts under the workspace's own agreement with it.
These summaries were checked on October 23, 2026; each provider's current page is authoritative. The AI settings page in the app shows the same terms for the provider a workspace uses.
All traffic is encrypted in transit (TLS). Passwords are salted and hashed (PBKDF2), API keys and session tokens are stored only as SHA-256 hashes, and integration credentials (git tokens, AI provider keys) are stored encrypted. Access to production systems is restricted and audited. No system is perfectly secure; if we learn of a breach affecting your data, we will notify you without undue delay.
You can access and update your account information in the app. You can export or delete telemetry through the product's search and retention controls. Depending on where you live (for example under the GDPR or CCPA), you may have rights to access, correct, delete, or port your personal data, and to object to or restrict certain processing. To exercise any of these, email [email protected] — we respond to verified requests within 30 days.
ZipLogger is a developer tool for businesses and is not directed at children under 16. We do not knowingly collect personal data from children.
When this policy changes materially, we will update the date at the top and, for significant changes, notify account owners by email. Continued use of the service after a change takes effect constitutes acceptance.
See also our Terms of Service.