DiveBridge Privacy Policy

Effective October 27, 2026

DiveBridge helps a diver review and transfer selected Garmin dive activities into the diver's PADI web logbook. This policy describes the information the extension handles, why it is needed, where it goes, and how it is retained.

Information handled

DiveBridge handles the minimum data needed for its import workflow:

• a user-created, revocable Garmin Personal API key and short-lived bearer tokens;
• Garmin dive summaries, selected FIT archives, dive metrics, and optional coordinates;
• the active PADI browser-session token already maintained by PADI Learning;
• recent PADI log summaries needed for duplicate detection;
• reviewed dive fields sent to PADI only after confirmation; and
• the user's preferred Boat/Shore entry type.

Use

Information is used only to find Garmin dives, compare them with the live PADI logbook, let the user review them, and create only the recreational PADI logs the user explicitly confirms. It is not used for advertising, marketing profiles, creditworthiness, lending, analytics, or any unrelated purpose. DiveBridge does not sell user information.

Storage and retention

The Garmin key and Boat/Shore preference are stored in extension-local browser storage. The user can remove them by disconnecting Garmin, clearing extension storage, revoking the key, or uninstalling DiveBridge. Garmin bearer tokens, PADI session tokens, duplicate rows, FIT archives, parsed profiles, and active fingerprints remain only in memory while needed. DiveBridge does not maintain duplicate history.

Transmission and sharing

At the user's direction, DiveBridge communicates over HTTPS directly with Garmin at personal.connectapi.garmin.com and with PADI at learning.padi.com and divelog.global-prod.padi.com. There is no DiveBridge application server, database, analytics service, advertising network, or cloud copy of the user's dives. The developer therefore does not receive or retain keys, tokens, dive profiles, or PADI logs.

Public policy and support pages

The public DiveBridge policy and support pages are static and receive no extension data. Their hosting provider may process ordinary request metadata, such as an IP address, under the provider's own privacy policy. This is separate from the extension's Garmin-to-PADI workflow.

Human access

The developer cannot access information processed locally by the extension. A human will not read user information unless the user deliberately supplies specific information for support and consents to that access, or access is necessary for security or legal compliance.

Security

Provider communications use HTTPS. DiveBridge requests only the Garmin and PADI access required for its stated functionality, contains no remote executable code, and does not request broad browsing access. The read-only Garmin key is revocable but should still be treated as a secret.

User choices

Users control each lookup and import. PADI is changed only after confirmation. Users can exclude dives, save drafts, disconnect Garmin, revoke the key, clear extension storage, or uninstall DiveBridge. PADI logs already created are controlled through PADI.

Third-party services

Garmin and PADI process information under their own terms and privacy policies. DiveBridge is independent and is not affiliated with, sponsored by, or endorsed by Garmin or PADI.

Children

DiveBridge is not directed to children and does not knowingly collect children's information for the developer.

Changes and contact

This policy may be updated when behavior or legal obligations change. Material data-practice changes will be disclosed before they take effect. For questions or privacy requests, use the verified developer contact shown on DiveBridge's Chrome Web Store listing.