MergeTap
What it doesAccountsPricingPrivacy

Privacy notice

Effective 22 October 2026

The short version

MergeTap runs primarily on your device and talks directly to Azure DevOps and Microsoft Entra, or to GitHub, using credentials you supply. Anonymous usage analytics is off until you enable it in Settings; when enabled, it sends only app-open and screen-view events to the provider's self-hosted Aptabase instance.

There is one optional feature that changes this. If you switch on "Also notify when the app is closed" for an account, MergeTap's notification server stores that account's credential, encrypted, and checks Azure DevOps for you every 15 minutes. For a GitHub account it checks GitHub the same way. It then sends your notifications through Google's Firebase Cloud Messaging, so the titles of pull requests and the names of projects pass through Google to reach your phone. This is off until you turn it on, it applies only to the account you turn it on for, and turning it off asks the server to delete what it holds. If the server cannot confirm the deletion, the app tells you.

If you never switch server notifications on, none of your pull request, build or deployment content is transmitted to the provider of this application, and the app never asks your phone for a push token. Anonymous usage analytics contains no such content.

Two further exceptions: buying a subscription, handled by Apple or Google and by RevenueCat, who tell us whether a subscription is active — never who you are or what you reviewed — and a crash report, sent only if the app crashes, to a self-hosted error-tracking instance the provider of this application runs themselves.

Controller

Responsible for data processing within the meaning of Article 4 (7) GDPR is Nicolas Mehlei, whose full details are in the imprint.

The provider processes the anonymous usage events described below on a self-hosted system. For an account you have registered for server notifications, we also process what is described under "Notifications when the app is closed" below. Your use of Azure DevOps is governed separately by Microsoft, and your use of GitHub by GitHub, Inc.; each acts as controller for the data held in your organization or repositories.

What is stored on your device

The following is written to storage on your device and nowhere else:

  • Access credentials — personal access tokens, tokens obtained through Microsoft sign-in, and tokens obtained through the MergeTap GitHub App — held in the operating system's secure credential store (Android Keystore, iOS Keychain).
  • Account and organization settings you have configured.
  • For an account registered for server notifications: the identifier MergeTap's server gave that registration, and a secret that proves the registration is yours. The secret is held in the secure credential store, and the app presents it when you switch the feature off or remove the account, to ask the server to delete the registration. The server also deletes a registration on its own if you replace that account's credential within the same organization, or if Google reports the push token as no longer valid.
  • Notification preferences, and the identifiers of commits you have already reviewed, so the app can tell you when a pull request has changed since you last looked at it.
  • Pull request, build and approval data fetched from Azure DevOps or GitHub, held only for as long as the screen showing it is open.

What leaves your device, and to whom

Requests go to Microsoft- and GitHub-operated endpoints authenticated with your own credentials, to our self-hosted Aptabase instance only if you enable anonymous usage analytics, to RevenueCat if you buy a subscription, to our own self-hosted crash-reporting instance if the app crashes, and to MergeTap's notification server only for an account you have registered for server notifications:

  • api.revenuecat.com
  • aptabase.nm-hosts.de
  • dev.azure.com
  • mergetap-relay.azurewebsites.net
  • vssps.dev.azure.com
  • vsrm.dev.azure.com
  • app.vssps.visualstudio.com
  • login.microsoftonline.com
  • api.github.com
  • github.com
  • *.actions.githubusercontent.com
  • *.blob.core.windows.net
  • bugsink.hapi.nm-hosts.de

Notifications when the app is closed

This section applies only to an account for which you have switched on "Also notify when the app is closed" in that account's settings, after confirming a message that describes it. For any other account, none of it happens.

What the app sends to MergeTap's notification server when you switch it on, and keeps up to date while it is on:

  • The account's credential: the personal access token, the Microsoft sign-in token, or the GitHub App token for that account. The server stores it encrypted and uses it only to read your pull requests, builds and approvals from Azure DevOps or GitHub on your behalf, about every 15 minutes.
  • A push token. The app requests this from your phone's operating system only for a registered account, and only then. It identifies your phone to Google's push service.
  • The name of your Azure DevOps organization or your GitHub login, your notification preferences, and the anonymous identifier RevenueCat uses for your installation, which the server uses to check whether your subscription is active.
  • Afterwards, the server sends each notification through Google's Firebase Cloud Messaging to reach your phone. The notification content, including the title of a pull request and the name of its project, therefore passes through Google. Google's privacy notice governs what it does with that; we do not control it.

Anonymous usage analytics

MergeTap uses Aptabase Plus on aptabase.nm-hosts.de, a server operated by the provider of this application. It records only that the app opened and which named screen was viewed, together with technical metadata the SDK adds such as app version, operating system, country, and build mode.

For each event, the SDK creates a random session identifier that expires after one hour of inactivity. The server necessarily receives the connection IP address and user agent; Aptabase uses them to derive country and a daily-rotating anonymous user identifier. The raw IP address is not included in the event data shown in Aptabase, and the app uses no device or advertising identifier.

The event schema is closed: account names, organization names, project names, pull request titles or identifiers, build data, comments, credentials, and route parameters are never included. Aptabase is configured only for product analytics; crash reporting remains with Bugsink.

Analytics is disabled by default. You can enable, disable, or re-enable this processing at any time under Settings → Share anonymous usage analytics. Disabling it stops and disposes the analytics client immediately.

Crash reporting

If the app crashes or hits an unhandled error, a report is sent to Bugsink, a crash-reporting instance the provider of this application runs and controls themselves — it is not a third-party service, and no data from it is shared with anyone else. The app uses the Sentry SDK to send these reports, configured to point at Bugsink rather than at Sentry's own service.

