epok
Open demoStart trial

Privacy Policy

Last updated: October 21, 2026

1. Information We Collect

Account Information

When you sign in with Google, we receive your name, email address, and profile picture. We use this to create and manage your account.

Log Data

You send log data to Epok for storage and analysis. This data may contain application logs, system metrics, trace IDs, and other operational data from your infrastructure. We process this data solely to provide our service.

Billing Information

Paddle handles checkout and payment details as our merchant of record. We use your account email, Paddle customer and subscription identifiers, plan, billing period and payment status to manage your subscription and access. We do not collect or store your full card number or security code. Paddle describes its processing in its Privacy Policy.

Usage Data

We collect basic usage information such as pages visited, features used, and API calls made. This helps us improve the Service.

2. How We Use Your Data

  • To provide, maintain, and improve the Service
  • To run anomaly detection, alerting, and pattern analysis on your logs
  • To send you alerts and notifications you have configured
  • To communicate service updates and security notices
  • To provide customer support
  • To manage subscriptions, reconcile payments and respond to billing questions

3. Data Isolation

Each tenant's data is logically isolated. Your log data is never shared with, visible to, or accessible by other tenants. All queries and API requests are scoped to your tenant.

4. Data Retention

Log data is retained according to your plan's retention period (14 days on Trial, 30 days on Team and Growth). After the retention window, data is automatically and permanently deleted. Account information is retained as long as your account is active. Billing records may be retained where needed for accounting, legal obligations or resolving payment disputes; they do not follow the telemetry retention window.

5. Data Location

Your log data is stored in the European Union (Helsinki, Finland) on infrastructure operated by a reputable EU data-center provider. Account data and metadata are stored in the same region. The Company is incorporated in Bangalore, India. By using the Service, you consent to the processing of your data in both the EU and India as necessary to operate the Service.

6. Service Providers and Payment Partner

We use the following third-party services to operate Epok:

  • EU data-center provider (Germany/Finland) — Infrastructure and compute (specific provider disclosed under NDA for enterprise customers)
  • Cloudflare (Global) — CDN, DNS, DDoS protection, and TLS termination
  • Google OAuth (US) — Authentication only; we receive name and email
  • PostHog (US/EU) — Product analytics (page views, feature usage)
  • New Relic (US) — Infrastructure monitoring
  • Sentry (US) — Error tracking for the Service itself
  • Anthropic (US) — Claude models for root-cause drafting when enabled; receives selected incident evidence as described below

Apart from the AI processing described below, service providers receive only the minimum account, billing, request, or product-usage data needed for their function. Cloudflare, for example, processes traffic routed through its network to provide these services.

Payment partner

Paddle (UK/US) processes buyer information in its own capacity as our authorized reseller and merchant of record, including for payments, tax and fraud prevention. Its Privacy Policy explains these purposes and how to exercise your rights with Paddle.

7. AI Data Processing

Epok uses Anthropic Claude models for AI features: Haiku for routine drafting and Sonnet for Deep RCA and playbook import. Drafting can run automatically when incidents are analyzed, as well as when you request an AI feature.

RCA prompts include ranked causes, scores, service names, error categories, timing, metric and trace summaries, dependencies, and similar incidents with resolution notes. Deep RCA can also include your architecture context, matched playbook steps and links, RUM routes and impact, and affected customer names or IDs, tiers, and error counts when available.

Hypotheses list up to 5 ranked causes; Deep RCA lists up to 8. Cause titles and explanations are truncated after 150–200 characters, and up to 3 historical resolution notes after 200 characters. Truncation adds an ellipsis. Architecture context drops notes, then network details if it exceeds 8,000 characters; this is not a hard cap on the remaining context.

Log text can leave Epok. Deep RCA uses normalized messages from up to 15 alerts, each truncated after 200 characters. RCA can also include pre-error log messages truncated after 150 characters. Ask Epok result summaries can send up to 8 raw log messages, each limited to 240 characters, with timestamps, service names, and levels, plus your question and a result digest. Alert-title rewriting and noise scoring send normalized log patterns (up to 300 characters) and alert titles; pattern labelling sends normalized messages up to 500 characters. These are field limits, not a universal limit on the whole prompt.

There is no automatic redaction todayfor secrets or personal data before AI requests. Pattern normalization, truncation, and prompt-injection guards are not sensitive-data scrubbing. We do not control Anthropic's retention; see its commercial data-retention policy. Epok does not train models on your telemetry. Under Anthropic's commercial terms, API inputs are not used to train its models by default; see its policy pages.

There is no self-serve AI off switch. Operators can disable AI for an entire deployment. Workspace-specific disabling requires a deployment configuration change; it is not wired into the current deployment. If you need AI off for your workspace, contact [email protected] before sending data and wait for confirmation. Avoiding AI buttons does not stop background drafting. Deterministic detection and RCA ranking do not require an external model.

8. Data Sharing

We do not sell your data. We may share data only in the following cases:

  • With your consent
  • To comply with legal obligations or valid legal process
  • To protect the rights, safety, or property of Epok, our users, or the public
  • With the service providers and payment partner described in this policy, for their stated purposes

9. Security

We use industry-standard security practices to protect your data, including encryption in transit (TLS), secure authentication (OAuth 2.0, JWT), and access controls. No system is 100% secure, and we cannot guarantee absolute security.

In the event of a data breach that affects your personal data or log data, we will notify you via email within 72 hours of becoming aware of the breach, consistent with GDPR requirements.

10. Cookies and Analytics

We use essential cookies for authentication (session tokens). We do not use advertising or third-party tracking cookies.

We use PostHog for product analytics to understand how features are used and improve the Service. PostHog collects page views, button clicks, and feature usage data. This data is associated with your account but does not include the contents of your log data.

11. Your Rights

You have the right to:

  • Access the personal data we hold about you
  • Request correction of inaccurate data
  • Request deletion of your account and associated data
  • Export your data

To exercise these rights, contact us at [email protected]. We will respond to rights requests within 30 days.

12. Changes to This Policy

We may update this policy from time to time. We will notify you of material changes via email or through the Service. Continued use after changes constitutes acceptance.

13. Contact

Questions about privacy? Contact us at:

Jyngle Technologies Private Limited
WeWork Prestige Cube, Site No. 26, Laskar Hosur Road, Adugodi
Bengaluru, Karnataka 560030, India
[email protected]