Getting Started
Data Security & Ownership
This guide breaks down how Delphi ensures your data stays private, secure, and entirely under your control—without the technical jargon.
Our documentation is moving to this website! We will leave this website up until all our customers transition to our new studio :)
Your Knowledge, Your Control
At Delphi, you maintain full ownership of all content you upload to create your Digital Mind. Your intellectual property remains exclusively yours, and you retain complete control over how your data is used, shared, and accessed. Your training data is stored in its own private index and is not shared or used to train any external models. Who can use your Digital Mind and leverage its capabilities is fully under your control. If you decide to unsubscribe from Delphi, your data can be exported to an external platform or deleted entirely. This ownership model ensures that your valuable knowledge remains under your control while still allowing you to scale your impact through our platform. The simplicity of our ownership policy reflects our commitment: your content is yours, period.Your Security, Our Priority
For up-to-date information about our compliance certifications, our security systems, and privacy practices, see our Trust Center, Terms of Use, and Privacy Policy. At Delphi, we take security very seriously to protect customer data and ensure a safe, reliable experience. Our security approach includes multiple layers of protection, similar to how a bank secures its money—using safes, alarms, cameras, and strict access controls. Below is a clear breakdown of the key security measures we use:Data Protection Measures
Data Protection Measures
- Encryption at Rest (Stored Data Protection): All stored customer data is locked using AES-256 encryption, which is one of the strongest forms of digital security. Think of it like storing valuables in a high-security safe that only authorized people can open.
- Encryption in Transit (Data Moving Protection): When data travels over the internet (e.g., when you log in or send a message), we encrypt it using TLS 1.2+. This is similar to sending a letter in a locked, tamper-proof envelope instead of a postcard.
- Daily Backups: We save copies of our data every night, so if anything goes wrong, we can restore lost information, just like a safety net.
Network Security (Preventing Hackers from Getting In)
Network Security (Preventing Hackers from Getting In)
- Firewalls and Access Control Lists: These are security barriers that filter internet traffic, blocking anything suspicious, similar to a security checkpoint at an airport.
- Private Subnet (Data Isolation): Customer data is processed in a private, separate section of our cloud environment that cannot be accessed by the public internet. This is like storing confidential documents in a restricted area with limited keycard access.
- DDoS Protection (Defending Against Attacks): We use Cloudflare and AWS Shield to protect against attacks where hackers try to flood our system with excessive traffic, like a traffic jam blocking all the roads to a business.
- Web Application Firewall (WAF): This system monitors and blocks harmful internet traffic, preventing threats before they reach our platform, just like a security guard screening visitors before they enter a building.
Continuous Monitoring and Compliance
Continuous Monitoring and Compliance
- Automated Security Monitoring: We use tools like Sentry.io, Axiom, and Logfire to continuously check our system’s health. If anything unusual happens, an alert is sent to our security team immediately, like a home alarm system detecting an intruder.
- Audit Logs (Tracking Who Does What): Every action in our system is recorded using AWS CloudTrail, ensuring a clear record of who accessed what, when, and why—similar to security cameras keeping track of who enters a building.
- Regulatory Compliance (Meeting Legal Standards): We follow strict security regulations including SOC 2, GDPR, and CCPA. These are industry standards that ensure we handle customer data responsibly, just like food safety regulations ensure restaurants maintain hygiene.
Application Security (Protecting Our Software from Hackers)
Application Security (Protecting Our Software from Hackers)
- Penetration Testing (Hiring Ethical Hackers): Every year, we hire expert security testers to try and break into our system. If they find any weak points, we fix them immediately—similar to testing locks on a house to find and fix vulnerabilities.
- Vulnerability Scanning: We use tools like Snyk and AWS GuardDuty to scan for weaknesses in our system and update any outdated security measures before they become a risk.
Secure Access and Identity Protection
Secure Access and Identity Protection
- Role-Based Access Control (RBAC): Employees and system users only get access to the data they need, nothing more. This is like a workplace where only finance employees can access payroll records, and IT staff can access servers.
- Credential Management (Protecting Passwords and Secrets): We use AWS Key Management Service (KMS) and 1Password to securely store passwords and secret access keys, ensuring they’re encrypted and only accessible to authorized people.
Incident Response (How We Handle Security Threats)
Incident Response (How We Handle Security Threats)
- Incident Response Plan: If something goes wrong, we follow a structured process to detect, analyze, and respond to the issue immediately, just like an emergency plan for handling fires in a building.
- Root Cause Analysis (Fixing the Problem for Good): After any security event, we investigate what caused it and take steps to prevent it from happening again, just like learning from a car accident to avoid future crashes.