Skip to content
Try for free

Privacy notice. What we process and why.

As YGMR Danışmanlık Limited Şirketi (“Postlip Metrics”, “we”), under Article 10 of the Turkish Personal Data Protection Law No. 6698 (“KVKK”) and the Communiqué on the Procedures and Principles of the Obligation to Inform, we tell you about the personal data we process through the Postlip Metrics website (metrics.postlip.com), panel (panel.metrics.postlip.com), APIs and SDKs (together the “Service”).

Version 2026-11-10 · Effective: 10 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. Data controller

  • Company: YGMR Danışmanlık Limited Şirketi
  • Address: Yeşilova Mah. 1. Değer Sk. No:28 İç Kapı No:3 Küçükçekmece/İstanbul
  • MERSİS number: 0953096784700001
  • Trade registry: İstanbul Ticaret Odası, registry no. 1155924
  • Tax office and number: Küçükçekmece Vergi Dairesi / 9530967847
  • Phone: 0850 346 69 51 (weekdays 09:00–18:00, Turkey time)
  • E-mail: destek@postlip.com
  • Personal data requests (KVKK): kvkk@ygmr.com.tr

2. Data we control and data we process for others

Postlip Metrics is a measurement and marketing service for companies that want to measure the traffic, behaviour, conversions and marketing of their products (the “Customer”). For personal data we act in two separate capacities:

  • As data controller: data about the visitors of the website, the people who write to us or call us, panel users (the Customer’s employees and representatives it invites to the panel) and the Customers’ contract and billing contacts. Most of this notice is about this data.
  • As data processor: the measurement data a Customer sends to the Service from its own website, app and server, the contacts it adds to Mailing & SMS and the data coming from the ad, analytics and social media accounts it connects. The Customer is the data controller of this data; we process it only on the Customer’s behalf, on its instructions and to provide the Service (KVKK Art. 3, Art. 12). This relationship is governed by the Data processing agreement, an annex to the terms of service.

If you use a website or app measured with Postlip Metrics, contact the owner of that website or app for information and requests about that data. We pass any such request that reaches us to the Customer concerned without delay.

3. The personal data we process

Whose dataCategories of dataHow it is collected
Website visitorTransaction security: IP address and browser details, only to deliver the page to you and to apply the rate limit, transiently. No access log is kept; the website has no visitor measurement, no advertising and no third-party script.Automatically, when you visit the website.
Someone who writes to us or calls usIdentity and contact: name, e-mail address, phone number and organisation if given. Request: the content of your message or call.E-mail and phone.
Panel userIdentity and contact: name, e-mail address. Account: organization memberships, role and app scope, language preference, notification settings, time of last sign-in. Security: an irreversible hash of the password; two-step verification details (the authenticator app’s secret encrypted, only keyed hashes of e-mail codes and recovery codes); sessions (shortened browser details and a keyed hash of the IP address); failed sign-in counters. Records of actions: the audit log of what you do in the panel (action, time, value before and after, a hash of the IP address and browser details). If you turn on browser notifications, the device’s push subscription (push address, encryption keys, browser and operating system name).The invitation, setting up the account and using the Service.
Customer’s representativeIdentity and contact; contract, order and billing details (company name, tax office and number, address, invoice and payment records).Offer, contract and billing.

The measurement data, contacts, content and files you view and manage in the panel on the Customer’s behalf are the Customer’s data; for them the section “Data we process on the Customer’s behalf” below applies.

4. Purposes and legal grounds

PurposeLegal ground (KVKK Art. 5)
Opening accounts by invitation, signing users in, applying roles and permissions; providing the Service.Formation and performance of a contract (Art. 5(2)(c)).
Notices the Service needs: invitations, two-step verification codes, password reset and security e-mails, plan usage and support access notices, the alert and report e-mails you set up.Performance of a contract (Art. 5(2)(c)).
Information security: preventing unauthorised access and abuse (rate limits, account lockout, CAPTCHA on risky sign-ins, two-step verification, the audit log).Legal obligation (Art. 5(2)(ç); KVKK Art. 12) and legitimate interest (Art. 5(2)(f)).
Answering you when you write or call, preparing offers and giving support.Directly related to forming a contract (Art. 5(2)(c)) and legitimate interest (Art. 5(2)(f)).
Invoices, commercial books and records; requests of the authorities.Expressly provided for by law and legal obligation (Art. 5(2)(a), Art. 5(2)(ç)).
Protecting our rights in a dispute.Establishing, exercising or protecting a right (Art. 5(2)(e)).

We do not send you commercial electronic messages (marketing e-mails or SMS); notices about the Service are not commercial messages. We do no processing for our own purposes that relies on explicit consent.

