Clear boundaries for the data we use.

How Commerce Cockpit uses data

Our current validation product uses approved marketplace data to show source-specific operations, freshness and exceptions, bind access to the correct seller and store, detect failures or misuse, and support authorized users. Its current read-oriented scope excludes buyer and order records, payments, banking data, marketplace passwords, browser cookies, MFA codes, identity documents and marketplace write actions.

Authorization and protection

Marketplace access is tied to an approved application, reviewed scope and exact seller/store authorization. We keep admitted credentials on the server, restrict service access, use encryption for protected credential and host storage, and exclude tokens from source code, browser storage, chat, ordinary email, screenshots and client responses. A connection may be limited to validation; broader Production use and credential refresh are assessed separately.

Retention, requests and deletion

We retain product data for approved service, security, support and documented legal or platform purposes. An authorized, store-scoped disconnection stops local access and refresh and removes active credentials and retained inspection facts for that store. Logs, backups, support records, vendor copies and provider-side grants have separate handling and may remain for a justified period or hold. Deletion is not automatic or instantaneous across every location.

For access, correction, deletion or disconnection, email privacy@titanlinkinc.com. We verify the requester's authority and affected store without asking for secrets in ordinary email, then review applicable exceptions and coordinate the response.

Service environment and data location

Titan Link uses selected infrastructure and business service providers to operate its services. The current Commerce Cockpit application and encrypted recovery storage used for marketplace validation are hosted in the United States. Marketplace providers process seller data under their own platform relationships. Provider roles, access paths, and location records are maintained internally and reviewed when service architecture or data flows change.