← In My Pocket Labs

App privacy

TheBridge Recovery App Privacy Notice

Effective October 5, 2026

This notice applies to the TheBridge Recovery mobile application. It is separate from Bridge Recovery’s website privacy policy.

Who operates the app

The app is published and technically operated by In My Pocket Labs LLC for Bridge Recovery. Bridge Recovery provides the programs and information shown in the app, and authorized Bridge Recovery staff use organization records to coordinate check-ins, events, transportation requests, and Coach callback requests. In My Pocket Labs LLC operates the app technology and hosted service.

What the app does

The app provides Bridge Recovery information and lets adults view meetings and published events, submit a private event RSVP, check in for a visit, request transportation when Bridge has enabled ride availability, and request a callback from a peer recovery coach. It provides recovery-community information and coordination. It does not provide diagnosis, medical advice, treatment recommendations, emergency response, or a guaranteed ride.

Information the app processes

Private guest session

The app creates an authenticated guest session with its hosted service. The service assigns a persistent guest identifier and uses request identifiers to associate your check-ins, RSVPs, ride requests, Coach callback requests, and privacy requests with your app session, prevent duplicates, limit abuse, and return only your own request status. You do not create a named public profile, but this identifier is still data associated with your use of the app.

First-use choices saved on your device

At first use, you may enter an optional name, phone number, and email address and choose update preferences. The app saves these first-use choices on your device so it can remember them. This first-use step does not send those details to Bridge or the hosted service, and choosing an update preference alone does not activate messages. If you later separately submit a check-in, RSVP, ride request, or Coach callback request, the information in that form is sent to Bridge’s hosted service as described below.

Visit check-ins

A check-in can include the visit date and time, whether you chose an anonymous check-in, the reason selected for the visit, and optional name, email address, and phone number. If you choose an anonymous check-in, the app omits those optional contact fields from the submitted check-in. Authorized staff may use check-ins for Bridge operations and protected reporting.

Event RSVPs

An RSVP includes the event, whether you are interested, going, or cancelling, and optional name and email address. Your RSVP is private from other attendees. Authorized Bridge staff can view attendance information needed to operate the event.

Peer recovery coach callback requests

When you tap Send in the Coach form, the app saves your name, phone number or email address, preferred location in Cleveland or Dahlonega, workable weekdays and time of day, optional brief note, and agreement to be contacted in Bridge’s private hosted request system. The request is linked to your authenticated guest session and remains saved after you close the app or if an email alert is not sent. Authorized Bridge staff use it to review your request and arrange follow-up.

The app keeps a random request number on your device so it can retrieve your request status. The hosted service also records submission times and email-delivery attempts and results to show status and prevent duplicate sending. Email-service acceptance means accepted for sending; it does not confirm arrival in Bridge’s mailbox, staff review, a callback, or resolution. Sending a Coach request does not book an appointment or guarantee a callback time. Please leave medical and treatment details out of the optional note.

Optional private Coach-request updates

In version 1.7.0 and later, you can separately choose “Enable private updates” on the Coach screen. Agreeing to a callback does not enable these notifications. If you choose private updates and grant notification permission, the app registers a device identifier, native push token, platform provider, and enabled preference through your authenticated guest session with Bridge’s hosted service. On iOS the identifier is the app vendor identifier and delivery uses Apple Push Notification service; on Android the app uses an Android device identifier and Firebase Cloud Messaging token.

This registration supports generic updates about your own Coach request and appointment status when the relevant delivery service is enabled. It does not establish that delivery is currently available or guarantee that a notification will arrive. Notification content is designed to avoid contact, recovery, and appointment details on the lock screen; opening an update retrieves your own protected status in the app. Turning private updates off disables that device’s Coach-update eligibility. Revoking notification permission in device settings prevents the operating system from displaying notifications but is separate from disabling the hosted registration. Device-registration and delivery records follow the operational retention and deletion process described below. These identifiers are used for this requested service, not advertising or cross-app tracking.

Ride requests

