{"id":3,"date":"2024-07-02T02:56:47","date_gmt":"2024-07-02T02:56:47","guid":{"rendered":"http:\/\/vertex-integration.hopto.me\/?page_id=3"},"modified":"2026-07-09T17:24:18","modified_gmt":"2026-07-09T22:24:18","slug":"privacy-policy","status":"publish","type":"page","link":"https:\/\/www.tempus-trade-capital.com\/?page_id=3","title":{"rendered":"Privacy Policy"},"content":{"rendered":"\n<h1 class=\"wp-block-heading\">Table of Contents<\/h1>\n\n\n\n<p>1. Policy Scope and Status<\/p>\n\n\n\n<p>2. Information We Collect<\/p>\n\n\n\n<p>3. How We Use Information<\/p>\n\n\n\n<p>4. Cookies, Tracking Technologies, and Similar Tools<\/p>\n\n\n\n<p>5. Disclosure of Information<\/p>\n\n\n\n<p>6. Payment Processing and PCI Scope<\/p>\n\n\n\n<p>7. Data Security<\/p>\n\n\n\n<p>8. Retention and Deletion<\/p>\n\n\n\n<p>9. Privacy Rights and Request Handling<\/p>\n\n\n\n<p>10. Children&#8217;s Privacy<\/p>\n\n\n\n<p>11. Health Information and HIPAA Status<\/p>\n\n\n\n<p>12. International Data Transfers<\/p>\n\n\n\n<p>13. User Choices and Controls<\/p>\n\n\n\n<p>14. Public Areas, Comments, Reviews, and User-Submitted Content<\/p>\n\n\n\n<p>15. Financial, Trading, and Proprietary Information Boundaries<\/p>\n\n\n\n<p>16. Privacy Incidents, Security Incidents, and Breach Response<\/p>\n\n\n\n<p>17. Changes to This Policy<\/p>\n\n\n\n<p>18. Contact Information<\/p>\n\n\n\n<p><\/p>\n\n\n\n<h1 class=\"wp-block-heading\">1. Policy Scope and Status<\/h1>\n\n\n\n<p>This Privacy Policy explains how Tempus Trade Capital collects, uses, discloses, retains, and protects information when individuals access or use a WordPress and WooCommerce eCommerce website, create or use an account, log in or log out, browse anonymously, purchase proprietary products, access podcasts, register for or attend real-time training sessions, submit support requests, subscribe to communications, or interact with related online services.<\/p>\n\n\n\n<p>This document is intended to operate as a public-facing privacy notice and as an implementation baseline for the website, payment, account-management, training, podcast, analytics, marketing, security, and customer-support workflows that support the site.<\/p>\n\n\n\n<p>This policy does not constitute legal advice. Privacy obligations depend on jurisdiction, customer location, company role, data type, vendor role, processing purpose, business thresholds, sector obligations, and contractual commitments. Qualified privacy counsel should review this document before external publication.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1.1 Website Environment Covered<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A WordPress website using WooCommerce or equivalent eCommerce functionality.<\/li>\n\n\n\n<li>User registration, authentication, session handling, logout, password reset, and account profile features.<\/li>\n\n\n\n<li>Anonymous browsing, cookies, log files, analytics, security telemetry, and advertising or conversion measurement tools if enabled.<\/li>\n\n\n\n<li>Payment checkout flows involving payment processors, card networks, ACH providers, PayPal, Stripe, WooCommerce-related payment extensions, banks, clearing houses, fraud controls, and transaction settlement providers.<\/li>\n\n\n\n<li>Digital and proprietary products, subscription or membership content, downloadable materials, licenses, educational resources, software, training materials, trading education, market analysis, signals, podcasts, and real-time training sessions.<\/li>\n\n\n\n<li>Support, refund, dispute, chargeback, customer service, compliance, fraud-prevention, and security workflows.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">1.2 Entity Role<\/h2>\n\n\n\n<p>For most direct interactions with customers, Tempus Trade Capital acts as the business or controller responsible for deciding why and how personal information is processed. Certain vendors may act as processors, service providers, contractors, subprocessors, independent controllers, or independent businesses depending on their service function, contractual role, and legal regime. Payment processors and financial institutions often process some payment information under their own legal obligations and independent policies.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1.3 Key Definitions<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><td><strong>Term<\/strong><\/td><td><strong>Meaning in this Policy<\/strong><\/td><\/tr><\/thead><tbody><tr><td>Personal information \/ personal data<\/td><td>Information that identifies, relates to, describes, can reasonably be associated with, or could reasonably be linked to an identified or identifiable individual or household.<\/td><\/tr><tr><td>Sensitive personal information<\/td><td>Higher-risk data such as account credentials, precise geolocation if collected, government identifiers if collected, payment-related identifiers, financial account information, health data if collected, biometric data if collected, racial or ethnic origin, political opinions, union membership, religious beliefs, sexual orientation, and similar data depending on jurisdiction.<\/td><\/tr><tr><td>Payment data<\/td><td>Information used to initiate, process, authenticate, authorize, settle, refund, dispute, or reconcile a transaction, including order amount, billing details, payment token, transaction ID, card brand, last four digits, ACH-related metadata, PayPal identifiers, Stripe identifiers, processor risk signals, and chargeback records.<\/td><\/tr><tr><td>Proprietary product data<\/td><td>Access entitlements, license keys, download logs, subscription status, course progress, attendance, product usage, support history, anti-piracy indicators, and product-integrity telemetry related to proprietary offerings.<\/td><\/tr><tr><td>Anonymous browsing data<\/td><td>Information generated by site visits that may not directly identify a user by name but can still be personal information under some privacy laws, including IP address, device identifiers, cookies, browser metadata, referrer URLs, timestamps, page views, and session identifiers.<\/td><\/tr><tr><td>Processing<\/td><td>Any operation involving data, including collection, recording, organization, storage, use, disclosure, transfer, analysis, retention, deletion, and destruction.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h1 class=\"wp-block-heading\">2. Information We Collect<\/h1>\n\n\n\n<p>Tempus Trade Capital collects information in proportion to the services requested, the transaction being performed, the security risk presented, and the operational requirements of the website. The site should not be configured to collect more information than is reasonably necessary for identified business, legal, security, and customer-support purposes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2.1 Information from Anonymous Visitors<\/h2>\n\n\n\n<p>When an individual browses the website without registering or logging in, the website and associated service providers may collect technical and usage data. This can include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>IP address, approximate location derived from IP address, browser type, operating system, device type, language settings, screen resolution, referral source, URL path, page views, timestamps, clickstream activity, and session identifiers.<\/li>\n\n\n\n<li>Cookie identifiers, analytics identifiers, advertising identifiers, anti-fraud identifiers, consent-preference identifiers, and security telemetry.<\/li>\n\n\n\n<li>Server logs, CDN logs, WAF events, bot-detection events, rate-limit events, and threat-intelligence indicators used to protect the site and prevent abuse.<\/li>\n<\/ul>\n\n\n\n<p>Anonymous use does not guarantee that browsing data is legally anonymous. IP addresses, cookies, device identifiers, and event logs may be personal information if they can reasonably be linked to a person, device, account, household, or transaction.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2.2 Account Registration and Authentication Data<\/h2>\n\n\n\n<p>When a user creates an account, logs in, logs out, requests password reset, changes profile settings, manages subscriptions, or accesses purchased content, the site may collect and process:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Name, username, email address, password hash, account ID, customer ID, role, permissions, subscription status, membership tier, purchase history, product entitlements, course or training access rights, and account preferences.<\/li>\n\n\n\n<li>Authentication logs, successful and failed login attempts, logout events, password reset requests, MFA status if enabled, session cookie records, device metadata, IP address, user-agent, and security challenge outcomes.<\/li>\n\n\n\n<li>Fraud, abuse, and access-control telemetry, including suspicious account activity, velocity indicators, account-takeover indicators, and administrative audit logs.<\/li>\n<\/ul>\n\n\n\n<p>Passwords should be stored only as salted cryptographic hashes through WordPress or a vetted identity provider. The policy should not promise that passwords can be recovered. Password reset workflows should issue reset tokens instead of exposing stored credentials.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2.3 eCommerce, Order, and Payment Information<\/h2>\n\n\n\n<p>When a customer purchases a product, subscription, training session, membership, downloadable content, or other offering, the website may collect order and transaction information necessary to complete the sale and maintain records.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><td><strong>Data Type<\/strong><\/td><td><strong>Examples<\/strong><\/td><td><strong>Primary Purpose<\/strong><\/td><\/tr><\/thead><tbody><tr><td>Order data<\/td><td>Items purchased, SKU, product name, subscription term, quantity, price, discount, coupon, taxes, shipping status if applicable, invoice, order ID, order notes.<\/td><td>Fulfillment, access control, accounting, refunds, customer support, dispute handling, and business records.<\/td><\/tr><tr><td>Billing data<\/td><td>Name, billing address, email, phone if required, tax information if required, VAT\/GST details if applicable.<\/td><td>Payment authorization, fraud screening, tax compliance, invoice records, chargeback defense, and customer support.<\/td><\/tr><tr><td>Payment processor data<\/td><td>Processor token, transaction ID, authorization code, card brand, last four digits, expiration month\/year if returned by processor, ACH token\/mandate metadata, PayPal payer ID, Stripe customer\/payment method IDs, processor risk scores.<\/td><td>Payment processing, recurring billing, fraud prevention, reconciliation, chargebacks, refunds, and processor compliance.<\/td><\/tr><tr><td>Financial institution and clearing data<\/td><td>Bank, payment network, card network, ACH or clearing-house metadata, settlement status, processor response codes.<\/td><td>Authorization, settlement, returns, reversals, dispute management, and compliance with payment rules.<\/td><\/tr><tr><td>Fraud and security data<\/td><td>IP address, device fingerprint if enabled, velocity checks, billing mismatch, blocked transaction reason, risk score, WAF\/security event ID.<\/td><td>Payment fraud prevention, account-takeover prevention, chargeback reduction, and security monitoring.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Tempus Trade Capital should not intentionally store full payment card numbers, card verification values, raw magnetic stripe data, raw chip data, online banking credentials, or full ACH credentials in WordPress or WooCommerce. Full payment credentials should be handled by validated payment processors or financial institutions through tokenized, hosted, embedded, or redirected checkout workflows designed to reduce PCI DSS scope.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2.4 Proprietary Products, Licenses, and Digital Content<\/h2>\n\n\n\n<p>Because the website contains proprietary products and restricted-access materials, Tempus Trade Capital may process product-integrity and entitlement data necessary to protect paid content and enforce access restrictions.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Product access status, subscription state, membership level, course or product completion status, license keys, download counts, download timestamps, product version, entitlement history, renewal and cancellation status.<\/li>\n\n\n\n<li>Support tickets, bug reports, product feedback, feature requests, account notes, refund requests, dispute history, and correspondence about proprietary materials.<\/li>\n\n\n\n<li>Anti-abuse or anti-piracy indicators, including unusual download volumes, credential-sharing indicators, excessive concurrent access, IP or device anomalies, violation reports, and administrative review outcomes.<\/li>\n\n\n\n<li>Telemetry from software, scripts, data products, training portals, or proprietary tools only where disclosed, necessary, and proportionate to licensing, support, security, analytics, or product-improvement purposes.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">2.5 Podcasts, Media, and Streaming Data<\/h2>\n\n\n\n<p>When users access podcasts or media content through the website, embedded players, RSS feeds, podcast platforms, CDN services, or third-party hosting providers, the site or those providers may process:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Episode access logs, stream starts, downloads, completion events if available, subscription\/follow events if available, timestamps, user-agent, IP address, device or application type, referral source, and approximate location.<\/li>\n\n\n\n<li>Comments, ratings, reviews, questions, feedback, forms, and correspondence submitted in connection with podcast content.<\/li>\n\n\n\n<li>Platform-specific analytics generated by podcast directories, hosting providers, embedded media providers, or analytics vendors.<\/li>\n<\/ul>\n\n\n\n<p>Podcast platforms and directories may process listener data under their own privacy policies. Tempus Trade Capital should not represent that it controls all data collected by third-party podcast applications, directories, hosting providers, or embedded media services.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2.6 Real-Time Training Sessions and Events<\/h2>\n\n\n\n<p>When users register for or attend real-time training sessions, webinars, workshops, coaching sessions, livestreams, or similar events, Tempus Trade Capital and its service providers may process event-related information.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><td><strong>Session Data<\/strong><\/td><td><strong>Examples<\/strong><\/td><td><strong>Notes<\/strong><\/td><\/tr><\/thead><tbody><tr><td>Registration and attendance<\/td><td>Name, email, account ID, session ID, purchase ID, attendance status, check-in time, join\/leave times, calendar responses.<\/td><td>Used to provide access, validate paid attendance, issue reminders, and maintain records.<\/td><\/tr><tr><td>Interactive content<\/td><td>Chat messages, Q&amp;A, polls, survey responses, uploaded files, feedback forms, breakout room participation.<\/td><td>May contain personal information voluntarily submitted by attendees.<\/td><\/tr><tr><td>Audio\/video and recordings<\/td><td>Voice, likeness, screen share, meeting video, transcript, captions, recording metadata.<\/td><td>Recordings should be announced before or at session start. Attendees should be given instructions for disabling camera\/microphone where feasible.<\/td><\/tr><tr><td>Security and platform logs<\/td><td>IP address, device metadata, platform account identifier, moderator actions, abuse reports.<\/td><td>Used to protect sessions, enforce conduct rules, investigate disruptions, and preserve evidence.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>If a session is recorded, the registration page, session invitation, and in-session notice should clearly state that the event may be recorded, how recordings may be used, who may receive access, and how long recordings are retained. Attendees should not submit confidential, regulated, health, brokerage, tax, or third-party personal information through chat or Q&amp;A unless the service terms expressly authorize that submission.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2.7 Communications, Support, and Marketing Data<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Messages submitted through contact forms, email, support portals, chat widgets, comments, reviews, testimonial forms, survey tools, and social media interactions.<\/li>\n\n\n\n<li>Marketing subscription status, email engagement metrics, unsubscribe preferences, consent records, suppression-list entries, referral-source details, campaign identifiers, and communication history.<\/li>\n\n\n\n<li>Customer support records, refunds, billing issues, dispute communications, incident reports, abuse reports, and verification information used to respond to requests.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">2.8 Information from Third Parties<\/h2>\n\n\n\n<p>Tempus Trade Capital may receive information from service providers, payment processors, fraud-prevention vendors, analytics vendors, advertising platforms, affiliate\/referral partners, podcast platforms, training platforms, identity or authentication services, public sources, customer referrals, or business partners. Third-party data should be used only for disclosed purposes and subject to applicable contractual and legal restrictions.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2.9 Information Users Should Not Provide<\/h2>\n\n\n\n<p>Unless Tempus Trade Capital expressly requests it through a secure, approved workflow, users should not submit:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Government identifiers, full bank account numbers, full payment card numbers, CVV\/CVC codes, account passwords, private keys, seed phrases, trading account credentials, brokerage account credentials, tax documents, protected health information, children&#8217;s personal information, or third-party confidential information.<\/li>\n\n\n\n<li>Personal information about other individuals unless the user has authority to provide it and the disclosure is lawful and relevant to the requested service.<\/li>\n\n\n\n<li>Material non-public information, regulated financial information, or confidential trading information that Tempus Trade Capital is not contractually authorized to receive.<\/li>\n<\/ul>\n\n\n\n<h1 class=\"wp-block-heading\">3. How We Use Information<\/h1>\n\n\n\n<p>Tempus Trade Capital uses information for purposes that are reasonably necessary for operating the website, delivering products and services, processing payments, maintaining accounts, protecting the site, meeting legal obligations, and improving customer experience.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><td><strong>Purpose<\/strong><\/td><td><strong>Examples of Processing<\/strong><\/td><td><strong>Likely Legal \/ Business Basis<\/strong><\/td><\/tr><\/thead><tbody><tr><td>Provide website functionality<\/td><td>Page delivery, account access, login\/logout, session management, cart operation, checkout, product access, downloads.<\/td><td>Contract performance, legitimate interest, user request.<\/td><\/tr><tr><td>Process payments and orders<\/td><td>Authorize transactions, process cards\/ACH\/PayPal\/Stripe, tax calculation, invoicing, refunds, chargebacks, reconciliation.<\/td><td>Contract performance, legal obligation, legitimate interest, payment network obligations.<\/td><\/tr><tr><td>Deliver proprietary products<\/td><td>Provision paid access, enforce licensing, manage subscriptions, distribute materials, issue updates, prevent credential sharing and unauthorized distribution.<\/td><td>Contract performance, legitimate interest, fraud\/security prevention.<\/td><\/tr><tr><td>Operate podcasts and media<\/td><td>Stream or deliver episodes, measure engagement, manage comments or feedback, improve content.<\/td><td>Legitimate interest, consent where required for non-essential tracking.<\/td><\/tr><tr><td>Provide live training sessions<\/td><td>Register attendees, deliver event access, moderate sessions, record sessions where disclosed, answer questions, send follow-up materials.<\/td><td>Contract performance, legitimate interest, consent where required.<\/td><\/tr><tr><td>Communicate with users<\/td><td>Transactional emails, account alerts, support responses, receipts, renewal notices, security notices, policy updates.<\/td><td>Contract performance, legitimate interest, legal obligation.<\/td><\/tr><tr><td>Marketing and analytics<\/td><td>Newsletter, promotional messages, conversion analytics, audience measurement, campaign performance, retargeting if enabled.<\/td><td>Consent where required, opt-out where applicable, legitimate interest where permitted.<\/td><\/tr><tr><td>Security and fraud prevention<\/td><td>WAF logs, suspicious activity analysis, account-takeover prevention, bot mitigation, abuse detection, audit logging, incident response.<\/td><td>Legitimate interest, legal obligation, security necessity.<\/td><\/tr><tr><td>Legal and compliance<\/td><td>Records retention, tax\/accounting, payment disputes, sanctions or fraud controls if applicable, legal claims, regulator or law-enforcement responses.<\/td><td>Legal obligation, legitimate interest, contractual obligations.<\/td><\/tr><tr><td>Business operations<\/td><td>Vendor management, audit readiness, reporting, product improvement, service reliability, customer trust, corporate transactions.<\/td><td>Legitimate interest, contract management.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">3.1 Legal Bases for EEA, UK, and Similar Jurisdictions<\/h2>\n\n\n\n<p>Where GDPR, UK GDPR, or similar laws apply, Tempus Trade Capital relies on one or more lawful bases depending on the processing context: performance of a contract, legitimate interests, consent, compliance with legal obligations, protection of vital interests in rare emergency circumstances, or another legally recognized basis. Consent is not used as a blanket basis for all processing and may be withdrawn where processing depends on consent.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">3.2 Legitimate Interests<\/h2>\n\n\n\n<p>Legitimate interests may include operating and securing the website, preventing fraud and abuse, enforcing product licenses and access rules, maintaining business records, measuring service performance, responding to customer requests, improving products, protecting intellectual property, and asserting or defending legal claims. Where required, Tempus Trade Capital should maintain a legitimate-interest assessment that weighs business necessity against individual rights and reasonable expectations.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">3.3 Automated Processing, Profiling, and Fraud Controls<\/h2>\n\n\n\n<p>The website and vendors may use automated rules or scoring to detect spam, bots, suspicious logins, payment fraud, abusive transactions, credential sharing, and other security risks. These controls may restrict transactions, require additional verification, block access, flag an account for review, or prevent service abuse. Tempus Trade Capital should not use solely automated processing to make legally or similarly significant decisions unless permitted by applicable law and supported by required safeguards.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">4. Cookies, Tracking Technologies, and Similar Tools<\/h1>\n\n\n\n<p>The website may use cookies, pixels, tags, SDKs, local storage, server-side analytics, embedded content, and similar technologies. Some technologies are required for core functionality; others support analytics, personalization, marketing, advertising measurement, fraud prevention, and security.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><td><strong>Technology Category<\/strong><\/td><td><strong>Examples<\/strong><\/td><td><strong>Default Handling<\/strong><\/td><\/tr><\/thead><tbody><tr><td>Strictly necessary<\/td><td>Login session cookies, cart cookies, checkout cookies, CSRF tokens, security cookies, consent-preference cookies.<\/td><td>Operate without opt-in where permitted because the site cannot function securely without them.<\/td><\/tr><tr><td>Functional<\/td><td>Remembered preferences, training portal preferences, media player settings, localization settings.<\/td><td>Enable with disclosure and provide controls where feasible.<\/td><\/tr><tr><td>Analytics<\/td><td>Site analytics, podcast analytics, conversion events, product usage analytics, performance monitoring.<\/td><td>Use aggregated or privacy-preserving settings where feasible; obtain consent where required.<\/td><\/tr><tr><td>Advertising \/ targeted advertising<\/td><td>Retargeting pixels, lookalike audiences, ad platform tags, cross-context behavioral advertising identifiers.<\/td><td>Use only with appropriate notice, consent or opt-out, honoring applicable sale\/share\/targeted advertising rights and GPC where required.<\/td><\/tr><tr><td>Security \/ anti-fraud<\/td><td>Bot detection, WAF cookies, device or risk signals, rate-limit identifiers, payment fraud indicators.<\/td><td>Use as necessary to protect accounts, transactions, infrastructure, intellectual property, and users.<\/td><\/tr><tr><td>Embedded third-party content<\/td><td>Video players, podcast players, webinar platforms, social media embeds, maps, support chat widgets.<\/td><td>Disclose that third parties may collect data under their own policies when users interact with embedded services.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Users can often control cookies through browser settings, consent management tools, and device controls. Blocking cookies may impair account login, cart function, checkout, purchased content access, podcast playback, live training registration, or security protections.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">4.1 Global Privacy Control and Do Not Track<\/h2>\n\n\n\n<p>Where legally required, Tempus Trade Capital should honor recognized opt-out preference signals such as Global Privacy Control for browser-based requests to opt out of sale or sharing of personal information. Browser Do Not Track signals have not been uniformly adopted as a binding technical standard. The site should disclose how it responds to GPC and similar legally recognized signals, and should ensure the consent-management platform is configured accordingly.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">4.2 Cookie Governance Requirements<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Maintain an inventory of cookies, pixels, tags, embedded content, analytics tools, advertising tools, security tools, and session technologies.<\/li>\n\n\n\n<li>Classify each technology by purpose, provider, data collected, duration, jurisdictional impact, and consent\/opt-out requirement.<\/li>\n\n\n\n<li>Run periodic scans after plugin changes, theme changes, tag manager updates, payment extension changes, analytics changes, and marketing campaign launches.<\/li>\n\n\n\n<li>Prevent non-essential analytics or advertising tags from firing before required consent in jurisdictions that require prior opt-in.<\/li>\n\n\n\n<li>Honor opt-out signals by suppressing sale\/share\/targeted advertising tags and updating downstream vendor signals where feasible.<\/li>\n<\/ul>\n\n\n\n<h1 class=\"wp-block-heading\">5. Disclosure of Information<\/h1>\n\n\n\n<p>Tempus Trade Capital may disclose information to service providers and other parties where necessary for the purposes described in this policy. Disclosure should be limited to the minimum information reasonably necessary and governed by appropriate contracts, security requirements, and data-processing terms.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><td><strong>Recipient Category<\/strong><\/td><td><strong>Typical Data Disclosed<\/strong><\/td><td><strong>Purpose<\/strong><\/td><\/tr><\/thead><tbody><tr><td>Hosting, infrastructure, CDN, DNS, WAF, security vendors<\/td><td>IP address, server logs, account events, page requests, security events, device\/browser data.<\/td><td>Website delivery, uptime, security monitoring, DDoS protection, bot mitigation, incident response.<\/td><\/tr><tr><td>WordPress\/WooCommerce plugins and service providers<\/td><td>Account, order, cart, checkout, entitlement, subscription, support, analytics, and operational data depending on plugin function.<\/td><td>Website functionality, eCommerce, fulfillment, subscriptions, memberships, training access, support.<\/td><\/tr><tr><td>Payment processors and financial institutions<\/td><td>Billing details, order amount, transaction data, payment token, fraud signals, refund\/dispute records.<\/td><td>Payment authorization, settlement, fraud detection, chargebacks, refunds, compliance.<\/td><\/tr><tr><td>PayPal, Stripe, card networks, ACH providers, clearing houses, banks<\/td><td>Payment method metadata, transaction identifiers, payer or customer IDs, settlement status, processor responses.<\/td><td>Payment processing, settlement, risk review, dispute resolution, processor\/network compliance.<\/td><\/tr><tr><td>Email, SMS, and communication vendors<\/td><td>Name, email, phone if provided, subscription status, transactional messages, marketing preferences, engagement metrics.<\/td><td>Receipts, account alerts, support communications, marketing where permitted.<\/td><\/tr><tr><td>Podcast, webinar, livestream, training, and media platforms<\/td><td>Registration, attendance, stream\/download events, chat\/Q&amp;A, recordings, device\/IP data.<\/td><td>Deliver podcasts, live sessions, recordings, training access, moderation, analytics.<\/td><\/tr><tr><td>Analytics and advertising vendors<\/td><td>Cookie IDs, event data, page views, purchase or conversion events, pseudonymous identifiers.<\/td><td>Measurement, attribution, campaign management, personalization or targeted advertising where enabled and lawful.<\/td><\/tr><tr><td>Professional advisors<\/td><td>Relevant business records, dispute materials, compliance records.<\/td><td>Legal, accounting, tax, audit, insurance, and risk management.<\/td><\/tr><tr><td>Law enforcement, regulators, courts, payment networks<\/td><td>Information required by lawful requests, legal process, fraud investigation, payment network rules, or compliance obligations.<\/td><td>Legal compliance, protection of rights, fraud prevention, dispute resolution.<\/td><\/tr><tr><td>Business transaction parties<\/td><td>Relevant account, customer, order, vendor, and operational data subject to confidentiality protections.<\/td><td>Merger, acquisition, financing, reorganization, asset sale, due diligence, continuity of service.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">5.1 Vendor Governance<\/h2>\n\n\n\n<p>Tempus Trade Capital should require vendors that process personal information to implement appropriate security, confidentiality, privacy, breach-notification, deletion, subprocessors, audit, and data-return\/destruction controls. Higher-risk vendors should be reviewed through due diligence, security questionnaires, SOC 2 or ISO 27001 reports where available, PCI evidence for payment services, data-processing agreements, service provider or processor terms, and documented risk acceptance where gaps remain.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">5.2 Sale, Sharing, Targeted Advertising, and Cross-Context Behavioral Advertising<\/h2>\n\n\n\n<p>Tempus Trade Capital does not sell personal information for money. However, some privacy laws define sale, sharing, targeted advertising, or cross-context behavioral advertising broadly enough to include certain advertising pixels, retargeting tools, affiliate tracking, analytics, or data disclosures to ad networks. If these tools are enabled, the website should provide appropriate notices, consent controls, opt-out links, and GPC handling. If such tools are disabled, the policy should be updated to state that the site does not sell, share, or use personal information for targeted advertising as defined by applicable law.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">6. Payment Processing and PCI Scope<\/h1>\n\n\n\n<p>Payments should be processed through WooCommerce-compatible payment processors using tokenization, redirect, hosted fields, or other scope-reducing architectures. Tempus Trade Capital should avoid storing full payment credentials in WordPress, WooCommerce, logs, analytics systems, support tickets, chat transcripts, email, or backups.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">6.1 Payment Methods Covered<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Credit and debit cards processed by PCI-compliant payment processors and acquiring institutions.<\/li>\n\n\n\n<li>ACH or bank transfer workflows where enabled through a processor or financial institution.<\/li>\n\n\n\n<li>PayPal wallet, PayPal checkout, or related PayPal payment flows where enabled.<\/li>\n\n\n\n<li>Stripe, WooCommerce Payments, or other processor token\/payment-method integrations where enabled.<\/li>\n\n\n\n<li>Refunds, chargebacks, disputes, reversals, recurring billing, subscription renewals, tax calculations, fraud screening, and reconciliation.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">6.2 Payment Data Minimization<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Do not request or store CVV\/CVC codes outside processor-controlled payment fields.<\/li>\n\n\n\n<li>Do not collect card numbers, ACH credentials, online banking credentials, or payment secrets through contact forms, email, support tickets, chat, podcast comments, training chat, or file uploads.<\/li>\n\n\n\n<li>Use payment tokens rather than raw payment credentials for recurring billing and stored payment methods.<\/li>\n\n\n\n<li>Restrict administrator access to WooCommerce orders, payment metadata, refunds, and subscription controls by role and business need.<\/li>\n\n\n\n<li>Configure logging to avoid storing sensitive authentication data, full card numbers, full bank account numbers, raw processor payloads, secrets, private API keys, or OAuth tokens.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">6.3 Payment Processor Privacy<\/h2>\n\n\n\n<p>Payment processors, card networks, PayPal, Stripe, banks, ACH operators, and clearing houses may process payment information under their own privacy notices, legal obligations, risk controls, and payment network rules. Users should review the applicable processor privacy notices before submitting payment information. Tempus Trade Capital should maintain current links to payment processor privacy notices on the checkout page or in this policy when the production processor list is finalized.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">7. Data Security<\/h1>\n\n\n\n<p>Tempus Trade Capital should use administrative, technical, and physical safeguards appropriate to the sensitivity of the information, the website threat model, payment risk, account-takeover risk, product-access risk, and regulatory exposure. No security control eliminates all risk, but controls must be measurable, monitored, and operationally owned.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><td><strong>Control Area<\/strong><\/td><td><strong>Required Baseline<\/strong><\/td><\/tr><\/thead><tbody><tr><td>Transport security<\/td><td>Enforce HTTPS\/TLS across the site, checkout, account pages, admin access, APIs, webhooks, media delivery, and training integrations. Redirect HTTP to HTTPS.<\/td><\/tr><tr><td>Authentication<\/td><td>Use strong administrator passwords, MFA for administrators and privileged users, least-privilege roles, secure password reset, login throttling, and account-takeover monitoring.<\/td><\/tr><tr><td>WordPress\/WooCommerce hardening<\/td><td>Maintain timely patching for WordPress core, plugins, themes, PHP, database, web server, payment extensions, and training\/media integrations. Remove unused plugins and themes.<\/td><\/tr><tr><td>Payment security<\/td><td>Use tokenized processor integrations, restrict access to order\/payment metadata, avoid sensitive data in logs, maintain PCI DSS responsibilities, and monitor checkout changes.<\/td><\/tr><tr><td>Logging and monitoring<\/td><td>Collect authentication events, administrative changes, payment\/refund activity, account changes, plugin\/theme changes, WAF\/CDN events, backup activity, and suspicious access events.<\/td><\/tr><tr><td>Encryption and secrets<\/td><td>Protect secrets, API keys, webhook secrets, OAuth credentials, payment keys, SMTP credentials, database credentials, and backup encryption keys. Rotate keys after suspected exposure.<\/td><\/tr><tr><td>Backups and recovery<\/td><td>Maintain encrypted backups, access controls, retention limits, restore testing, immutable or tamper-resistant copies where feasible, and separation from production credentials.<\/td><\/tr><tr><td>Vendor and integration security<\/td><td>Review vendor privacy\/security terms, restrict data flows, document subprocessors, monitor integration changes, and disable unnecessary permissions.<\/td><\/tr><tr><td>Data retention and deletion<\/td><td>Apply documented retention schedules and deletion workflows to accounts, orders, logs, recordings, support tickets, marketing data, cookies, and backups.<\/td><\/tr><tr><td>Incident response<\/td><td>Maintain security incident triage, privacy incident assessment, payment incident escalation, breach notification analysis, evidence preservation, and customer communication workflows.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">7.1 Security Limitations<\/h2>\n\n\n\n<p>Users are responsible for maintaining the confidentiality of their account credentials, using unique passwords, protecting devices, logging out on shared devices, avoiding credential reuse, and promptly notifying Tempus Trade Capital of suspected unauthorized account activity. Tempus Trade Capital should not ask users to send passwords, payment secrets, trading account credentials, seed phrases, or authentication codes through email, chat, contact forms, podcast comments, or training sessions.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">8. Retention and Deletion<\/h1>\n\n\n\n<p>Tempus Trade Capital retains personal information only as long as reasonably necessary for the purposes described in this policy, unless a longer retention period is required or permitted by law, contract, tax\/accounting rules, payment network rules, dispute handling, fraud prevention, security monitoring, backup integrity, or legal preservation obligations.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><td><strong>Record Category<\/strong><\/td><td><strong>Illustrative Retention Criteria<\/strong><\/td><\/tr><\/thead><tbody><tr><td>Account profile<\/td><td>Retained while the account is active and for a reasonable period after closure to support reactivation, fraud prevention, dispute handling, legal claims, and audit requirements.<\/td><\/tr><tr><td>Order and payment records<\/td><td>Retained as required for accounting, tax, payment processor, card network, ACH, refund, chargeback, anti-fraud, and legal purposes.<\/td><\/tr><tr><td>Subscriptions and entitlements<\/td><td>Retained while access remains active and for a reasonable period after termination to document license history, renewals, cancellations, refunds, and disputes.<\/td><\/tr><tr><td>Training registrations and attendance<\/td><td>Retained for event delivery, customer support, proof of attendance, billing, disputes, and operational analytics.<\/td><\/tr><tr><td>Training recordings<\/td><td>Retained according to publication, educational reuse, contractual, and deletion schedules. Recordings should not be kept indefinitely without documented business need.<\/td><\/tr><tr><td>Podcast analytics<\/td><td>Retained based on platform reporting windows, aggregation requirements, and analytics minimization settings.<\/td><\/tr><tr><td>Support tickets and communications<\/td><td>Retained for issue resolution, customer history, quality assurance, legal claims, and compliance records.<\/td><\/tr><tr><td>Marketing data<\/td><td>Retained until unsubscribed, withdrawn, suppressed, or no longer needed. Suppression records may be retained to honor opt-out requests.<\/td><\/tr><tr><td>Security logs<\/td><td>Retained long enough to detect, investigate, and respond to threats, subject to minimization and legal requirements.<\/td><\/tr><tr><td>Backups<\/td><td>Retained according to backup schedules and overwritten or destroyed through routine cycles unless subject to legal hold or incident preservation.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">8.1 Deletion Requests<\/h2>\n\n\n\n<p>Deletion requests are subject to identity verification and lawful exceptions. Tempus Trade Capital may need to retain limited information to complete transactions, provide requested services, detect security incidents, prevent fraud, debug errors, comply with legal obligations, resolve disputes, enforce agreements, maintain tax\/accounting records, honor opt-out requests, protect intellectual property, or preserve evidence.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">9. Privacy Rights and Request Handling<\/h1>\n\n\n\n<p>Depending on location and applicable law, users may have rights to request access, confirmation of processing, correction, deletion, restriction, portability, objection, withdrawal of consent, opt-out of sale\/share\/targeted advertising, limitation of sensitive personal information, and non-discrimination for exercising privacy rights.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">9.1 How to Submit a Request<\/h2>\n\n\n\n<p>Requests should be submitted through a designated privacy request channel. Before publication, Tempus Trade Capital should insert the operational request method below:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Privacy contact email: [Insert privacy contact email].<\/li>\n\n\n\n<li>Postal address: [Insert mailing address].<\/li>\n\n\n\n<li>Web form: [Insert privacy request form URL if used].<\/li>\n\n\n\n<li>California toll-free number if legally required: [Insert number or state not applicable after counsel review].<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">9.2 Verification and Authorized Agents<\/h2>\n\n\n\n<p>Tempus Trade Capital may verify requests by matching information provided in the request against account, order, billing, or communication records. Higher-risk requests, such as deletion, access to sensitive information, or changes to account email, may require additional verification. Authorized agents may need to provide proof of authorization, and the user may be required to verify identity directly where permitted by law.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">9.3 Response Timing<\/h2>\n\n\n\n<p>Response deadlines vary by jurisdiction and request type. Tempus Trade Capital should maintain a DSAR log that records request intake, identity verification, scope, deadlines, exemptions, fulfillment, denial rationale, appeal\/escalation, and completion evidence. Where an extension is permitted and necessary, the company should notify the requester within the legally required timeframe.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">9.4 California Privacy Notice Addendum<\/h2>\n\n\n\n<p>This section is intended to support California Consumer Privacy Act \/ California Privacy Rights Act notice requirements where applicable. Applicability depends on statutory thresholds, data practices, and business status.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><td><strong>CCPA Category<\/strong><\/td><td><strong>Examples Collected in Prior 12 Months<\/strong><\/td><td><strong>Sources<\/strong><\/td><td><strong>Business \/ Commercial Purposes<\/strong><\/td><td><strong>Disclosed To<\/strong><\/td><\/tr><\/thead><tbody><tr><td>Identifiers<\/td><td>Name, email, username, billing address, phone, IP address, cookie IDs, customer ID, order ID, device identifiers.<\/td><td>User, device\/browser, account system, payment processor, analytics\/security vendors.<\/td><td>Account, checkout, order fulfillment, security, support, marketing, analytics.<\/td><td>Processors, hosting, payment providers, communication vendors, analytics\/security vendors.<\/td><\/tr><tr><td>Commercial information<\/td><td>Products purchased, cart contents, order history, subscriptions, renewals, refunds, chargebacks, product entitlements.<\/td><td>User, WooCommerce, processors, support systems.<\/td><td>Fulfillment, billing, support, accounting, fraud prevention, product access.<\/td><td>Payment processors, accounting\/tax providers, support vendors, hosting.<\/td><\/tr><tr><td>Internet\/network activity<\/td><td>Page views, login\/logout events, cookies, device\/browser data, referral source, security logs, podcast\/media access.<\/td><td>Website, browser, cookies, CDN\/WAF, analytics\/media platforms.<\/td><td>Site operation, analytics, security, fraud prevention, personalization where enabled.<\/td><td>Hosting, CDN\/WAF, analytics vendors, media platforms, security vendors.<\/td><\/tr><tr><td>Geolocation<\/td><td>Approximate location derived from IP address; precise geolocation only if a feature explicitly requests it.<\/td><td>Device\/browser, IP intelligence, analytics\/security vendors.<\/td><td>Security, localization, tax\/fraud controls, analytics.<\/td><td>Hosting, analytics\/security vendors, payment processors where relevant.<\/td><\/tr><tr><td>Audio, electronic, visual, or similar information<\/td><td>Training recordings, webinar audio\/video, chat, Q&amp;A, uploaded media, support call recordings if enabled.<\/td><td>User, training platform, support tools.<\/td><td>Training delivery, recordings, support, moderation, product improvement.<\/td><td>Training platforms, support vendors, storage\/hosting vendors.<\/td><\/tr><tr><td>Professional or employment-related information<\/td><td>Company, role, business contact details if voluntarily provided for business purchases or training.<\/td><td>User, forms, support, event registration.<\/td><td>Customer support, B2B transactions, training administration.<\/td><td>CRM, support, email, training vendors.<\/td><\/tr><tr><td>Inferences<\/td><td>Preferences, engagement, product interests, risk indicators, likely training interests, anti-fraud signals.<\/td><td>Website analytics, account\/order activity, marketing platforms, security tools.<\/td><td>Personalization, recommendations, fraud prevention, marketing where permitted.<\/td><td>Analytics, advertising, security, marketing vendors where enabled.<\/td><\/tr><tr><td>Sensitive personal information<\/td><td>Account credentials, payment-related data, precise geolocation if enabled, contents of communications not directed to the company only if provided.<\/td><td>User, payment processor, security systems.<\/td><td>Account security, payment processing, support, legal\/security compliance.<\/td><td>Processors and service providers as necessary; not used to infer characteristics unless legally permitted and disclosed.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>California consumers may have rights to know\/access, correct, delete, opt out of sale\/share, limit certain uses of sensitive personal information, and avoid discrimination for exercising rights. If the website sells, shares, or uses personal information for cross-context behavioral advertising, it must provide a clear opt-out mechanism and honor applicable browser-based opt-out preference signals such as Global Privacy Control.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">9.5 EEA, UK, and Swiss Addendum<\/h2>\n\n\n\n<p>Where GDPR, UK GDPR, Swiss FADP, or similar frameworks apply, users may have rights to access, rectify, erase, restrict processing, data portability, object to processing, withdraw consent, and lodge complaints with a supervisory authority. Tempus Trade Capital should identify its controller details, representative if required, data protection contact, purposes, legal bases, recipients, retention criteria, transfer mechanisms, and automated decision-making information in accordance with applicable transparency obligations.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">9.6 Canada Addendum<\/h2>\n\n\n\n<p>Where PIPEDA or substantially similar Canadian private-sector privacy laws apply, users may request access to their personal information, challenge accuracy, withdraw consent subject to legal or contractual limits, and challenge compliance. Tempus Trade Capital should collect only information needed for identified purposes, use meaningful consent, retain data only as necessary, apply safeguards appropriate to sensitivity, and maintain accountability for cross-border processing by vendors.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">9.7 Australia Addendum<\/h2>\n\n\n\n<p>Where the Australian Privacy Act 1988 and Australian Privacy Principles apply, individuals may have rights to transparency, access, correction, complaint handling, and protections for collection, use, disclosure, direct marketing, cross-border disclosure, security, and retention. Tempus Trade Capital should take reasonable steps to protect personal information from misuse, interference, loss, unauthorized access, modification, or disclosure and should destroy or de-identify information no longer needed, unless retention is legally required.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">9.8 New Zealand Addendum<\/h2>\n\n\n\n<p>Where the New Zealand Privacy Act 2020 applies, users may have rights relating to notice, access, correction, use, disclosure, unique identifiers, security, retention, and cross-border disclosure. As of May 1, 2026, New Zealand IPP 3A adds a notification obligation for indirect collection of personal information. Tempus Trade Capital should ensure overseas disclosures are supported by comparable safeguards or another permitted transfer basis and should maintain a notifiable privacy breach workflow where serious harm is possible.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">9.9 Other U.S. State Privacy Rights<\/h2>\n\n\n\n<p>Residents of other U.S. states may have similar rights depending on applicable state privacy law, including access, correction, deletion, portability, opt-out of targeted advertising, opt-out of sale, opt-out of certain profiling, appeal rights, and protection against discrimination. Tempus Trade Capital should update this section as new state privacy laws become effective or as data practices change.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">10. Children&#8217;s Privacy<\/h1>\n\n\n\n<p>The website, products, podcasts, and real-time training services are not directed to children under 13, and Tempus Trade Capital does not knowingly collect personal information from children under 13. If the company learns that it collected personal information from a child under 13 without required parental consent, it should delete the information or obtain legally sufficient parental consent where permitted and appropriate.<\/p>\n\n\n\n<p>If offerings are later directed to minors, include minors as an intended audience, or knowingly collect information from users under 13, Tempus Trade Capital must implement COPPA-compliant direct notice, verifiable parental consent, parental access and deletion rights, data minimization, retention limits, and vendor controls before launch.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">11. Health Information and HIPAA Status<\/h1>\n\n\n\n<p>Tempus Trade Capital is not intended to operate as a HIPAA covered entity or business associate through the ordinary eCommerce, proprietary product, podcast, or training workflows described in this policy. Users should not submit protected health information or medical records through the website, checkout, support, podcast comments, live training chat, or file uploads unless a separate HIPAA-governed workflow, business associate agreement, and HIPAA-specific notice and safeguards are in place.<\/p>\n\n\n\n<p>If Tempus Trade Capital later processes protected health information on behalf of a covered entity or business associate, it should maintain a separate HIPAA compliance program, business associate agreements, risk analysis, administrative safeguards, physical safeguards, technical safeguards, workforce training, audit controls, incident response procedures, and breach notification workflows.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">12. International Data Transfers<\/h1>\n\n\n\n<p>Tempus Trade Capital may process information in the United States and may use vendors located in or accessing data from other jurisdictions. International transfers should be supported by appropriate contractual, technical, and organizational safeguards, including data-processing agreements, standard contractual clauses where required, transfer impact assessments where required, encryption, access controls, vendor due diligence, and subprocessors management.<\/p>\n\n\n\n<p>Users accessing the website from outside the United States acknowledge that their information may be transferred to and processed in jurisdictions that may have privacy laws different from those in their place of residence. This transfer disclosure is not a waiver of rights under applicable law.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">13. User Choices and Controls<\/h1>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Account controls: Users may update certain account profile details by logging into their account, subject to security controls and verification requirements.<\/li>\n\n\n\n<li>Marketing communications: Users may unsubscribe from promotional emails using unsubscribe links or designated contact methods. Transactional, security, legal, and service messages may still be sent.<\/li>\n\n\n\n<li>Cookies: Users may manage cookies through browser settings and any site-provided consent tool. Necessary cookies may remain required for secure operation.<\/li>\n\n\n\n<li>Payments: Users may manage stored payment methods where the payment processor and WooCommerce account functionality support it. Stored processor tokens may be deleted or disabled subject to subscription, chargeback, and legal requirements.<\/li>\n\n\n\n<li>Training recordings: Users may choose whether to enable camera or microphone where platform functionality permits. If they participate in recorded sessions, their name, voice, image, chat, or Q&amp;A may appear in the recording.<\/li>\n\n\n\n<li>Privacy rights: Users may submit requests through the privacy request methods described in this policy.<\/li>\n<\/ul>\n\n\n\n<h1 class=\"wp-block-heading\">14. Public Areas, Comments, Reviews, and User-Submitted Content<\/h1>\n\n\n\n<p>If the website allows comments, product reviews, testimonials, community posts, podcast comments, chat, Q&amp;A, forums, or other public or semi-public submissions, users should understand that submitted content may be visible to other users, attendees, moderators, administrators, service providers, or the public depending on feature configuration. Users should not include personal information, confidential information, regulated information, trading account information, brokerage credentials, payment secrets, or third-party information in public or semi-public areas.<\/p>\n\n\n\n<p>Tempus Trade Capital may moderate, remove, restrict, retain, disclose, or preserve user-submitted content where reasonably necessary to operate the site, enforce terms, protect users, investigate abuse, comply with law, protect intellectual property, or preserve evidence.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">15. Financial, Trading, and Proprietary Information Boundaries<\/h1>\n\n\n\n<p>The privacy policy governs data processing for website and service interactions. It does not govern investment performance, trading outcomes, financial advice duties, or securities-law obligations except where personal information is processed in connection with those workflows. Users should not submit brokerage credentials, trading account credentials, account statements, tax records, material non-public information, or third-party financial records unless a specific secure workflow expressly requests that information and defines the applicable terms.<\/p>\n\n\n\n<p>Product usage, training attendance, subscription status, license metadata, and access logs may be used to protect proprietary content, enforce license restrictions, prevent unauthorized sharing, and support customer service.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">16. Privacy Incidents, Security Incidents, and Breach Response<\/h1>\n\n\n\n<p>Tempus Trade Capital should distinguish between a security incident, a privacy incident, a reportable personal data breach, a reportable payment data incident, a contractual notification event, and a regulator-notification event. Not every security incident is a reportable breach, but each suspected incident involving personal information, payment data, credentials, proprietary product access, training recordings, or customer records should be triaged and documented.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><td><strong>Response Step<\/strong><\/td><td><strong>Operational Requirement<\/strong><\/td><\/tr><\/thead><tbody><tr><td>Intake and triage<\/td><td>Record incident source, time, impacted systems, data types, suspected actor, indicators, and initial severity.<\/td><\/tr><tr><td>Containment<\/td><td>Preserve evidence, disable compromised access, rotate secrets, restrict affected integrations, block malicious activity, and protect backups.<\/td><\/tr><tr><td>Scope and impact analysis<\/td><td>Identify affected data subjects, jurisdictions, data categories, systems, vendors, payment processors, logs, training recordings, accounts, and product entitlements.<\/td><\/tr><tr><td>Notification analysis<\/td><td>Evaluate legal, regulatory, payment network, contractual, vendor, and customer notification obligations with counsel where appropriate.<\/td><\/tr><tr><td>Eradication and recovery<\/td><td>Patch vulnerabilities, remove malicious code, restore trusted state, validate integrity, monitor for recurrence, and document closure.<\/td><\/tr><tr><td>Lessons learned<\/td><td>Update controls, vendor terms, detection rules, policies, training, retention, logging, and evidence artifacts.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h1 class=\"wp-block-heading\">17. Changes to This Policy<\/h1>\n\n\n\n<p>Tempus Trade Capital may update this policy to reflect changes in legal requirements, website functionality, payment processors, analytics tools, advertising practices, product offerings, podcasts, training services, vendor relationships, security practices, or business operations. Material changes should be posted on the website with an updated effective date. Where required by law or contract, Tempus Trade Capital should provide additional notice or obtain consent before applying material changes.<\/p>\n\n\n\n<h1 class=\"wp-block-heading\">18. Contact Information<\/h1>\n\n\n\n<p>Questions, privacy requests, complaints, or concerns should be directed to:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><td><strong>Contact Field<\/strong><\/td><td><strong>Value to Publish<\/strong><\/td><\/tr><\/thead><tbody><tr><td>Company<\/td><td>Tempus Trade Capital<\/td><\/tr><tr><td>Privacy Contact Email<\/td><td>[Insert privacy contact email]<\/td><\/tr><tr><td>Postal Address<\/td><td>[Insert company mailing address]<\/td><\/tr><tr><td>Privacy Request Web Form<\/td><td>[Insert privacy request form URL if used]<\/td><\/tr><tr><td>Data Protection Officer \/ Representative<\/td><td>[Insert if applicable or state not appointed]<\/td><\/tr><tr><td>California Request Methods<\/td><td>[Insert methods if CCPA applies]<\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>Table of Contents 1. Policy Scope and Status 2. Information We Collect 3. How We Use Information 4. Cookies, Tracking Technologies, and Similar Tools 5. Disclosure of Information 6. Payment Processing and PCI Scope 7. Data Security 8. Retention and Deletion 9. Privacy Rights and Request Handling 10. Children&#8217;s Privacy 11. Health Information and HIPAA [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"open","template":"","meta":{"_acf_changed":false,"footnotes":"","_members_access_role":[],"_members_access_error":""},"class_list":["post-3","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.tempus-trade-capital.com\/index.php?rest_route=\/wp\/v2\/pages\/3","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.tempus-trade-capital.com\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.tempus-trade-capital.com\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.tempus-trade-capital.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tempus-trade-capital.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3"}],"version-history":[{"count":2,"href":"https:\/\/www.tempus-trade-capital.com\/index.php?rest_route=\/wp\/v2\/pages\/3\/revisions"}],"predecessor-version":[{"id":360,"href":"https:\/\/www.tempus-trade-capital.com\/index.php?rest_route=\/wp\/v2\/pages\/3\/revisions\/360"}],"wp:attachment":[{"href":"https:\/\/www.tempus-trade-capital.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}