Privacy in plain language
Trendsly uses the information needed to return a search, protect the service, understand what shoppers need, and remember choices you ask this browser to keep. It does not run third-party advertising or behavioural profiling scripts on these pages.
Privacy notice updated July 20, 2026
01
Search text is sent to Trendsly when you search. The page also places the text in the q part of the page URL so the search can be shared or reopened.
A shared search can therefore appear in browser history, bookmarks, messages, and a network provider's request records. Do not put private or sensitive information in a search.
02
An uploaded outfit image first makes a request-scoped detector pass through a loopback service. Detector regions, confidence scores, and signed request context stay transient. Your browser then crops the detected or manually selected region locally; only that chosen crop—or the whole image when you explicitly choose that fallback—is sent to the loopback search service.
Private temporary server files are removed when each request finishes, including when it fails. Product analytics do not store uploaded image bytes, image hashes, crop boxes, detector regions, confidence scores, or detector context. Images are not added to shared URLs or used to build a public profile. Avoid uploading an image you do not have the right to use.
03
Saved products, collections, watchlists, owned-item markers, and directory-vote choices are stored in this browser's local storage. Trendsly does not currently create a cloud account for them.
They remain until you remove them in Trendsly, clear this site's browser data, or use a different browser or device.
04
Cloudflare and the Trendsly reverse proxy process connection information such as an IP address, time, requested URL, response status, and timing to deliver and protect the site. Provider retention is governed by the configured account and provider terms.
Origin proxy logs may include a full requested URL—and therefore shared search text—plus a source or edge address, referrer, user agent, status, and timing. Retention follows the host's active rotation configuration; a stricter Trendsly-only rotation policy is prepared but is not represented here as active until its host-level installation is verified. The current search service does not intentionally log search text or image bytes.
05
Trendsly keeps a private 30-day record of product events such as searches, result counts, zero-result searches, filters, product opens, retailer clicks, fixed-choice relevance feedback, device class, and referring site.
A random short-lived browser session is hashed by Trendsly. The product-insight record does not store raw IP addresses, uploaded images, precise device fingerprints, or advertising identifiers. Search text is included so we can identify missing products, so do not put private information in a search.
06
Brand votes update an aggregate score. An IP-derived key is held briefly in memory to limit duplicate votes and excessive searches; it is not added to the stored vote record.
Brand suggestions are stored privately with the information you submit so the catalogue team can review them.
The public site does not need an account cookie. During a password-protected review, a signed, HTTP-only access cookie may be set for up to 24 hours.
07
When you open a retailer or brand website, your browser may identify https://trendsly.ca/ as the referring site. Trendsly does not send the full page address, your search text, or your filters in that referral. Evidence sources and Trendsly's social links do not receive a Trendsly referrer. Every external destination handles the request under its own privacy practices.
Contact Trendsly about a privacy question