A ride request can include your contact name; optional phone and email; selected contact method and consent; pickup and destination descriptions, including confirmed map coordinates in versions with ride-map selection; requested date and arrival or return times; whether the request is round trip; passenger count; practical accessibility needs; app-push, text, and email notification preferences; request status; and coordination notes. A request is not a guaranteed ride. Authorized Bridge staff review requests and can approve, decline, cancel, or update them.

In version 1.6.0 and later, before sending a ride request, the app saves its original details and a random request reference on your device so you can check an interrupted submission without creating a duplicate request. This local pending copy remains until the app receives a confirmed request receipt and verifies that the local copy has been removed. An unconfirmed response or unsuccessful local removal can leave the copy saved. Opening the screen does not automatically submit it again; choosing to check the pending request uses its original details and reference. The app can also show your own staff-confirmed dates and times and appointment status.

Optional ride-status push notifications

If ride-status app push is available on your platform and you explicitly turn it on, the app asks for notification permission. It then registers a stable device identifier and that device’s native push token through the authenticated guest session. Android uses a Firebase Cloud Messaging token. The iOS app can register an Apple Push Notification service token after permission and consent; iOS delivery is enabled only after that service connection has been verified. The hosted service uses the guest identity, device identifier, token, platform provider, and current ride preference to make only that consenting device eligible for relevant ride-status updates.

Eligible Android updates are delivered through Google Firebase Cloud Messaging. When iOS delivery is enabled and verified, eligible iOS updates are delivered through the Apple Push Notification service. Both use neutral lock-screen wording—“Your request has an update”—and do not include ride, recovery, pickup, destination, or location details. Tapping the notification opens the app’s ride-status screen. Push delivery is best-effort and is not guaranteed. Turning the in-app push choice off revokes that exact device registration and removes it from eligibility for later ride-status push notifications.

Published content and directions

The app downloads published event details and ride-availability settings from its hosted service. If you choose a directions button, the app passes the published destination address to the selected Apple Maps or Google Maps service in a secure web link. The app does not include your device coordinates in that link. The selected maps provider processes that interaction under its own terms and privacy policy.

One-time foreground location

Location behavior varies by app version. In predecessor versions with a meeting-location option, the iOS and Android apps may request foreground location after you choose it; the position is read once and discarded, and the displayed meeting list is not ranked or filtered using it. In the corrected successor, the Meetings screen does not request location and shows source-verified regional snapshots filtered by time. Across versions, optional Check-In location is requested only after you turn on the preview and tap “Use current location”; coordinates and device-reported accuracy remain on the device and are omitted from the submitted Check-In. The Check-In preview is separate from the optional ride-location feature below. The app does not request background location or continuously track you.

Optional ride pickup and destination maps

In app versions that offer ride-map selection, you can choose “Use my current location” for a one-time foreground position, search for a place, or place and adjust a pin on a map. The app asks for location permission when you request your current position; Android may also require foreground permission for place search. You can decline and use a map pin or type an address instead. Search text, map areas, and reverse-address lookups are processed by your phone’s map/location services under the applicable Apple or Google terms and privacy policy.

A location is added to your ride form only after you confirm it. When you submit the ride request, the chosen pickup and destination descriptions and coordinates are saved in Bridge’s private hosted request system, linked to your guest session, and made available to authorized staff for arranging that ride. The pending-request copy on your device includes these confirmed details as described above. Canceling the location picker does not change the ride form. This feature does not continuously track you or the driver.

How information is used

  • Provide the check-in, RSVP, event, ride-request, Coach callback, privacy-request, and request-status features you choose.
  • Let authorized staff coordinate events and transportation requests, review Coach callback requests, and arrange follow-up.
  • Protect request ownership, prevent duplicate submissions, limit abuse, and maintain security.
  • Operate protected Bridge reports and correct operational records.
  • Meet a documented applicable legal or recordkeeping necessity.

Hosted services and exports

The app sends hosted application requests over HTTPS to Supabase infrastructure in the United States. Supabase provides authentication, application-service, database, and hosting functions. Supabase describes its data-processing role in its Data Processing Addendum.

