Encryption
Protect data in transit and at rest using modern security practices.
Security
Controls for team and enterprise access.
Capital Almanac is designed around encryption, role-based access, administrative controls and auditable workflows. Certifications are shown only when they are formally confirmed.
Access controls
Use role permissions and administrative policies to govern access.
SSO and provisioning
Support enterprise identity patterns including SSO, SAML and SCIM where enabled.
Auditability
Maintain audit-oriented controls for sensitive research workflows.
Data handling
Keep source, customer and application data boundaries explicit.
Administration
Manage accounts, workspaces and permissions from one administrative layer.
Source context
Keep the source trail visible.
Capital Almanac keeps source context, reporting periods, freshness and unavailable-data states visible so researchers can see what supports a record or conclusion.
Source provenance
Keep the provider, document and evidence trail close to the supported fact.
Linked evidence
Open filings, calls, announcements and other source documents from the research view.
Freshness metadata
See reporting period and update context instead of treating every record as equally current.
Connected records
Understand how companies, people, investors and transactions relate to one another.
Capital Almanac
See how Capital Almanac fits your research process.
Tell us what your team researches, which markets matter and where source visibility or workflow integration would save the most time.
Clear answers for serious research.
How Capital Almanac handles source material, unsupported information and the path from a research question to a reviewable answer.
What security controls does Capital Almanac describe publicly?
The public security story focuses on encryption, role-based access, administrative controls, identity patterns, data handling and audit-oriented workflows. Certifications or attestations should only be presented when they have been formally confirmed for the service.
Are SSO or provisioning capabilities available in every deployment?
No capability should be assumed solely from a marketing summary. Enterprise identity requirements such as SSO, SAML, SCIM, role design and audit needs should be confirmed during deployment planning for the specific customer environment.
Where should a security team ask deployment-specific questions?
Use the enterprise sales and implementation process for requirements that depend on configuration, contractual terms or a particular control. That keeps the answer tied to the environment being evaluated rather than relying on a broad public claim.