1. Executive Summary

Truefolio is built on the principle that financial transparency requires absolute data security. Our architecture is designed by a founding team of senior engineers from Google, Amazon, and Wix to ensure that while investment skill is public, investment access and identifiable wealth remain entirely private and secure.

2. Data Access Architecture

Truefolio utilizes a non-custodial data architecture. We do not, and cannot, touch your money.

• Plaid Integration: We utilize Plaid as our secure gateway. Truefolio never sees, handles, or stores your brokerage login credentials.
• Restricted Scopes: Our integration is restricted to the /investments/holdings and /investments/transactions endpoints. This ensures our access is strictly read-only.
• Tokenization: We use the item/public_token/exchange flow to receive a secure, permanent access_token. These tokens are stored using GCP Secret Manager, ensuring they are never exposed in plaintext or application logs.

3. Infrastructure & Encryption

Our backend is hosted on Google Cloud Platform (GCP), leveraging the same infrastructure security models used by global enterprises.

• Encryption at Rest: All databases utilize AES-256 encryption at the storage layer.
• Encryption in Transit: All data moving between your browser, our servers, and Plaid is encrypted via TLS 1.2+ with HSTS (HTTP Strict Transport Security) to prevent man-in-the-middle attacks.
• Credential Management: Environment variables and API keys are managed through GCP Secret Manager, providing audit trails and preventing unauthorized access.

4. Data Persistence & Anonymization

To provide institutional-grade Time-Weighted Return (TWR) calculations, Truefolio must retain a historical record of portfolio transactions. This data is protected through a multi-layered isolation strategy:

• Logical Segregation: Financial transaction data is stored in separate tables from user identity records, linked by internal UUIDs.
• Dollar Masking: Your own account can display your dollar amounts. Other members see percentage-based portfolio information rather than your absolute dollar balances.
• Field-Level Minimization: We only persist the data points required for performance math (e.g., Ticker, Date, Quantity, Price). We do not store or transmit non-essential PII often associated with brokerage or bank accounts.
• Storage Layer Security:All persisted transaction data is encrypted using AES-256 via Google Cloud's managed storage layer.

5. Principle of Least Privilege

Access to production systems is strictly limited and monitored.

• Audit Logging: All administrative access to the production database is subject to automated audit logging, providing a transparent trail of all internal data interactions.
• Infrastructure as Code: Our environment is managed programmatically, reducing the risk of manual configuration errors that could lead to security vulnerabilities.

6. Deletion

Users maintain total ownership of their data.

• Brokerage Removal: Removing your brokerage in Truefolio immediately removes its portfolio, transactions, holdings, and performance records from our active database, and revokes the brokerage connection.
• Account Deletion: Deleting your account hides it from other members and disconnects your brokerage immediately. Eligible accounts have a 30-day restoration window so you can recover your account and portfolio history. After that window, your data is scheduled for permanent deletion. Restoring brings your history back; reconnect your brokerage to resume syncing. See our Privacy Policy for eligibility and deletion details.

7. Compliance & Audits

• Independent Third-Party Audit:Prior to our production release, Truefolio's infrastructure and application code undergo a rigorous security audit. This is conducted by an independent cybersecurity professional specializing in vulnerability research.
• Scope of Testing:The audit includes a “Grey-box” penetration test focusing on API security, PII isolation, and OAuth token handling. All “High” and “Critical” findings are remediated and verified before data is live in production.