Roboflow
Roboflow · Data analysis · US · roboflow.com
services/roboflow.yamlVendor data-handling terms
The policy does not state whether uploaded images, datasets or annotations (User Content) are used to train Roboflow's own models.
“To ensure that content from the Websites and Mobile Apps is presented in the most effective manner for you and for your computer and to understand and analyze your usage trends and preferences, to improve our services, and to develop new products, services, and features”
“We retain your information for so long as it needs to be kept for legitimate business or legal purposes. / Without limiting the foregoing, at minimum, we retain your data for so long as you are engaged in Active Use, as hereinafter defined, of the Websites and Mobile Apps.”
“We may process data both inside and outside of the United States and will rely on legally-provided mechanisms to lawfully transfer data across borders. / In many cases, we will use European Commission-approved Standard Contractual Clauses as a legal mechanism for data transfers from the Designated Countries.”
Domains and endpoints
observed means seen in Unseen deployments; vendor-documented means listed by the vendor. Vendors do not publish complete lists.
| Host | Role | Source |
|---|---|---|
| api.roboflow.com | api | observed |
| roboflow.com | app | observed |
Assessment
Reasoning: A computer-vision platform where users upload images and datasets. The policy covers usage data and retention but does not state whether uploaded content trains Roboflow models, and names no hosting region. Uploads of images from production sites or internal documents need a contract that settles both.
Flags: Training-use of uploaded images and datasets not stated · Storage region not stated · Assessed 2026-09-16. The assessment is Unseen's; the terms above are the vendor's.
Changelog
- 2026-09-16Documented. Retention and transfer terms verified against the Roboflow privacy policy; training-use of uploads not stated.
- 2026-09-15Listed from the Unseen catalogue with observed domains.
Corrections
Pull request on GitHub, or the form below. Changes are reviewed and recorded in the changelog.