To know what an AI investment platform can access, inspect the specific permissions on the connection—not just a “connect” or “secure” label. Check which records it can read, whether it can change or trade anything, whose account permissions it inherits, what information reaches AI providers, and how to revoke access and remove retained data. Use the checklist below against the platform’s authorization screen and current contracts and security materials before connecting an account.
Start with the actions and data the connection permits
Write down both the records an integration can reach and the actions it can perform. “Connect” does not tell you whether access is read-only or allows changes.
As an Amazon Associate I earn from qualifying purchases.
- Data: holdings, transactions, balances, fund or LP records, private documents, research notes, and exported files.
- Actions: view, edit, share, export, delete, place trades, or transfer money.
Check the actual consent screen, API scopes, and documentation for the connection you plan to use. Carta documents scope names that distinguish read_ endpoints from readwrite_ endpoints. Trading 212 says API-key permissions can include read-only access or permission to place orders. These are examples of vendor-documented permission models, not evidence about another platform’s settings. Carta API authentication and scopes; Trading 212 API-key permissions.
Check whose identity and permissions control access
Ask whether the integration inherits the permissions of the person who authorized it, whether its scope is limited to one account or organization, and what happens if that person changes roles or leaves the firm.
#1 Best Overall
Carta says an API application’s access matches the granting user’s access and checks that user’s current role. If the user loses permission to an endpoint, a request can return 403 Forbidden. AngelList says its MCP uses the same authentication and authorization infrastructure as its web app and can reach only data the user could see there. Verify that the specific connection follows the same rules in your deployment. Carta API authentication and scopes; AngelList MCP server.
For team use, verify tenant and document boundaries
In an organization, a user’s account permission is only one boundary. Ask how the service separates organizations and accounts, and whether every document request checks the requesting user’s identity, role, tenant, and document-level permission.
Rank #2
- Can an investor-facing portal user access only their own records, rather than a management interface or another investor’s files?
- Are private documents protected when downloaded through the platform’s API or AI features?
- Are access changes and document activity recorded in logs that an administrator can review?
Prism describes tenant isolation, role and document controls, auditability, authenticated document delivery, and LP-linked portal scope in its materials. Treat those statements as the vendor’s description of its controls; request current documentation and confirm how they apply to your account. Prism trust centre; Prism security.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesAsk what information is used as AI context
Read-only access does not settle the privacy question. A platform may be unable to alter a brokerage account while still processing account data or documents to answer prompts. Ask the vendor to identify:
- Which prompts, documents, holdings, and derived outputs are sent to model providers.
- Whether data is retained, for how long, and whether it may be used to train models.
- Which subprocessors receive it and whether those terms vary by account tier.
- Whether data is automatically included in each query or used only when a user selects it.
Kimpton’s security overview says users decide when vault documents and portfolio information are used as AI context. Confirm the current behavior, retention period, and training terms in the privacy notice and contract for your account; a vendor statement such as “never used for training” is not a substitute for reviewing those terms. Kimpton security overview.
Find out how revocation and deletion work
Locate the exact steps to disconnect an account, revoke its token, delete imported copies, and request deletion of the platform account. Ask whether revocation takes effect immediately and what happens to data already exported to logs or backups.
Rank #4
AngelList describes its scoped token as revocable. Kimpton’s materials describe revocable connections and say data associated with a disconnected portfolio is deleted. Those statements do not establish exact operational timing or the treatment of every backup, log, or prior export. Ask for the applicable timing and scope in writing. AngelList MCP server; Kimpton security overview.
Recommended Free Tools
Request evidence you can review
Ask for current security and contractual materials, then compare them with the access the platform proposes and your organization’s requirements. Useful items include:
Best Value
- The trust-centre materials and current security report.
- The data-processing agreement and retention schedule.
- The incident-response process and notification commitments.
- Details of audit logs, administrator controls, and access monitoring.
Prism describes a trust centre and multiple security controls; that can help identify what to request, but the underlying materials still need review. The Cloud Security Alliance’s 2026 research note recommends limiting maximum OAuth scopes for AI SaaS tools and monitoring OAuth-related events. Prism trust centre; Prism security; Cloud Security Alliance research.
Compare platforms with the same questions
If you are assessing more than one platform, use one questionnaire and record whether each answer is documented, contractual, or only stated verbally. That makes gaps visible without treating different permission models as equivalent.
| Assessment area | What to record |
|---|---|
| Permissions | Scope granularity; data categories; account boundaries; read, write, trade, or transfer capabilities. |
| AI data handling | Information sent to model providers; retention; training use; subprocessors; user controls over context. |
| Identity and administration | How user roles apply; administrator controls; role-change behavior; tenant and document isolation. |
| Lifecycle and monitoring | Revocation procedure; deletion scope and timing; audit logs; current independent assurance and security materials. |
For each answer, keep the evidence beside it: the current authorization screen, documentation, contract clause, or security report. Vendor pages explain what a company publicly says its controls do; they are not independent confirmation that those controls work as described. Recheck the actual configuration and current terms before connecting financial or private investment data.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
