This Notice explains how THE TRADE LOAD, operated as an individual business, handles personal information when providing the website, accounts, educational content, product access, support, optional opening news and optional marketing emails. It covers information handled by THE TRADE LOAD; independent payment providers also explain their own processing in their privacy notices.
1. Responsible operator and contact
Business name: THE TRADE LOAD
Business type: Individual business
Representative: Harold Arthur Prichard
Privacy department: worker
Contact email: contact@the-trade-load.com
Requests can be sent by email without creating an account. The Contact Us form is also available to visitors and former members. Section 12 explains available rights and request handling.
2. Personal information processed
The following categories describe the records handled by the service.
Scroll horizontally to view all columns
| Category | Information | Source |
|---|---|---|
| Account and authentication | Email address, account identifier, salted password hash when a password is set, account creation and verification status, session-token hashes and expiry, verification and recovery references, and the selected social sign-in provider and its account identifier when connected | Account holder, the account service and the selected sign-in provider |
| Administrator authentication | Encrypted authenticator secrets, hashed recovery codes, enrollment and verification state, and related security events | Authorized administrators and the account service |
| Residence | Country or territory confirmed at checkout or voluntarily saved in Account, relevant U.S. state or Canadian province or territory, confirmation time and notice version, history, and the residence snapshot associated with an order. A closure request records residence only when already available | Account holder and the service |
| Learning records | Lesson identifiers, playback position, watched time, completion, locale, update time, timeline version, and saved reflection text | Use of learning features |
| Free test access records | Enrollment and order references, recorded amount and currency, access dates and status | Enrollment activity and the service |
| Purchase and payment records | Account identifier and purchase email; internal and PayPal order, payment and refund references; amount and currency; payment, refund and product-access status; transaction and verification dates; checkout choices, document versions and the accepted contract record; PayPal payer email, retained in payment evidence as a hash | Buyer, PayPal and the service |
| Security and administration | Available IP address and approximate connection country, requested route or lesson, timestamps and response status, account association, sign-in and recovery failures, request identifiers, administrator actions, and account-support notes with their edit history | Browser, network services and authorized administrators |
| Optional website analytics | Browser-reported page path, event time and related request information, including the available IP address and signed-in account association | Browser, only after the analytics choice is enabled |
| Contact and rights requests | Contact name, reply email, subject, message, submission time and reference, signed-in or guest status, and correspondence or evidence needed to handle the request | Requester and support services |
| Refund and withdrawal requests | Consumer name and statement where supplied, original purchase email, order and request references, submission time, handling history and outcome | Requester, payment provider and the service |
| Opening-news requests | Email address, request reference, first and latest request times, request count, consent version and wording, and expiry time | Requester and the service |
| Optional account marketing emails | Account identifier and email address, opt-in status, consent version and displayed wording, consent time when selected, and withdrawal time | Account holder and the account service |
| Email and operational diagnostics | Provider message or event references, message category, pseudonymous correlation identifiers, delivery, bounce or failure status, event times, diagnostic codes and counts | Service, email provider and operational monitoring |
| Browser storage | Sign-in and checkout cookies, the browser's analytics choice and expiry, unfinished email-verification information, reflection drafts and recovery versions, and playback settings selected in the player | Browser and service functions, as described in Section 9 |
Security logging also applies to visitors without an account. Contact, opening-news and authentication rate limits use identifiers derived from email, IP address or account information; hashing does not make those records anonymous. The separate email-delivery tracking table stores delivery references and status, rather than message bodies or recipient addresses. Email providers and mailboxes still process the actual messages.
The approximate connection country comes from Cloudflare's request metadata when available and is kept with the related security record for the same retention period. It is an IP-based estimate, not proof of a person's residence or nationality; a VPN, proxy or shared network can affect it. Authorized administrators can use it when reviewing a security incident. It is not sent to Slack, and missing country information is not filled in for historical records.
PayPal collects payment credentials in its own checkout. This website does not ask for a payment card number, and the local payment ledger does not store full card numbers. Payment responses can contain additional information that is processed transiently while a transaction is checked. Do not include trading-account passwords, health information or unrelated sensitive information in reflections or support messages; submitted text may be received and stored as part of the request.
3. Purposes of processing
Account and authentication records support registration, sign-in, verification, recovery and account protection. Learning records provide requested lessons, resume playback and retain saved reflections. Residence confirmations help identify relevant privacy and consumer protections and preserve the circumstances of an order or request. Residence is supplied by the account holder, not inferred from an IP address, and does not determine applicable law by itself.
Purchase, checkout and payment records support order verification, product access, receipts, refunds, withdrawal requests, fraud prevention and necessary legal records. Checkout choices and a payment redirect alone do not establish a completed purchase. New checkout is available only when enabled. Verification, refunds and necessary record handling for existing transactions can continue when new checkout is closed.
Support records allow requests to be answered and their outcomes documented. Security and operational records help investigate access failures and misuse, protect content and accounts, and maintain service reliability. Restricted administrators receive necessary purchase, refund, support and incident notifications. Contact Us messages are delivered to admin@the-trade-load.com; privacy requests can be sent directly to contact@the-trade-load.com. Opening-news requests are stored separately from member accounts in our Cloudflare database and are available to authorized administrators. After registration, we send an acknowledgement to the submitted email address. Registration does not send an email to the administrative inbox.
Contact Us allows ten attempts per day, and the opening-news form has a separate limit of five attempts per day. Each form checks the submitted email address, the signed-in account where applicable, and trusted network information; limits reset at midnight in Korea (UTC+09:00). These limits do not restrict requests sent directly by email. Optional opening news is handled separately from necessary account, transaction and security messages.
Optional website analytics report page visits to help us understand use of this course website. These automatic browser reports are disabled until you enable analytics. When you change playback speed, volume or caption size, the player saves the selected settings in your browser so they can be restored on a later visit. These settings are not sent to our server or saved in your account database. Keeping you signed in across browser sessions is a separate optional choice. Analytics and remembered sign-in choices are separate from account registration, purchase confirmations and opening-news requests.
4. Legal bases where EEA or UK data protection law applies
The basis depends on the purpose of the processing and the law that applies.
Scroll horizontally to view all columns
| Purpose | Basis |
|---|---|
| Create and authenticate accounts, deliver requested learning features, process orders and provide product access | Performance of a contract or requested steps before entering a contract |
| Protect accounts and content, investigate failures or misuse, and maintain reliable operations | Legitimate interests in service security and reliability, subject to necessity and balancing against individual rights |
| Answer support and rights requests | Performance of a contract, an applicable legal duty, or legitimate interests in resolving and documenting a request, as appropriate |
| Keep necessary transaction, tax, accounting or legal-claim evidence | An applicable EEA or UK legal obligation, or a separately justified basis such as legitimate interests where permitted; a Korean legal duty is not automatically an EEA or UK legal-obligation basis |
| Remember sign-in across browser sessions and collect optional browser page-view analytics | Your separate optional choice, with consent where required; each can be turned off without losing ordinary account or purchased access |
| Send optional opening news | Consent, which can be withdrawn without losing account or purchased access |
| Send optional account marketing emails about THE TRADE LOAD news, updates and offers | Separate consent, which can be withdrawn without losing account, Preview or purchased access |
Consent is not the basis for every service activity. Section 12 explains withdrawal of consent and objections to processing based on legitimate interests. Security limits and access checks are used to operate and protect the service. Related concerns and requests for review can be raised through the contact channel.
Rules on storing or accessing information on your device apply separately from the legal basis for processing personal information. Necessary session, checkout, verification and draft-recovery functions serve the feature you request. We do not use an account agreement or a security purpose to enable the optional choices in Section 9.
5. Required and optional information
An email address, a supported sign-in method and confirmation of the applicable signup documents and age eligibility are required for a site account. Email signup requires a password; signup through an available Google or Facebook option does not require a separate site password. Email ownership is checked through the provider where its verified information supports that check, or through a code sent to the email address. Residence is not required for signup, sign-in, free Preview access or self-service account closure. Essential sign-in cookies and service-security records support these functions.
Social sign-in is optional. Choosing an available Google or Facebook button takes you to that provider to authenticate and authorize the connection. We use its account identifier and available email information to register or authenticate your account. We do not request access to posts, friends, contacts or messages, and do not store a provider password or retain provider access or identity tokens in the account database. An existing account with the same email is not automatically merged: sign in to the existing site account and confirm your identity before connecting another method in Account → Sign-in methods. You can disconnect a method there while keeping another sign-in method, or close the site account. Disconnecting does not delete your Google or Facebook account or the provider's own records; authorization can also be managed in that provider's settings.
Before starting a new checkout, you confirm your current country or territory of residence and, for the United States or Canada, the relevant state, province or territory. A saved account residence can prefill the checkout fields, but each new checkout requires your confirmation. We save the confirmed residence with its wording, version and time alongside the order's purchase terms and choices. Later changes to your account residence do not overwrite earlier order records. You can also voluntarily save or update residence in Account for consumer support and privacy requests. If residence is unknown, we do not assume a country; relevant requests and retention duties receive a separate assessment, with proportionate additional information requested only where needed.
Reflections, opening-news requests and promotional choices are optional. A contact request requires enough information to identify a reply address and understand the request. A rights request may require proportionate identity verification. Not supplying optional information does not prevent ordinary account access; omitting information needed for a particular request may prevent that request from being completed.
6. Service providers and other recipients
Access is limited to the information needed for the stated purpose. Hosting and communication providers process information for service delivery, while PayPal also handles information for its independent payment, fraud-prevention and legal purposes.
Scroll horizontally to view all columns
| Recipient | Information and purpose |
|---|---|
| Cloudflare | Website delivery, network protection, application execution, D1 account, transaction and separate opening-news storage, R2 protected assets and log archives. Requests and stored records are processed through the services used by THE TRADE LOAD |
| Resend, operated by Plus Five Five, Inc. | Recipient and reply addresses, email contents and delivery metadata for verification, recovery, transactions, support, administrative notifications, opening-news registration acknowledgements and requested opening-news delivery when that delivery service is used |
| Google LLC (Gmail and Apps Script), with mail delivered through Cloudflare Email Routing | Receives and retains administrative and support messages, replies, attachments and mailbox security records. Apps Script checks mailbox identifiers, dates and labels and holds restricted disposal-tracking references. Mailbox storage is separate from Resend delivery |
| Google and Meta (Facebook), when you choose their available sign-in option | Authenticate the selected provider account and return its account identifier and available email information. The selected provider receives the sign-in request and browser/network information during your visit to its service. This does not send your course progress, reflections or purchase records to it. Provider account processing is described in the Google Privacy Policy or Meta Privacy Policy |
| Slack | Restricted service-security and continuity notifications containing fixed diagnostic categories and explanations, status, timestamps, counts and links with opaque incident identifiers. The links require administrator authentication and authorization to view the related records. Outgoing alerts exclude account identifiers, request IDs, request paths, raw errors, arbitrary operation names, member email addresses, IP addresses, passwords, support-message bodies and payment amounts. Incident identifiers, times and categories can be correlated with internal records; minimization is not a claim of anonymization |
| PayPal | Payment and refund processing, fraud checks and transaction confirmation. The Korean merchant service is provided under PayPal Pte. Ltd.'s terms; a buyer's PayPal provider can differ by region |
| Authorized administrators and professional advisers | Access, security, support, accounting and specific legal matters, only to the extent necessary for the relevant function |
| Public authorities | Information required by applicable law or a valid legal process |
Provider notices describe their own services and processing. Domain registration or DNS service alone does not give a provider access to the application's member database. An authenticator app is chosen and used by the administrator; the server verifies authenticator codes locally rather than sending them to Google for verification.
Font files are provided from this website through its hosting provider. Pages and lessons do not request Google Fonts stylesheets or font files from Google.
7. International processing and transfers
THE TRADE LOAD is operated from Korea and uses international infrastructure and communication services. Storage, network delivery and remote support can occur in different countries. The contracting company's registered country does not establish every processing location.
Scroll horizontally to view all columns
| Service | Countries and processing locations |
|---|---|
| Cloudflare, Inc. | Cloudflare is a U.S.-based provider whose network, infrastructure and support operate across multiple countries. Website requests and Email Routing use that global infrastructure. The application's D1 database and R2 bucket currently report Asia-Pacific (APAC), with D1 read replication disabled and no country-specific restriction. APAC identifies a storage region, not an individual country, and does not limit network or support processing to that region. See Cloudflare's network locations, subprocessors and D1 / R2 location information |
| Resend | United States: message contents, delivery logs, webhook payloads and account records are stored there. The sending-domain region does not change this storage country |
| PayPal | Korean merchant contracting entity in Singapore; PayPal describes processing in the United States and other countries and applies its regional privacy notices |
| Slack Technologies Limited, Ireland | United States for workspace customer data at rest under the current Pro trial. Slack identifies its Irish entity as the provider for Korean customers; this contracting location is separate from the U.S. storage location. International support and subprocessor processing is described in Slack's privacy information |
| Google LLC (Gmail and Apps Script) | Google LLC is a U.S.-based provider that processes information on servers in countries around the world. Cloudflare Email Routing forwards contact and administrative messages to the ordinary Gmail mailbox used by THE TRADE LOAD. The mailbox and its disposal-tracking script have no country-specific location policy; their individual storage and processing countries are not disclosed for this account. See Google's international processing information and data-center locations |
Transfers occur as the relevant feature is used: website requests, locally served font files, account or learning updates and opening-news registrations reach Cloudflare; messages sent using Resend reach that provider; checkout and refund requests reach PayPal; qualifying operational incidents reach Slack; and delivered messages reach the administrative mailbox. Application API and browser font requests use HTTPS. Delivery between mail providers follows their mail transport arrangements.
Scroll horizontally to view all columns
| Recipient and provider contact | Transferred information and purpose | Retention information |
|---|---|---|
| Cloudflare, Inc. — privacyquestions@cloudflare.com; privacy information | Request IP, approximate connection country and browser information; account, authentication, residence, learning, transaction, opening-news and security records processed by the application. Hosting, storage, access protection and service operation | Application records follow Section 8. D1 Time Travel keeps a rolling recovery history of seven days on Workers Free or thirty days on Workers Paid. Separate R2 archives are not governed by that recovery window |
| Plus Five Five, Inc. (Resend) — privacy contact | Email and reply addresses, message contents and delivery identifiers. Verification, recovery, service messages, routing support, opening-news registration acknowledgements and requested opening-news delivery when that delivery service is used | THE TRADE LOAD uses Resend Free: email and log data is retained for thirty days, backups for seven days, and remaining customer data is deleted within ninety days after ending the Resend account. These are provider retention periods, separate from the local delivery records and recipient mailbox copies |
| PayPal Pte. Ltd. for the Korean merchant service — privacy contact | Order and refund references, amount, currency and transaction requests for payment, refund and reconciliation. Information entered directly into PayPal is also governed by its own notice | PayPal retains records for payment, fraud-prevention and applicable legal requirements under its regional notice. Its retention is separate from THE TRADE LOAD's transaction record schedule |
| Slack Technologies Limited — privacy@slack.com; dpo@slack.com; privacy information | Fixed service-security and continuity diagnostic categories and explanations, status, timestamps, counts and opaque incident links for restricted incident response. The website does not send account identifiers, email addresses, IP addresses, request paths or free-text incident details to Slack. Related records are available only after administrator authentication and authorization | The workspace is configured to delete messages and files after ninety days. Necessary evidence for an ongoing investigation or legal duty is preserved separately with restricted access. Slack performs retention cleanup on its own schedule; local incident cleanup does not delete Slack messages |
| Cloudflare Email Routing and Google LLC (Gmail and Apps Script) — Google privacy contact | Sender and recipient addresses and messages delivered to contact@the-trade-load.com or the administrative inbox, including replies and supplied attachments. The authorized Apps Script reads message identifiers, dates and labels for disposal and stores associated timing references | The verified rules forward to Gmail. The hourly mailbox automation moves completed inquiries to Trash ninety days after their completion label is first observed, and handled alerts after thirty days from that observation. Opening-news correspondence held in the mailbox is marked for disposal after delivery or withdrawal; otherwise a one-year limit applies, with individual review where requests share a conversation. Open matters and necessary statutory evidence are separated. Script references remain while needed for classified-mail disposal and are cleaned when tracking is no longer needed. Gmail Trash retains deleted mail for up to thirty days unless permanently deleted earlier; subsequent system and backup deletion has its own cycle |
The table distinguishes provider locations, confirmed storage regions and global processing. The linked provider lists describe their infrastructure and support scope; they do not mean that every location receives every THE TRADE LOAD record. We review provider disclosures and relevant service settings when transfer arrangements change, update this Notice and provide any notice or separate consent required by law. Cloudflare and Google do not provide an individual processing-country record for each request in the service configurations used here. The regional and global descriptions above reflect the available location information.
For necessary overseas processing entrustment and storage used to provide accounts, purchased learning access and related verification, recovery and transaction messages, the identified Korean transfer basis is Article 28-8(1)(3)(a) of the Personal Information Protection Act: processing needed to enter into or perform the requested service contract, with the required transfer information disclosed in the privacy notice. This covers the necessary hosting, storage and transactional-mail functions of Cloudflare and Resend only to the extent those conditions are met. The required disclosures and safeguards are assessed against the actual service and processing scope described above.
Opening-news registration uses one initially unchecked choice to request opening news. This form does not collect separate overseas-processing consent, and neither a news request nor reading this Notice is recorded as that consent. Opening-news registration records are stored with Cloudflare. Resend processes the submitted recipient address, acknowledgement message and delivery metadata to send the registration acknowledgement; the request is not forwarded to the administrative mailbox. If the requested opening news is later sent through Resend, the recipient address and message are processed under the delivery arrangements described above. Applicable international-transfer requirements remain separate from the opening-news choice.
Slack is used only for limited alerts needed to detect and respond to failures affecting account security, payments and purchased access. The identified Korean ground for necessary processing entrustment supporting those contractual services is Article 28-8(1)(3)(a), conditional on necessity and the required transfer disclosures. Restricted access, reduced message contents and ninety-day retention support safeguards; they are not independent transfer grounds. This assessment does not extend to general marketing, user correspondence or unrestricted staff use of Slack. Account details and IP addresses remain in the restricted service records. An opaque incident link does not grant access to those records or make the notification anonymous.
Information entered directly into PayPal is collected under PayPal's own payment arrangement; order or refund information sent by THE TRADE LOAD to PayPal requires its own applicable transfer basis for the relevant processing. Separate consent, contractual necessity and applicable overseas safeguards must be assessed for their actual scope; merely naming a legal provision does not satisfy its conditions.
Transfer objections, consent withdrawals and questions about safeguards can be sent to contact@the-trade-load.com. Optional opening-news requests can be withdrawn without closing an account. If processing necessary to provide an account, a requested message or a PayPal payment cannot proceed lawfully, the affected feature may be unavailable; any alternative and remaining legal retention requirements are assessed for the request. Withdrawal does not automatically erase records subject to a lawful retention duty.
For EEA and UK data, an applicable adequacy decision or appropriate safeguard must cover the actual transfer. Resend's DPA incorporates EU Standard Contractual Clauses and the UK Addendum. Cloudflare and Slack also publish processing agreements with transfer safeguards; their use must match the actual parties, destination and processing. These mechanisms are separate from the Korean transfer basis above. Information about applicable safeguards can be requested through the privacy contact.
8. Retention and deletion
Retention depends on the record, its purpose and applicable obligations. Account closure ends sign-in and course access and deletes sign-in credentials, active sessions and challenges, current residence details and ordinary saved learning records. Necessary transaction, request, consent and security evidence is handled separately. Closure is not a claim that every message, archive or provider copy has already been erased.
Scroll horizontally to view all columns
| Record | Retention or deletion criteria |
|---|---|
| Active account and learning information | While needed for the account and requested learning features; ordinary account and learning records are removed on successful closure |
| Administrator authentication secrets and recovery-code hashes | While needed for authorized administrator authentication; removed with the sign-in account on closure, subject to separately retained audit evidence |
| Product access and free test access records | While needed to administer granted access. Closure ends access; remaining order and enrollment references follow the relevant transaction or request assessment |
| Contracts, withdrawals, payments and supply evidence | Five years where the Korean e-commerce retention duty applies. Additional tax or accounting duties can require a different period or starting date for the affected evidence |
| Unfinished checkout choices before a payment-provider order exists | Choices recorded with a ninety-day purpose limit are eligible for scheduled deletion ninety days after recording only when no provider order, payment check, purchase or related financial record exists. A privacy request, closure review, preservation hold or other linked disposal review prevents this limited cleanup. Payment, refund and dispute evidence follows its separate assessment. This is an internal purpose-based limit, not a statutory retention period |
| Consumer complaint and dispute evidence | Three years where the Korean e-commerce complaint retention duty applies; unresolved claims and different applicable duties are assessed separately |
| Confirmed EU OSS tax evidence | Ten years from the end of the relevant transaction year only where the actual transaction and tax scheme require it; residence alone does not establish OSS applicability |
| Advertising evidence | Six months where the Korean e-commerce advertising-record duty applies; this is not permission to collect advertising-tracking data |
| Operational detection samples | One hour, followed by scheduled cleanup |
| Operational alert delivery records | Thirty days, followed by scheduled cleanup. Resolved incident records are cleared after thirty days from resolution; unresolved incidents are assessed while still needed |
| Local email-delivery observations | Thirty days from send acceptance, followed by scheduled cleanup. Webhook replay references are cleared after seven days. Provider-held emails and mailbox copies are separate |
| Independent availability monitor notification records | Completed or otherwise non-pending delivery records and their local Slack delivery references are cleared after seven days from creation. Pending retries are retained until handled; this does not delete messages already delivered to Slack or email |
| Sessions, recovery codes and unfinished verification | Ordinary sign-in uses a browser-session cookie, with a server-side maximum of seven days. An explicitly remembered sign-in expires after ninety days without qualifying use; active use can renew it as explained in Section 9. Sign-out or security revocation can end either session earlier. Codes and verified recovery grants expire after five minutes. Expired database records are cleaned during relevant account operations or closure. Expiry and physical deletion are different events |
| Social sign-in connections and unfinished sign-in requests | Provider and account-identifier links remain until disconnected or the site account is closed. Temporary browser-binding, verification and contact-email information for a sign-in request expires after ten minutes; expired requests are deleted during subsequent social sign-in starts or scheduled hourly maintenance. Provider tokens are used transiently for verification and are not saved in this database. Provider-held records follow the provider's own policies |
| Contact and opening-news form rate-limit records | Older daily buckets are cleaned during a subsequent form request once older than two days; this is not a guarantee of deletion at an exact clock time |
| Ordinary support correspondence | Staff mark resolved inquiries with a completion label. The hourly automation moves eligible messages to Gmail Trash ninety days after it first observes that label. Open inquiries are excluded. Necessary consumer-complaint, transaction and legal-claim evidence is classified separately under its applicable period or documented hold |
| Routine operational alert emails | Staff mark handled alerts with a completion label. The hourly automation moves eligible messages to Gmail Trash thirty days after it first observes that label. Unresolved incidents and necessary investigation evidence are excluded and assessed separately |
| Opening-news registration records | Each record expires 365 days after the latest explicit request for that email address. Expired records are excluded from the active administrator list and deleted by hourly database cleanup. Opening-news use ends earlier when the requested news has been delivered or the request is withdrawn; staff handle those events and disposal separately. Necessary complaint, consent or legal-claim evidence may remain separately for a documented purpose and expiry; a request does not authorize indefinite marketing use |
| Account marketing preferences and consent records | Linked to the active account. Withdrawal ends marketing eligibility immediately; the choice, displayed wording and relevant consent or withdrawal times remain with the account to honor the preference and identify its basis. These records are deleted with account closure and are not converted into the separately retained account-document or transaction evidence |
| Opening-news correspondence in a mailbox | Staff record delivery or withdrawal and label the correspondence for disposal; the hourly mailbox automation moves eligible messages to Gmail Trash. Otherwise, the purpose limit is one year from the request. The automation uses the newest active message date for grouped conversations, so staff handle individual requests separately where needed to meet each request's limit. This mailbox schedule is separate from the database registration schedule |
| Slack alert messages and files | The workspace message and file retention setting is ninety days from creation. Only evidence necessary for an ongoing incident, legal obligation or claim is preserved separately with restricted access and a recorded review date |
| General visitor access and member authentication history | Ninety days from the event under an internal security and incident-investigation schedule. This covers visitors without accounts and applies to application records in D1 and R2. Relevant investigation or legal holds can postpone deletion |
| Optional browser page-view reports | Ninety days from the event under the application access-record cleanup schedule. Turning off analytics stops new optional reports. Requests concerning reports already received can be made through the privacy contact; any necessary preservation is assessed separately |
| Email-verification and password-attempt state without an account | Eligible state is removed by scheduled cleanup ninety days after its last recorded state update. An active account, unexpired verification challenge, explicit security lock, related privacy request or preservation hold prevents this cleanup. Necessary account-security and closure safeguards remain subject to their separate purpose and review. This is an internal purpose-based schedule |
| Administrator access and administration history | Administrator access to personal-information functions and ordinary administration history: two calendar years. Administrator access-right grants, changes and revocations: three calendar years. These are purpose-based operating schedules, not a claim that the same statutory period applies to every event. Payment and refund evidence follows its separate transaction or complaint period. These categories are not subject to the general ninety-day log rule |
| Account-support notes | While needed for active support. After closure, ordinary notes are cleared ninety days after the later of closure or their last update, unless a relevant documented hold applies. Necessary transaction and complaint evidence is kept separately |
| Account document acceptances and residence history | While the account is active, then ninety days after closure to verify the closure and relevant account choices. This is an internal purpose-based schedule, not a universal statutory period. Purchase-specific confirmations and residence evidence remain under the separate transaction rules |
| Privacy-request and closure case contents | Contact address, residence and case narrative are retained for three calendar years after the response and outstanding disposal and provider checks are completed. An incomplete request or documented hold prevents the completion clock from starting. At expiry, the case contents and associated free-text evidence are removed; a minimal restricted closure and disposal reference remains to prevent delayed writes from restoring erased records |
| Replay-prevention and authentication safety references | Minimum identifiers needed to block a delayed payment or stale authentication operation are kept separately from case contents while that replay risk exists. They are restricted to that purpose, remain subject to review and are not treated as anonymous. Erasing case contents does not remove these safeguards or authorize indefinite use for another purpose |
| D1 recovery history and R2 archives | D1 Time Travel has a rolling recovery window of seven days on Workers Free or thirty days on Workers Paid. Scheduled application cleanup checks each archived log record's period, verifies the replacement containing any unexpired or held records, and removes the superseded R2 object. Failed steps are retried. The R2 seven-day incomplete-upload rule is separate from this completed-object disposal |
| Cloudflare Workers Logs, where enabled | Cloudflare's current platform-log retention is three days on Free and seven days on Paid. This is separate from application access and authentication logs stored in D1 or R2 |
| Gmail recovery and Google-held backup copies | Deleted mail stays recoverable in Gmail Trash for up to thirty days unless permanently deleted earlier. Google describes subsequent storage-system deletion as generally taking around two months and encrypted backup retention as up to six months, subject to security or legal exceptions. These are provider deletion cycles, separate from active use for the mailbox purposes above |
| Other provider copies | Follow the applicable provider recovery cycle and necessary legal obligations. Resend Free periods are in Section 7. Local record cleanup does not remove messages already delivered to a mailbox or Slack |
Established automatic rules apply to eligible completed Korean purchase evidence and resolved refund-complaint text where the relevant residence and record classification are confirmed. Purchase evidence must first be classified for additional accounting, tax and other duties. Unknown, cross-border and other exceptional records, including unpaid records outside the limited unfinished-checkout category above, require a separate recorded assessment. New relevant transaction events can change the applicable retention calculation. A documented dispute hold applies only to relevant evidence and must be released when no longer necessary.
Public channels, private channels, direct messages and files in the Slack workspace are configured for ninety-day retention. Member overrides of message retention are disabled. Mailbox disposal depends on classifying requests as pending, resolved, opening news, statutory evidence or subject to a hold. An authorized Google Apps Script automation is installed to check those labels hourly and move eligible messages to Gmail Trash. It does not empty Trash or immediately erase Google backup copies, and unclassified mail still requires review.
Staff classify mailbox messages; the automation does not infer completion or legal significance from their contents. It reads message identifiers, dates and labels rather than message bodies or headers. It keeps restricted timing and classification references in Google Apps Script, without sending them to another service. Completed-inquiry and routine-alert clocks start when the completion label is first observed, not on the email receipt date. Evidence clocks use a conservative classification date and restart when a new message may introduce a relevant event; they do not replace the record-specific statutory assessment. A new reply or an unclassified message in a tracked conversation is returned for review. Pending items, drafts and holds are excluded, and conflicting retention labels use the latest expiry. Grouped opening-news correspondence can require individual review to enforce each request's one-year purpose limit without prematurely removing a newer request. Confirmed delivery or withdrawal must also be recorded for disposal; labels do not authorize continued marketing use.
Operational cleanup runs on a five-minute schedule. General log expiry, eligible account-record erasure and completed-case minimization run hourly in bounded batches and retry failed work. Account-linked security cleanup also checks for remaining copies after the applicable periods; it does not extend the shorter general-log periods. These are cleanup schedules, not a guarantee of deletion at the exact expiry second. A hold records its evidence scope, reason and review date; the review date does not release it automatically. Provider requests and backups require separate verification. Other categories require an actual expiry and disposal process; a pending review is not authority to retain records indefinitely. Electronic records are deleted from the relevant active database or object storage, with separate handling of archived and provider copies. Email contact@the-trade-load.com for the retained categories, grounds or status of a request.
9. Cookies, browser storage and external requests
Optional analytics and remembered sign-in choices start off. You can open Cookie settings from the website footer, allow or reject the optional choices together, or save individual choices. No automatic browser page-view reporting starts merely because you visit, create an account, buy access or read this Notice. Your selection applies to this website in the current browser, rather than every device or independent website you use. Playback controls separately save the settings you select, as described below.
Scroll horizontally to view all columns
| Technology | Purpose and duration |
|---|---|
| ttl_member_session cookie, ordinary sign-in | Necessary to authenticate the account you signed in to. The default cookie has no persistent expiry and is intended for the browser session; the server session lasts at most seven days. Browsers can restore session cookies when reopening a previous session, so use Sign out on a shared device |
| ttl_social_flow cookie | Necessary only when you start social sign-in or connect a provider. Binds the provider's response to the browser that requested it and expires after ten minutes; completion or cancellation clears it. It does not contain your provider password or access token |
| ttl_member_session cookie, Keep me signed in | Optional persistent sign-in after you select the unchecked sign-in choice or enable it in Cookie settings. Lasts up to ninety days. In browsers that support safe coordination between tabs, a pointer or keyboard interaction in a visible page can renew it for another ninety days; otherwise it keeps its existing expiry. Automatic playback progress, background polling and merely leaving a tab open do not renew it. Sign-out or revocation ends it earlier |
| ttl_checkout_intent cookie | Essential association with a checkout request, up to two hours |
| ttl:privacy-preferences local storage | Saves the optional analytics choice, record version, choice time and expiry so the site can honor an acceptance or refusal. Kept for up to 180 days from the saved choice. It does not contain an advertising identifier. If it is missing, invalid or expired, analytics remain off until you choose again |
| Playback settings in local storage | Saves the playback speed, volume, audible volume and caption size that you select in the player. Stored in the current browser for this website, without a preset expiry, until replaced by later selections or removed through browser settings or by the browser itself. These settings are not stored in the account database, sent to our server, or synchronized across devices or different website addresses. If browser storage is unavailable, playback controls still work for the current player but cannot retain your changes for a later visit |
| Pending email-verification session storage | Email address, verification reference and expiry/resend times used to resume an unfinished verification; removed on completion, when expired data is processed, or when the browser tab session ends |
| Reflection draft session storage | Unsaved text and recovery versions within the browser tab session. Cleanup also occurs through related account actions; this is not a guaranteed twenty-four-hour background deletion |
| Locally provided font files | Loads font stylesheets and files from the website's hosting provider; no current Google Fonts network request is required |
| PayPal hosted checkout | When checkout is enabled and you complete its confirmations, the payment action takes you to PayPal's website. The course website does not load a PayPal checkout script or iframe on the initial page visit. PayPal explains the storage and processing on its own website |
Optional website analytics sends automatic browser page-view reports only while that choice is enabled. It is separate from necessary requests to deliver a page or lesson, save learning progress, check an access attempt, process a payment, or protect an account. Necessary server access, security, payment, administrator and PDF-download records can therefore continue after you reject optional choices, subject to the purposes and periods in this Notice. The analytics choice does not authorize advertising tracking.
Rejecting optional choices stops those browser reports. Rejecting optional items in Cookie settings also turns off remembered sign-in for a signed-in account while keeping the current session signed in; the introductory banner changes only the analytics choice. It does not clear the playback settings you selected, close an account, remove a purchase, erase saved progress or reflections, cancel a payment or refund request, or withdraw a separate opening-news request. Turning an individual optional choice back on requires a new affirmative action. Sign out ends the current sign-in; use the contact channel for requests about personal records already held.
You can change or withdraw optional choices through Cookie settings at any time. Browser settings can also block or remove cookies and local storage, although blocking necessary sign-in or checkout storage can prevent those requested functions from working. Clearing browser storage removes the saved choice; it does not create permission to enable optional features. A Global Privacy Control signal disables optional browser analytics even if a previous choice enabled it; it does not disable sign-in or playback controls. The application does not use advertising pixels or cross-site behavioral advertising and does not otherwise change its operation in response to the separate Do Not Track signal. This describes this course website's choices, not every independent practice of a linked service or another website.
10. Security
Access controls, salted password hashing, protected sessions, administrator multi-factor authentication and security-event records help protect personal information. Access to administrative alerts and records is restricted. Pseudonymous references can still be linked to related service records and are not treated as anonymous. No online service can guarantee the absence of risk. Suspected compromise can be reported to contact@the-trade-load.com.
11. Opening news and optional messages
Opening-news requests are optional and limited to news about THE TRADE opening. Submitting a request does not create an account or purchase access. The email address and request record are stored in a separate database table for authorized administrators to review, without a link to a member account, password or sign-in session. The registration table does not store visitor IP addresses; separate security and form-limit records follow the rules in this Notice. Repeated requests for the same normalized email address update one record. Registration does not send an email to the administrative inbox or add the address to a general marketing subscription.
After registration, an acknowledgement is sent through Resend to the submitted email address. It confirms receipt of the request; it is not an account-verification email or the requested opening announcement. Sending this acknowledgement does not end the opening-news request. Acknowledgement delivery records and provider copies follow the email-retention arrangements in Sections 7 and 8.
The opening-news choice must be actively selected to submit this form. Declining it does not affect website, account or purchased course access. The request record includes the consent version and opening-news wording displayed in the form, together with server-recorded request times. A repeated explicit request updates the record with the latest request and consent details. Separate overseas-processing consent is not collected or inferred.
To withdraw an opening-news request, contact contact@the-trade-load.com from the submitted email address. Account creation and purchases alone do not subscribe an address to opening news or other promotional messages. Necessary account-security, transaction and support replies can still be sent for their separate purposes.
Signup offers a separate, initially unchecked choice: "Email me news, updates, and offers from THE TRADE LOAD." The accompanying text says "Optional. Unsubscribe at any time." Selecting this choice gives permission to use the account email address for those marketing emails after successful email verification and account creation. Declining it does not prevent signup, Preview or purchased course access. Accepting the Terms of Use or Privacy Notice, signing in, resetting a password, requesting opening news or buying access does not select this choice.
The account preference is stored in Cloudflare with the account identifier, email address, selected status, displayed wording and version, and the time of affirmative consent or withdrawal. Opening-news requests remain separate and are not reused as general marketing permission. A refused or withdrawn choice is excluded from marketing recipients. This preference does not authorize advertising tracking or independently establish an international-transfer ground. Any marketing delivery remains subject to the applicable notice, transfer and email rules; storing this choice does not itself send a marketing message.
You can withdraw account marketing consent through Account → Marketing emails → Unsubscribe, or by contacting contact@the-trade-load.com from the account email address. Withdrawal stops marketing eligibility without affecting account, learning or purchase access. Account closure deletes the account-linked preference. Cookie settings control browser choices separately and do not change opening-news requests or account marketing consent.
12. Privacy rights and requests
Depending on applicable law, rights can include access, correction, deletion, restriction, portability, objection, withdrawal of consent and a complaint to a regulator. Email contact@the-trade-load.com or use Contact Us, including after account closure. The email channel remains available when the form's daily limit is reached. A request should identify the relevant account or email address and the requested action; proportionate verification may be needed to protect another person's information.
Self-service closure is available from the account area after current-password and closure confirmation, or an account-email confirmation code and closure confirmation when the account has no site password, including when no residence has been provided. Unknown residence does not prevent account closure or remove applicable rights; any remaining records receive a purpose-based retention assessment. An in-flight payment operation may need to finish first, and a primary administrator must transfer that role before closure. Closure ends access but does not automatically issue a refund, cancel a pending refund or waive consumer rights. There is no self-service export of every personal record; access and portability requests can be made through the contact channel.
Requests are handled within the time required by applicable law. An internal review or retention assessment does not replace that deadline. Where a request cannot be granted in full, the applicable reason and available next steps should be provided. Where required, a refusal can be appealed through the same contact channel. Objections to legitimate-interest processing and to direct marketing are handled under the relevant legal rules. Withdrawal of consent does not affect earlier lawful processing.
13. Age and children
Accounts and paid access are intended for people aged nineteen or older who have also reached the age of legal majority where they live, if higher. Signup includes confirmation of eligibility; the ordinary signup flow does not collect a date of birth or an identity document to independently verify age. Suspected ineligible use can be reported to contact@the-trade-load.com for restriction and appropriate deletion, subject to necessary legal records.
14. Regional information
Where EEA or UK law applies, Sections 4 and 12 describe the relevant bases and rights. Complaints can be made to the competent EEA supervisory authority or the UK Information Commissioner's Office.
U.S. state rights depend on the applicable law and business thresholds. The service does not sell personal information or share it for cross-context behavioral advertising. Applicable requests, authorized-agent requests and appeals can be submitted to the privacy contact. If those practices change, the applicable notice and choices must be provided before the change.
Korean and other applicable local rights remain available regardless of the residence selected in an account. Necessary local-language notices or additional regional information must accompany this Notice where required. Choosing a residence or accepting a document does not waive mandatory protections.
15. About this Notice
This Notice applies from the effective date shown above. Questions about this Notice or the handling of personal information can be sent to contact@the-trade-load.com. Records subject to applicable legal retention or a documented preservation hold remain protected.
Material changes receive the notice or separate choice required by applicable law. This Notice does not retrospectively authorize processing, replace separate consent where required, or convert a refusal or withdrawal of optional opening news into consent. Accepted document versions are preserved separately so the notice associated with a recorded choice can be identified.