Last updated: September 3, 2026
Filament is built around security, privacy, and isolation. We treat customer warehouse data, dashboards, AI conversations, user records, and credentials as confidential information and apply controls across their full lifecycle.
Platform Architecture
Filament is a managed analytics platform that synchronises data from connected applications into a dedicated Neon PostgreSQL database for each customer organisation. The platform database containing user accounts, organisation settings, and integration configuration is kept separate from customer warehouse databases.
Each warehouse database has dedicated PostgreSQL roles, with public and cross-tenant connections revoked. Application connections resolve the correct database for the authenticated organisation before any query is run.
Data Residency
Customers select a warehouse region during onboarding: US West (Oregon), EU Central (Frankfurt), or Australia (Sydney). Customer warehouse data is stored at rest in the selected region and is not moved without an explicit customer request.
Platform data is stored centrally, and application traffic, telemetry, and processing by some sub-processors may occur outside the selected warehouse region. Current locations and purposes are published in our sub-processor list and governed by our Data Processing Addendum.
Authentication & Access Control
Customer authentication is provided through Better Auth, with email/password and Google sign-on. Passwords are hashed using scrypt with per-password salts. MFA and passkeys are available for customer accounts, and organisation roles and resource permissions control what each user can view, edit, and share.
MFA is mandatory for all administrative, production, and internal accounts. Privileged production access is restricted to the CEO/CTO, logged, reviewed quarterly, and granted only for a documented business need. Access is revoked within 24 hours when personnel leave.
Application & API Security
Every data-accessing API route and server action authenticates the user, authorises access to the resource, and scopes the operation to the correct organisation. Server-action input is validated with Zod, and SQL is parameterised through Drizzle ORM or tagged templates rather than constructed by concatenating user input.
Production changes go through pull-request review and automated tests. Dependabot continuously monitors dependencies, security-critical updates are targeted within 48 hours, and remediation targets are based on severity. Controls are mapped against the OWASP Top 10.
Encryption
All data transmission uses TLS 1.2 or higher, including browser, database, integration, and internal service connections. Platform and warehouse databases and their backups use provider-managed AES-256 encryption at rest. OAuth tokens and API keys receive an additional AES-256-CBC application-encryption layer before database storage, with keys held separately in deployment environment variables.
Cloud Infrastructure & Monitoring
Vercel provides application hosting, a web application firewall, and L3, L4, and L7 DDoS protection. Neon provides the platform and warehouse databases, while Trigger.dev and Fivetran provide managed job orchestration and data pipelines. Critical providers are reviewed annually under our Vendor Risk Management Policy.
Dash0 provides real-time application monitoring for errors, performance anomalies, and potential security events. Authentication events, application activity, deployments, database connections, and background jobs are logged according to defined retention periods.
AI Processing & Model Training
AI requests are routed through Vercel AI Gateway, which Filament configures to mandate zero data retention for downstream providers. Current model providers include Anthropic, Google, and OpenAI. Customer personal data is contractually prohibited from being used to train, improve, or develop their models, and Filament does not train its own models on customer personal data.
Model providers process queries and supporting schema or data context only to return the requested result. Conversation history retained by Filament remains customer data within the platform and is protected by the same access, encryption, and retention controls.
Data Processing, Retention & Deletion
We process customer personal data only to provide the service and on the customer’s documented instructions. We do not sell it or disclose it for third-party marketing. Our DPA covers privacy rights, sub-processor obligations, international transfers, and audit rights.
Customer warehouse data is retained for the subscription term plus seven days. A full SQL export may be requested within seven days of termination and is provided through an encrypted channel. Platform user account data is retained for 30 days after account deletion, and application logs containing personal data are rotated after 30 days. Backups expire within their defined retention windows unless longer retention is required by law.
Backup & Disaster Recovery
Platform and warehouse databases have encrypted point-in-time recovery. The platform database has a seven-day recovery window, and warehouse retention is configured by customer tier. Weekly encrypted off-platform backups and geographically separate replicas provide recovery options if the primary database provider is unavailable. Recovery procedures and objectives are documented and tested annually.
Incident Response
Our documented process follows the NIST lifecycle: preparation, detection and analysis, containment, eradication and recovery, and post-incident activity. We notify affected customers without undue delay and within 72 hours of becoming aware of a personal data breach, provide updates as facts become available, and assist with regulatory obligations. The process is tested through an annual tabletop exercise.
Operational Security
We apply least privilege, individual accounts, mandatory MFA, encrypted production access, and audit logging for critical operations. Personnel with access to customer personal data complete screening, sign confidentiality obligations, and receive security awareness training at onboarding and at least annually. Risk and access controls are reviewed on a defined schedule.
Compliance & Standards
Our programme addresses the Australian Privacy Act 1988, Australian Privacy Principles, Notifiable Data Breaches scheme, GDPR, and UK GDPR where applicable. We are not yet SOC 2 or ISO 27001 certified; alignment toward SOC 2 Type II and ISO/IEC 27001:2022 is in progress. Our critical infrastructure and AI providers maintain independent certifications documented in the sub-processor list.
Your Security Responsibilities
Enable MFA or passkeys, use strong unique passwords, review organisation membership and permissions regularly, keep integration credentials secure, and report suspected security issues promptly.
Security Contact
For security questions, vulnerability reports, policy summaries, or detailed security documentation, contact team@filamentanalytics.com. Our response target is within 24 hours.