This notice explains what MDB Mobile collects, how it's used, and who it's shared with. It covers the MDB Mobile iOS app and the internal web application it displays.
Effective date: September 9, 2026
Applies to: Miami Dolphins football operations staff and other authorized users
Distribution: Private, via Apple Business Manager — not on the public App Store
At a glance
Who can use it?
Authorized club staff, signed in with a Dolphins Okta account
Where it works?
Only on the club's corporate network (VPN)
Advertising or tracking?
None — no ad SDKs, no analytics, no cross-app tracking of any kind
Selling data?
Never
Who sees your account activity?
The club's own systems, plus Okta (sign-in) and Microsoft Teams (error alerts)
Questions?
See Contact Us, below
Who this notice is about
MDB Mobile is an internal tool for football operations — roster, transactions, scouting, and related workflows. Three groups of people appear in it, and this notice covers all three, even though only the first group actually uses the app.
Uses the appClub staff
- Corporate sign-in identifier
- Role and access permissions
- Saved preferences
- Scouting reports and comments you author
- Access records (see "Diagnostics," below)
Appears in the appPlayers
- Name, position, roster and depth-chart status
- Transaction and injury information
- Scouting reports and comments authored by staff
Appears in the appPlayer agents
- Directory and contact information
- Notes authored by staff
- Client lists
Signing in
MDB Mobile does not have its own username or password. You sign in with your existing Dolphins Okta account — the same one used across other internal club systems — and Okta handles authentication on the club's behalf. MDB Mobile never sees or stores your Okta password.
Because the app is restricted to the club's corporate network, it will not load outside the office or off the corporate VPN, regardless of who is signed in.
What we collect, and why
About you, to run your account: your Okta sign-in identifier, your assigned role and permissions, and any preferences you save (like a default club view). These exist so the app knows who you are and what you're allowed to see.
What you create, attributed to you: scouting reports and comments you write about players are stored and linked to your account, the same way they would be in a shared team document. They are visible to other staff with the appropriate permission.
About players and agents: roster, transaction, depth-chart, and injury information, plus staff-authored reports and notes, all held in the club's personnel systems — the same records used across football operations, not something MDB Mobile creates on its own.
Diagnostics — how we find and fix problems
Like any internal system, MDB Mobile keeps basic operating records: every request to the server is logged with a timestamp and the page or action requested, so engineering can diagnose issues. These logs are kept for 90 days, then automatically deleted.
When something breaks unexpectedly, an alert is posted to an internal Microsoft Teams channel monitored by the engineering team. That alert includes the signed-in username, the page that failed, and technical error details — so a problem can be traced to what happened, without staff needing to file a ticket. These alerts are retained under the club's standard Microsoft 365 retention policy, the same as any other Teams message.
Voice search
If you search for a player by speaking to Siri, the audio is transcribed by Apple, under Apple's own terms, before MDB Mobile ever receives it — the app only receives the finished text of your search, never a recording.
What MDB Mobile does not do
No analytics - No usage or product analytics tools of any kind.
No advertising - No ad networks, no ad identifiers, no marketing pixels.
No cross-app tracking - Nothing about your use of MDB Mobile is shared for tracking across other apps or sites.
No device access - No access to your camera, microphone, photos, contacts, or location.
No selling data - Information is never sold or shared with data brokers.
No public exposure - The app and its data are reachable only from the club's corporate network.
On your device
Signing in stores an authentication token on your device so you don't have to sign in every time you open the app. This — along with everything else the app stores locally — is removed automatically if you delete MDB Mobile from your device.
Who we share information with
MDB Mobile shares information with two outside services, both acting on the club's behalf, never as independent recipients of your data:
- Okta — to authenticate your sign-in.
- Microsoft (Teams) — to deliver the error alerts described under Diagnostics, above.
Beyond these, information stays within the club's own systems.
Your rights and choices
Because MDB Mobile is an internal tool tied to your employment or engagement with the club, questions about your information — including requests to review, correct, or ask about data held about you — should go to the contact below rather than through the app itself.
This notice is governed by United States law. Staff, players, and agents covered by MDB Mobile are based in the United States; occasional international travel doesn't change that.
Changes to this notice
If this notice changes in a way that affects what's collected or how it's used, we'll update the effective date above. Continued use of MDB Mobile after a change means you've had the chance to review it.
Contact Us
Questions about this notice or your information in MDB Mobile:
Email: TCComplianceMD@dolphins.com
Mail: Miami Dolphins, Ltd., 347 Don Shula Drive, Miami Gardens, FL 33056