1. Scope
This Policy applies to the public website at www.capital4trade.com and the authenticated Capital4Trade member portal available after login through the same domain. It does not apply to mycreditapp.ai or other websites and applications that publish their own privacy or cookie policies.
This Policy should be read together with the Capital4Trade Privacy Policy, which explains how Capital4Trade processes personal information more broadly.
2. Cookies & Similar Technologies
2.1 Cookies
A cookie is a small piece of data stored by a browser at the request of a website. Cookies may be temporary or persistent and may be available only to the host that created them or, when configured, to a broader domain. Capital4Trade uses a host-only authentication cookie after a successful login.
2.2 Local Storage
Local storage is browser storage associated with a website. Unlike a cookie, local-storage data is not automatically included in requests to a server. Local-storage entries generally remain until the website or user removes them and do not have a built-in expiration unless the application implements one.
2.3 First-Party and Third-Party Technologies
A first-party technology is created or controlled through the domain the user is visiting. A third-party technology is provided through another organization or domain. The technologies identified in Section 4 are first-party technologies. Capital4Trade does not currently use third-party analytics or advertising cookies.
3. Categories Used by Capital4Trade
3.1 Strictly Necessary
Strictly necessary technologies support authentication, security, delivery of requested services, and recording that the informational cookie notice has already been displayed. They cannot be disabled through a Capital4Trade preference panel because the relevant service or requested function would not operate as intended.
3.2 Functional
Functional storage remembers choices made by a user, such as a preferred calendar provider, dismissal of a profile-completion card, or completion of guided tours. These entries do not contain authentication tokens and are not used for advertising or cross-site tracking.
4. Current Technology Inventory
The following inventory reflects technologies currently identified or approved for deployment on the Capital4Trade domain:
| Name | Technology / Category | Purpose | Duration |
|---|---|---|---|
| jwt | First-party cookie · Strictly Necessary | Authenticates the user after a successful login and maintains the secure account session. HttpOnly; Secure in production; SameSite=Lax; Path=/. | 24 hours, or earlier upon logout or server-side revocation |
| c4t_calendar_pref | Local storage · Functional | Remembers the user's last selected calendar provider to facilitate creation of events. Contains no credentials or authentication data. | Until updated or deleted by the application or user |
| profile_complete_card_dismissed | Local storage · Functional | Records that the user dismissed the profile-completion card so the interface can remember that choice. Contains no sensitive information. | Until deleted by the application or user |
| c4t_tours | Local storage · Functional | Records which guided tours or onboarding prompts the user completed or dismissed so they are not unnecessarily repeated. | Until deleted by the application or user |
| c4t-cookie-notice | Local storage · Strictly Necessary / Preference | Records acknowledgement of the informational notice, including the applicable policy version and acknowledgement date, so the notice is not repeatedly displayed. | 6 months, or until deleted by the user |
4.1 Authentication Cookie Details. The jwt cookie is created only after a successful login — not merely because a person visits the public website, begins registration, or requests a password reset. Password-recovery tokens are separate from the jwt session cookie. The jwt value is not exposed to client-side JavaScript and is not stored in localStorage or sessionStorage. There is no "Remember me" option. On logout, the application immediately removes the cookie and invalidates the session through its server-side revocation mechanism.
5. Technologies We Do Not Currently Use
Capital4Trade does not currently use browser cookies or similar technologies for analytics, behavioral advertising, cross-context advertising, or social-media tracking. Based on the current technical inventory prepared for this Policy, Capital4Trade has not identified Google Analytics, Google Tag Manager, Microsoft Clarity, Sentry, PostHog, Hotjar, Meta Pixel, LinkedIn Insight Tag, or comparable browser-tracking tools.
Capital4Trade does not currently use persistent cookies for CSRF protection, language, visual theme, or consent management. CSRF protection for authenticated requests does not rely on a CSRF token stored in localStorage or sessionStorage.
If Capital4Trade later introduces a non-essential analytics, advertising, or similar technology, it will update this Policy and, where required, obtain consent before activating that technology. Non-essential categories will be disabled by default until the user makes a valid choice.
6. Informational Notice
Because Capital4Trade currently uses only technologies that are necessary for authentication, security, requested functionality, or storage of the notice preference, the website presents an informational notice rather than requesting consent for technologies that are not in use.
6.1 Notice Text
"Capital4Trade uses strictly necessary cookies and local storage to authenticate users, protect the Platform, remember functional preferences, and support requested functionality. We currently do not use analytics or advertising cookies. Learn more in our Cookie Policy."
6.2 Notice Controls. The notice provides a "Got It" button and a link to this Cookie Policy. Selecting "Got It" creates the c4t-cookie-notice local-storage entry described in Section 4. The notice is presented again after six months, when the policy version changes, or when the user deletes site data. A permanent "Cookie Settings" link is available in the website footer.
7. Managing Cookies & Local Storage
Users can inspect, block, or delete cookies and local storage through browser settings. Browser instructions vary by provider and device. Deleting the jwt cookie will end or disrupt the authenticated session and require the user to log in again. Blocking necessary cookies may prevent account access or requested Platform features from functioning.
Deleting functional local storage will reset the associated preference or interface state. Capital4Trade may recreate an entry when the user again selects the relevant preference, dismisses a prompt, completes a guided tour, or acknowledges the informational notice.
8. Hosting & Server-Side Monitoring
8.1 Railway Hosting
The Capital4Trade platform is hosted through Railway. Infrastructure providers may process technical request data and may, in some configurations, use a strictly necessary routing, security, load-balancing, or anti-abuse cookie. Capital4Trade will update the inventory in Section 4 if production verification identifies an additional browser cookie.
8.2 Microsoft Application Insights
Microsoft Application Insights may be used for server-side monitoring of the Capital4Trade API when configured. In the current architecture, it does not monitor browser activity or create a browser cookie. Related processing of server logs and technical request information is addressed in the Privacy Policy.
8.3 Server-to-Server ERP Integration
Capital4Trade's backend communicates with its enterprise resource planning system through secure server-to-server APIs to support Platform functionality. This integration does not communicate directly with the user's browser and does not create or access browser cookies, local storage, or session storage. Personal and business information processed through this integration is addressed in the Privacy Policy.
9. Changes to This Policy
Capital4Trade may update this Policy to reflect changes in technology, law, infrastructure, or business practices. The revised Policy will state its updated date. If a change introduces a non-essential technology that requires consent, Capital4Trade will provide the required choice before activating that technology for the affected user.
10. Contact Us
Questions or requests concerning cookies, local storage, or this Policy may be submitted as follows:
Transport Networks LLC, doing business as Capital4Trade Network
Email: support@capital4trade.com · Subject line: Privacy Request
Contact form: capital4trade.com/contact
Mail: 11410 NW 20 Street, Suite 224, Miami, Florida 33172, United States