Buyer and messaging privacy
How ApparelWin handles buyer correspondence, Instagram, Messenger, WhatsApp, email, and authorized LinkedIn company Page management, including data use, retention, and deletion requests.
Buyer information helps ApparelWin coordinate sample development, factory review, bulk production planning, quality checks, packaging, and shipment communication.
Project materials are used to understand the requested apparel style and should not be treated as a public catalog submission.
Messages you send us are used to answer your enquiry, prepare quotations, confirm specifications, and keep you updated on sampling, production, and shipping. We do not use them for advertising and we do not sell them.
Buyer correspondence and attachments from Instagram, Messenger, WhatsApp, and email are stored on servers and cloud file storage that we operate through Alibaba Cloud. We keep copies of files sent through those channels because platform file links can expire.
For buyer, order, and non-LinkedIn messaging records, we do not set a fixed deletion date. We keep them as needed for your account, production, after-sales service, and record-keeping obligations, and handle deletion requests as described below. LinkedIn API data has separate, shorter limits in the next section.
A Page administrator authorizes our application through LinkedIn. We use administrator identifiers, authorization credentials, approved permissions, Page identifiers, and public comments to manage authorized company Pages, publish content, and read and reply to comments. Access is limited to staff authorized for the relevant Page.
We do not use member or comment data obtained through LinkedIn APIs for sales leads, CRM enrichment, advertising, recruiting, cross-platform profiles, or exports. This data is excluded from our AI assistance and automatic translation features. These limits do not apply to original business materials independently supplied to us.
LinkedIn's rules limit other members' profile caching to 24 hours and member activity content, timestamps, and local derived translations to 48 hours. Our online application schedules expired-field cleanup and hides expired content. These limits also apply to other copies; offline storage and backups are not exceptions. Necessary IDs and URNs, authorization records, and content-free security or usage audit records may be retained only where permitted and needed for access control, deduplication, or accountability.
New LinkedIn comment threads are excluded from persistent browser message caches. Legacy copies are removed when identified during application use. A browser that cannot contact our service does not restore unclassified old threads.
For a LinkedIn data request, email [email protected] and include the company Page and relevant post or comment links. We verify the request and handle our local copies under LinkedIn data requirements. Do not send passwords, access tokens, or cookies. Removing our local data does not remove the original content from LinkedIn; disconnecting authorization stops future access but does not itself erase every local record.
