Skip to content
QuantIDE

Security & data handling

Built so there is nothing for us to lose.

Most platforms secure your research by guarding the copy they hold. QuantIDE holds none. Your code, research and credentials stay on your own machines, and this page lists everything that does leave them.

Request the diligence packEvery connection the app makes

What we hold

A short list, by design.

The safest copy of your research is the one that was never made. QuantIDE runs on your hardware, so the list of what we could ever lose is the list on the right.

Never held by us

  • Strategy and research source code
  • Backtests, results and reports
  • Broker, exchange and data credentials
  • Positions, orders, balances and trading history
  • AI conversations and the files they touched

All of it lives on your machines, as files you can read, back up and delete.

Held by us

  • Your email address and username
  • A one-way hash of your password, never the password
  • Subscription status. Cards are held by Stripe, not by us
  • Licence checks, with an identifier for each installed device
  • Anonymised usage and crash data, which you can switch off
  • Anything you send to support

The detail is in the privacy policy.

Data flow

Every connection the app makes.

This is the complete list. Nothing listed here carries your strategy to us, and nothing else leaves your machine. Your security team can verify it at the firewall.

Your QuantIDE account

Sign-in and a check that the subscription is active.

Encrypted in transit. Carries no project data.

The AI engine you choose

The conversation, and the project files the engine opens to do the work you asked for.

Your own account with the provider, under its terms. Can be switched off entirely.

Your broker and data providers

Whatever that API needs: market data, orders, account queries.

Direct from your machine with your keys. It never passes through us.

Yahoo Finance

Requests for historical prices, when research asks for them.

Cached on your disk. Public data only.

Updates

A check for a new version, and the signed installer.

Verified before it installs. You choose when.

Usage and crash reports

Anonymised detail of which features are used, and what failed when the app crashes.

No code, prompts, files or credentials. Can be switched off.

Credentials and capital

Keys stay with you. So does the trigger.

01Encrypted on your device

Broker, exchange and data credentials are encrypted at rest on the machine that uses them. They are never sent to us, and never included when a stack is shared with a colleague or an engineer.

02One key, one connection

Each integration is its own project with credentials scoped to that connection alone. We recommend keys with withdrawals disabled and the narrowest permissions the strategy needs, and adapters are written to work with them.

03Nothing trades by default

Live order routing is never on out of the box. It is built, tested against paper, and switched on by you. Every trading decision and every account stays yours.

Blackshore Agency

How our engineers are given access.

Engineering capacity is only useful if it is safe to let in. Access is granted by you, for the work you name, and ends when it does.

Approved per engagement

Nobody works in your stack until you approve the engagement and the engineers on it. You see their names before they start.

Under confidentiality

Every engineer works under a confidentiality agreement, and a mutual NDA can be signed before the first call.

Sandbox and paper keys only

Engineers never ask for your live trading credentials. Work is built and tested against paper or sandbox accounts and handed to you to switch on.

Servers in your name

When a strategy needs to run around the clock, engineers set up a server in your name and manage it. You pay the provider directly, enter live keys yourself, and can remove our access at any moment.

Every change on the record

Work arrives as commits in your repository, reviewable and reversible, so there is a complete account of who changed what and when.

Revocable at any time

Access can be withdrawn at any moment, and ends with the engagement. What was built stays with you.

Our own house

How we run what we do hold.

Signed software

Installers are code-signed, and notarised on macOS. Updates are signed and verified before they install, and you choose when to install them.

Accounts

Passwords are stored as one-way hashes. Payments are handled by Stripe; we never see or store a full card number. Every connection to our services is encrypted in transit.

Staff access

Multi-factor authentication on every administrative system. Access to account records is limited to the people who need it, and logged.

Incidents

If an incident affects your data, we tell you within 72 hours of confirming it: what happened, what it touched, and what we have done.

Disclosure

Security reports go to security@quantide.io. We acknowledge within two business days and do not pursue good-faith research.

Due diligence

Run diligence on us. We expect it.

For funds, family offices and their operations teams, we provide the following under NDA, usually within two business days of the request.

Questionnaire

Your security questionnaire, completed in full, or our standard responses.

Data flow

A diagram of every component and connection, matching this page.

Subprocessors

Every third party that handles account or billing data, and why.

Agreements

Mutual NDA, data processing agreement and engagement terms.

Request the diligence packArrange a private briefing

Questions

What risk teams ask.

Is QuantIDE SOC 2 or ISO 27001 certified?

Not today. The design makes most of that scope unnecessary: we do not hold your research, code, credentials or trading data, so there is no store of it to certify. What we do hold, your account and subscription, is described on this page in full. We complete security questionnaires in full, and the diligence pack is available under NDA.

Where is our data stored?

Your projects, research, results and credentials are files on the machines you install QuantIDE on, or on a server in your name that our engineers set up and manage for you, and nowhere else unless you put them there: your own git remote, your own backup. We host nothing. Account and subscription records are held by us and by Stripe.

Can we run QuantIDE with no AI at all?

Yes. AI features can be switched off entirely, after which the only connections out are the account check and updates. Where a mandate rules out AI, Blackshore Agency engineers can do the work by hand, inside your workspace.

Do the AI providers train on our code?

We do not use your code or strategies to train anything, and the engines run under your own account with the provider, so its terms are the ones you agreed. If your organisation holds an enterprise or zero-retention agreement with that provider, that is the agreement that applies.

Can Blackshore Agency engineers see our positions or move money?

No. Engineers build and test against sandbox or paper credentials and never ask for your live keys. On a server they manage for you, live keys are entered by you, and their access to that server is yours to grant and to revoke. Live order routing is switched on by you, after it has been tested against paper.

What happens to our work if we cancel?

It stays where it always was: on your disk, in your repository, as source code you own. Nothing you built depends on a hosted service we could switch off.

How do we report a vulnerability?

Write to security@quantide.io. We acknowledge within two business days, keep you informed until it is fixed, and will not pursue good-faith research that respects our users’ data and stops at proof of the issue.

Your research stays yours. Ours is to prove it.

Arrange a private briefing