5. Data we process on the Customer’s behalf

As data processor, within the Customer’s settings and instructions, we process the following:

  • Measurement data. The web SDK on the Customer’s website, its mobile app or its server sends messages to the Service: the event’s name and time, the page address, title and referrer, the properties the Customer defined in its event schema, screen, language and time zone, source and campaign details, sessions and interactions (clicks, scrolls, page layout, errors). Identifiers are pseudonymous: a randomly generated anonymous id and the Customer’s own user and account ids. The web SDK does not read the values of form fields; it strips values that look like e-mail addresses or phone numbers and sensitive query parameters from addresses.
  • IP address and browser details. During ingestion they are used only to find the country and city, the device, operating system and browser, and to tell bot traffic and the Customer’s internal traffic apart; then they are dropped: they are not stored with the event, the session or the person, in logs or in the audit log. The only exception is conversion forwarding to ad platforms, described below. Country and city come from the DB-IP IP geolocation database on our own server (CC BY 4.0, db-ip.com); the IP address is not sent anywhere for this.
  • Cookieless counting. In the consent-required mode no persistent id is created for a visitor who has not given analytics consent. To join the same day’s visits, a one-way hash is computed from the IP address, browser details and app id with a random salt for that day, and stored instead of the anonymous id. The salt is deleted at the end of the day; that day’s hash can never be computed again, and the next day the visitor counts as new.
  • Personal data screening. Each property in the event schema has a personal data class and an action: as the Customer chooses, the value is kept, hashed with a key, dropped, or the message is refused. A message with an e-mail address, phone number, Turkish identity number, IBAN or card number in an undefined field is refused. Click and ad ids are exempt from this screening.
  • Identity details and contacts. The e-mail, phone, first name, last name and address a Customer sends with an identify call are not stored with the event; they are written only to the Customer’s Mailing & SMS contact record. Contacts’ identity and contact details such as name, e-mail, phone, address and notes are kept encrypted; company, job title, city, country and tags are kept unencrypted for filtering and search; search and de-duplication use keyed hashes. Contacts’ e-mail and SMS permissions and their proof, sends and delivery, open and click records are kept; no IP address is stored on opens and clicks.
  • Leads, content and connected accounts. Lead inbox records (event, source and campaign details, notes; contact fields are not stored), blog posts and author details, files in the media library, and the campaign, spend and post data read from the ad, analytics and social media accounts the Customer connects.

The Customer chooses the retention of measurement data per app (by default: events and sessions 25 months, interactions 3 months); data past it is deleted every day. The Customer can have all of a person’s data in an app erased with a deletion request filed in the panel or through the Management API.

6. Transfers of personal data

  • To the suppliers whose services we use to run the Service, as data processors and only as far as needed: to the e-mail delivery provider (EU/US), the recipient’s e-mail address and the message content of invitations, verification codes, password resets, security, alert and report e-mails. The Service’s servers are in data centres in Turkey; database backups are taken on these servers too.
  • If the platform has turned on CAPTCHA for risky sign-ins, after repeated failed sign-in attempts the security verification provider’s (US) widget runs on the sign-in page, and the provider processes your browser’s details for the check. We do not send your IP address to this provider.
  • If you turn on browser notifications, they are delivered end-to-end encrypted through your browser’s own push service; that service cannot read their content.
  • To public authorities and courts empowered by law, when they ask, within a legal obligation.
  • To our legal, accounting and independent audit advisers, as far as needed and under confidentiality.
  • To the organization you are a member of: your role, your last sign-in, whether two-step verification is on and what you do in the organization appear in its member list and audit log.

Transfers on the Customer’s behalf. The data we process on the Customer’s behalf is transferred only on the Customer’s instructions, to the recipients the Customer chooses: the ad, analytics and social media platforms it connects, the e-mail and SMS providers it connects for Mailing & SMS and the Message Management System (İYS), and the webhooks and alert channels it sets up.

Conversion forwarding to ad platforms. If the Customer turns on conversion forwarding to an ad platform it connected, only the conversion events of visitors who gave marketing consent (or that come from a source the Customer marked as not needing consent) are sent to that platform. As far as the platform uses them, it receives: the event’s name, time, value and products, the page address, click and browser ids; the user id and the e-mail, phone, first name, last name, city, postal code and country of the Mailing & SMS record only as SHA-256 hashes. Platforms that ask for them also receive the visitor’s IP address and browser details; these two are kept encrypted for this purpose only until they are sent, are written to no event, person or log, and are deleted when delivery succeeds or finally fails, in any case within 7 days. Nothing is sent to ad platforms for a visitor without marketing consent. If the Customer syncs a segment to a connected ad account as an audience, only the hashed match keys of people with marketing consent are sent.

