How to Share a MyVeridex Trading Profile and Check Its Visibility

5 min read trading 5/4/2026

MyVeridex lets you publish a trading profile at a username URL. Set the username and public-profile option in Settings, save the profile, then inspect the address while logged out before sending it. Treat it as a public page, with the account selection and data coverage you actually see, rather than a private invitation or an independently audited report.

Check the account data before changing visibility

Open the account you intend to describe and compare its currency, broker, account context, last successful sync and available history with your source records. MyVeridex currently offers MT4 and MT5 connections. A broker name in a directory is not confirmation that a particular server or account can connect successfully.

Connection uses the investor password rather than the master trading password. The official MetaTrader guide explains the read-only permission. Do not put either credential in your bio, a screenshot, an export sent to someone else or the profile URL. Read-only access limits trading permissions; it is not an absolute security guarantee.

If some history came from a supported statement import, disclose that. Imported closed-trade history cannot recreate a complete past floating-equity path. A successful connection also does not prove that the service retrieved every historical transaction. Check the dates and reconcile the figures before sharing them.

Publish the profile through Settings

Open Settings and the Public Profile section.
Choose a public username and review the name, bio and social links that will accompany it. Use a bio that accurately describes the account context and reporting scope.
Turn on the public-profile option and use Save Profile. A toggle change alone is not proof that the change has been saved.
Copy the displayed profile address. The address uses https://myveridex.com/@your-username, with your actual saved username.
Open that address while logged out, or in a separate private browser session, and inspect what a recipient can see.

These steps describe the current Settings controls. They do not require a new trading account, a transfer or sharing a password with the recipient. Do not enable visibility if you lack permission to disclose the account's information.

Inspect the public page instead of assuming its scope

Check	What to look for	Why it matters
Identity and URL	The expected username, name, bio and social links	A mistyped URL or stale profile can describe someone else
Accounts shown	Every account visible on the page, including broker, currency and account context	Do not assume that only the currently selected dashboard account becomes public
Trade-log coverage	The dates and count of trades actually displayed	The current public view shows a recent closed-trade list, limited to twenty entries; it is not the full transaction ledger
Aggregated figures	Which accounts, periods and currencies feed each figure	Do not present combined numbers as one account's result or add different currencies without a stated method
Status and freshness	Visible account status and the source's last successful update	A working link does not establish current, complete or independently audited data

The current sharing workflow is a profile-level public setting. It does not establish a per-recipient password, an expiring invitation or an individual-trade hiding control. If the displayed scope does not meet your privacy needs, leave the profile private and prepare a permitted, redacted evidence pack instead. The evidence checklist explains how to retain useful source detail.

Add a short disclosure next to the link

State the account context, selected accounts, reporting period, timezone and known gaps. Explain whether figures come from a connection, a supported import or both. Say whether risk figures describe closed-trade balances or observed equity. For a full-period review, supply the permitted source records separately; the recent public trade list is not a substitute.

Do not call the profile immutable, independent proof of ownership or a formal audit. MyVeridex account checks have a defined product scope; read what the account checks establish. A recipient decides what evidence it requires. Publishing a profile does not guarantee a successful evaluation, a payout or investment interest.

Recheck after editing or turning the profile off

Save any visibility change, reload Settings and inspect the public address while logged out again. Verify the outcome before treating the change as complete. Turning a page private cannot retract copies, screenshots or exports that a recipient has already kept, and should not be described as instant removal from every cache.

Keep a dated note of the address and scope you shared. If the data later changes, explain the correction to the recipient rather than relying on a previous screenshot. For collecting a defined observation period, use the separate 90-day record protocol.

Frequently asked questions

Where is the public-profile sharing control?

Use Settings, choose a public username in Public Profile, turn on the visibility option and save the profile. Inspect the saved address while logged out before sharing it.

Is the profile a private or password-protected report link?

The described control publishes a profile-level public page. Do not assume recipient-specific passwords, expiry or individual-trade hiding controls. Inspect the actual visible scope and keep the profile private if it is unsuitable.

Does the public trade list contain the entire account history?

No. The current public view limits its recent closed-trade list to twenty entries. Provide the permitted source statement and ledger separately if the recipient needs a complete period.

Does turning the profile private remove copies someone already has?

No. Save the visibility change and check the logged-out page, but previous screenshots, exports and copies can remain with their recipients.

Pedro Penin, Founder of MyVeridex.