Data Export, Retention, and Backups

Verified account owners may request a copy of their account data, profile data, care-team links, notes, routines, reports, and other reasonably exportable information. Bridge may require identity verification, authority confirmation, organization approval, or guardian/professional authorization before releasing data about another person.

Verified users may request correction or deletion where legally available. Some information may be retained where necessary for security, safety, audit logs, legal obligations, dispute resolution, professional/organization records, backup integrity, or compliance with applicable law.

Bridge should maintain database backups through its infrastructure provider, including routine backup snapshots and restoration procedures appropriate to the production plan. Backups are intended for disaster recovery, security, continuity, and accidental-loss protection—not for routine user browsing. Deleted data may remain in backups for a limited period until backup expiration.

• Review backup status before each production launch and after major schema migrations.
• Restrict database and backup access to authorized administrators only.
• Log administrative exports and restoration events where technically available.
• Test restoration procedures periodically before relying on production data at scale.
• Do not use production exports for development unless de-identified or approved under policy.

Bridge aims to acknowledge verified export, correction, or deletion requests within a reasonable period and respond within timeframes required by applicable state, federal, organizational, or contractual law. Complex requests, child/dependent records, provider records, and legal exceptions may require additional review.