Transfers abroad. The providers of the e-mail delivery and security verification services are established abroad. The data these services need (the e-mail address and the message content; the browser details of the sign-in check) is transferred abroad under KVKK Art. 9, within the standard contractual clauses announced by the Board and the related safeguards. Most ad, analytics and social media platforms are abroad too; for transfers to them on the Customer’s instructions, the Customer as data controller provides the legal basis under KVKK Art. 9 (the data subject’s explicit consent or the Customer’s standard contract with the platform) and informs the visitors.

7. Cookies

The website writes no cookies and has no visitor measurement, advertising or third-party script. The panel uses only the strictly necessary session cookie and a cookie that remembers your language; there are no analytics or advertising cookies. Their names and lifetimes, and what the Postlip Metrics web SDK stores in the browser on measured websites, are in the Cookie policy.

8. Retention periods

  • Panel account: while your account is open. When you ask for your account to be closed, or when the Customer’s contract ends, your account data is erased, except records the law requires us to keep.
  • Session records and the audit log: for security and accountability, while the organization’s contract lasts; when it ends they are erased with the organization’s other data. Even if your account is closed, what you did in an organization stays in its audit log.
  • E-mail verification codes are valid for 5 minutes and can be used once; only keyed hashes of the codes are kept.
  • E-mails you send us and call notes: 1 year after your request is settled; correspondence that leads to a contract is kept with the contract records.
  • Contract, order and invoice records: while the contract lasts, then for the periods the law sets (e.g. TTK Art. 82 for commercial books and records, VUK Art. 253 for tax records).
  • Data past its period is erased, destroyed or anonymised. Erasure requests are carried out within 30 days at the latest. Database backups rotate; erased data leaves the backups within 35 days at the latest.

9. Security of the data

  • Each organization’s data is separated from the others in the database by row-level security rules; the parts of the Service connect with separate database roles, each with only the rights it needs.
  • Connections are encrypted with TLS. Connection tokens, provider passwords, signing keys, two-step verification secrets and the identity details of Mailing & SMS contacts are kept encrypted with AES-256-GCM; passwords, write keys and API keys are stored only as irreversible hashes.
  • Panel sign-in is protected by two-step verification, which the Customer can make mandatory in its organization; sign-ins are rate-limited, and after repeated failed attempts the account is locked for a while.
  • Every change is written to the audit log. The platform team’s support access needs a reason, lasts at most 24 hours and is read-only; it shows no measurement data, contacts or e-mail addresses, is written to the audit log and is e-mailed to the organization’s owners.
  • Application logs never contain request bodies, personal data or IP addresses; the servers keep no access log.
  • If a personal data breach occurs, it is notified to the Personal Data Protection Board within 72 hours of our learning of it at the latest, and to the people affected as soon as possible. A breach that affects data we process on a Customer’s behalf is also notified to the Customer.

10. Your rights

Under KVKK Art. 11 you have the right, regarding your personal data, to:

  • learn whether it is processed;
  • ask for information about it if it is processed;
  • learn the purpose of the processing and whether it is used for that purpose;
  • know the third parties in Turkey or abroad to whom it is transferred;
  • ask for it to be corrected if it is incomplete or wrong;
  • ask for it to be erased or destroyed under the conditions of KVKK Art. 7;
  • ask for the correction, erasure or destruction to be notified to the third parties it was transferred to;
  • object to a result against you that comes solely from analysis by automated systems;
  • claim compensation if you suffer damage from unlawful processing.

11. Making a request

Under the Communiqué on the Procedures and Principles of Application to the Data Controller, send your request in writing to Yeşilova Mah. 1. Değer Sk. No:28 İç Kapı No:3 Küçükçekmece/İstanbul, or from the e-mail address you gave us before and that is registered with us, to kvkk@ygmr.com.tr.

Your request is settled free of charge as soon as possible according to its nature, within 30 days at the latest (KVKK Art. 13); if the action costs extra, the fee in the Board’s tariff may be charged. If your request is refused, the answer is insufficient or it is not answered in time, you can complain to the Personal Data Protection Board (KVKK Art. 14).

Your request should include:

  • your name and surname, and your signature on a written request;
  • your Turkish identity number (for foreigners, nationality and passport or identity number);
  • your residential or business address for notices;
  • an e-mail address, phone or fax number for notices, if any;
  • the subject of your request and any supporting documents.

As a user of a website or app measured with Postlip Metrics, send your request to the owner of that website or app; if it reaches us, we pass it on without delay.

12. Changes to this notice

When this notice changes, the new version is published on this page; the top of the page shows the effective date and the version. We also e-mail organization owners about a material change.