Privacy Policy

1. Data we handle

Account data. When you create an account we store your name, email address, and a hashed password (never the plaintext). If you sign in with Google or GitHub, we store the provider account id.

Billing data. Paid plans are processed by Stripe. We store your plan, subscription status, and a Stripe customer id — we never receive or store card numbers; Stripe handles payment details under its own terms.

Telemetry you send us. The core of the service is the error events, transactions, session replays, profiles, and related metadata your applications send to jentry. You control what is sent. For this data you are the controller and jentry is a processor acting on your instructions. This data can include whatever your SDK captures — stack traces, request URLs, breadcrumbs, IP addresses, and user identifiers you attach. You are responsible for not sending data you shouldn’t; jentry applies server-side scrubbing of common secrets and PII (passwords, tokens, card numbers, SSNs) and lets you configure additional scrubbing.

Marketing analytics. On our public marketing pages only (not the logged-in app), we use Google Analytics 4 with IP anonymization to understand acquisition. See “Cookies” below.

2. Cookies

Essential cookies keep you signed in and remember your theme — the app does not work without them. Analytics cookies (Google Analytics) are set only on the marketing site to measure visits; they use anonymized IPs and do not identify you personally. We do not use advertising or cross-site tracking cookies in the app.

3. How we use data

To provide and secure the service, process your telemetry into issues/metrics, handle billing, send service and alert emails, prevent abuse, and — for marketing analytics only — measure and improve our site. We do not sell your data.

4. Sharing & subprocessors

We share data only with vendors that help us run jentry, under their own data-protection commitments:

• Stripe — payment processing.
• SendGrid — transactional and alert email delivery.
• Google Analytics — marketing-site analytics only.
• DigitalOcean — hosting infrastructure.
• Anthropic — only if you enable AI issue analysis (Seer), and only the specific issue text you submit for analysis.

We may also disclose data if required by law, or to protect the rights and safety of jentry and its users.

5. AI agents connected over MCP

You can connect an AI app — Claude, ChatGPT, Cursor, VS Code or another client of the Model Context Protocol (MCP) — to your jentry account (see Connect AI agents). When you do:

• What it can do. The agent acts as you, in the organizations you belong to and with your role in each: it can read what you can read (issues, events, performance data, settings, members) and make the changes you can make. Deleting, merging, revoking and anything sent outside jentry show a preview and run only once you confirm. An agent cannot create or reveal tokens or secret keys, change your password or 2FA, or pay, charge or refund anything — a plan upgrade comes back as a Stripe Checkout link that you open and pay yourself.
• How access works. Access is granted by you with OAuth (you sign in to jentry and click Allow) or with a token you create in Settings → AI agents. Connections and tokens are listed there and can be revoked at any time; resetting your password revokes them all. OAuth access tokens expire after one hour and refresh tokens after 90 days of disuse, rotating on every use. We store only a hash of each token.
• What reaches the AI provider. What the agent reads is sent to the AI app you connected and is handled under that provider’s terms (for example Anthropic or OpenAI). Before it leaves jentry we mask e-mail addresses and remove IP addresses, cookies, authorization headers, request bodies and stack-frame variables from event data.
• What we keep. We do not receive or store your conversations with the AI app — only the tool calls it makes to jentry. For each connection we keep the app’s self-declared name, its redirect address, when it was created and last used; changes an agent makes are recorded under your name, marked as made through an agent, in the issue activity and the organization audit log, and kept like any other activity. Revoked or expired tokens are deleted about 30 days later, and app registrations that were never used after about a week.

6. Retention

Telemetry is retained per your plan (7, 30, or 90 days) and then pruned automatically; issue records and rollup counts may persist longer. Account and billing records are kept while your account is active and for as long as needed for legal and accounting obligations. Marketing analytics follow Google Analytics’ retention settings.

7. Security

Passwords are hashed, transport is encrypted (TLS), privileged keys and secrets are encrypted at rest, and access is scoped. No system is perfectly secure, but we take reasonable measures appropriate to the data we hold.

8. Your rights

You can access, correct, export, or delete your account data — from your settings or by emailing us. For telemetry your applications sent us, your organization’s administrators control access and deletion. If you are an end user of a service that uses jentry, please contact that service (the controller of your data); we will support their requests as their processor.

9. International transfers

jentry is operated from infrastructure that may process data in the United States and other regions. By using the service you understand your data may be processed in those locations, with appropriate safeguards.

10. Changes

We may update this policy; material changes will be reflected by the “Last updated” date above and, where appropriate, announced in-product or by email.