{"id":261,"date":"2026-10-05T23:52:31","date_gmt":"2026-10-05T23:52:31","guid":{"rendered":"http:\/\/mychinawarehousing.local\/cookie-policy\/"},"modified":"2026-10-26T01:14:58","modified_gmt":"2026-10-26T01:14:58","slug":"politica-de-cookies","status":"publish","type":"page","link":"https:\/\/mychinawarehousing.com\/es\/cookie-policy\/","title":{"rendered":"Pol\u00edtica de cookies"},"content":{"rendered":"
\n

At a glance<\/strong><\/p>\n

The reviewed public site has no installed advertising pixels, visitor analytics or embedded chat widgets. Public browsing does not require an \u201caccept all\u201d tracking choice.<\/p>\n<\/div>\n

\n

1. Cookies and similar technologies<\/h2>\n

Cookies are small values stored by a site in your browser and sent with relevant later requests. localStorage and sessionStorage are different browser-storage mechanisms. Browser caching, history, downloaded files and server records are distinct; deleting one does not necessarily delete the others.<\/p>\n

This inventory describes the current My China Warehousing application reviewed on 6 October 2026. Names and lifetimes may vary with WordPress configuration and login choices. The stored expiry shown in your browser identifies the actual cookie on your device.<\/p>\n<\/section>\n

\n

2. Current public browsing and inquiry flow<\/h2>\n

The current theme does not intentionally set cookies for ordinary anonymous public-page browsing or persist public tool entries in localStorage or sessionStorage. WordPress core separately uses the emoji rendering-support cache listed below. There are no active WordPress plugins in the reviewed installation, and no visitor analytics, advertising pixels, session recording or embedded messaging widgets were identified in the public implementation.<\/p>\n

Contact links take you to WhatsApp or Telegram. New website inquiry submissions are disabled; the old inquiry endpoint redirects to the direct-contact page. The historical inquiry receipt cookie is not issued by that current flow. Old saved inquiry records are server records and remain a separate privacy matter.<\/p>\n

No optional tracker settings panel is provided because those tracking categories are not installed. This is a description of the reviewed configuration, not permission to introduce optional tracking later.<\/p>\n<\/section>\n

\n

3. WordPress functional cookie inventory<\/h2>\n
\n\n\n\n\n\n\n\n\n\n\n\n
WordPress cookies and browser storage by feature<\/caption>\n
Name \/ category<\/th>\nPurpose and when used<\/th>\nDefault lifetime \/ control<\/th>\n<\/tr>\n<\/thead>\n
wpEmojiSettingsSupports (sessionStorage)<\/td>\nWordPress stores a timestamp and emoji rendering-support results for the current browser tab. It contains no inquiry or contact fields and is not an advertising profile.<\/td>\nTab-scoped storage; normally cleared when the tab closes, subject to browser session restoration. The support test may be refreshed; it is not a timed deletion of business records.<\/td>\n<\/tr>\n
wordpress_test_cookie<\/td>\nFirst-party check of cookie support when visiting the login page; no inquiry text.<\/td>\nSession; cleared according to the browser session.<\/td>\n<\/tr>\n
wordpress_[hash], wordpress_sec_[hash], wordpress_logged_in_[hash]<\/td>\nFirst-party authentication for signed-in WordPress users. Exact names depend on installation and HTTPS.<\/td>\nNormally browser-session cookies, or up to 14 days with Remember Me; WordPress can use a short grace period. Logout invalidates the authentication session.<\/td>\n<\/tr>\n
wp-settings-[user_id], wp-settings-time-[user_id]<\/td>\nFirst-party administrative interface preferences for authenticated users.<\/td>\nNormally one year; removable in browser site-data settings.<\/td>\n<\/tr>\n
wp_lang<\/td>\nFirst-party login-screen language preference when that feature is used.<\/td>\nNormally session duration.<\/td>\n<\/tr>\n
wp-postpass_[hash]<\/td>\nFirst-party access to a password-protected post if that feature is used. It is not a public visitor advertising cookie.<\/td>\nNormally 10 days under WordPress defaults; configuration can change it.<\/td>\n<\/tr>\n
mcw_quote_receipt (historical)<\/td>\nPreviously issued a random receipt identifier after an accepted website inquiry. New submissions and issuance are disabled. The value did not contain the inquiry itself.<\/td>\nHistorical expiry: 15 minutes. Clearing it does not delete the saved inquiry.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

These are functional WordPress cookies or rendering storage, and a historical application cookie, not an assertion that every listed cookie is set on every visit. The current public pages do not offer a comment form or visitor registration flow. Staff authentication is separate from ordinary browsing.<\/p>\n<\/section>\n

\n

4. Tools, search, server logs and downloaded files<\/h2>\n

Shipment calculations run in the browser. If you choose to carry carton values to the contact page, those values are placed in the destination URL and may appear in server logs and browser history. Copying a result uses your clipboard on request. Neither action creates a saved business inquiry.<\/p>\n

Search and public resource requests may reach the site\u2019s server. Technical logs and historical database inquiries are not browser cookies. See the Privacy Policy<\/a> for their handling.<\/p>\n

Downloaded files, ordinary browser cache, autofill and history are controlled through your device and browser. Clearing a cookie does not delete a downloaded inventory file, clipboard contents or a previously shared chat attachment.<\/p>\n<\/section>\n

\n

5. External links and provider storage<\/h2>\n

The WhatsApp and Telegram contact buttons and locally hosted QR images are links, not embedded chat sessions. Viewing the QR image does not automatically send the team your inventory details.<\/p>\n

WordPress may also request fallback emoji images from s.w.org automatically when the browser cannot render an icon. That image request can reveal IP address, browser details and applicable request headers to the image provider. It is separate from an advertising pixel and from clicking a chat link. Opening a messaging, corporate, platform or carrier link visits another service, which may set its own cookies and collect technical information under its policies. This site\u2019s cookie controls cannot clear storage on those domains. No message is sent merely because you open the link.<\/p>\n<\/section>\n

\n

6. How to inspect, block or delete storage<\/h2>\n