Appearance
Data and privacy
What is sent to the model
The diff of the files in a pull request, after exclusions; nothing else. Specifically:
- added, removed, and surrounding context lines of each changed file, as GitHub provides them;
- the file paths those changes belong to;
- the pull request's title and description;
- any review instructions you wrote in a configuration file.
What is not sent: files you did not change, files matched by an exclude pattern, files GitHub gives no diff for, your repository history, issues, or secrets stored in GitHub.
EasyMerge never clones your repository. Outside a pull request diff it reads the configuration file .easymerge.yaml, if your repository has one, and the files allowed by a configuration scan. Neither is sent to the model. Dependency-security data comes from GitHub Dependabot rather than from EasyMerge reading application source.
TIP
The reliable way to keep something away from the model is an exclude pattern. An excluded file is never read.
Which model
Anthropic Claude is the model by default; Google Gemini is the supported alternative.
The configuration scan
Project status includes a limited configuration scan. You can start it with Scan configuration, or a Pro automation can run it on a daily or weekly schedule.
On the repository's GitHub default branch it reads the file and folder listing, and the contents of a fixed set of documentation and configuration files: README files, dependency manifests and lockfiles, test and tooling configuration, CI workflows and deployment files. The full list is on the guide page.
Your application source is never read. Nor are files that look like secrets: .env files, .pem, .key, .p12 and id_rsa are never fetched, even though a committed .env file is noticed in the listing and reported.
None of this reaches the model. The scan checks project configuration only. Dependency alerts shown in EasyMerge are metadata supplied by GitHub Dependabot; see Security Center.
What is stored
| Data | Notes |
|---|---|
| Pull request metadata | Repository, PR number, title, description, author, branches |
| Findings | File, line range, severity, comment body, suggestion |
| Skipped files | Path and skip reason; no content |
| Configuration file | The settings read from .easymerge.yaml, including any instructions, and the problems found in it |
| Project status results | The status, its signals, the commit scanned, and the paths of the files inspected and skipped; no file contents |
| Dependency security | Dependabot alert details, affected package and manifest, fix PR and checks metadata, sync state, and your handling decision |
| Automations | Repository, schedule, notification choice, enabled state and run history |
| Your display mode | Technical or Decision view, against your own account |
| Your GitHub access token | Stored encrypted |
| Support tickets | Subject, description, category, every message on the ticket, and the repository or review it was filed against |
| Support attachments | The files you attach to a ticket or a reply, kept with the message. A file you upload but never send is deleted after 24 hours |
Findings are also posted to GitHub as review comments, where they follow your repository's own retention and visibility rules.
A support ticket is what you type into it, so keep secrets out of it: the form says so, and so does the attachment field. Everyone linked to the installation can read the ticket and download its files, and so can the EasyMerge support team. Attachments are checked for malware before they can be sent; a file that fails is refused and never reaches the ticket.
The waitlist
The waitlist form stores your email address, your name, your occupation and the time you joined, in a Google Sheet. Joining again with the same email adds nothing.
Two checks run before anything is stored, and neither keeps what it reads:
- Cloudflare Turnstile checks the form for automated sign-ups, using your IP address and browser characteristics;
- your IP address limits how often the form can be submitted, five times a minute.
Site analytics
easymerge.dev uses Google Analytics to count page views. Nothing is set until you choose on the cookie banner:
- Decline, or no choice yet: no analytics cookie; Google receives only cookieless signals, such as the page and the time, that cannot link your visits;
- Accept: Google Analytics cookies recognise your browser across visits, for up to two years.
Advertising features are always off, and analytics data is never joined to your account or waitlist details. Cookie settings in the site footer changes your choice; it is stored in your browser only. The EasyMerge dashboard itself does not use Google Analytics.
Who can see it
Only people who have signed in and whom GitHub reports as having access to the installation. GitHub decides this, not EasyMerge, and it is re-checked every time someone opens the dashboard. Losing access on GitHub means losing access in the dashboard.
Within an installation, admins and members see the same reviews; the difference is that only admins may change settings, and only admins may change other people's roles. Being made an admin grants no extra visibility into code or reviews.
Dependency alerts have an additional repository check. You need write, maintain or admin access on GitHub to see their contents in EasyMerge. The EasyMerge admin role does not override that requirement.
Deleting your data
Uninstalling the GitHub App on GitHub is the way to delete your data. It stops all reviews for that account immediately, revokes EasyMerge's access to your code, and removes everything stored for that installation: its repositories, pull requests, reviews, findings, project status results, dependency-security data, automations, and support tickets with their attachments. The dashboard will no longer show them.
Removing a single repository from the installation is not a deletion. It disappears from the dashboard, but its pull requests, reviews, findings, project status, dependency-security data and automation history are kept and reappear if you add the repository back. Uninstall the app to delete them.
Review comments already posted to your pull requests belong to your repository, and are not removed. Delete them on GitHub if you want them gone.
Data retention
We automatically delete review findings based on your configured Data retention (days) setting (for example, after 30 days). See Organization settings.
Permissions EasyMerge holds
Read access to code, and write access limited to pull request comments and check runs. It cannot push commits, create or delete branches, change settings, or merge anything. See Install the GitHub App for the full list.