Data handling
How Vision handles input images, and what to keep in mind when adding image processing to your application.
Input images
Tigrate processes Vision input images during the request and does not store those input images. This statement applies to the Vision APIs described here.
Processing providers
Requests are delivered through RapidAPI and may use downstream processing providers. A response may identify a provider. Processing without image storage by Tigrate does not mean the image stays on the user’s device or inside your AWS account.
If your integration needs specific processing locations, contractual retention terms, or provider details, contact us before sending production data.
Face comparison scope
The face comparison endpoint performs 1:1 comparison of supplied images. It does not provide a 1:N face-search database. Face comparison is also distinct from facial liveness, which is planned separately.
Your application’s responsibilities
Explain image processing in your own product flow, collect the permissions appropriate to your use, and control access to results. Avoid putting images and extracted fields into analytics, error trackers, or application logs by default.
Other Tigrate products
Rebound stores uploaded educational content for its own features and has a separate privacy policy. The website privacy policy covers this company website. Neither should be substituted for product-specific data handling.