Security & Data Privacy
Our commitment to protecting your data and respecting your privacy.
Overview
At Alkimi, we are deeply committed to the security of our platform and the protection of your data. We understand that trust is paramount, especially for enterprise and educational institutions. This document outlines the comprehensive security measures and data privacy practices we have implemented to safeguard your information.
Data Security
We employ a multi-layered approach to data security, ensuring your information is protected at every stage. The diagram below provides a high-level overview of our security architecture.
Your Browser
Cloudflare Edge Network
WAF, DDoS Protection
Google Cloud Platform (VPC)
Secure Private Cloud Environment
Cloud Run
Backend Service
Cloud SQL
PostgreSQL Database
Connection (IAM & SSL)
Database Security Layers
Data Encryption
- In Transit: All data transmitted between your browser and our services is encrypted in transit using industry-standard TLS 1.2 or higher, enforced by our partners at Google Cloud and Cloudflare.
- At Rest: All your data, including knowledge base content, agent configurations, and chat histories, is encrypted at rest using the built-in AES-256 encryption capabilities of our database provider, Google Cloud SQL.
Data Storage & Isolation
We utilize a multi-tenant architecture with strict logical data isolation. Your organization's data is segregated from other customers' data at the database level using PostgreSQL's Row-Level Security (RLS). This ensures that a given user, connected through a properly authenticated database connection, can only view or interact with the data that pertains to their organization.
Furthermore, we employ PII (Personally Identifiable Information) anonymization techniques within our database for sensitive data fields, providing an additional layer of privacy protection.
Network Security
Our infrastructure is hosted within a Google Cloud Virtual Private Cloud (VPC). We utilize carefully configured firewalls and network access control lists to block unauthorized access, and our databases are not exposed to the public internet, only accessible by authenticated services within our secure environment.
Data Centers & Physical Security
Our services are hosted on Google Cloud Platform and Cloudflare, which maintain state-of-the-art data centers with robust physical security controls, including 24/7 monitoring, biometric access, and redundant power and cooling.
Monitoring & Logging
Our major cloud and database services are configured with comprehensive audit logging enabled. We log network traffic, administrative access, and database activity to provide a detailed audit trail for security monitoring and incident response.
Application Security
Security is an integral part of our development process, from design to deployment. The following diagram illustrates our commitment to a Secure Software Development Lifecycle (SSDLC).
1. Design & Planning
Threat Modeling for all new features
2. Development
Automated Code Scanning (SAST & SCA) & Secure Coding Standards
3. Testing & QA
Mandatory Peer Reviews & Secrets Scanning in CI/CD
4. Deployment & Maintenance
Continuous Monitoring, Dependency Updates & Responsible Disclosure
Secure Development (SSDLC)
We are committed to building secure software. Our development process includes automated code analysis and dependency scanning through GitHub Advanced Security to identify and remediate potential vulnerabilities before they reach production.
Vulnerability Management
We use continuous, automated vulnerability scanning to monitor our applications and infrastructure for emerging threats. We strive to address identified vulnerabilities promptly based on their severity and impact.
Access Control
Access to data within the Alkimi platform is governed by a robust Role-Based Access Control (RBAC) system that employs a "defense-in-depth" strategy, using both the application middleware and the database to enforce permissions. The diagram below illustrates how these two layers work together to protect your data.
User Initiates Request
1. Middleware RBAC Check
Prepares a secure, context-aware database session after role checks.
2. Database RLS Enforcement
Policies filter data based on the secure session context.
Data Returned
Only if both checks pass
Access Denied
If either check fails
This layered approach ensures that even if a flaw were to exist in the application logic, the database's own security rules (Row-Level Security) would act as a final, authoritative backstop, preventing any unauthorized data access. The application middleware performs initial role-based checks and prepares a secure, context-aware database connection, but the database policies have the ultimate say on what data is visible. For a detailed breakdown of the default roles and their specific permissions, please see our Help & Guides.
Conversation Sharing
The platform provides features for users to share their conversations via secure, unguessable links. This form of access is also governed by strict controls:
- User-Initiated: Sharing is always initiated by the user, who has full control over whether to make a conversation accessible to others.
- Visibility Controls: Users can choose between two visibility levels for each shared link:
- Organization: The link is only accessible to other authenticated members of the user's organization.
- External: The link is accessible to anyone who has it.
- PII Redaction: To further protect privacy and prevent accidental data exposure, the platform includes a PII (Personally Identifiable Information) detection and redaction feature, which is enabled by default on all shared chats.
- Revocation of Access: Users retain full control and can revoke access to any shared conversation at any time by deleting the share link from their account settings.
Authentication
We support strong authentication measures, including Single Sign-On (SSO) with providers like Google and Microsoft, to ensure secure and convenient access to your account. For accounts using password-based authentication, we enforce password complexity requirements. We strongly recommend enabling Multi-Factor Authentication (MFA) with your SSO provider for the highest level of security.
Compliance Roadmap
We are committed to a continuous journey of security and compliance improvement.
GDPR
We are actively working towards compliance with the General Data Protection Regulation (GDPR). We act as a data processor for the content you provide and give you control over your data, including the right to access and delete it, as outlined in our Privacy Policy.
Future Certifications (SOC 2)
We are building our security program and internal controls with the goal of undergoing a SOC 2 audit in the future. We have implemented many foundational security best practices and are using the internal guides in our documentation to prepare for this important milestone.
For Higher Education (FERPA)
Our Commitment to Student Privacy
We understand the importance of protecting student privacy under the Family Educational Rights and Privacy Act (FERPA). We are actively working towards ensuring Alkimi can be used by higher education institutions in a FERPA-compliant manner and are building our platform with student privacy protections in mind.
Handling Student Data
When a higher education institution uses Alkimi, we understand that the institution acts as the custodian of student education records, while students (who are typically adults) retain their rights under FERPA. We act as a service provider and process data only on behalf of and at the direction of the institution.
- Data Custodianship: The higher education institution acts as the custodian of student education records uploaded to the Alkimi platform, while students retain their FERPA rights to access, review, and control disclosure of their information. Our role is that of a data processor working under the institution's direction.
- Limited Data Collection: We only collect the minimal personal information necessary to provide our service: user's email, first and last name, and an optional profile picture, all of which are managed by the user.
- Data Use: We will not use student data for any purpose other than providing and improving our services as directed by the institution. We do not use student data for advertising or marketing. The only time PII is shared with a third party is when it is necessary for a model provider to process a request (e.g., to address a user by name in a response), and we maintain appropriate data processing agreements with those providers to protect this information.
Data Privacy
Privacy Policy
Our Privacy Policy provides detailed information about the data we collect, how we use it, and your rights regarding your data. We are committed to transparency and empowering you to control your information.
Data Retention & Deletion
You have control over your data. You can delete your knowledge collections, agents, and account at any time. Knowledge collections are permanently deleted immediately upon request. Other data (accounts, agents, and conversations) is marked for deletion and permanently purged from our systems within one year, or sooner at our discretion or upon request, in accordance with our data retention policy.
For conversations that do not need to be retained, we offer a Temporary Chat feature. These one-off chats are not stored in our database and are permanently discarded the moment you navigate away from the page, offering a higher level of privacy for sensitive discussions.
Responsible Disclosure
If you believe you have discovered a security vulnerability in our platform, we encourage you to report it to us responsibly. Please email us at [email protected] or [email protected] with the details. We are committed to working with the security community to address and resolve any potential issues.
Further Questions?
We understand that enterprise and educational customers may have detailed security and compliance questionnaires. If you have any further questions, please don't hesitate to reach out to our team.