A crash report includes the error message, the code location it occurred at, the app version, and basic device/OS information needed to diagnose it. Personal access tokens, Microsoft Entra tokens and GitHub tokens are stripped before the report leaves your device.

Nothing is sent unless the app actually crashes or hits an unhandled error — there is no routine or background reporting.

If you buy a subscription

Payment is taken by Apple's App Store or Google Play, never by this application. We never see or handle your card details.

Purchases are managed through RevenueCat, a subscription service that validates the store's receipt and tells the app whether a subscription is active.

  • RevenueCat receives an anonymous identifier for your installation, the store receipt, and technical details of the device needed to validate it.
  • It does not receive your Azure DevOps or GitHub credentials, your pull requests, or anything else this app shows you — those never leave your device except to Microsoft or GitHub and, for an account you have registered for server notifications, to MergeTap's notification server.
  • If you never open the subscription screen and never buy anything, no purchase data is created.
  • RevenueCat acts as a processor on our behalf. Its own privacy notice is at https://www.revenuecat.com/privacy.

What we do not do

Stated explicitly, because these are the things users most often have to assume about an application:

  • No account identity, organization, project, pull request, build, deployment, comment, credential, or other work content in usage analytics.
  • No crash or error reporting to any third party — crash reports go only to our own self-hosted instance, see Crash reporting above.
  • No advertising, and no advertising identifiers.
  • No push token is requested, and no push service is involved, for an account you have not registered for server notifications. Their notifications are generated on your device. A push token is requested only when you switch on server notifications for an account.
  • No other use of a credential stored for server notifications: it is used only to read your Azure DevOps or GitHub data in order to notify you, and we ask the server to delete it when you switch the feature off or remove the account.
  • No sale of personal data, and no sharing of it for advertising.
  • No linking of purchase data to your Azure DevOps or GitHub identity or your work.

Legal basis

Processing on your device serves solely to provide the functions you have asked for, and rests on Article 6 (1) (b) GDPR — performance of a contract and steps taken at your request.

Storing credentials in the operating system's secure store is technically necessary to provide the service and is likewise covered by Article 6 (1) (b) GDPR.

Server notifications rest on your explicit consent under Article 6 (1) (a) GDPR, given when you switch the feature on and confirm the message shown. You can withdraw it at any time by switching the feature off; withdrawal does not affect anything done before.

Processing a subscription — validating a store receipt and keeping track of whether it is active — is performance of the contract you enter when you buy it, also Article 6 (1) (b) GDPR.

Anonymous usage analytics rests on your consent under Article 6 (1) (a) GDPR, given when you enable it in Settings. You can withdraw that consent at any time by switching it off; withdrawal does not affect events sent before then.

Retention and deletion

Data stored by the application remains on your device until you remove it. Removing an account deletes its stored credentials. Uninstalling the application removes everything the application has stored on the device.

For an account registered for server notifications, MergeTap's server also holds that registration until you switch the feature off or remove the account in the app, both of which ask the server to delete it. If the server cannot be reached at that moment the app tells you, and the server copy remains until the request succeeds. Uninstalling the app does not by itself delete the server copy; switch the feature off first. To have it removed in any other case, use the contact address in the imprint.

Anonymous Aptabase usage events are retained for no longer than five years and may be deleted earlier when they are no longer needed for product-usage analysis. Because they contain no account, device or advertising identifier, the provider cannot reliably identify which events belong to one person for an individual deletion request. Switching analytics off prevents new events.

If you have never switched server notifications on, the provider holds no notification registration or work content about you. Anonymous analytics events may still exist if you previously enabled analytics and events were sent.

Your rights

Under the GDPR you have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20), and to object to processing (Art. 21).

For data held by MergeTap's notification server, analytics processing, and any request concerning the application itself, use the contact address in the imprint. Anonymous analytics events contain no stable account or device identifier, so the provider may be unable to associate an individual event with you. Rights concerning Azure DevOps or GitHub data held by those services are exercised against the relevant organization and service operator.

You also have the right to lodge a complaint with a supervisory authority (Art. 77 GDPR), in the member state of your residence, place of work, or the place of the alleged infringement.

Permissions the app requests

Notifications — used to alert you about pull requests and approvals awaiting you: generated on your device, or, for an account you registered for server notifications, delivered through Google's Firebase Cloud Messaging. Declining this permission leaves every other function intact.

Network access — required to reach Azure DevOps.

Third-party services

Azure DevOps Services and Microsoft Entra ID are operated by Microsoft. Your use of them is subject to Microsoft's own terms and privacy statement, available at https://privacy.microsoft.com/privacystatement.

Google's Firebase Cloud Messaging carries notifications for accounts registered for server notifications. It is operated by Google under Google's own terms and privacy policy. MergeTap's notification server is hosted on Microsoft Azure.

Depending on your organization's configuration, Microsoft may process data outside the European Union. That processing is outside our control and is governed by Microsoft's agreements with your organization.

Changes to this notice

This notice was last updated on 22 October 2026. Where the application changes what it stores or whom it contacts, this notice is updated in the same change.

Stop being the bottleneck.

The review that blocks your colleague, and the deployment that blocks your release, both fit in the time it takes to make a coffee.

Get it on Google PlaySee pricing
MergeTap

Pull requests and deployment approvals from Azure DevOps and GitHub, on your phone. Built by one developer who kept missing approvals while away from a desk.

Product

What it doesAccountsPricing

Legal

Privacy noticeDelete your dataImprint

Contact

Email support
© 2026 Nicolas Mehlei · Wedel, GermanyNo account required. Your credentials stay on your device unless you switch on server notifications for an account.