The current service uses Google Firebase Cloud Messaging on Android for ride-status push notifications on devices that have explicitly opted in. Optional Coach-request updates use the same platform providers when the separate Coach delivery service is enabled and the device has opted in. The iOS app is configured to use the Apple Push Notification service only after iOS delivery has been enabled and verified. Google or Apple processes the registered device token and delivery request for the applicable enabled platform to provide that service. The app has no active external SMS, calendar, driver-dispatch, analytics, crash-reporting, advertising, payment, chat, or clinical-record service.

When Coach email alerts are enabled, In My Pocket Labs uses Google to send a copy of your submitted name, contact details, preferred location, availability, optional note, and request identifier from apps@inmypocketlabs.com, using the name Bridge Recovery, to Bridge Recovery at daniel@bridgerecovery.org. If you provide a valid email address, it may be included as Reply-To so Bridge can respond; your address is not used as the sender address. Google processes the message for email delivery. Message copies or delivery records may remain in the sending account, provider systems, and Bridge’s receiving mailbox. In My Pocket Labs does not control Bridge’s mailbox retention. An email provider’s acceptance is not proof of arrival in that mailbox.

Authorized Bridge staff can download organization records as CSV files. Once downloaded, that copy is under the receiving organization’s control and may not follow the hosted database’s backup lifecycle. Requests concerning an exported copy are coordinated with Bridge Recovery.

Retention

Guest-session identifiers and member records are retained only for as long as reasonably needed to provide the requested feature, maintain accurate organization and security records, resolve disputes, prevent duplicate or abusive requests, and meet a documented applicable legal or recordkeeping necessity. When information is no longer needed for those purposes, authorized operators delete or anonymize it through the applicable operational process. Different records may be kept for different periods because active requests, completed records, and security records serve different purposes. This is not an indefinite blanket exception.

Coach requests are retained while needed for follow-up and the operational, privacy, security, or documented recordkeeping purposes described above. Email-delivery status is separate from staff follow-up and resolution. There is no automatic fixed-day deletion schedule for Coach requests. Removing the hosted request does not automatically remove email copies, exports, provider delivery records, or backups; those copies may follow separate retention and deletion processes.

The hosted service uses daily physical database backups. The provider documents a seven-day accessible daily-backup window for the current plan, and point-in-time recovery is disabled. Deletion from the active database may not immediately remove a copy from an existing backup. Backup copies age out under the provider’s backup lifecycle unless a documented applicable necessity requires otherwise. Staff-downloaded CSV copies are separate and are addressed above.

Cancelling an RSVP or ride request changes its status; it does not itself delete the underlying record.

Your choices and requests

You may omit fields the app marks optional. Some information is required to submit and coordinate a ride request. You can cancel an RSVP or an eligible pending ride request from the app.

You can submit an access, correction, or deletion request in the app. The request creates a protected staff-review receipt; it does not erase records automatically. In My Pocket Labs coordinates verified requests through authorized tenant-scoped administration and with Bridge Recovery when organization records or exported copies are involved. Enough information may be required to locate the guest session or submitted record and verify that the requester is authorized to act on it.

You can use the in-app privacy-request feature for a Coach callback request. It creates a protected staff-review receipt, not automatic deletion. Hosted-record removal and follow-up for email copies, exports, provider records, and backups are considered separately. In My Pocket Labs coordinates with Bridge Recovery and the applicable provider as needed, and explains confirmed removal and any remaining retention limits when responding to your request.

A documented applicable security, dispute-resolution, legal, or recordkeeping necessity may limit deletion of a specific record. This is not an indefinite blanket exception. Backup copies may remain until they age out under the provider’s backup lifecycle.

Security

The app sends hosted requests over HTTPS/TLS and restricts member records by authenticated guest identity and staff records by staff authorization. No system can guarantee absolute security.

Children

The app is intended for adults age 18 and over and is not directed to children. A verified request concerning inadvertently submitted information uses the same coordinated handling process described above.

Changes

We may update this notice when app features, providers, or legal requirements change. The current effective date appears above.

Contact

For questions or requests to access, correct, or delete personal information, email daniel@inmypocketlabs.com. Please provide only the information reasonably needed to locate your request. Do not send passwords, access tokens, or unrelated sensitive information by email.