Security and trust

Built to protect the account, not just the interface.

Tidava is a standalone analysis terminal — no broker connection, no funds, no order execution. This page explains how we protect accounts, user isolation and access control.

Start Free Trial → See Signal Pages
Account data
Encrypted
Sensitive account data is protected in transit and at rest.
User scope
Isolated
One user should not see another user’s account or private workspace state.
Admin access
Restricted
Sensitive routes are locked down more tightly than normal product flows.
Login defense
5x lockout
Repeated failed attempts trigger temporary lockout and audit tracking.
Access model
Analysis-only
No broker keys, no funds and no order execution are requested.

What we protect

A terminal can look polished and still handle sensitive data badly. The goal here is simple: keep credentials, account state, and user-specific settings protected and correctly scoped in normal use.

Account credentials. Passwords and session data are hashed, protected and never echoed back into the UI.
Per-user state. Preferences, account selections, and private data should stay scoped to the signed-in user instead of leaking across sessions.
Admin controls. Sensitive operations deserve tighter routing, stronger access checks, and a smaller blast radius if a session is abused.

Encryption at rest

Stored account secrets are treated as sensitive material, not general app settings. Encryption reduces risk; it does not remove all operational risk.

Access and origin controls

Session checks, trusted host handling, rate limits, and tighter upstream/origin exposure reduce easy abuse and make direct scraping or brute-force attempts harder.

User-visible controls

People can rotate their password, manage active sessions and remove account data without needing a broker connection.

What we never claim

Strong security copy is precise. Weak security copy sounds absolute. That is not the standard we want.

Not “unhackable.” No public web platform should say that.
Not “guaranteed safe.” Security is layers, monitoring, and sensible limits, not magic wording.
Not vague hype. Trust pages should explain what is protected, what users control, and what good operational behavior still matters.

Can another user see my account or workspace?

No. Account data and workspace state are scoped to the signed-in user. Tidava never holds a broker balance or exposes one user’s private state to another.

Can I connect a broker account?

No. Tidava does not connect to broker accounts, does not hold funds and cannot place orders. It is a standalone market-analysis terminal.

Does Tidava replace my judgment?

No. Tidava is a market-analysis platform. It helps users read the market more clearly; it does not replace a licensed adviser.

Security belongs beside Education and Pricing

For a trading terminal, trust is not footer copy. It belongs beside Education and Pricing because users decide whether to trust a platform long before they become long-term customers.

Education

Explains how to read a signal and how to think with the product.

Security

Explains how accounts, keys, and access are handled so trust is earned before a connection is made.

Risk disclosure

Explains clearly that trading involves risk and that analysis does not guarantee results.