Optional enquiry journey measurement
With the updated optional analytics preference, VCM may link contact-page opens, enquiry-form starts, and email-link clicks to a consented visit. These events contain only an event label and visit identifier; form text, search text and enquiry email addresses are not copied into analytics. The server records a provider-accepted enquiry only after the configured delivery provider accepts it, and only for a visit with the corresponding consent. Each goal is counted once per visit. Email clicks do not confirm that an email was sent, delivered or converted into a purchase. Journey records are deleted with their visit under the same inactivity retention policy. Declining optional analytics keeps these measurements off.
Optional first-party visit analytics
If you allow visit analytics, VCM records a random browser-visit identifier, first and last check-in, entry-page category, coarse device/browser/OS, browser-reported mobile model where supported and approximate network country, recognised campaign source or referring hostname, and estimated active seconds. We discard referral paths, search queries, URL fragments and unrecognised campaign values. Anonymous network addresses are shortened to IPv4 /24 or IPv6 /48 ranges. If you sign in, your verified VCM email and network IP may be linked to that visit. We cannot access your Google, Facebook or browser-account email. A signed, HttpOnly first-party cookie lasts 30 minutes after the latest check-in; your allow/decline preference is stored for up to 180 days. You can change it using Visit analytics preferences. Global Privacy Control and Do Not Track disable this optional reporting. Only the verified VCM owner account can read visitor records. They are removed after 30 days of inactivity on the next report or write; database backups follow provider retention. Essential signed-in activity records are separate. Only the model browser hint is requested after optional analytics consent; other high-entropy hints are not requested. Exact iPhone models are often unavailable and are never guessed. Country is estimated from the network IP, may reflect a VPN, and is not physical-location verification. Existing records have unknown country/model until a new check-in supplies them. Sources and durations are estimates; blocked requests and declined consent leave gaps.
Signed-in account activity
For signed-in accounts we record the verified account email, sign-in time, first recorded visit, last activity, reported device category, model/family where available in ordinary browser headers, browser and operating system, approximate network country, network IP address where available, and estimated active seconds. This supports account security and service administration and is separate from optional visitor analytics. It does not record form contents, passwords, verification codes or session tokens. Only the verified vertexcapitalmarkets@gmail.com owner account can read these records through the activity dashboard. Records older than 30 days of inactivity are removed on the next activity write or owner report request, and are excluded thereafter; backup retention follows the database provider. Active time is approximate and may miss activity or include idle intervals. Device and IP metadata are not proof of identity. Contact customer care for access or deletion requests.
Individual account management records
When you apply, we store your verified user ID, name, country, preferred capital, broker preference and risk-questionnaire answers. Individual account references, dated statement figures, trades, broker funding records, fee calculations, agreement versions and acknowledgements may be recorded for your private reporting. Your records are accessible to your verified account and authorised management administrators. Administrative changes retain the acting user ID and time. We do not request identity-document uploads or broker passwords here. Identity-review and signed-mandate references relate to separate secure processes. Exported reports are downloaded to your device. Retention and deletion requests should be raised with customer care; obligations depend on the final service agreement and applicable rules.
Visitor analytics
This website includes Vercel Web Analytics. When enabled for the deployed project, it helps us understand visitor numbers, popular pages, referral sources, approximate locations and device types. Browsing alone does not provide us with your name or email address.
Website performance monitoring
This website includes Vercel Speed Insights. When enabled for the deployed project, it measures page-loading speed, visual stability and responsiveness. Measurements can include page URLs, timing information and technical browser or device information. We use these measurements to identify slow pages and improve the browsing experience.
Limits of these integrations
Our analytics and performance components remove query parameters and URL fragments from the page URLs they report. We have not added session recordings, form-entry recording, individual demo-trade tracking or custom sales-event tracking through these integrations. Vercel processes collected information under its own privacy practices.
Browser privacy preferences
Our analytics and performance components skip sending measurement events when the browser exposes an enabled Global Privacy Control signal or a Do Not Track value of 1. Browser support varies. These checks do not prevent essential hosting requests, measurement-script downloads or requests made by separate external services.
Enquiry preparation
Without a configured delivery provider, the enquiry form keeps your entries in the open page and prepares text for you to review, copy or open in your email app. It does not send the enquiry to VCM or store it in a VCM database. Opening an email draft does not mean that an email has been sent.
Optional direct enquiry delivery
If direct delivery is configured, the form identifies that mode before submission. Your name, email address, selected service, package, platform and message are passed through the website's enquiry route to Formspree. A successful response means the provider accepted the submission; it does not guarantee inbox delivery or a reply. The website code does not intentionally log form contents or create a separate enquiry database.
Email correspondence
Emails you send are processed by the relevant email providers, including Gmail for our published business address. Correspondence may be retained by the business and its providers. A fixed business retention period has not yet been published.
Trading journal storage
Trading plans, journal entries and selected currency are saved in your browser. They are manually entered records, not broker positions or verified results. Clearing site storage removes them.
Saved market watchlist
The Markets page saves selected watchlist symbols in your browser's local storage. This is separate from the trading journal and does not place trades.
External charts and links
Loading TradingView charts makes requests to external services. Those services may receive technical information such as your IP address and browser details and may use cookies or similar technologies. Removing or pausing a chart does not undo earlier requests. Telegram and other external links open services governed by their own privacy practices.
Hosting and security logs
This website is hosted on Vercel. Hosting and security services may process request information, IP addresses, timestamps and technical logs to deliver the website, diagnose errors and respond to abuse. These records are separate from visitor analytics.
Information you should not submit
Do not send broker passwords, private API keys, identity documents, payment-card details or account statements through a general enquiry. The market workspace does not require a deposit or broker credentials.
Privacy questions
Contact our published business email with questions or requests concerning information you have provided. How a request can be handled depends on the records held and applicable obligations. The legal business identity, jurisdiction and detailed retention arrangements still need to be published.