OpenAI compatible API. Attested gateway. Public status.
Data Processing Addendum draft
Draft DPA terms for customer counsel review. Production legal workloads require a signed agreement or written exception.
1 URLbase_url migration
100smodels and routes
0prompt logs by default
StatusDraft for review. Not signed by loading this page.
ProcessorLore Hex Corp
SignerJoseph Perla, CEO
Default retentionNo prompt/output storage by TrustedRouter.
This DPA is a procurement draft for counsel review. It becomes binding only when executed by the customer and Lore Hex Corp or incorporated into a signed master agreement. Do not treat this page as an executed agreement.
Draft DPA
Data Processing Addendum terms to review.
Written to track GDPR Article 28 style processor obligations and the TrustedRouter zero-content-storage architecture.
| Processor | Lore Hex Corp, Delaware C Corporation, 1111 Brickell Ave, Floor 10, Miami, FL 33131. EIN 41-5339728. DUNS 144992055. |
|---|---|
| Authorized signatory | Joseph Perla, CEO, signing as officer of Lore Hex Corp. |
| Security contact | security@trustedrouter.com. |
| Customer role | Customer is controller or processor, depending on the matter. TrustedRouter acts as processor or subprocessor for customer data submitted to the service. |
| Subject matter | Hosted AI routing, model-provider selection, billing, authentication, abuse prevention, usage reporting, and optional customer-configured observability export. |
| Duration | For the term of the customer agreement and any legally required wind-down period. |
| Categories of data | Account data, API key metadata, billing metadata, model request metadata, prompts and outputs in transient processing, and optional customer-enabled observability exports. |
| Data subjects | Customer personnel, clients, adverse parties, witnesses, experts, vendors, and other people whose data customer elects to submit. |
| Customer instructions | TrustedRouter processes customer data only to provide and secure the service, comply with customer configuration, route selected requests, satisfy legal obligations, and follow documented customer instructions. |
| Confidentiality | Personnel and contractors with access to production systems must be bound by confidentiality duties appropriate to their role. |
| Security measures | Attested prompt gateway, fail-closed production prompt path, TLS, API key hashing, BYOK envelope encryption, KMS-backed secret handling, access control, logging redaction, Sentry exclusion from the enclave path, and metadata-only durable storage by default. |
| Zero-retention commitment | TrustedRouter does not persist prompt or output content by default. Durable records contain metadata needed for billing, routing, abuse controls, support, and status. Customer can explicitly enable content export to a configured observability destination, but legal workloads require written approval before content export is enabled. |
| Subprocessors | TrustedRouter may use the listed platform vendors and downstream model providers. Model providers receive prompt/output content only when customer traffic is routed to that provider. |
| Provider routing for legal work | Privileged attorney work product defaults to trustedrouter/zdr. trustedrouter/e2e or a named provider allowlist may be used when approved in writing. Broad fallback aliases may include providers with unknown or non-ZDR posture unless filtered and are not the default for sensitive legal work. |
| Assistance | TrustedRouter will provide commercially reasonable assistance for security reviews, data subject requests, breach assessment, DPIAs, and deletion or export of metadata under the signed agreement. |
| Deletion and return | On termination, TrustedRouter will delete or return customer metadata according to the signed agreement, except where retention is required for legal, billing, fraud prevention, or security purposes. |
| Audit | Until SOC 2 is available, audit evidence consists of public source code, trust/attestation evidence, public subprocessors, security documentation, and reasonable written responses. On-site audits require a signed agreement. |
| Incident notice | TrustedRouter will notify customer without undue delay after confirming a security incident affecting customer data, with details available at the time and follow-up updates as investigation proceeds. |
This draft is intended to accelerate review, not replace counsel's negotiated DPA. A legal team should request signature, confirm route restrictions, and confirm whether SOC 2 absence is acceptable before production use.