These terms govern the service relationship between Alone AI Teknoloji Ltd. Şti. and a business using the UPPU platform. Annex 1, the Data Processing Annex (the company creation screen shows it as the "data processing annex"; its binding Turkish text calls it the "veri işleyen eki"), at the end of this page is an integral part of the agreement and is accepted together with it when a company is created.
1. Parties and acceptance
1.1. These Terms of Service (the "Agreement") are made between Alone AI Teknoloji Ltd. Şti., with its registered office at Cumhuriyet Mah. Kartal Cad. Kalay Plaza No:65/1-2, Kartal / İstanbul, Türkiye and MERSIS number 0055220317400001 ("UPPU"), and the legal entity, trader, tradesperson, self-employed professional or public authority or body that creates a company on the UPPU platform (the "Customer").
1.2. The Agreement is concluded when the box "Hizmet sözleşmesini ve veri işleyen ekini kabul ediyorum" ("I accept the service agreement and its data processing annex.") is ticked on the company creation screen. The annex named in the box is Annex 1, the Data Processing Annex, on this page. The person accepting declares that they are authorized to represent and bind the Customer. The accepted version and the time of acceptance are recorded on the company.
1.3. UPPU is intended only for businesses and self-employed professionals acting for commercial or professional purposes and for public authorities and bodies acting within their public duties; the service is not offered to consumers within the meaning of the Consumer Protection Law No. 6502. The Customer confirms that it uses the service for its commercial, professional or public activity.
1.4. If the parties have signed a separate quote, order form or contract, that document prevails where it conflicts with this Agreement.
2. Definitions
- Platform
- UPPU's panel at app.uppu.net, the chat widget, the customer API (API v1), webhooks (webhook v1), the help center pages published by the Customer and the infrastructure that runs them.
- Channel
- A web chat, WhatsApp Business Platform number, Facebook Page (Messenger), Instagram professional account, Telegram bot or email address connected to the Platform (on the email channel, the Customer forwards emails arriving at its support address to an address provided by UPPU).
- Person
- A natural person who writes to the Customer through a channel or to whom the Customer sends messages.
- User
- A person invited to the Platform by the Customer who uses the Platform on the Customer's behalf (owner, admin, agent, auditor).
- Customer Data
- Messages, media, person identifiers, consent records and related information that reach the Platform through the Customer's channels or are sent from it, and content that the Customer or its Users upload to or create on the Platform (such as knowledge base and help center articles and canned replies).
- Meta
- The Meta Platforms companies that provide the WhatsApp, Messenger and Instagram services.
- Telegram
- The Telegram companies that provide the Telegram messaging service and the Telegram Bot API.
3. The service
3.1. UPPU is a software service that gathers messages from the Customer's channels in a team inbox, lets Users answer them and allows the Customer's own systems to connect to the Platform through an API and webhooks. The features of the service are presented for information on the Services and Developers pages of the website; features shown as "Coming soon" on those pages are not committed. The features and limits available to the Customer depend on the Customer's plan and are shown in the panel.
Effective date: the second and third sentences of clause 3.1 take effect on 20 December 2026 under clause 16.1. Until then, the following sentence applies in their place: "The current scope of the service is described on the Services and Developers pages of the website."
3.2. The Customer sets up the web chat channel itself. WhatsApp, Messenger, Instagram and Telegram channels and API access are enabled for the Customer by UPPU on request. UPPU may decide not to enable such access because of a risk of abuse, Meta's or Telegram's rules or technical reasons.
3.3. UPPU may change features to improve the service. Changes that materially restrict a feature the Customer uses are announced reasonably in advance; in the case of such a change, the Customer may terminate the Agreement before the change takes effect in the manner set out in clause 15.2 or clause 17. New fields, events and endpoints may be added to API v1; the Customer's systems must ignore fields they do not recognize. Changes that break existing behavior are made in a new API version or announced in advance.
3.4. The service is provided without any committed uptime percentage. The parties may agree a separate service level in writing.
4. Accounts, users and security
4.1. Opening an account requires a verified email address and an age of at least 18.
4.2. The Customer is responsible for inviting Users, setting their roles and for the actions of its Users on the Platform. The Customer ensures that its Users comply with this Agreement.
4.3. Passwords, two-factor authentication tools, API keys and webhook secrets must be kept confidential. If the Customer becomes aware of unauthorized use, it revokes the key concerned and informs UPPU without delay. UPPU recommends that Users turn on two-factor authentication.
5. Trial use
5.1. UPPU may offer new companies a free, time-limited trial. The trial period and quotas are shown in the panel and on the Pricing page.
5.2. When the trial ends, the company becomes read-only until paid use begins: messages can be read and people's data exported, but new messages cannot be sent. Data is not deleted because the trial ended; the retention periods continue to run as usual.
5.3. Trial use is provided as is; no fees arise during the trial.
6. Fees, invoicing and payment
6.1. The scope, fee and period of paid use are set out in the quote given to the Customer. Unless stated otherwise, fees exclude VAT and other statutory taxes.
6.2. UPPU collects fees by invoice. Unless agreed otherwise, invoices are payable within 7 days of their date.
6.3. If a payment is not made by its due date, the Customer is notified in writing. Unless a different period is agreed in the quote or otherwise in writing between the parties:
- if payment is not made within 14 days of the due date, the panel becomes read-only for all Users of the company until payment is made;
- if payment is still not made within 30 days of the due date, UPPU stops the service at a time it has notified in writing at least 72 hours in advance.
If the subscription ends and is not renewed, the panel also becomes read-only and UPPU may stop the service after giving at least 72 hours' notice. While the service is stopped, the panel, the API, webhooks, the chat widget and automatic replies stop and no messages can be sent on the channels. Only the following stay available in the panel: the subscription, payment and billing details pages; the personal data request (KVKK) pages, the retention setting, the export and erasure of a contact's data; actions that narrow access or stop data flows (for example revoking an API key, disabling or deleting a webhook, disconnecting a channel, removing a member or an invitation); the page for accepting the Agreement; leaving and closing the company. Messages arriving on the Meta, Telegram and email channels continue to be recorded. Once payment is made, the restrictions are lifted automatically. The retention and termination provisions of this Agreement apply to the deletion of data.
Effective date: this text of clause 6.3 takes effect on 20 December 2026 under clause 16.1. Until then, its previous text applies: a Customer whose payment is late receives a written notice; if payment is not made within 15 days of the notice, the company may be made read-only.
6.4. Meta's WhatsApp Business Platform fees are not included in UPPU's fees. Meta charges them according to its current price list to the payment method the Customer has set on its WhatsApp Business account. Adding a valid payment method to the WhatsApp Business account is the Customer's responsibility.
6.5. If UPPU wishes to change its fees, it announces the change at least 30 days before it takes effect. If the Customer does not accept the change, it may terminate the Agreement before the effective date in the manner set out in clause 17.
7. Meta and Telegram channels; third-party terms
7.1. The Customer connects its WhatsApp Business account, phone numbers, Facebook Page and Instagram account with its own Meta account and by accepting Meta's terms. These assets belong to the Customer and are held in Meta's systems. The Customer declares that it has the necessary authority over these assets.
7.2. The Customer complies with Meta's current terms, in particular the WhatsApp and Meta terms for the WhatsApp Business Platform, the WhatsApp Business Messaging Policy and Commerce Policy, the Meta Platform Terms and the Messenger Platform and Instagram policies. In particular, the Customer:
- obtains opt-in permission in the form Meta requires before messaging people on WhatsApp, and honors requests to opt out;
- on WhatsApp, uses only templates approved by Meta outside the 24-hour customer service window; on Messenger and Instagram, sends messages outside the 24-hour window only where Meta allows it and uses message tags only for their intended purpose; uses the human agent tag (HUMAN_AGENT) only for replies personally sent by a human agent within 7 days of the person's last message, never for automated or promotional messages;
- offers people a way to reach a human if it uses automated replies or a bot;
- keeps its business profile information accurate and up to date;
- does not message about products and services that Meta prohibits or restricts; does not use WhatsApp for purposes Meta's terms do not allow, and in particular does not use it to offer a technology such as a large language model, a generative AI platform or a general-purpose AI assistant as the main service rather than as a feature that supports its business (Meta decides which uses fall under this); this rule also applies to the Customer's own automations connected through the API and webhooks;
- does not use data obtained through the channels for any purpose other than what messaging with those people requires; does not build profiles of people, enrich this data with other data or use it to train AI models (subject to the exceptions Meta permits);
- when linking an Instagram account to a Facebook Page, informs the account owner that Page administrators can see the Instagram messages.
7.3. Meta may restrict, suspend or charge for accounts, numbers, templates or messaging under its own rules. Such decisions by Meta and interruptions of Meta's services are outside UPPU's control.
7.4. If Meta asks for a Customer's access to be cut off, or if the Customer's use violates Meta's terms, UPPU may disconnect the channel concerned. If the Customer removes UPPU's partner access from its WhatsApp Business account (Meta's PARTNER_REMOVED notification), UPPU deletes the access tokens concerned and closes the channel. Removing UPPU from a Facebook Page or Instagram on Meta's side invalidates the token at Meta; the encrypted token stored in UPPU is deleted when the channel is disconnected in the panel or when the company's data is purged.
7.5. Notices and requests that Meta sends to UPPU about the Customer are passed on to the Customer. Under Meta's terms for technology providers, UPPU keeps an up-to-date list of customers containing the Customer's legal name and contact details and may give this information to Meta if Meta asks.
7.6. Telegram. The Customer creates its Telegram bot with its own Telegram account and enters the bot's token in the panel itself. The bot and its token belong to the Customer; UPPU stores the token encrypted and runs the bot only on the Customer's behalf to provide the service. As the bot's developer, the Customer complies with the Telegram Terms of Service and the Telegram Bot Developer Terms. In particular, the Customer:
- keeps for its bot, in BotFather, a privacy policy that people can easily access and that names the Customer as data controller and UPPU as data processor;
- does not send unsolicited messages;
- does not use Telegram's name or brand in the bot's name, username or promotion in a way that suggests a connection with Telegram;
- does not use the Platform to circumvent Telegram's bans, restrictions or moderation decisions;
- does not use data obtained through the channel to build datasets or train AI models.
7.7. Telegram may restrict or block bots or messaging under its own rules. Such decisions by Telegram and interruptions of Telegram's service are outside UPPU's control. If Telegram asks for it, or if the Customer's use violates Telegram's terms, UPPU may disconnect the bot concerned. When a bot is disconnected, its token is deleted from UPPU; the bot's conversation history is deleted within the periods in clause E.12 of Annex 1. Clause E.8 of Annex 1 applies to messages on the Telegram channel passing through Telegram's systems abroad and to the protection of data on this channel.
8. Customer obligations and acceptable use
8.1. The Customer uses the Platform in accordance with applicable law, this Agreement and the terms of Meta and Telegram. In particular, it is prohibited to:
- send unsolicited bulk messages or marketing messages without permission;
- send content that is unlawful, deceptive, threatening, hateful, infringes the rights of others or contains malware or phishing;
- impersonate another person;
- test or try to bypass the security of the Platform, circumvent rate limits or reverse engineer the Platform (except where the law allows it);
- resell or rent the Platform to third parties without UPPU's written permission.
8.2. Commercial electronic messages. The Customer is responsible for obtaining the consents required under Law No. 6563 and its regulation for the commercial electronic messages it sends to people, for meeting its registration and checking obligations in the Message Management System (İYS), and for honoring refusals. The Platform's consent records and the checks described below do not replace these obligations. Sending a Marketing template from the panel requires the person's marketing consent recorded on the Platform; the Customer is responsible for the accuracy of these records. In addition, where the Customer is in Türkiye, the company owner either connects the Customer's İYS account in the panel or declares in the panel that the Customer meets its İYS obligations itself. For a Customer outside Türkiye no İYS connection is used; the basis is the owner's declaration. On the declaration route UPPU checks only the consents recorded on the Platform. While an İYS connection exists for a Customer in Türkiye, the İYS consent of the recipient's Türkiye (+90) number is checked on the Customer's behalf before a Marketing template is sent from the panel; the template is not sent if there is no consent or if İYS cannot be reached. Numbers outside Türkiye and sends through the API are not checked with İYS. The İYS connection, the check and the declaration do not relieve the Customer of its obligations under this clause.
8.3. Personal data. The Customer is the data controller of the data relating to people. Informing people, relying on an appropriate legal ground, obtaining explicit consent where necessary and answering people's applications are the Customer's responsibility. The web chat channel cannot be activated without the address of the Customer's own privacy notice. The Customer processes special categories of personal data only where there is a basis under Article 6 of the KVKK, only to the extent necessary and by taking the adequate measures determined by the Board under Article 6(4) (Annex 1, clause E.2).
8.4. The Customer is responsible for the security of its API and webhook integrations, for the data transferred to its own systems by webhook and for the processing of that data in its own systems.
8.5. The Customer is responsible for content it publishes publicly in the help center or otherwise through the Platform. If UPPU is notified that such content is unlawful, or if a competent authority requests it, UPPU may remove the content concerned, limited to that content, and informs the Customer without delay unless legally prevented.
Effective date: this clause takes effect on 20 December 2026 under clause 16.1.
9. UPPU's obligations, support and maintenance
9.1. UPPU provides the service with due care and applies the technical and organizational measures listed in Annex 1.
9.2. Support is provided at info@uppu.net on weekdays from 09:00 to 18:00 (Türkiye time).
9.3. Planned maintenance is announced in advance where possible. Urgent security work may be carried out without prior notice.
10. Personal data
10.1. For Customer Data, the Customer is the data controller and UPPU is the data processor. UPPU processes this data only on the Customer's behalf and in accordance with Annex 1, the Data Processing Annex.
10.2. UPPU is the data controller for Users' account data, contract and billing details and security logs. This processing is described in the Privacy Policy and the KVKK Privacy Notice.
10.3. The Customer can set the retention period for conversations in the panel to anything between 30 and 730 days; if it does not, the Platform's default (365 days) applies. The period runs from the conversation's last activity.
11. Intellectual property
11.1. The rights in the Platform, software, interface, documentation and the UPPU brand belong to UPPU or its licensors. The Customer is granted a non-transferable, non-exclusive right of use for the term of the Agreement and for its own business purposes only.
11.2. Customer Data belongs to the Customer. The Customer authorizes UPPU to process this data only to provide the service.
11.3. UPPU may use the Customer's suggestions and feedback about the service to improve it, without incurring any obligation towards the Customer.
12. Confidentiality
The parties use information learned under the Agreement that is marked confidential or is confidential by nature (including prices, technical details and Customer Data) only to perform the Agreement and do not disclose it to third parties. Legal obligations are reserved. This obligation continues after the Agreement ends.
13. Suspension
UPPU may suspend the service in whole or in part in the event of a serious breach of the Agreement or of Meta's or Telegram's terms, unlawful use, situations that threaten the security of the Platform or other customers, a request from competent authorities, or late payment (clause 6.3). Where possible, suspension is announced in advance with reasons; the service is restored once the cause is removed.
14. Liability
14.1. UPPU is not liable for damage arising from interruptions and decisions of Meta or other third-party services, problems in the internet infrastructure, the Customer's own systems, or actions taken in accordance with the Customer's instructions.
14.2. UPPU's total liability under this Agreement is limited to the fees paid by the Customer to UPPU in the 12 months before the event causing the damage. UPPU is not liable for indirect damage or loss of profit. The limitations in this clause do not apply in cases of intent or gross negligence or in other cases where liability cannot be limited by law.
14.3. The Customer bears the damage arising from claims and sanctions brought against UPPU because of the Customer's use in breach of this Agreement, the terms of Meta or Telegram, or the law.
15. Term and termination
15.1. The Agreement takes effect when the company is created and continues for an indefinite period. For paid use, the period stated in the quote applies.
15.2. The Customer can end the Agreement at any time by closing the company in the panel ("Delete company"; Turkish: "Firmayı sil"); this closure serves as notice of termination (clause 17). Connected channels must be disconnected first. Refunds of fees paid in advance are subject to the terms of the quote.
15.3. UPPU may terminate the Agreement with 30 days' notice given in the manner set out in clause 17, or immediately in the event of a material breach by the Customer.
15.4. 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 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. Clause E.12 of Annex 1 applies to the company record, legal records and audit logs.
16. Changes to the Agreement
16.1. UPPU may change this Agreement. Changes are notified to company owners by email at least 30 days before they take effect and published on this page with a new version number.
16.2. If the Customer does not accept a change, it may terminate the Agreement before the effective date in the manner set out in clause 17. Changes required by law or for security reasons may take effect at shorter notice.
16.3. The version of the Agreement accepted by each company is recorded. Earlier versions are kept accessible in this page's archive.
16.4. When a new version is published, the company owner is asked to accept it in the panel within 30 days of the time it is presented for acceptance in the panel, and a reminder is sent before the last day. If within that period the new version is not accepted and the Agreement is not terminated, the panel becomes read-only for all Users of the company until the owner accepts it. During that time the company owner is redirected to the acceptance page and other Users can view data; requests about personal data can be handled, access can be restricted and the company can be closed; the API, webhooks and the message traffic of connected channels keep working.
Effective date: this clause takes effect on 20 December 2026 under clause 16.1.
Update of 20 November 2026: the second and third sentences of clause 3.1 and clauses 6.3, 8.5 and 16.4 take effect on 20 December 2026; the other changes to the Agreement and Annex 1 take effect on 20 November 2026. A Customer that does not accept a change may terminate the Agreement before the effective date in the manner set out in clauses 16.2 and 17.
17. Notices
UPPU's notices are sent to the company owner's email address registered in the panel. The Customer's notices to UPPU are sent to info@uppu.net or to the KEP address aloneai@hs01.kep.tr. Closing the company in the panel under clause 15.2 serves as the Customer's notice of termination and is recorded in the audit log. Other notices of termination and formal notices, including a termination by UPPU under clause 15.3, are given through a notary, by registered letter, by telegram or by KEP with a secure electronic signature, as required by Article 18(3) of the Turkish Commercial Code No. 6102. Notices to UPPU by notary or registered letter are sent to UPPU's registered office stated in clause 1.1. Such notices by UPPU are sent to the address the Customer has notified to UPPU in writing or, failing that, to the Customer's address in the trade registry or official records.
18. Evidence agreement
The parties agree that, in disputes arising from this Agreement, the electronic records kept in UPPU's systems (including audit logs, contract acceptance records and delivery records) constitute evidence under Article 193 of the Code of Civil Procedure No. 6100; the right to submit counter-evidence is reserved.
19. Governing law and jurisdiction
This Agreement is governed by the laws of the Republic of Türkiye. Where the Customer is a trader or a public legal entity, the Istanbul Anatolian Courts and Enforcement Offices have jurisdiction over disputes under Article 17 of the Code of Civil Procedure No. 6100; in all other cases the general rules of jurisdiction apply. Where a quotation, order form or agreement separately signed by the parties in writing or with a secure electronic signature designates the competent court, jurisdiction is determined by that designation.
20. Miscellaneous
20.1. Neither party is liable for obligations affected by force majeure (such as natural disasters, epidemics, war, widespread infrastructure outages or decisions of competent authorities).
20.2. The Customer may not assign its rights and obligations under the Agreement without UPPU's written consent.
20.3. If a provision of the Agreement is invalid, the remaining provisions are not affected.
20.4. The Agreement is drawn up in Turkish. The English translation is for information; in the event of a conflict the Turkish text prevails.
Annex 1: Data Processing Annex
This annex is also published on its own page: Data Processing Annex.
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.