Private context deserves careful boundaries.
Capital Record is designed so authenticated users access their own records, consequential writes require clear intent, and operational logs avoid financial payloads.
Access and identity
- ChatGPT connections authenticate through OAuth/OIDC.
- Token issuer, audience, signature, and expiration are verified before tool access.
- External identities resolve to an internal user on the server. Tools do not accept a caller-supplied user ID.
- The beta is invitation-only, and new enrollment can be disabled without removing existing access.
Memory integrity
- Qualitative AI-generated memories begin as proposals.
- A proposal becomes canonical only after explicit user approval.
- Rejected or dismissed proposals do not overwrite approved memory.
- History and provenance help users understand what was stated, proposed, approved, changed, or retracted.
Data and operations
- Traffic is served over HTTPS.
- Capital Record does not store brokerage credentials and does not offer trade or money-movement endpoints.
- MCP audit logs record operational metadata such as tool, category, outcome, and duration—not tool arguments or financial responses.
- Production and development data environments are kept separate.
Report a security concern
Email support@capitalrecord.ai with “SECURITY” in the subject. Do not include passwords, access tokens, private keys, or unnecessary financial information.