Skip to content
Try for free

Cookie policy. What your browser keeps.

This policy explains how the Postlip Metrics website (metrics.postlip.com), the panel (panel.metrics.postlip.com) and the Postlip Metrics web SDK running on our Customers’ websites, all operated by YGMR Danışmanlık Limited Şirketi, use cookies and browser storage. How personal data is processed in general is explained in the Privacy notice.

Version 2026-11-19 · Effective: 19 November 2026

Translation

This is an English translation for convenience. The Turkish text is the binding one; where the two differ, the Turkish text prevails.

1. Cookies and browser storage

A cookie is a small record a website writes to your browser, which your browser sends back to the website with later requests. Local storage (localStorage) stays in your browser until you delete it, session storage (sessionStorage) until you close the tab; both are read only by the pages of the website that wrote them and are never sent to the server by themselves.

Strictly necessary records are needed for the service to work and do not depend on your consent. Functional records only remember a choice of yours (language, appearance). Analytics and marketing records are used only on measured websites, according to the consent mode the website’s owner chose.

2. The website

The website writes no cookies and has no visitor measurement, advertising or third-party script. The language is chosen by the address (/ and /en); fonts come from the website’s own server.

NameTypePurposeLifetime
metrics.themeLocal storage, functionalRemembers your choice if you pick the Dark or System appearance; removed when you return to the default Light appearance.Until you change or delete it

3. The Postlip Metrics panel

The panel uses only the cookies it needs to work; there are no analytics or advertising cookies and no third-party measurement script.

NameTypePurposeLifetime
metrics_sessionCookie, strictly necessary (HttpOnly, SameSite=Lax, Secure over HTTPS)Keeps you signed in; during two-step verification it also carries the sign-in step.At most 14 days, extended while in use; deleted on sign-out
metrics_localeCookie, functionalRemembers the language you chose.1 year
postlip_viewCookie, functional (SameSite=Lax, Secure over HTTPS)Remembers which view (Ads or Metrics) a member who uses both products last worked in. Its value is only the word ads or metrics; it carries nothing about the person.1 year
metrics.theme, metrics.sidebarCollapsed, metrics.sidebar.groups, metrics.sidebar.studio, metrics.sidebar.pinned, metrics.releaseNotesSeen, metrics.tableColumns, metrics.sections, metrics.developerView, metrics.overview.systemStatusLocal storage, functionalAppearance, sidebar layout, pinned pages, table columns, open sections, the developer view preference and the last release note read.Until you delete it
metrics.webPushLocal storage, functionalThis device’s notification record, if you turned on browser notifications.Until you turn notifications off
postlip.ads.draft.<id>.stepLocal storage, functionalRemembers the step you were on while creating an ad.Until the ad is published or discarded, or you delete it
metrics.creative.brandNudge.<organization>.<app>Local storage, functionalRemembers that you dismissed the brand kit reminder with “Not now”.Until you delete it
postlip.ads.returnTo, postlip.ads.studioReturn, metrics.oauth.returnSession storage, strictly necessaryBrings you back to where you were in creating your ad after connecting an account or generating an image.Until the tab is closed or the return is complete

Protection against request forgery (CSRF) uses no separate cookie: the session cookie is not attached to other websites’ background requests (SameSite=Lax), and the panel refuses state-changing requests from other websites.

If the platform has turned on CAPTCHA for risky sign-ins, after repeated failed sign-in attempts the security verification provider’s widget loads on the sign-in page. The widget may use the provider’s own security cookies or browser storage; it does not load unless a check is asked for.

4. The Postlip Metrics web SDK (on measured websites)

Our Customers add the Postlip Metrics web SDK to their own websites. On these websites the website’s owner is the data controller: it chooses the consent mode, shows the cookie notice and the consent tool, and passes the visitor’s choice to the SDK. The SDK writes no cookies; it keeps its records in browser storage, under the website’s own address.

Consent modes (the website’s owner chooses one per source):

  • Consent required (the default): no persistent id exists until the visitor gives analytics consent; the anonymous id and the session live only in the tab’s session storage and are deleted when the tab closes. Interactions are not captured and click ids are not sent. The server joins the same day’s visits with a one-way hash computed with a daily salt that is deleted at the end of the day (cookieless counting).
  • Implied consent: analytics and marketing measurement are on until the visitor declines; declining removes the ids from local storage, and cookieless counting goes on.
  • No consent needed: only for internal apps where consent is not legally required; everything is on.
NameWhereWhat for
mtr_aid, mtr_uid, mtr_sLocal storage with analytics consent; session storage without itThe anonymous id, the website’s user id and the session.
mtr_aLocal storage with marketing consent; session storage without itSource and campaign details of the first and last touch. Click ids are kept only with marketing consent; without it they stay only in the page’s memory.
mtr_cLocal storageThe visitor’s analytics and marketing consent choice (a refusal is remembered too).
mtr_rLocal storage, only with analytics consentThe retry queue of messages that could not be sent while the connection was down.
mtr_t, mtr_l, mtr_cfgSession storageThe tab id, the page layouts sent in this session and a cache of the website’s measurement settings.
mtr_d, mtr_internalSession and local storageOnly if the website’s team adds ?metrics_debug=1 or ?metrics_internal=1 to the address: a test or internal traffic flag.

The SDK does not write the cookies of the ad and analytics tools running on the website; it only reads them: the ad platforms’ click cookies (_fbc, _fbp, li_fat_id, _ttp) are kept and sent only with marketing consent; the analytics tool’s cookies (_ga, _ga_…) are read only with analytics consent. Those tools write these cookies; the website’s own cookie policy covers them.

When the visitor withdraws analytics consent, the ids and the retry queue are removed from local storage and measurement goes on within the tab; when they withdraw marketing consent, the source details and click ids are removed. If the website’s owner chose so, the browser’s Global Privacy Control signal turns marketing consent off.

5. Managing your preferences

You can delete or block cookies and site data in your browser’s settings; if you block the panel’s session cookie, you cannot sign in to the panel. You can change your consent on a measured website through that website’s consent tool; send requests about your data on that website to its owner. Questions: destek@postlip.com; requests about your personal data: kvkk@ygmr.com.tr.

6. Changes to this policy

When this policy changes, the new version is published on this page; the top of the page shows the effective date and the version.