Privacy Policy
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.
- People who sign in to the Bridge console (our clients and their team members): we decide what is collected about them, and are responsible for it as the controller. Sections 1 to 4 below.
- Users of our clients’ apps, and people who click their ads: the app developer (our client) decides what is collected and why, and is the controller. We process that data only on the client’s behalf and on its instructions, as its processor (or service provider). If you use an app measured with Bridge, the app’s own privacy policy applies to you, and requests about your data should go to its developer. Section 5 below describes what Bridge processes for them.
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
- Account details: your name, email address, role, and the apps you can access; if you set one, a password, which we store only as a salted cryptographic hash (never the password itself).
- Google sign-in: if you use it, the identifier of your Google account and its email address. We receive only your basic profile (name, email); we never receive your Google password or access to your Google data.
- Invitations and links: who invited you, when, and one-time links for invitations, password resets and confirming an email address (stored only as hashes).
- Activity: when you sign in, and a log of actions taken in the console and through connected AI assistants (for example, a budget change applied or an ad created), kept for security and accountability.
- Billing details: for a client’s workspace, its plan and prices, its invoices and whether they were paid, the email address its bills go to, its Stripe customer reference, and the brand and last four digits of its saved card. Card numbers are entered on Stripe’s own pages and never reach Bridge.
- Connected AI assistants: when you connect an assistant such as Claude to Bridge, a record of that connection and the tokens that authorise it (stored as hashes).
- Technical data: our hosting provider processes your IP address and browser details to deliver the service and protect it from abuse. Bridge does not store your IP address with your account.
2. Why we use it, and on what basis
- To provide your account and the service you or your organisation signed up for, and to bill for it where fees apply (performance of a contract).
- To keep the service secure: authenticating you, limiting repeated failed sign-ins, investigating misuse, and keeping an audit trail (our legitimate interests in a secure service).
- To send you service emails: invitations, password resets and address confirmations; invoices and payment reminders; notices about access to a workspace or its limits; and alerts about ads Bridge starts or stops on a schedule. We do not send marketing.
- To meet legal obligations where they apply.
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.
| Data | What 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 parameters | Knowing 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
- Ad clicks: 90 days. The IP address in its original form: at most 30 days; after that only as a salted hash, whose salts are rotated weekly and deleted after 90 days.
- When a click led to an install, its device characteristics and hashed IP are erased at 90 days as well, but its click identifier, campaign, browser user agent and approximate location stay with the install record, so later purchases can still be credited to the right campaign.
- Device signals on installs (vendor identifier, device model, hashed IP): removed after about 95 days.
- Installs and purchase events: about 25 months (two years and a month), then deleted.
- Responses from advertising platforms: 30 days.
A client can ask us to delete its data earlier, or all of it when it stops using Bridge.
6. Who else handles data
- Cloudflare hosts Bridge, its database and storage, delivers its emails, and protects it from attacks.
- Anthropic (Claude) writes Bridge’s campaign analyses. It receives totals by campaign and ad (spend, installs, trials, revenue, countries), their names, and the client’s app descriptions, never data about an individual app user.
- Stripe handles payments. It receives a workspace’s name, the email address its bills go to (or an admin’s), and each invoice’s amounts and lines. It collects the card, billing address and tax details entered on its own pages, under its own privacy policy. It receives no data about the users of a client’s apps.
- Google, when you sign in with Google.
- The platforms a client connects (for example Meta, Google, Apple via RevenueCat, Figma), as described in section 5, under the client’s own agreements with them.
- An AI assistant you connect, such as Claude, receives what it asks Bridge for on your behalf, within your access, under your own agreement with its provider.
- Authorities, where we are legally required to disclose information, and a successor if the service is transferred.
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