Snapshot 223460
Normalized text
Scripts and page chrome removed; this is what change detection compares.
Security & Trust Your data, your control however you deploy Grengin Bring your own API keys, get full audit trails, and verify the code yourself. Grengin does not train models on your business data. Request Security Review View Architecture Security Features Built for security-conscious teams Every feature designed with enterprise security requirements in mind. Data Encryption All data encrypted at rest (AES-256) and in transit (TLS 1.3). Your conversations are protected end-to-end. No Training Guarantee Grengin does not use your business data to train models. With your own API keys, model-provider processing is governed by your agreements with those providers. Secure Infrastructure Hosted on AWS. AWS holds SOC 2 Type II for its data centers; Grengin itself is not yet SOC 2 audited. Access Controls Role-based access, SSO integration, and granular permissions. Control exactly who can do what. Audit Logging Complete audit trails of all AI interactions. Export logs for compliance reviews and investigations. PII Protection Automatic detection and optional redaction of sensitive information before it reaches AI models. Managed by Grengin We operate the app, so we are in the data path Stated plainly rather than buried. Your traffic passes through systems we run, and everything below exists to make that a decision you can audit instead of a leap of faith. Try Grengin for free Eject whenever you like: one-click export into your own cloud, same schema, your data comes with you. Your workspace runs in our AWS account, in the region you choose when you sign up. Model keys are stored with envelope encryption and used only to serve your workspace. Sub-processors are listed publicly and a DPA is signed before your first prompt. No SOC 2 report yet. When there is one it will be linked here, not described. DPA Sub-processors The Grengin Data Guarantee Grengin does not use your business conversations to train models. You bring your own API keys and control which model providers process your requests. Model-provider processing is covered by your direct agreements with each provider Review each provider's training and retention terms before connecting a key We'll sign a Data Processing Agreement (DPA) on request Infrastructure Security architecture Built on AWS with defense-in-depth security practices. Multiple layers of protection ensure your data stays safe. Network Security: VPC isolation, WAF, DDoS protection Application Security: Regular penetration testing, dependency scanning Data Security: Encryption at rest and in transit, key rotation Access Security: Zero-trust architecture, privileged access management Monitoring: Security monitoring and automated alerting Data Handling AI Governance and Security: Frequently Asked Questions How we store, protect, and handle your data—expand any question for the full answer. Data Handling & Privacy Where is my data stored? Depends on how you run Grengin. Self-host the marketplace image (or build from source) and everything lives in your own AWS account, in the region you pick—we never see it. When we manage it for you, your workspace runs in our AWS account, in the region you choose at signup. How long is data retained? On self-host, retention is entirely up to you—it's your database and your storage. When we manage it for you, conversation history is retained until you delete it. You can delete data at any time, and we purge it from our systems within 30 days of deletion. Who has access to my data? Self-host: no one at Grengin, ever—we have no credentials to your instance. Managed by Grengin: only authorized employees with a legitimate business need, and all access is logged. Neither path shares data with third parties beyond what's needed to serve the request (e.g., sending your prompt to the model provider you chose). Is my data used for AI training? Grengin does not use your conversations to train models. You bring your own API keys, so review the training and retention terms of each provider you choose. The same applies whether we manage it for you or you self-host. What happens if there's a breach? On self-host, a breach of the underlying cloud account is between you and your provider—Grengin was never in the data path to breach. When we manage it for you, we have incident response procedures in place and will notify affected customers within 72 hours as required by GDPR, and we will publish our incident-response summary on request. Can I switch between Grengin-managed and self-hosted? Yes, in either direction. Export your managed workspace and run the same image in your own account, or start self-hosted and hand it over to Grengin later if you'd rather stop operating infrastructure. Same schema, same software, your data comes with you. Prefer to keep everything in your own infrastructure? Self-host Grengin in your AWS account, or build it from source. Grengin is then never in the data path. Self-host on AWS → Build from source Ready for a security review? Our security team is standing by to answer your questions and provide documentation. Contact Security Team See Grengin in Action