WeDisplay · Legal
Cookie Policy
This Cookie Policy explains how EN6IA, operating as "WeDisplay" ("WeDisplay", "we", "us", or "our"), uses cookies and similar technologies on our marketing websites and dashboard (collectively, the "Service"), what each cookie does, and how you can manage your choices. It should be read together with our Privacy Policy, which explains more broadly how we handle personal information.
1. What Cookies Are
Cookies are small text files that a website stores on your browser or device. They let a site recognize your browser between visits and across pages — for example, to keep you signed in, or to remember a choice you made. Some cookies are deleted automatically when you close your browser ("session" cookies); others stay on your device for a set period ("persistent" cookies) until they expire or you delete them. We use only a small number of first-party cookies, described below, and do not use tracking pixels, browser fingerprinting, or third-party advertising cookies of our own.
2. The Cookies We Use
The table below lists every cookie WeDisplay itself sets. We do not set any other cookies beyond these.
| Name | Provider | Category | Purpose | Duration |
|---|---|---|---|---|
authjs.session-token( __Secure-authjs.session-token on HTTPS) | WeDisplay (first-party) | Strictly Necessary | Keeps you signed in after login | Session / up to 7 days |
wd-ref | WeDisplay (first-party) | Functional | Remembers the referral code from a ?ref= link so a referral is credited at sign-up | 90 days — set only if you grant Functional consent |
wd-consent | WeDisplay (first-party) | Strictly Necessary | Stores your cookie-consent choices | ~6 months |
wd-currency | WeDisplay (first-party) | Functional | Remembers the currency you chose to see prices in on our pricing page — display only; every plan is billed in US dollars | 1 year |
NEXT_LOCALE | WeDisplay (first-party) | Functional | Remembers which language you are viewing the site in | 1 year |
authjs.session-token (or, on an HTTPS connection, its cookie-prefixed variant __Secure-authjs.session-token) is set by our authentication system the moment you sign in, and is what keeps you logged in as you move between pages of the dashboard; without it, the Service would have to ask you to sign in again on every request. wd-ref is set only when you land on our site through a partner or referral link and have granted Functional consent — it exists purely so that the referral gets credited correctly if you later sign up, and it carries no information about you personally beyond the referral code itself. wd-consent records the choices you make in the cookie-preference control described in Section 5, so we don't ask you again on every visit; because it is what makes your preference stick, it is itself set regardless of your choice. wd-currency and NEXT_LOCALE hold nothing but a display preference: the currency you selected on our pricing page — where converted amounts are approximate and every plan is billed in US dollars — and the language the site is shown in, which is recorded when you choose a language, or when we show French by default to a visitor in Québec so that the choice is not made again on every visit. Neither identifies you, neither is shared with anyone, and deleting either simply returns the site to its defaults.
3. Cookie Categories
Our cookie-preference control (Section 5) groups cookies into four categories, defined below. These definitions exist so the consent tool is ready to describe any future cookie accurately — as of the effective date of this Policy, WeDisplay uses no Analytics or Marketing cookies of any kind. If that ever changes, we will update this Policy, the table in Section 2, and the preference control before any new cookie is set.
- Strictly Necessary. Cookies required for the Service to function — such as staying signed in and remembering your cookie-consent choice. These cannot be switched off because the Service cannot operate without them, and we do not ask for consent to set them.
- Functional. Cookies that enable optional convenience features, such as referral attribution. They are off unless you turn them on, with one narrow exception listed in the table in Section 2: the two cookies that do nothing but remember how you asked the site to be shown to you — your language and the currency prices are displayed in. Those carry a display preference and nothing else, and are set at the moment the preference is made so that the Service can be presented the way you asked for it.
- Analytics. Cookies that would help us understand how visitors use the Service (for example, which pages are viewed) so we can improve it. Not currently used.
- Marketing. Cookies that would support advertising or campaign measurement, such as tracking clicks from an ad to a conversion. Not currently used.
4. Third-Party Cookies
WeDisplay itself does not embed third-party analytics, advertising, or social-media cookies into our marketing site or dashboard. However, if a customer chooses to embed third-party content into a screen, layout, or page — for example a YouTube or Vimeo video, a Canva design, or a Power BI or Tableau dashboard — that content is loaded directly from the third-party provider's own servers, inside an embedded frame the provider controls. That provider may set its own cookies or use similar technologies in connection with that embed, governed by its own cookie and privacy policies, not this one. WeDisplay does not control, and is not responsible for, cookies set by third-party services that a customer chooses to embed. We encourage you to review the relevant provider's policy if you have questions about cookies set through an embedded item.
5. Managing Your Choices
You can change your cookie choices at any time using the "Cookie preferences" link in the footer of our site. It reopens the same consent selector shown on your first visit, where you can accept or reject Functional, Analytics, and Marketing cookies independently, or reject all optional cookies at once. Strictly Necessary cookies cannot be turned off through this control because the Service cannot function without them, as explained in Section 3.
You can also control or delete cookies through your browser's own settings — most browsers let you view, delete, and block cookies, either for all sites or for specific ones, and to be notified before a cookie is set. Blocking or deleting the authjs.session-token cookie will sign you out and prevent you from staying signed in. Because cookie controls vary by browser, consult your browser's help documentation for exact steps.
We do not currently detect a specific Global Privacy Control (GPC) or Do Not Track (DNT) browser signal. However, apart from the language and display-currency preferences described in Sections 2 and 3, Functional, Analytics, and Marketing cookies are off by default until you affirmatively opt in: WeDisplay sets no analytics, advertising, or tracking cookie of any kind for a visitor who has not consented — including visitors whose browser sends a GPC or DNT signal. You remain in full control of non-essential cookies through the "Cookie preferences" control described above, at any time.
6. Changes to This Policy
We may update this Cookie Policy from time to time — for example, if we introduce a new cookie or change how an existing one is used. If we make a material change, such as introducing Analytics or Marketing cookies where none exist today, we will update the effective date below, revise the table in Section 2, and, where required by law, seek your renewed consent before any new non-essential cookie is set. We encourage you to review this Policy periodically.
Questions about this document? Contact [email protected]. See all policies in the Legal Center.