Legacy reader tools stay browser-local. Explicit saves in signed-in My SCS use the Site database. Public request counts remain separate, and new REAL engagement collection stays off.
Legacy tools stay local. Signed-in My SCS saves go to your member workspace.
Reading and local tools never submit an assessment.
Public page requests count automatically. Optional action sharing remains a separate choice.
Supply Chain Savings is the service brand. The operator is Martingale and Medallion. The public contact is mandujanotony31@gmail.com.
Assessment intake is unavailable. Reading, applying a local profile, saving member work or exporting a file does not create an assessment, send an email, book transportation or subscribe you to notifications. Administrative and editorial workspaces remain restricted to the owner.
Reading interests, shipping profiles and comparison cases in My Freight and Compare use browser-local storage when you explicitly apply or save them. Device remembrance is optional. Signing in does not automatically upload or migrate this legacy data into My SCS. The browser-local Impact Brief remains separate too.
In My SCS, you explicitly save lanes, products, diagnostic load plans, five-mode cost scenarios and frozen decision briefs. Those records and their revision history are stored in the Site’s hosted D1 database under the trusted account identifier supplied by ChatGPT sign-in. This account identifier is used for member ownership and access checks, not as an anonymous analytics identifier. A successful save is confirmed by a receipt; an unfinished form or uncertain network response is not a confirmed save.
Saved inputs can include the names, routes, dimensions, entered charges, notes and assumptions you provide. A frozen brief contains copies of its selected source revisions, so later source edits do not silently rewrite it. Only enter information you are entitled to store; do not enter passwords, payment details or unnecessary sensitive information.
The application restricts member reads and writes to the signed-in member’s workspace. This is application access control, not end-to-end encryption or a promise that the operator and hosting provider cannot administer the database. Signing out clears the application’s current private workspace display; downloaded files, other open browser contexts and browser backups need their own care.
No member save sends a freight request or forwards your inputs to an outside carrier, referral service, payment provider or email address. The separate owner-only staging Site and existing browser-local records are not automatically copied into the public member database.
The Site does not invite or accept public assessment forms. An owner sign-in does not turn a reader action into consent to submit a request. No tool sends your profile, question, contact details or comparison inputs to an inbox.
Existing administrative TEST records, if any, remain owner-only. They use a restricted D1 database, access checks and duplicate-prevention information. The separate assessment-retention rule describes those retained records; it does not govern member workspaces or invite a public request.
You may initiate an email to the published contact yourself for service questions, corrections or privacy requests. Email is separate from this Site’s administrative database; the application neither sends nor forwards it for you.
REAL v2 aggregate-event collection and account-linked engagement history are disabled. The optional history preference is a clearly labeled TEST-only review control, not permission that activates live collection. Declining or revoking it does not block the workspace. TEST preference records use a separate namespace; revocation erases their linked test-history epoch while retaining minimal replay-prevention preference metadata.
Existing public page-request counts and the older optional action controls described below are unchanged. Saved member records and their revision history are application data, not engagement measurements. No payment service or live market-data feed is connected. Optional Microsoft Clarity analytics is separate and requires the consent described below.
Automatic public page-request counts began at release on 25 October 2026 UTC; the first day is partial. Eligible successful HTML GET requests to reviewed, canonical public pages are counted by the Site without JavaScript or a page-view opt-in. A normal public-page reload can count again, including a reload by the owner. Private/admin pages, APIs, assets, HEAD requests, redirects and errors are excluded.
The request counter stores only namespace (REAL or TEST), UTC day, reviewed page path and count. It creates no measurement cookie and stores no IP address, user-agent, referrer, account identifier, visitor ID, session ID or one-use receipt. Headers are inspected transiently to apply exclusions. Query strings, fragments and search terms are discarded from the counters. Profiles, lanes, scenario inputs, prices, contact details and inquiry text are not collected by this counter. Page titles in the owner report come from the current source catalog, not a per-request browsing record.
The design excludes requests carrying DNT: 1 or Sec-GPC: 1, along with obvious bots and prefetches. Explicit internal/test requests stay TEST. Adding scs_count=off to a URL excludes that request only; it is not a persistent preference, does not cover other links and cannot undo earlier requests. There is no local-storage switch that claims to stop the initial server request after it has already arrived.
Repeats and undetected bots may count. Cache or browser-history restores, network failures and exclusions can undercount. No exactly-once guarantee, unique-visitor count, connected browsing journey, complete audience census or organic-search attribution is claimed. Google Search Console is connected for Google search impressions, clicks and indexing reports; it does not require a visitor analytics cookie or identify individual readers. Counts cannot be isolated as your individual contribution because no person identifier is stored.
Browser-local test counters and optional first-party action-category sharing retain their independent, off-by-default controls. Enabling or stopping them does not change automatic public page requests. The optional action stream sends a category and a short-lived one-use retry identifier, not a page path, profile, contact record or persistent person/session identifier. Its categories cover article openings, calculator interactions and administrative assessment-review/save confirmations; those last two are not public reader-pilot features. You can stop new optional action sends on the measurement page; a request already in flight may finish.
The former separately opted-in page-view collector closed on 25 October 2026. Historical opted-in views remain a separately labelled legacy dataset in the owner report. They are not automatic request counts, are not added to the new totals and do not backfill earlier browsing. There is no page-view consent checkbox to enable.
These counters do not create an assessment, clear local shipping tools or publish administrative records. The request report is owner-only. Microsoft Clarity is available only after you select Accept analytics in Privacy settings. It measures clicks, scrolling, device/browser information and masked session activity on a reviewed subset of public information pages. Articles, search, tools, uploads, account and financial pages are excluded; URL and referrer exclusions can also prevent collection. Strict masking is configured, but no recording system is a guarantee against all disclosure. Do not enter confidential information on monitored public pages. We do not send account identifiers, names, emails, custom user IDs or shipping profiles to Clarity. Its own pseudonymous cookies, including _clck and _clsk, can connect page views and sessions; these are different from SCS account IDs. Microsoft may process network information and use collected information for its own purposes under the Microsoft privacy statement, including improving its services. Advertising storage is denied and no advertising integration is enabled. Microsoft describes its cookies here. Our local consent preference lasts up to 180 days. Closing Privacy settings stores a separate local display preference so the panel stays closed across pages and reloads; it does not accept analytics or change your consent. Use the Privacy settings button to reopen it. This display preference remains until browser storage is cleared. If storage is blocked, closing works for the current page but may not be remembered. Reject analytics is equally available; browser GPC/DNT signals override acceptance. To withdraw, open Privacy settings and select Reject analytics. The page reopens without analytics and attempts to clear first-party Clarity cookies. If it cannot reopen, close the page; already-sent data and in-flight requests cannot be recalled. Clearing browser storage removes the saved preference. Microsoft currently documents 30 days for ordinary playback and 9 months for click/heatmap data and labeled or favorited sessions; see its retention policy. For privacy requests, use the contact route stated in this notice; withdrawal does not itself delete previously collected vendor data. No advertising pixel or email notification is configured. Standard hosting infrastructure processes incoming requests and may retain separate operational logs; the application’s counts-only storage does not mean the platform has no logs.
PAGE COUNTS & OPTIONAL MEASUREMENT →Your My SCS workspace, including archived lanes, products, diagnostic plans, cost scenarios, frozen briefs and their associated revision history, is retained until you choose permanent deletion. Archiving hides a record from active lists; it does not erase its content or history. There is no automatic 30-day or 90-day expiry for these core member records.
Data & account provides a full export of your core workspace and all its associated record-revision history. Export checks a consistent saved revision across pages; if the work changes while exporting, restart rather than treating a partial copy as complete. The export does not include another member’s work or separate operator editorial/forecast records.
Permanent deletion requires an explicit confirmation and the current workspace revision. It removes the saved member records, frozen snapshots, associated record-revision history and prior save receipts from the active application database. A minimal empty revision marker, trusted account key, timestamps and non-content erasure receipt remain to reject delayed pre-deletion saves and unsafe retries. They do not retain the erased inputs or snapshots. Work deliberately saved after a confirmed deletion is new work; replaying an old erasure does not delete it.
This deletes the My SCS saved workspace, not your ChatGPT account, public articles, separate operator research or optional engagement preferences. Use the separate revoke control for optional TEST history. Deletion cannot recall copies you downloaded, emailed or copied elsewhere. Hosting-platform backups and operational records may retain earlier data; no immediate backup-erasure schedule or forensic-erasure guarantee is claimed.
EXPORT OR PERMANENTLY DELETE SAVED WORK →Existing owner-test assessment payload and internal note text expire after 30 days; the reader pilot does not accept new public assessments. They are erased on the next service activity after expiry, or earlier operator deletion. This is activity-triggered cleanup, not a promise that a timer erases data at an exact instant.
Automatic request buckets use a rolling 90 UTC-day window. Expired request buckets are pruned on eligible collection or an owner request-report read, not by a scheduled job. Optional action-category counts have their own 90-day window and collection-triggered cleanup. Inactive storage and platform backups can retain data longer.
One-use optional-action receipts support duplicate prevention for 24 hours, with cleanup on the next valid action collection activity. Legacy opted-in views had their own receipts; that collection is now closed. Owner reads of the legacy report prune its expired 90-day buckets and receipts older than 24 hours; there is no scheduled cleanup. Automatic page-request counts create no receipt or person/session identifier.
Assessment receipt lookup is available for a limited period; minimal anti-replay/security metadata can remain after payload deletion. Deletion does not recall copies you exported or emailed. Hosting-platform backups may retain earlier data.
The 30-day rule describes only the separate assessment service, not My SCS member data. It is not a promise to erase the operator’s separate editorial history, published source records or internal administrative workspace on that schedule.
The Site uses hosted application infrastructure and a D1 database. Hosting, authentication and network infrastructure necessarily handle requests and may maintain their own operational records. The application’s decision not to store IP addresses or user-agents in aggregate metrics is not a claim that infrastructure has no logs.
Essential security controls may use cookies or short-lived browser references for sign-in, request protection and receipt recovery. These are distinct from the automatic request counter and optional action measurement. The service uses restricted administrative access and request validation, but no service can promise absolute security or uninterrupted availability.
Source links take you to independent websites with their own practices. My SCS runs a pinned Cargo engine inside this application. Its results are diagnostic, not certified loading instructions. The Cargo Crate handoff page links to a separate application with its own access and storage rules; no SCS profile, scenario or account credential is attached to the link.
Use the relevant legacy tool to clear local profiles or saved cases. In My SCS, use Data & account for full export or confirmed permanent deletion of saved member work. Use the measurement page to stop new optional action-category sends. For automatic page requests, the design respects DNT/GPC request headers and the per-request URL exclusion described above; stopping an optional counter does not retract a page request. For a question about a submitted assessment, access or deletion, email mandujanotony31@gmail.com and identify the request without including unnecessary sensitive details. The operator may need enough information to locate the correct record and confirm the request.
A contact link opens your email application. You decide whether to send; this Site does not send or forward that email for you. Email correspondence is separate from the Site’s assessment database and its expiry process. No response time or legal-compliance certification is promised by this page.
Material changes to these operating practices should be reflected here with an updated date. This notice describes SCS 2.0 with member saves, billing off, public assessment intake off and new REAL engagement collection off. Opening those services would require separate changes and updated disclosures.