Trust Center · Privacy & Data Handling
How data is stored and processed in cloud, self-hosted and hybrid deployments, and what personal information OrenGen itself handles. It's written for IT, privacy and procurement reviewers. Our Privacy Policy is the governing document; this page explains how it applies.
Cloud
Self-Hosted
Hybrid
Governed
By deployment model
The deployment model decides where records sit and which parties can process them, so it's the first thing to settle in any data-handling review.
Stored: in a hosting provider's data centers, in the regions the service is configured to use.
Processed by: the operator of the service and the providers it relies on for hosting, communications and billing.
Settle: which providers are involved, where they store data, and on what terms.
Stored: on servers you own or lease, inside your network boundary.
Processed by: your systems and the people you grant access to, which during a build can include OrenGen.
Settle: whether any component calls an outside model or service. A self-hosted open-source model keeps prompts and documents inside your boundary; a commercial model reached through an API receives whatever is sent to it.
Stored: sensitive records in your environment; less sensitive workloads in the cloud.
Processed by: both sides, across a boundary that should be documented and owned by a named person.
Settle: exactly which data crosses the boundary, in which direction, and on what terms.
We work with leading commercial and open-source AI models, so the model is part of the data-handling decision, not a fixed default. Infrastructure explains how we choose a deployment model.
OrenGen products
Our product lines are OrenAgents (Buy-Lingual™ AI Voice and AI Employees), OrenNexus™, OrenWeb and OrenSocial.
When you use one, what you put into it, such as contacts, messages, call recordings and transcripts, and website content, is stored and processed by OrenGen and by the service providers behind that product for hosting, communications and billing. Subscription billing is processed through Stripe.
Section 3 of the Privacy Policy lists what is collected, including conversation transcripts and voice recordings from AI voice services, and section 5 explains who it's shared with.
Subprocessors →Personal information
This covers OrenGen's own website, forms and communications, separate from the systems we build for clients.
Section 3 of the Privacy Policy covers what you give us through forms, accounts and messages, and what our systems record automatically. Section 8 explains how to ask us to access, correct, delete or export your information.
Mobile information is not shared with third parties or affiliates for marketing or promotional purposes (Privacy Policy, section 5.6). You can stop our text messages at any time by replying STOP.
Please don't put protected health information, student records or the details of a legal matter into our contact or booking forms.
Describe the kind of data involved instead, and share the details once there is an agreed way to handle them.
Privacy Policy →Regulated data
Some data carries obligations beyond the Privacy Policy. Here is what we can state for each.
Our healthcare work focuses on healthcare administration. We do not provide clinical decision support, diagnosis or treatment guidance, we are not a contract research organization, and we do not replace validated clinical systems of record.
Healthcare →OrenGen does not currently hold CMMC, FedRAMP, DoD Impact Level, CJIS or HITRUST authorizations, is not a 21 CFR Part 11-validated system, and does not maintain corporate personnel security clearances.
Public Sector →Non-attorney disclosure. OrenGen Worldwide LLC provides legal operations support: contract review support, clause extraction and document workflow automation. OrenGen is not a law firm, does not provide legal advice or legal opinions, and does not represent clients. All legal-support outputs require review by a licensed attorney or by the client.
Section 10 of the Privacy Policy explains that information may be transferred to, stored and processed in the United States or in other countries where our service providers operate.
Data handling
In a Mission Brief we map your data classes, where each one may be stored and which vendors may touch it, then match a deployment model to the answers.
