German operation
The Simple8 service and its processing engine run in Simple8-operated infrastructure in Germany.
SECURITY AND PROCUREMENT
Simple8 operates its service and processing engine in Germany. Review the documented data flow, retention categories, access controls, encryption, availability, and operational responsibilities before connecting production systems.
The Simple8 service and its processing engine run in Simple8-operated infrastructure in Germany.
Customer requests stay inside the Simple8 service and are not sent to OpenAI, Anthropic, Google, Microsoft, or another external model provider.
Simple8 processes account and access data, request content, result and cache data, technical and security logs, usage and billing records, support data, and backup or recovery data only for their documented service purposes.
The production API includes a 99.9% monthly availability SLA.
The Simple8 service and its processing engine run in Simple8-operated infrastructure in Germany.
Simple8 uses a language-processing engine that is built, versioned, and operated as part of the Simple8 service.
Customer requests stay inside the Simple8 service and are not sent to an external model provider.
Customer content is not used to train or fine-tune models.
| Data category | Purpose | Default retention | Customer control | Deletion |
|---|---|---|---|---|
| Account data | Contract and access | Contract term plus applicable statutory retention | Account administration | Deleted or restricted after contract termination, subject to statutory retention |
| Request content | Generate result | Short-lived request processing; asynchronous job data expires after one hour by default | Production retention follows the signed plan and data-processing schedule | Deleted after request completion or job expiry unless an agreed cache policy applies |
| Cached result | Reuse unchanged content | Plan-specific period in the signed retention schedule | Invalidate and export under the project policy | Deleted on invalidation, expiry, or contract termination |
| Security logs | Protect and investigate | Rolling period in the signed security and retention schedule | Available through the documented incident or support process | Deleted on schedule except during a documented incident or legal hold |
| Usage records | Billing and capacity | Contract term plus applicable billing and statutory retention | Reporting and export | Deleted or anonymized after billing and statutory retention |
| Backups | Recovery | Backup cycle and expiry in the signed security and retention schedule | Restoration and deletion follow the documented recovery policy | Expires through documented backup rotation after primary deletion |
No.
Customer content is processed by the Simple8 service and processing engine operated in Germany.
The security pack lists the infrastructure and every relevant non-model service provider.
No.
Customer content is not used to train or fine-tune models.
Contractual data-handling terms cover evaluation, abuse prevention, support access, retention, and available customer controls.
Yes.
Production plans support documented retention controls, including shorter contractual periods where the workflow and operational requirements allow them.
A full on-premise model deployment is not offered.
Enterprise architectures can keep selected cache or database components in the customer environment while the managed service and processing engine remain in Germany.
PLAIN LANGUAGE AND EASY LANGUAGE
Create your free account and use up to 15,000 characters free every month.