Privacy Policy

When you connect Evaal to GitHub, Linear, Slack, and Calendar, Evaal reads metadata about activity in those systems: pull request review times, issue transitions, channel activity patterns, calendar load. Evaal does not read the contents of your private Slack messages, the contents of private repositories beyond what is needed to compute review-graph metadata, or the contents of calendar event descriptions beyond title and attendees.

Evaal stores aggregated and per-engineer signals required to compute the metrics you have enabled. The full data inventory will be enumerated in the final policy.

Evaal does not train any model on your code, your messages, your tickets, or your metadata. Customer data is never used to improve models that serve other customers.

Evaal does not sell, rent, or share customer data with third parties for marketing, advertising, or analytics purposes.

Evaal does not share individual-engineer burnout signals or cognitive-load scores with anyone other than the manager who has been granted that view.

Evaal stores customer data in the region you select at signup (currently EU and US regions are planned for general availability). Data does not cross regions without explicit customer consent.

Subprocessors used by Evaal will be listed in the final policy. Customers will be notified of any change to the subprocessor list before it takes effect.

Customers and the engineers in their connected organisations may request access, correction, or deletion of personal data Evaal holds about them. Email hello@evaal.ai with the request and Evaal will respond within the timelines required by the applicable law (GDPR Article 12, CCPA, or equivalent).

Evaal will publish a Data Subject Request workflow before general availability.

Material changes to this policy will be communicated to active customers at least 30 days before they take effect. The current version is always reachable at evaal.ai/privacy.