Teisinė informacija
Cookie Policy
Atnaujinta: 2026-08-13
Wetapoint teisiniai dokumentai skelbiami tik anglų kalba. Tekstas anglų kalba yra įpareigojanti versija.
This Cookie Policy explains how Wetapoint uses cookies and similar client-side storage on our website and web application. It supplements the Privacy Policy.
1. What are cookies and local storage?
A cookie is a small text file a website places on your device. Local storage (localStorage and sessionStorage) is a browser API that lets a website store data on your device without sending it to the server on every request. We use both to operate the Service.
2. The two categories we use
We group client-side storage into two categories: strictly necessary, which is required to deliver the site and is exempt from prior consent, and advertising, which is set only if you opt in.
3. Your choices
On your first visit to wetapoint.com a consent banner asks you to accept or reject non-essential cookies. Rejecting is as easy as accepting, and rejecting is what happens if you make no choice — advertising cookies stay off until you actively turn them on.
You can change or withdraw your choice at any time through the Cookie settings link in the site footer. Withdrawing consent takes effect immediately: we signal the withdrawal to Google, delete the Google cookies reachable from our domain, and reload the page so the Google tag is no longer present.
We implement Google Consent Mode v2 in its “basic” form. The Google tag is not loaded at all — no script, no cookie, no request to Google — until you consent. When you do, the four consent signals (ad_storage, ad_user_data, ad_personalization, analytics_storage) are set to granted before the tag fires; when you withdraw, they are set to denied.
4. Strictly necessary cookies
| Name | Provider | Purpose | Duration |
|---|---|---|---|
| wp_session | Wetapoint | HttpOnly cookie identifying your signed-in browser session in the web application. Set by the server, not readable by JavaScript. | 15 minutes; renewed on sign-in and token refresh. |
5. Advertising cookies (Google Ads)
We advertise Wetapoint through Google Ads. If — and only if — you accept advertising cookies, we load the Google tag (gtag.js) for our Google Ads account, which measures whether a visit that came from one of our ads led to a sign-up, and allows Google to show you our ads again on other sites (remarketing). The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.
| Name | Provider | Purpose | Duration |
|---|---|---|---|
| _gcl_au | Google Ireland Limited | Conversion linker. Stores an ad click identifier so a later sign-up can be attributed to the ad that brought you here. | 90 days |
| _gcl_aw, _gcl_dc, _gcl_gb | Google Ireland Limited | Conversion linker cookies written when you arrive from a Google Ads, Display, or in-app ad click; they carry the click identifier for conversion measurement. | 90 days |
| wp_gclid, wp_gbraid, wp_wbraid | Wetapoint | Google Ads click attribution. Stores the click identifier from the ad you arrived through so that, if you later create an account, we can report that one sign-up back to Google Ads as a conversion. Written by us, not by Google, and only after you opt in. | 90 days |
The wp_ cookies are ours. They hold nothing but the click identifier Google itself put in the ad link, and they exist so the sign-up conversion can be reported from our server rather than from your browser. They are deleted the moment you withdraw consent.
These are first-party cookies on wetapoint.com. Once the Google tag is loaded, Google may additionally set or read its own third-party cookies on google.com and doubleclick.net (for example NID and IDE) for remarketing and fraud prevention. Those cookies are controlled by Google under its Privacy Policy and advertising terms; you can also manage them in Google My Ad Center. Nothing in this section applies until you opt in, and none of it runs in the signed-in web application.
6. Local storage
The web application stores authentication state (access and refresh tokens), UI preferences (panel widths, theme, map viewport, radio settings), and transient session state in your browser's localStorage and sessionStorage. This data never leaves your device except when explicitly sent as part of API requests (for example, the authentication token in request headers). The marketing website at wetapoint.com stores only your theme preference and your cookie-consent choices in localStorage — a record of whether you accepted advertising cookies and when.
7. Analytics
We do not use product analytics cookies or third-party analytics scripts, and we do not run analytics inside the signed-in web application. The only non-essential cookies we set are the Google Ads cookies described in section 5, and only with your consent.
8. Third-party embeds
Some pages embed third-party components (Stripe for payments, Mapbox for maps) that may set their own cookies or use their own client-side storage, governed by those providers' privacy policies.
9. Managing stored data
Beyond the Cookie settings link described in section 3, you can view and delete cookies and local storage in your browser's developer tools or settings. Clearing essential storage will sign you out. Clearing functional storage will reset your UI preferences to defaults and will make the consent banner appear again on your next visit.
10. Changes
We may update this policy as we add or remove client-side storage, or as the law changes. The date at the top reflects the most recent revision.