● contact

Who to write to — and what actually happens next

One published mailbox, three subject lines, and a straight answer about what we do and do not commit to. An address, a phone number or a response time we have not committed to is named as missing rather than filled in with something plausible.

The one address
[email protected]

This is the address the Terms and the privacy notice already publish. We route by subject line instead of advertising department aliases, because an alias that bounces costs you a day and tells you nothing.

Three routes, one inbox

Each link pre-fills the subject so your message lands in the right pile.

Commercial & partnerships

Evaluating the terminal for a desk, asking what a seat would cost, or proposing a data or distribution partnership. There is no price list and no procurement track yet — the pricing page says so in full — so this is a conversation, not a quote request.

Include Who the users would be, what they would replace, and the question you actually need answered.

[email protected] · “Sales — AtlasVector” →

Product support

A number looks wrong, a screen will not load, an account is stuck in the email → phone → authenticator ladder. Every trading surface is a simulated account, so no support request here can move money.

Include The page URL, the ticker, the time you saw it and what you expected instead. A screenshot settles most of it.

[email protected] · “Support — AtlasVector” →

Security disclosure

Report a vulnerability. We ask that you test only against accounts you own, take no more data than proves the finding, and give us a chance to fix it before publishing. There is no bug-bounty programme and no monetary reward — we will credit you by name if you want that, and say so plainly rather than imply a payout.

Include Reproduction steps, the affected URL or endpoint, and how you would like to be credited.

[email protected] · “Security disclosure — AtlasVector” →

Before you write about cost or access: what it costs and what needs an account answers both in full, including the fact that no list price is set.

What we commit to, and what we don’t

The second answer is the one a risk function needs, so it is written out rather than left blank.

Privacy and data-rights requests

Answered within the timeframe applicable law requires. That is a legal obligation rather than a courtesy, and it is the same commitment the privacy notice makes.

The privacy notice →

Everything else

No response time is contracted for a message sent to this address. There is no support tier, no ticket queue and no on-call rota behind it — messages go to a shared mailbox read by the people who build the product. The one timeline we have written down, the incident notice, is published in advance on the service-levels page and is not in force until a signed agreement incorporates it.

The published service levels →

What doesn’t exist yet

Listed rather than omitted — listed here rather than omitted.
  • No phone lineThere is no support number to answer one, so none is printed. Mail is the only route to us, including on a market day.
  • No published postal addressNone is published as a contact route. Post would be slower than the mailbox above and would reach the same people.
  • No uptime history or incident logThe status board reports what is answering right now, and the service-level terms are published in advance — but nothing retains an availability series and no incident register exists, so no uptime percentage and no incident history is published. Those rows are listed as outstanding on the due-diligence index.
  • No support tiersNothing is sold, so nothing is tiered. Every message arrives in the same place with the same priority.

One thing not to send

Don’t send account numbers, statements or anything you would not put on a postcard, and don’t ask what to buy. AtlasVector is a markets-research platform and not an investment adviser — nobody at this address can tell you what to do with your money. Research — your decisions, your risk. See the disclaimer.