Bridge

Privacy Policy

Effective 6 November 2026. Bridge is now provided by Diamobyte Software FZCO, which has taken over from Maciej Bajko.

Bridge (bridgemmp.com) is a mobile measurement service: it attributes app installs and purchases to the ads that brought them, and reports and acts on the results for the app developers who use it. Bridge is provided by Diamobyte Software FZCO, Dubai, United Arab Emirates (“we”, “us”). Contact: maciej.bajko@diamobyte.com.

Two kinds of people, two roles.

Tapped an ad and passed through bridgemmp.com? Your browser went through this domain on the way to the App Store or Google Play, so the app’s developer can tell which ad you came from. Section 5 says what was recorded and for how long. For questions or deletion, contact the developer listed on the store page of the app.

1. People who sign in to the console: what we collect

2. Why we use it, and on what basis

3. Cookies and similar technology in the console

The console uses three strictly necessary cookies: bridge_session keeps you signed in, for up to 30 days; bridge_ws remembers the workspace you last opened, for up to a year; and bridge_auth_msg carries the message to show after a refused Google sign-in, for two minutes. It also uses your browser’s local storage for preferences such as the theme and the last page you opened. There are no advertising or analytics cookies in the console. The payment pages that open when you add a card or pay an invoice are run by Stripe, which uses its own cookies there.

4. How long we keep it

Account details for as long as your account exists, and a workspace’s billing details and invoice records for as long as the workspace exists. A workspace cannot be deleted while it has unpaid invoices. Deleting one also removes its saved card from Stripe, which keeps its own records of invoices and payments as financial rules require. You can delete your account yourself, from Your account in the console, or an admin can remove you; either way your account, its access and its AI assistant connections are deleted at once. Activity logs, which record what an account did, are kept after that for security and accountability and deleted after about 25 months. One-time links expire after an hour to seven days.

5. Data processed on behalf of our clients

What follows depends on how each client sets Bridge up. The client is responsible for telling its users about it, for any consent required, and for its lawfulness.

DataWhat it is used for
Ad click data when someone follows a client’s ad link through Bridge: time, the ad’s identifiers (campaign, ad set, ad, placement, click identifiers such as Meta’s fbclid and browser identifiers), the landing address and its campaign parametersKnowing which ad a person came from
Network and device signals from that click: IP address, network provider, approximate location (country, region, city) derived from it, browser user agent, operating system version, and coarse device characteristics (screen size, time zone, language preferences)Matching an install to the click that led to it; detecting relays and VPNs
App install and identity signals sent by the client’s app: an app-specific user identifier, the device’s vendor identifier (iOS) or, on Android, the install referrer and, where the client’s app provides it, the advertising identifier; device model; and, if the client’s app sends an email address, its hash (the email itself is hashed on arrival and never stored)Matching installs and purchases to clicks
Purchase events from the client’s subscription provider (such as RevenueCat): the app user identifier, product, price, currency, revenue, trial and renewal status, and Apple Search Ads attribution where available Measuring revenue and return on ad spend

Bridge does not read the iOS advertising identifier (IDFA), does not collect names, phone numbers, contacts or precise location, does not sell personal data or share it with data brokers, and does not use it for its own advertising or to build profiles. None of these identifiers follows a person between different apps.

Sent to advertising platforms on the client’s instruction

When a client connects an advertising platform, Bridge sends conversion events there for the client, under the client’s own agreement with that platform. For Meta’s Conversions API this can include the click and browser identifiers, the browser user agent, the IP address (only if the client turns that on), a hashed app user identifier and hashed approximate location. For Google it can include app and conversion identifiers. The client chooses which platforms receive data.

How long it is kept

A client can ask us to delete its data earlier, or all of it when it stops using Bridge.

6. Who else handles data

These providers may process data outside your country, including in the United States. Where required, transfers rely on safeguards such as the European Commission’s Standard Contractual Clauses offered by those providers.

7. Security

Data is sent over encrypted connections; passwords and one-time links are stored only as hashes; access tokens for connected platforms are encrypted at rest; IP addresses are hashed with rotating salts; and access to each client’s data is limited to the people the client has invited. No system is perfectly secure, and we cannot guarantee the security of data sent to us.

8. Your rights

Depending on where you live (for example under the EU and UK GDPR, the UAE Personal Data Protection Law, or Californian law), you may have the right to access, correct, delete or receive a copy of your personal data, to restrict or object to its use, and to complain to a data protection authority. Console users can write to us at maciej.bajko@diamobyte.com. Users of an app measured with Bridge should contact that app’s developer, who controls their data; we will help the developer respond.

9. Children

The console is for business use and not intended for children. Clients whose apps are used by children are responsible for meeting the laws that apply to them before using Bridge with those apps.

10. Changes

We may update this policy. The date above shows when it last changed; significant changes will be announced in the console.

11. Contact

Diamobyte Software FZCO, Dubai, United Arab Emirates · maciej.bajko@diamobyte.com