Investboard uses AI in six clearly bounded places: for language, summaries and context. Not for calculations, forecasts, orders or decisions.
The language model enters only after Investboard has calculated, checked and limited the data to the purpose at hand. Every AI function follows the same principle: the evidence stays visible and the decision stays with you.
66 bounded uses
AWS Bedrock with EU profileNo order execution
01Transparency register
Six uses. Six defined purposes.
We count every independent function path backed by Bedrock. A use may explain, summarize or match an existing template. None may control your wealth.
01
Portfolio chat and tutor
Purpose
Answer questions about portfolios, taxes, signals and your own mandate in clear language.
Evidence
Curated portfolio aggregates, fixed rules, selected tools or the current mandate draft.
Fixed boundary
Explains options and relationships, but does not choose for you.
02
In-context explanation
Purpose
Explain a metric, chart, news item, market value or plan deviation where it appears.
Evidence
Only the values already visible and calculated in that specific component.
Fixed boundary
No free-form portfolio analysis and no additional unsupported figures.
03
Market lens
Purpose
Frame precomputed market and portfolio facts in no more than two measured sentences.
Evidence
A fixed facts block covering market regime, allocation, mandate status and changes.
Fixed boundary
No new figures or claims; uncertainty returns the deterministic version.
04
Workspace matching
Purpose
Match a free-form description to an existing workspace template.
Evidence
The user's description and the fixed catalogue of available templates.
Fixed boundary
Output must pass a defined schema and has no bearing on an investment decision.
05
Quarterly letter
Purpose
Describe a completed quarter in calm, readable language.
Evidence
Prepared quarterly findings and a fixed allow-list of figure tokens.
Fixed boundary
Two output checks before storage; a blocked draft is never displayed.
06
CSV import column mapping
Purpose
Propose which column carries which role when a broker export arrives in a format we do not recognise yet.
Evidence
The column headers, the detected delimiter, the shape of the values, and for columns holding a few recurring short words, those words themselves (such as “buy” or “dividend”). Amounts, quantities, prices, dates and security identifiers never leave Investboard.
Fixed boundary
The model supplies the mapping and nothing else. Every number is computed by the deterministic parser from your file, and a proposal is accepted only when the arithmetic in the file confirms it.
Sequence matters
Calculate first. Phrase second.
Rules and calculations establish the finding. AI makes it readable.
02Processing
From finding to explanation, in five controlled steps.
The model has no open access to Investboard. Every request follows a bounded path.
01
Deterministic basis
Calculations, rules and thresholds are produced without a language model.
02
Curated context
Only fields intended for the particular purpose are assembled.
03
Bedrock in the EU
The central client accepts only an EU inference profile and starts in Frankfurt.
04
Guardrails
Inputs, numeric grounding, advice boundaries and output shape are checked.
05
Explanation or fallback
Only a passing answer appears. Otherwise it is blocked or replaced by fixed wording.
03Data protection
EU data residency is technically enforced.
We do not rely on a label. The Bedrock integration sets concrete boundaries for region, access and logging.
EU inference profile
Every model call uses a geographically bound EU profile in AWS Bedrock. The shared client technically rejects any model identifier without the “eu.” prefix.
Frankfurt as the source region
Investboard connects to AWS Bedrock in eu-central-1. The EU profile may distribute processing within the European AWS geography, not outside that geography.
Encrypted transport and IAM
Requests travel over the encrypted AWS interface. Access uses role-based AWS permissions under the principle of least privilege.
No optional content logging
Investboard does not enable optional Bedrock model-invocation logging to CloudWatch or S3 in its AWS infrastructure.
No use for training
AWS states that Amazon Bedrock inputs and outputs are not used to improve base models and are not made available to model providers.
04Data minimization
The model sees a slice, not your account.
For every purpose, the application assembles a fixed data shape. Raw database rows and technical access rights are not passed through to the model.
Intended context
The specific question or description you submit
Calculated aggregates, allocations and plan deviations
Public security names and tickers when needed for the answer
Rule findings, visible component values and bounded conversation history
Structurally excluded
Brokerage credentials, passwords and order permissions
IBANs, account numbers and raw linked-account rows
Email address, full name, phone number and postal address from your profile
Open access to databases, brokerage accounts or other user accounts
Free text remains free text: if you type personal data into a question, Investboard detects common patterns and warns you. The text is not silently changed. Do not submit such details when they are not needed for your question.
05Safe use
Guardrails before, during and after the answer.
Language models can be wrong. Investboard therefore never treats an answer as the sole source of truth.
Input checks
Overlong, off-topic or manipulative inputs are bounded. Common personal-data patterns trigger a visible warning.
Numeric grounding
Figures in outputs are checked against the supplied context or a fixed list of permitted values.
Advice boundary
Buy and sell instructions, guarantees and certain claims about the future are excluded. The user decides.
Output checks
Severe violations are blocked. Where fixed wording is available, the surface falls back to it.
Traceability
Blocking decisions and many interactive calls are logged for technical review. Blocked quarterly letters are recorded as blocked and are not delivered.
06Verifiable foundations
The infrastructure claims come from first-party sources.
For Amazon Bedrock properties, we link to current AWS documentation. Investboard-specific boundaries are additionally enforced in code and tests.
No. Investboard uses AI to explain calculated findings, summarize content and match existing templates. The model cannot place an order, move money or make a decision for you.
Where are AI requests processed?
Requests start with Amazon Bedrock in Frankfurt and use a geographically bound EU inference profile. AWS may distribute processing within the European AWS geography, but cannot route it to another geography.
Are my inputs used for training?
Under Amazon Bedrock's published terms, customer inputs and model outputs are not used to improve base models and are not made available to model providers. Investboard does not use them to train its own models either.
Can an AI answer still be wrong?
Yes. Language models can make mistakes despite guardrails. Investboard therefore precomputes figures, checks outputs against context, blocks severe violations and deliberately keeps decisions outside the model.
GDPR data protectionEncrypted in transitEU hosting
Trust starts with a visible boundary.
See Investboard in the demo account or read how the rest of the security architecture protects your data.