Log In Start Free Trial →
🧠 ARIA Intelligence
Ask any financial question. Structured answer, sourced.
Navigation Home About ValixData Pricing Help Center Contact Terminals Find My Terminal with ARIA All 130+ Terminals Private Equity Hedge Fund Family Office M&A Advisory Real Estate Technology Platform Document Intelligence Report Builder Watch Alerts
Data & Privacy

What we keep.
And what we don't.

ValixData is built for finance professionals. The questions you ask and the analysis you run reflect how you think about markets, companies, and decisions. We designed our data model around one principle: we only store what is strictly necessary to operate the service. Nothing else.

Our commitment
We do not log your ARIA conversations. We do not build behavioral profiles from your activity. We do not track what you analyze, what you search for, or how you use the platform beyond what is required to keep your account and your terminals working. We do not sell data. We do not share data with advertisers. We do not train our models on your queries.

What we keep — and why

Seven things. Each has a specific, functional reason. If we could achieve the same outcome without storing it, we would.

01 Your email address and authentication credential Our server

We need to know who you are to let you in. Your password is hashed — we store a cryptographic representation of it, not the password itself. We cannot recover your password. If we couldn't store your email, you would start from scratch every session.

02 Your subscription and payment relationship Stripe

We store a Stripe customer ID and your current plan. Your payment details live entirely within Stripe — we never see or store a card number. We need the plan record to know which terminals you're entitled to and to enforce access limits. Without it, the platform would be free for everyone.

03 Which terminals you own Our server

A list of your terminal subscriptions — for example, Private Equity, Credit, Global Macro. Without this, your terminals disappear every time you close your browser. This is an entitlement record, not a behavioral record. It records what you paid for, not what you do.

04 Your command center tile selections Our server

If you build a custom command center — pinning specific KPI tiles from different terminals — that selection needs to survive across sessions. This is a preference you set explicitly, stored alongside your terminal list. You can change or delete it at any time.

05 Your watch alert thresholds Our server

If you set an alert — "notify me when HY OAS crosses 325bps" — that condition must be stored on our server. Watch alerts are checked on a scheduled basis while your browser is closed. There is no client-side alternative for a feature that works when you're not looking at the screen. You can delete any or all watches at any time.

06 Email verification status Our server

Whether your email address has been confirmed. This is a security control — unverified accounts have restricted access. It needs to survive between sessions.

07 API keys, if you generate them Our server

If you use the developer API, we store a cryptographic hash of your API key — the same approach as passwords. We cannot recover the key itself. It is shown to you once at creation. If you don't use the API, no API key is stored.

What we cache — not your data

Three things are stored temporarily at the terminal level, not the user level. The same content is served to everyone on that terminal. None of it is personal.

NOVA overnight analysis — per terminal, resets daily
ARIA generates a fresh brief for each of the 130 professional terminals every night. This is cached so it loads instantly for all users on that terminal — not regenerated for each person. It contains no personal data. It deletes itself after 7 days.
Market data — FRED, EIA, BLS feeds, TTL-controlled
Live data from public sources is cached to avoid hammering public APIs on every page load. The same cached values are served to all users. No personal data. Expires based on source update frequency.
Public intelligence pages — Divergence, Clock, Daily Brief
The weekly Divergence report and Market Regime Clock are the same for every visitor. They are cached to serve efficiently. No user data involved.
What we do not store — ever
Your ARIA conversations
What you ask ARIA stays in your session. When you close the tab or log out, the conversation is gone. We do not log the questions. We do not store the responses. We cannot go back and read what you asked.
Behavioral profiles — what you click, how long you hover, what you read
We do not track which KPI tiles you look at, which articles you expand, which scenarios you run, or how long you spend on any section. There is no behavioral profile being built on your activity. The platform does not watch you use it.
The topics you analyze
If you spend a session analyzing HY credit conditions or a specific company's financials, that analytical focus is not recorded anywhere. We do not infer your investment thesis, your portfolio positions, or your areas of professional interest from your behavior.
When you log in and how often
We do not maintain a server-side log of your session times, login frequency, or visit patterns. Features like streak counters live on your device — in browser localStorage — not on our servers.
Documents you upload for ARIA analysis
When you upload a document — a 10-K, a term sheet, a transcript — ARIA analyzes it in memory during that session. The document is not stored on our servers. It is not used to train any model. When your session ends, it is gone.
Third-party tracking or advertising data
We do not use advertising trackers, third-party analytics pixels, or cross-site tracking of any kind. We do not share your identity or usage patterns with any advertising network. We do not run ads.
Your data as training data
Your conversations with ARIA, the documents you analyze, and the questions you ask are not used to train or fine-tune any AI model — ours or anyone else's. Your work is yours.
The principle behind all of this
There is one question we ask before storing anything: did the user give us this, or are we taking it by observing them? Email addresses, terminal selections, watch thresholds, tile preferences — you give us these directly, for a specific purpose. Behavioral patterns, analytical focus, timing habits, conversation content — these are things we would take without asking. We don't take them. The line between the two is the line between a service relationship and surveillance. We stay on the right side of it.

Your data, your control

The seven things we store can be accessed, corrected, or deleted at any time. No waiting period. No friction.

Delete your account and everything in it

Deleting your account permanently removes your email, your terminal subscriptions, your command center configuration, and your watch alerts from our servers. The deletion is immediate and irreversible. Your Stripe billing relationship is cancelled at the same time. We retain nothing after deletion.

Delete account →

Export what we have on you

You can request a copy of every piece of data we hold about you — your account details, terminal list, watch thresholds, and command center configuration. It arrives as a JSON file within 24 hours. There will not be much in it.

Request export →
Last updated April 20, 2026. Questions about this policy: Contact Us · Our full promise → · Full privacy policy →