Frequently Asked Questions
Do you use our data — or your content — to train AI models?
No. CARAVAN does not license, sell, or supply its content library as training data for third-party AI models, and we do not use client or user data to train models. Our AI is applied to our own licensed library to build metadata and adapt content for the platforms we serve. That is the entire scope.
Where does the AI actually run?
On our side, before delivery. We enrich and adapt content within CARAVAN’s environment, then hand your platform a finished record or asset. Nothing about the integration requires you to run AI infrastructure of your own.
How do you know the AI-generated metadata is accurate?
Because a person checks it. Every mapping, tag, translation, and adaptation is reviewed by CARAVAN’s human reviewers before delivery.
What do you need from us to get started?
Your taxonomy or content schema, a set of sample records, and roughly an hour with whoever owns your content structure. If you don’t have a formal taxonomy, we can propose one based on your platform and user segments.
Can the metadata match our existing field names and IDs?
Yes. We conform to your schema rather than asking you to adopt ours — your field names, your enums, your identifiers. That is the point of the service.
How is adapted content different from machine translation?
Machine translation swaps words. Adaptation changes reading level, cultural references, examples, foods, measurements, length, and format — then puts the result in front of a qualified reviewer who speaks the language and knows the subject. The content stays identical; everything around it is rebuilt for the audience.
Does using AI change the compliance picture?
No. The same SOC 2, HIPAA, and GDPR commitments that govern our licensing apply here. No protected health information or personally identifiable data enters our AI pipelines — enrichment operates on content, not on people.
What does this cost?
Metadata enrichment and content adaptation are configured as part of a content licensing agreement and scoped to the size of your library and the number of variants you need. Contact us for pricing against your specific requirements.
Can we evaluate the output before we commit?
Yes. We provide a sample dataset mapped to your taxonomy so your content and engineering teams can assess quality, structure, and fit before anything is signed.
