In short: this website uses no cookies at all. The UPPU panel stores only the cookies it needs to work, the "Remember me" cookie when you ask for it, and preferences (language, theme, sidebar, inbox sound); UPPU sets no advertising, analytics or tracking cookies. On the three panel pages where you connect a Meta channel, Meta's SDK is loaded (section 2). Businesses' chat widget uses no cookies either; it keeps values such as a visitor key, messages not yet sent and pre-chat form answers in the visitor's browser (section 3).
1. The uppu.net website
This website uses no cookies. It writes nothing to your browser's storage (localStorage, sessionStorage). It loads no third-party content such as analytics, advertising, maps, video, social media plug-ins or external fonts; all files of the site come from uppu.net. The language is chosen only through the page address (Turkish pages at the root, English pages under /en/) and is not stored in your browser. That is why the site has no cookie consent banner.
The site's server sets no cookies either; our server settings remove cookie headers from its responses (last checked: 7 November 2026). If a cookie is ever needed for a technical reason, it will be listed on this page with its name, purpose and duration before it is used.
Pages you open through links on our site (app.uppu.net, for example) follow their own cookie rules; the panel is described below.
2. The UPPU panel (app.uppu.net)
The panel sets the session and CSRF cookies for every visitor who opens its pages (including the sign-in, sign-up and password reset pages); these are first-party cookies the service needs to work. Only for users who tick "Remember me" when signing in, it also sets the "Remember me" cookie, which is written only at this request. In addition, three functional cookies remember three preferences (language, theme and sidebar). The panel uses no advertising, analytics or tracking cookies.
| Name | Type | Purpose | Duration |
|---|---|---|---|
__Host-uppu-session | Essential, first-party; for every visitor; HttpOnly, Secure, encrypted | Keeping you signed in | 120 minutes after the last activity; closing the browser does not remove it before then |
XSRF-TOKEN | Essential, first-party; for every visitor; encrypted, readable by the page's code | Preventing cross-site request forgery (CSRF) | Same as the session |
remember_web_… | Optional, first-party; set only if you tick "Remember me" when signing in; encrypted | Recognising you without a new sign-in after your session expires or you close the browser; removed when you sign out in this browser | 400 days |
lang | Functional, first-party; written when a visitor who is not signed in opens a panel page whose address carries a language (?lang=): the language switch on the page, the sign-in and sign-up links on our English pages, the link in the panel's invitation email (the inviting company's language) and the link in the password reset email (the account's email language); HttpOnly; value tr or en | Showing the panel pages you open before signing in (sign-in, the second step of two-step sign-in, sign-up, password reset, invitation) in that language; ignored while you are signed in, when the language comes from your account's or your company's setting (or, if neither is set, the panel's default language) | 365 days |
appearance | Functional, first-party | Remembering the light, dark or system theme you chose | 365 days |
sidebar_state | Functional, first-party | Remembering whether the sidebar is open or closed | 7 days |
Legal ground: for the essential cookies (session and CSRF), KVKK Art. 5/2-c (conclusion and performance of a contract: using the panel) for the user who opens the company and accepts the Terms of Service, and Art. 5/2-f (legitimate interest: providing the panel) for users who join the team by invitation or through the company's email domain and for other visitors who open the panel's sign-in pages. For session security and preventing cross-site request forgery, Art. 5/2-ç (legal obligation: the data security measures in Art. 12 of the KVKK) and Art. 5/2-f (legitimate interest) also apply to everyone. The "Remember me" cookie is written only when you explicitly ask for this function by ticking the box on the sign-in form; its legal ground is the same as the session cookie's.
The functional cookies hold only the language code (tr or en), the theme or whether the sidebar is open or closed; they carry nothing that identifies you, such as your name, email address or account ID. The theme and sidebar cookies are written only when you make a choice in the panel. The language cookie is written when you open a panel page whose address carries a language: when you use the language switch on the page, click the sign-in or sign-up link on our English pages, or open an invitation or password reset link sent to you. Other than with the language switch, the cookie is written without a separate language choice from you and also stays for 365 days; you can change the language at any time with the language switch and delete the cookie in your browser. Our legal ground for the functional cookies is KVKK Art. 5/2-f (legitimate interest: remembering the language and appearance you chose). Deleting these cookies only resets your preferences; it does not stop you from using the panel.
The panel also keeps the following in your browser's storage; none of it is sent to the server, and its legal ground is the same as the functional cookies':
appearance(localStorage): your theme preference; it stays until you delete it.uppu:inbox:sound(localStorage): whether the inbox sound is on or off; it stays until you delete it.uppu.terms-banner:{company}:{version}:{deadline}(sessionStorage): remembers that you closed the banner about a new version of the Terms of Service in this session; it is removed when the browser tab closes.uppu:sidebar:groups(localStorage): whether menu groups are open or closed; only in the menu of UPPU platform administrators; it stays until you delete it.
Meta connection pages: when one of the three panel pages where you connect a WhatsApp, Messenger or Instagram channel is opened, the Facebook JavaScript SDK is loaded from connect.facebook.net so that the connect button can work. We place the SDK on these pages. Meta then receives your IP address and browser details, even if you do not press the button. Your browser sends no cookies to Meta when the SDK file is requested, and the SDK is initialised with its session-cookie option and automatic app-event logging turned off. When you open the Facebook Login window, Meta uses its own cookies on its own domain. The legal ground for this transfer is set out in our KVKK Privacy Notice; that it is a transfer abroad is stated in the transfers section of the same notice. This transfer is subject to Article 9 of the KVKK; its basis will be stated in the transfers section of our Privacy Policy once the legal review is complete. Meta's processing of this data for its own purposes is subject to Meta's privacy and cookie policies. The SDK is not loaded on any other panel page; however, if you move to another panel page in the same tab after opening one of these three pages, it stays loaded in the browser until you reload the page or close the tab.
3. The chat widget (on businesses' websites and through its full-page link)
The UPPU chat widget, whether added to a business's website or opened through its full-page link, uses no cookies. When added to a website, it runs on the business's website, but in a separate frame loaded from cdn.uppu.net. The values below stay in the visitor's browser, in that frame's own storage (the localStorage of the cdn.uppu.net domain; if unavailable, sessionStorage or memory only). The business's page and its scripts cannot reach this storage. {site key} is the channel key in the widget's installation code; each business's widget keeps its own values.
| Name | When it is written | Content and purpose | Lifetime |
|---|---|---|---|
uppu:v1:{site key} | When the widget first opens a session with UPPU, for example as the visitor sends their first message | A random visitor key that recognizes the visitor in the same browser, and the time it was written | Until the visitor or the browser deletes it. When the widget loads, a key older than a week is renewed; a key that has not been renewed for 400 days is not accepted: the visitor counts as new and the key is removed. |
uppu:v1:{site key}:outbox | When the visitor sends a message | Messages that have not reached UPPU yet: the message text, the visitor's name and the pre-chat form answers (email, phone) that go with the first message. The message is not lost if the page reloads or the tab closes. | Each message is removed once UPPU receives it or rejects it for good. Until then it waits and is sent when the widget loads again. |
uppu:v1:{site key}:prechat | Only if the business has turned on the pre-chat form, when the visitor fills it in | The form's name, email and phone answers and when they were given, so that the form is not asked again when the page reloads | Removed when the first message carrying the answers reaches UPPU or when UPPU rejects the answers. Answers older than 24 hours, and all answers once the business has turned the form off, are removed the next time the widget loads; if the widget never loads again in that browser, they stay until the visitor or the browser deletes them. |
uppu:v1:{site key}:lang | Only if the widget has a language picker, when the visitor chooses a language | The chosen language's code, to show the widget in that language the next time too | Until the visitor or the browser deletes it. It is ignored if the chosen language is no longer offered. |
uppu:probe | Each time the widget loads | A temporary value written and removed at once to check whether storage is available | Removed at once |
Full-page chat link: if the business has turned this link on, the chat opens on its own page at https://cdn.uppu.net/c/{site key} rather than in a frame on the business's website; the link can be shared, for example, in an email signature, a QR code, a social media profile or the business's mobile app. This page uses no cookies either; it keeps the values above, under the same names and for the same lifetimes, in the browser storage of the cdn.uppu.net domain. If the page is opened inside the business's mobile app, the values stay in the storage of that app's in-app browser (WebView); because the app controls that browser, it can reach this storage. The link to the business's privacy notice is shown on this page too, in the message box.
When the business's users preview the widget in the UPPU panel, the same values are kept with :preview after the site key (for example uppu:v1:{site key}:preview:outbox), only in sessionStorage (if unavailable, in memory), and are removed when the browser tab closes.
When the widget or the full-page chat is loaded, the visitor's IP address and browser details are written to the access logs of UPPU's servers, even if the widget is never opened. UPPU keeps these logs as data controller for its own security (KVKK Privacy Notice).
These values in browser storage are written because of the widget the business adds to its website or the full-page chat link it shares, and on the business's behalf; for these values UPPU is the business's data processor (Data Processing Annex E.2). As the data controller, and under clause 8.3 of the Terms of Service, the business mentions them in its own cookie and privacy notice, determines their legal ground and, where necessary, obtains the visitor's explicit consent. The visitor key is not limited to one session: it is renewed while the widget is used and stays valid for 400 days after its last renewal. The access logs, on the other hand, are UPPU's own processing as data controller; the business also mentions them in its own privacy notice and may link to UPPU's KVKK Privacy Notice.
4. API, webhooks and public pages
messaging.uppu.net and the webhook domains use no cookies, sessions or browser storage. The public help center pages on the panel's domain (app.uppu.net/help/…; only where a business has published its help center) use no cookies, sessions or browser storage either.
5. How to manage cookies
You can view, delete or block cookies in your browser settings. If you delete or block the panel's essential cookies, you are signed out and cannot use the panel. Deleting the functional cookies only resets your preferences. You can delete the values in the browser storage of the panel and the chat widget with your browser's setting for clearing history and site data. How to exercise your rights under Article 11 of KVKK is explained in our KVKK Privacy Notice.
6. Contact
For questions, write to kvkk@uppu.net. Details about your personal data are in our Privacy Policy and KVKK Privacy Notice.