FerryAPI

Trust and security - FerryAPI

FerryAPI trust and security notes for data minimization, no training use, API key handling, usage visibility, and production AI API boundaries.

Page summary

FerryAPI trust and security notes cover data minimization, no training use, API key handling, usage visibility, and production AI API boundaries.

Data handling

Customer prompt bodies and model response bodies are not retained for training or secondary training; billing and support use minimized metadata.

Production guidance

Keep API keys server-side, create separate keys by environment or product, send only task-needed data, monitor usage, and use human review for high-risk decisions.