Enterprise data

Data Processing Overview

A practical overview of the data path, customer responsibilities, provider variation, and enterprise review.

Last updated: 2026-08-28

How a request moves

Your application sends a request to HippoAPI, which authenticates the key, applies account and model controls, routes the request to the selected model service, and returns the resulting response.

Technical logs may record identifiers, model, token or media usage, timing, status, and error information needed for billing, security, and troubleshooting.

Model and provider differences

Data handling, location, retention, and subprocessors can differ by model and availability path. The public catalog identifies model capabilities and prices, but does not by itself create a data-processing commitment.

Organizations with residency, retention, zero-data-retention, or regulated-data requirements must obtain written confirmation for the models and service terms they intend to use.

Enterprise review

Contact [email protected] with the intended models, regions, data categories, retention needs, expected volume, and required contractual documents. Do not send production data during the review.