This annex is Annex 1 of the Terms of Service and is accepted together with the agreement, under the same version, when a company is created. The same text appears at the end of the Terms of Service; this page publishes the annex separately so that it can be read and printed on its own.
This annex sets out, under Article 12 of the Turkish Personal Data Protection Law No. 6698 ("KVKK"), the terms for processing in which the Customer is the data controller and UPPU the data processor. It is the document called the "data processing annex" in the box on the company creation screen (the box's binding Turkish text calls it "veri işleyen eki"). Terms not defined in this annex have the meaning given in the Agreement and in the KVKK.
E.1. Subject, duration and purpose
UPPU processes Customer Data for the term of the Agreement and until the deletion periods in clause E.12 of this annex expire, solely to provide the service to the Customer: receiving, storing and showing messages to Users; delivering the Customer's replies and templates; tracking delivery; applying Meta's and Telegram's messaging rules; if the Customer is in Türkiye and its Message Management System (İYS) account is connected in the panel, checking the İYS consent of the recipient's Türkiye (+90) number with the Customer's İYS account and on the Customer's behalf before a Marketing template is sent from the inbox; keeping contact records, Users' notes about people, contact fields and consent records; and passing data to the integrations defined by the Customer.
E.2. Data subjects and data categories
- Data subjects: people who write to the Customer through the channels or to whom the Customer sends messages; web chat visitors (including those who fill in the pre-chat form); people recorded by the Customer through the API or the panel's consent import with whom there has been no conversation yet; third parties whose details appear in shared content (for example people in contact cards and the other recipients of an email).
- Data categories: channel identifiers (WhatsApp BSUID and phone number, Messenger PSID, Instagram IGSID, Telegram user ID and, if the person shares their own number, phone number, the sender's email address on the email channel, web visitor ID); name and display name; answers to the pre-chat form on web chat (name, email address, phone number and first question); message contents; the subject and headers of emails (sender, reply-to address, message ID and thread references); media files (including email attachments); shared locations and contact cards; delivery, read and error details; conversation, tag and assignment details; notes written by Users about a person and the values of contact fields defined by the Customer; satisfaction survey answers; consent and withdrawal records (purpose, status, how the consent was obtained, the text the person agreed to, reference and time, including records entered in the panel or imported in bulk); raw copies of messages (with all fields sent by the channel, for example the person's username and language code on Telegram, and all headers of an email, including its recipients).
- Special categories: the Platform is not designed to process special categories of personal data. The database (including message contents, contact notes and contact fields), its redo and binary logs and its backups are encrypted at rest; the database's slow query and error logs, the queue store, application logs, media files and media backups are not separately encrypted at rest, and backups are not kept off the server. If people send such data, or Users write such data in notes or contact fields, the Customer is responsible for the existence of a legal basis. If the Customer is going to process special categories of data, it is obliged to take the adequate measures determined by the Board under Article 6(4) of the KVKK; it assesses in advance whether the measures in this clause and clause E.6 meet them, and takes any measure the Platform does not provide itself.
- Identity number protection: UPPU may, in agreement with the Customer, enable identity number protection for a company; it is off by default. While it is enabled, Turkish identity numbers recognised in messages are shown masked to every role in the inbox. Only Users with the owner or admin role can reveal a number, message by message and by choosing a reason from a list; each reveal is recorded in the audit log. When the period set by UPPU has passed since the message was stored (at least 30 days; 90 days on the date of this annex), the number is masked permanently and the raw copy of the message is deleted. Recognition relies on the number's format and may miss some ways of writing it. The protection is not encryption and does not recognise special categories of data such as health information; no mask is applied to API responses, webhook payloads or the export of a person's data.
- Server access logs: the IP address and browser details of visitors to pages where the chat widget is loaded are written to the access logs of UPPU's servers and to the security log archive of these logs, even if the widget is never opened. UPPU keeps these records as data controller for its own security (retention periods: KVKK Privacy Notice); the Customer mentions this in its own privacy notice.
E.3. Processing on instructions
UPPU processes Customer Data only on the Customer's instructions. The Agreement, the Customer's settings in the panel (channels, retention period, webhook and API settings) and its written requests are the Customer's instructions. If UPPU considers an instruction to be unlawful, it informs the Customer and may decline to carry it out. If other processing is required by a legal obligation, the Customer is informed in advance unless the law prohibits this.
E.4. Deletion requests made directly by people
Meta's and Telegram's terms require data obtained through these channels to be deleted at the request of the person concerned or of the channel provider. When a deletion request reaches UPPU directly, UPPU reasonably verifies the requester's identity and then forwards the request to the Customer, together with the information needed to find the person (a phone number, or a channel and the person's ID on that channel), within 3 business days at the latest. The Customer finds the person with this information on the "Personal data requests" page of the panel and, within 10 business days, either fulfills the request with the erasure tool or notifies UPPU, with reasons, of a statutory retention obligation or another legal obstacle. UPPU tells the person the outcome and any reasons; the parties observe these periods so that the person can be answered within 30 days at the latest. If the Customer's API access is enabled, the erasure is reported to the Customer's systems with the contact.erased event. Individual erasure is not possible in a closed company; its data is deleted all at once when the period in clause E.12 expires.
E.5. Confidentiality and personnel
UPPU binds its employees and assistants who may access Customer Data to confidentiality and limits access to those who need it for their work. This obligation continues after the end of their duties and of the Agreement (KVKK Art. 12/4). Being a platform administrator does not give access to a company's panel or conversations. To investigate a technical problem, such as an incoming message that could not be processed, authorised UPPU staff may view raw copies of messages received by the Platform. In the panel, this is done only with a platform administrator account that has two-factor authentication enabled and after a written reason is entered; Turkish identity numbers recognised in the message are shown masked, and the viewing is recorded in the audit log of every company to which the copy can be attributed. Viewing through server administration tools is also recorded in the audit log. The technical access of authorised staff who operate the servers and the database is used only for maintenance, troubleshooting and incident response.
E.6. Technical and organizational measures
To ensure an appropriate level of security under Article 12 of the KVKK, UPPU applies at least the following measures:
- keeping data in UPPU's data center in Istanbul, on servers managed by UPPU;
- isolating each company's data with a mandatory company filter; tying permissions to roles and explicit rights; showing phone numbers masked to agents;
- TLS on all connections; encrypting Meta access tokens, Telegram bot tokens, WhatsApp PINs, İYS connection passwords, webhook addresses and secrets with AES-256-GCM using a rotatable key ring separate from the application's general encryption key (APP_KEY), with each encrypted value bound to its company and record;
- storing only the SHA-256 digest of API keys and of Telegram webhook secrets; scope, channel, IP range and expiry limits on API keys;
- signed webhooks and checks that prevent target addresses from pointing into internal networks;
- two-factor authentication and passkeys; mandatory two-factor authentication for platform administrators; limits on login attempts; password confirmation for sensitive actions;
- logging of data changes and security events in an audit log; passwords, codes and tokens are never logged;
- a firewall, mandatory access control (SELinux), administrative access by key only and from restricted addresses, and automatic security updates on the servers;
- nightly backups of the database and media files kept for 7 days, with a restore of the database backup tested every month;
- automatic nightly deletion of data whose retention period has expired, documented by destruction records.
UPPU may update these measures in line with technological developments; an update may not lower the level of protection.
E.7. Sub-processors
UPPU processes Customer Data in its own data center and does not use a cloud or hosting provider to host this data. Service emails (such as verification, password reset, invitation, alert and billing emails) are sent through mail.uppu.net; these emails do not contain people's names or message contents. UPPU informs the Customer, by writing to the company owner's email address registered in the panel (Terms, clause 17), at least 30 days before using a new sub-processor that will access Customer Data; if the Customer objects on justified grounds, it may terminate the Agreement.
E.8. Meta and Telegram channels and transfers abroad
UPPU stores Customer Data in Türkiye. On the WhatsApp, Messenger and Instagram channels connected by the Customer, messages pass through Meta's systems abroad because that is how these channels work. The Customer connects these channels with its own Meta account and by accepting Meta's terms directly; Meta processes this data under the terms between the Customer and Meta and is not a sub-processor of UPPU. For transfers through these channels, informing people and determining the transfer basis are the responsibility of the Customer as data controller. Because Article 9 of the KVKK also applies to data processors, UPPU's own obligations under that article as data processor are reserved. For transfers through the WhatsApp channel, determining the transfer basis and making any notifications to the Personal Data Protection Authority are the responsibility of the Customer as the exporting data controller. UPPU provides the necessary information on these matters on the Customer's request.
The Customer connects the Telegram channel by entering in the Platform the token of a bot it created with its own Telegram account, accepting Telegram's terms for bot developers directly; UPPU enables the right to use the Telegram channel for the company, through its package or a company-specific setting. UPPU runs the bot only with this token and on the Customer's behalf. Messages on the Telegram channel pass through Telegram's systems abroad because that is how Telegram works. Telegram processes this data under the terms between the Customer and Telegram and is not a sub-processor of UPPU. The bot's privacy policy, and, for transfers through this channel, informing people and determining the transfer basis are the responsibility of the Customer as data controller; UPPU's own obligations under Article 9 of the KVKK as data processor are reserved. Telegram's terms for bot developers also require user data to be kept encrypted at rest; as stated in clause E.2, message contents are kept encrypted at rest in UPPU's database, while media files are not separately encrypted. As the bot's developer, the Customer assesses compliance with these terms before connecting the bot.
E.9. Assistance with data subject requests
On the panel's "Personal data requests" page, the Customer can find a person without the inbox, by phone number or by a channel and the person's ID on that channel. The panel lets the Customer download a person's data in JSON format and the person's media files separately, and erase the person permanently; if the Customer's API access is enabled, the erasure is reported to the Customer's systems with the contact.erased webhook event. UPPU forwards requests it receives directly to the Customer within 3 business days at the latest and reasonably assists the Customer in answering them. Clause E.4 applies to deletion requests.
E.10. Data breach notification
When UPPU becomes aware of a data breach affecting Customer Data, it informs the Customer in writing without undue delay and within 48 hours at the latest. If some information is not yet known, the notification is not delayed for it; missing information is supplied without undue delay as it becomes known. The notification includes, as far as then known, the nature of the breach and when it was discovered, the categories of data and data subjects affected and the approximate number of people, the likely consequences, the measures taken or proposed and UPPU's contact person. UPPU assists the Customer in meeting its obligation to notify the Personal Data Protection Board and the people concerned.
E.11. Information and audits
UPPU answers the Customer's reasonable requests for information and documents showing compliance with this annex. With reasonable prior notice, subject to confidentiality and at its own cost, the Customer may carry out an audit, or have one carried out by an independent auditor, at most once a year. An audit after a data breach affecting Customer Data, or at the request of the Board or another competent authority, does not count towards this limit; in these cases too, UPPU may first respond with information and documents. Audits are conducted so as not to endanger the confidentiality of other customers' data or the security of the Platform.
E.12. Retention, return and deletion
- Conversations and messages are deleted automatically at the end of the period chosen by the Customer, counted from the conversation's last activity (30 to 730 days; 365 days if not chosen); incoming media files at most 90 days after receipt (earlier, together with the conversation, if it is deleted first); raw copies of messages after 90 days (or the Customer's retention period or, where it is enabled for the company, the identity number protection period in clause E.2, if shorter). The periods for other records (such as webhook events, the API log, uploaded media and records of messages that could not be processed) are in the retention table of the Privacy Policy. Those periods in that table that relate to Customer Data form part of this annex; UPPU may extend them only under clause 16 of the Agreement and with a new version, and may shorten them after notifying the Customer in advance.
- Before the Agreement ends, the Customer can export people's data from the panel, one person at a time, as JSON; if API access is enabled, it can retrieve messages and media through API v1. For a bulk export the Customer writes to UPPU, and UPPU provides it in JSON format within 30 days.
- The Customer Data of a closed company is permanently deleted, all at once, 365 days after closure; individual or earlier deletion is not possible during this period. The Customer can erase people's data in the panel before closing the company.
- The company record (name), the billing name and tax number of a legal entity or a buyer abroad, the accepted contract version and setup steps are kept for 10 years (Tax Procedure Law No. 213 and Turkish Commercial Code No. 6102), and audit logs for at least 3 years and at most 10 years; these records are not deleted when a closed company is purged and are destroyed when their period has passed. This purge deletes the tax office, billing address and billing email from the billing details and, for sole proprietors, also the Turkish ID number and name; the receipts of bank transfer notices are deleted too.
- Deleted data remains for at most 7 more days in database and media backups. It is also kept in the database change logs for deletion after 7 days; however, because a log file can only be deleted once it has been closed, this period may be exceeded.
- Each automatic deletion is documented by a destruction record containing only counts. On request, the deletion is confirmed to the Customer in writing.
E.13. Obligations arising from Meta
For data obtained through Meta channels, UPPU also: processes the data only on the Customer's behalf and on its instructions; keeps each customer's data separate; contractually prohibits the Customer from processing this data in breach of Meta's terms (clause 7.2); cuts off access at Meta's request; deletes the access tokens when the Customer removes UPPU's partner access from its WhatsApp Business account, and for Facebook Page and Instagram channels deletes the stored token when the channel is disconnected or when the company's data is purged; and does not use the data for profiling, enrichment or training AI models.
E.14. Obligations arising from Telegram
For data obtained through the Telegram channel, UPPU also: processes the data only on the Customer's behalf and on its instructions; keeps each customer's data separate; handles deletion requests from the person or from Telegram under clause E.4; deletes the bot's token when the Customer disconnects the bot; and does not use the data for profiling, enrichment or training AI models. The conversation history of a disconnected bot is deleted under the periods in clause E.12. If a breach affecting Customer Data also covers data of the Telegram channel, UPPU states this separately in the notification under clause E.10; the notice to users required by Telegram's terms is given by the Customer, with UPPU's assistance.
E.15. Liability and term
The parties' liability under this annex is subject to clause 14 of the Agreement; joint responsibility for data security measures under Article 12(2) of the KVKK is reserved. This annex remains in force after the Agreement ends until the Customer Data has been deleted.