Get the weekly research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.
The policy states that Personal Information is retained based on operational, legal, tax, fraud prevention, dispute resolution, and legal defense factors, without specifying fixed retention periods for any data category, and notes that financial regulatory requirements may require extended retention.
This analysis describes what Mercury's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
The policy does not specify fixed retention timelines for any category of Personal Information, including biometric data, financial records, or audio and video recordings; this approach requires users and compliance teams to rely on Mercury's internal retention schedules rather than disclosed timeframes.
Interpretive note: The criteria-based retention approach without specific period disclosures may meet some jurisdictional requirements (CCPA) while falling short of others (GDPR specificity expectations, BIPA destruction timelines); actual compliance depends on Mercury's internal retention schedule implementation and applicable regulatory interpretation.
Under this provision, Mercury retains Personal Information for indeterminate periods based on multiple operational and legal factors; users cannot determine from this policy alone how long specific data categories such as biometric identifiers, financial records, or call recordings will be held.
Cross-platform context
See how other platforms handle Data Retention Framework and similar clauses.
Compare across platforms →Monitoring
Mercury has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"We retain Personal Information only as long as necessary, and use the following factors to determine the retention period: Provide and maintain our Services Comply with legal and regulatory obligations Meet tax, accounting, and financial reporting requirements Prevent fraud and maintain security Resolve disputes and enforce our agreements Establish, exercise or defend our legal rights Because Mercury operates in a regulated financial environment, certain information may be retained for extended periods as required by law or industry standards.Excerpt from Mercury's Privacy Policy
1) REGULATORY LANDSCAPE: GDPR Article 5(1)(e) requires that personal data be retained no longer than necessary for its processing purpose, and European data protection authorities have enforced specific retention schedule disclosure obligations. CCPA and similar U.S. state laws require disclosure of retention periods or criteria for determining them. GLBA and related financial regulations impose minimum retention periods for financial records, which may conflict with deletion rights under state privacy laws. Illinois BIPA requires specific retention schedules and destruction timelines for biometric data. 2) GOVERNANCE EXPOSURE: Medium. The absence of specific retention periods for any data category, particularly biometric data subject to BIPA and audio recordings, creates potential compliance exposure in jurisdictions that require disclosed retention schedules. The general criteria-based approach may satisfy CCPA's disclosure standard but may not meet GDPR's specificity expectations or BIPA's destruction timeline requirements. 3) JURISDICTION FLAGS: Illinois BIPA requires that biometric data be destroyed within three years of collection or when the initial purpose is fulfilled, whichever comes first; this policy does not disclose a biometric-specific retention period. EEA and UK users under GDPR have the right to request erasure where data is retained beyond the necessary period. California residents may request the specific retention period or criteria for their data categories. 4) CONTRACT AND VENDOR IMPLICATIONS: Service providers and business partners receiving Personal Information should have data processing agreements that align with Mercury's retention criteria and specify deletion or return obligations upon contract termination. Biometric data shared with identity verification service providers should be governed by BIPA-compliant destruction timelines in vendor agreements. 5) COMPLIANCE CONSIDERATIONS: Legal teams should develop and document category-specific retention schedules for internal compliance purposes, particularly for biometric data, audio and video recordings, financial records, and marketing data. These schedules should be made available to users upon request consistent with CCPA disclosure obligations. The retention framework should be audited against GLBA, BIPA, and GDPR requirements to identify any gaps between the policy's general criteria and applicable legal minimums or maximums.
The policy does not specify fixed retention timelines for any category of Personal Information, including biometric data, financial records, or audio and video recordings; this approach requires users and compliance teams to rely on Mercury's internal retention schedules rather than disclosed timeframes.
Under this provision, Mercury retains Personal Information for indeterminate periods based on multiple operational and legal factors; users cannot determine from this policy alone how long specific data categories such as biometric identifiers, financial records, or call recordings will be held.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Mercury.