Provision record
RapidAPI · RapidAPI Privacy Policy · View original document ↗

Retention criteria based on relationship length and legal obligation

Common · 268 of 343 platforms
Stay ahead of the changes
Track RapidAPI and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Share 𝕏 Share in Share 🔒 PDF
ⓘ

This analysis describes what RapidAPI'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

How other platforms handle this

StockX

We use the following criteria to determine retention periods: how long the information is needed... whether there are contractual or legal obligations... whether the data is considered to be sensitive data.

Kling AI

We may retain some of your Data even after you cease to use our Services, for instance if the Data is necessary to meet our legal obligations, such as tax and accounting requirements.

Teladoc

Where specific retention periods are required by law, we comply with those timeframes; otherwise, we apply the criteria above to determine how long to retain the information.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
The criteria used to determine our retention periods... include such factors as (i) the length of time we have an ongoing relationship with you... (ii) whether there is a legal obligation... (iii) whether retention is advisable

Excerpt from RapidAPI's Privacy Policy

Provision details

Document information
Document
RapidAPI Privacy Policy
Entity
RapidAPI
Date stated by the document
Aug. 8, 2025
As printed in RapidAPI’s text (version CA-V-001318), not a ConductAtlas date.
Tracking information
First captured by ConductAtlas
May 5, 2026
Text quoted from version
CA-V-001318, captured May 5, 2026
Record ID
CA-P-054483
Document ID
CA-D-000680
Evidence Provenance
Source URL
Wayback Machine
Extracted-text SHA-256 (version CA-V-001318)
4e5b0fbe8389135315e61e28eedccb1df3a157d733b27725b8859f16705a4f7a
Analysis generated
May 7, 2026 06:40 UTC
Methodology
Evidence
✓ Excerpt found in version CA-V-001318, captured May 5, 2026 (checked Oct. 5, 2026)
Citation Record
Entity: RapidAPI
Document: RapidAPI Privacy Policy
Record ID: CA-P-054483
Version: CA-V-001318
Captured: 2026-05-05 06:37:31 UTC
SHA-256: 4e5b0fbe83891353…
URL: https://conductatlas.com/platform/rapidapi/rapidapi-privacy-policy/provision/CA-P-054483/retention-criteria-based-on-relationship-length-and-legal-obligation/
Accessed: Nov. 10, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Categories

Other risks in this policy

Get the weekly coverage letter

Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.

Frequently Asked Questions

What does RapidAPI's Retention criteria based on relationship length and legal obligation clause do?

The clause states: “The criteria used to determine our retention periods... include such factors as (i) the length of time we have an ongoing relationship with you... (ii) whether there is a legal obligation... (iii) whether retention is advisable”

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 268 platforms. See the full comparison.

Is ConductAtlas affiliated with RapidAPI?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by RapidAPI.