Privacy Policy

Alverium, Inc. ("Company," "we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, store, and protect your information when you use the Alverium desktop application, website, and related services (the "Service").

Our Core Principle: Local-First

Alverium is designed as a local-first application. Most of what you do in the desktop app happens on your own machine, and we deliberately minimise what we collect on our servers.

That principle has a boundary, and we would rather draw it than let you infer it. Some features are server-side by necessity — accounts, billing, the marketplace, cloud model training, the managed Sage path, and anything published to a public blockchain. Where a feature crosses that boundary, this policy says so.

Data That Stays on Your Machine

The following is stored on your local device and is not transmitted to Alverium servers:

• Exchange and broker API keys — stored in your OS credential store (macOS Keychain, Windows Credential Manager, libsecret)
• Wallet private keys and recovery phrases — stored in your local encrypted vault
• Trade history and open positions — local database
• Workspace layouts and watchlists — local configuration
• Strategy source code and custom indicators — local file system
• Backtest results — local database
• Search history — local database
• Locally-trained models — local file system
• Trade journal entries — local database
• Sage conversations in local mode, and the on-device personalisation corpus

We have no technical ability to read your exchange API keys, your wallet private keys, or your locally-stored strategy source. The exception worth naming: if you use a feature that necessarily sends data to us — cloud model training, the managed Sage path, or a support diagnostic you explicitly attach — then that data reaches our servers, on the terms described below.

Data We Collect

Account Information

When you create an Alverium account, we collect:

• Email address — authentication, password recovery, essential service communications
• Display name — shown in the marketplace if you publish
• Hashed password — stored using a modern, computationally-hard one-way hash; we never store plaintext passwords
• Device identifiers — for licence activation. The number of devices you may activate varies by subscription tier and is published with the tier details at https://alverium.net/pricing.

Marketplace and Publishing Data

• Install and licence history — which extensions you hold
• Reviews and ratings you submit
• Purchase and payout records — for billing, tax, and accounting purposes
• Publisher information — where you publish, including information required to pay you

Cloud Model Training (opt-in)

If you use cloud model training, we do not receive your market data or your trading history. A training job is described by parameters only — the model type, the instrument symbol, the timeframe, the names of the features to use, and the number of training epochs. The training run sources its own market data; nothing from your local database is uploaded.

The trained model is stored so you can download it, together with a checksum, and is retained until you delete it or delete your account. We do not reuse your trained models and we do not train shared models on your jobs.

Alverium Sage

Sage runs on your device by default. In that mode, your prompts and conversation never leave your machine and no sub-processor is involved.

If you use the managed cloud path, the prompt and the context assembled for that turn are sent to our infrastructure and to the model provider named in the sub-processor table below. We do not train models on your prompts and we do not sell prompt data.

Crash reports

When the application encounters an unhandled error, a crash report is sent to our error-monitoring provider (named in the sub-processor table below) so we can identify and fix the defect. Crash reports carry stack traces and application state, and the integration is configured to exclude your content. You can disable crash reporting in Settings.

Usage telemetry (opt-in)

If you opt in, we collect feature-usage statistics and performance metrics — which surfaces are used and how the application performs. This is designed to exclude user identifiers and the content of anything you view or trade. You can disable it at any time in Settings.

Payments

Payments are processed by Stripe. We receive transaction records and a customer reference; we do not receive or store your card details.

On-chain activity — read this section before you register anything on a blockchain

Where you use features that interact with a public blockchain, the position is fundamentally different from everything above, and we will not soften it.

• We do handle wallet addresses and on-chain activity. To show you your positions, resolve names, index records, and relay transactions you have signed, our services necessarily process public-blockchain data, including addresses you connect and transactions associated with them.
• Anything published to a public blockchain is public and permanent. It is visible to anyone, it is replicated across a network we do not control, and it cannot be edited or deleted — not by you, not by us, not by anyone. See "Your Rights" below for what this means in practice.
• Where a feature stores content off-chain in encrypted form, the encryption keys and access rules may be governed by a mechanism in which Alverium participates. Where that is the case, the relevant service appears in the sub-processor table below.

Data We Do Not Collect

• Your exchange or broker API keys and secrets
• Your wallet private keys or recovery phrases
• Your trade history, positions, or portfolio balances held locally
• Your locally-stored strategy source code or backtest results
• Your Sage conversations when Sage runs in local mode
• Keystroke data, screen recordings, or clipboard contents
• Card details

IP addresses are processed for security, abuse mitigation, and — where required — sanctions and jurisdiction screening. They are not used to build advertising or tracking profiles.

How We Use Your Data

• Email address — authentication, recovery, critical service notices
• Device identifiers — licence enforcement
• Marketplace data — deliver marketplace features, process purchases and payouts, display reviews
• Crash reports — identify and fix defects
• Usage telemetry (opt-in) — improve performance and prioritise what to build
• Cloud training parameters — execute the job you requested
• Sage cloud context — serve the turn you requested
• IP address and jurisdiction signals — security, abuse mitigation, and compliance screening

We do not sell or rent your personal data. We share it only with the sub-processors listed below, and where required by law.

Sub-Processors

We disclose these for transparency under GDPR Art. 28 and, for the AI features, EU AI Act Art. 50.

Where you use on-chain features, additional processors may be involved in resolving, indexing, relaying, or re-keying — including blockchain node providers and any key-management service used by an encrypted-record feature. Where a specific service applies to a feature you use, it is identified at the point of use.

Where compliance screening applies, we use third-party services for sanctions screening and jurisdiction determination.

We maintain the current, complete list at https://alverium.net/subprocessors and will give at least 30 days' notice before adding or replacing a sub-processor that processes your personal data. That page, not this table, is authoritative.

Data Retention

Statutory holds. Where law requires us to retain a record — sanctions and anti-money-laundering obligations, tax and VAT records, and ordinary financial records — we retain it for the required period and use it for no other purpose, even if you have asked us to delete it. Where that applies to a deletion request, we tell you which category was retained and why.

Your Rights

If you are in the European Economic Area or the United Kingdom, you have the right to access, rectify, erase, port, object to, and restrict processing of your personal data, and to withdraw consent for optional processing. To exercise any of these, contact privacy@alverium.net. We respond within 30 days.

Two limits, stated before you need them

1. Statutory holds. Where a law requires us to keep a record, we cannot delete it on request. See the retention table.

2. Data on a public blockchain cannot be erased, rectified, or ported — by anyone.

This is not a policy choice and it is not a limitation we can lift. A public blockchain is an append-only record replicated across independent parties worldwide. Once a transaction, an address association, a name registration, or an ownership change is written to it:

• We cannot erase it. No one can.
• We cannot rectify it. A correction can only ever be a new entry; the original remains.
• Portability does not apply in the usual sense — the data is already public and already portable by anyone.

Where you exercise a right against us, we will act on the data we hold — our account records, our indexes, our caches, our logs — and we will tell you plainly which data we could not reach. We cannot act on the chain itself.

Please consider this before you publish anything on-chain, including registering a name or associating a wallet with your account. If you would not want it public permanently, do not put it on a blockchain.

Data Security

• TLS for all data in transit
• Strong, industry-standard encryption at rest for data on our servers, and locally on your device
• Access controls limiting employee access to production data
• Independent security review of our cloud infrastructure

See our Security page for detail, and for how to report a vulnerability.

Children's Privacy

The Service is not intended for anyone under 18. We do not knowingly collect data from children.

International Transfers

We are a US company and our services are operated from the United States and the European Union. Where we transfer personal data out of the EEA or the UK, we rely on appropriate safeguards, including standard contractual clauses. You may request details of the mechanism applicable to a given transfer.

Changes to This Policy

We may update this policy. Material changes will be communicated via email or in-app notification at least 30 days before taking effect. The Last Updated date reflects the most recent change of any kind.

Contact

For privacy questions or requests:

Alverium, Inc. Email: privacy@alverium.net