This policy explains how personal data is processed on the uppu.net website and the UPPU platform operated by Alone AI Teknoloji Ltd. Şti. ("UPPU", "we"). Our formal notice under the Turkish Personal Data Protection Law (KVKK) is the KVKK Privacy Notice; cookies are covered in the Cookie Policy and deletion steps in the Data Deletion Instructions.
1. In short
- The uppu.net website uses no cookies and loads no analytics or tracking code, advertising tags or third-party content.
- We have two roles on the platform. For account, contract, billing and security data we are the data controller. For the conversations between businesses and their customers we are a data processor acting for the business; the business concerned is the data controller.
- Platform data is stored in our own data center in Istanbul. WhatsApp, Messenger and Instagram messages also pass through Meta's systems, and Telegram messages through Telegram's systems.
- We do not sell personal data, and we do not use it for advertising, profiling or training AI models.
- You can ask for your data to be deleted at any time: Data Deletion Instructions · kvkk@uppu.net
2. Scope and definitions
This policy covers:
- Website: uppu.net and www.uppu.net.
- Panel: the management and inbox application at app.uppu.net.
- Chat widget: the web chat that businesses add to their own websites, loaded from cdn.uppu.net, and the full-page chat link a business can turn on (cdn.uppu.net/c/…, or the same address on a custom domain the business has set up with UPPU).
- Customer API and webhooks: API v1 at messaging.uppu.net and the webhook v1 events sent to businesses' systems.
- Meta connections: the WhatsApp Business accounts, Facebook Pages and Instagram professional accounts that businesses connect to UPPU; if the business has turned on comment management, the comments on the posts of these Pages and accounts.
- Telegram bots: the bots that businesses create on Telegram themselves and connect to UPPU.
In this text, "business" means the company or organization using UPPU; "user" means a person who signs in to the panel on behalf of a business (owner, admin, agent, auditor); "person" means someone who writes to a business on WhatsApp, Messenger, Instagram, Telegram or web chat, to whom the business sends messages, or who comments on posts of the business's Facebook Page or Instagram account.
Effective date: the parts of this section about Facebook and Instagram comments take effect on 4 December 2026.
3. Our roles
3.1. Where we are the data controller
We decide the purposes and means of processing for:
- technical logs of website visitors;
- access logs of our platform servers (requests to the panel, API, chat widget and webhook domains);
- correspondence with people who email us, and KVKK applications;
- account and security data of panel users;
- contract and billing details of businesses;
- connection details of users who connect Meta accounts or Telegram bots to UPPU.
The purposes, legal grounds and retention periods of these activities are set out one by one in the KVKK Privacy Notice.
3.2. Where we are a data processor
When a business uses UPPU, we process the messages, media, identifiers and consent records of the people it talks to and, if the business has turned on comment management, the comments on its posts, on the business's behalf and on its instructions. The business is the data controller of this data: it decides why the data is processed, how people are informed and how long the data is kept. This relationship is governed by the Terms of Service and its Data Processing Annex.
Effective date: the parts of this section about Facebook and Instagram comments take effect on 4 December 2026.
If you wrote to a business and have a request about your data, contact that business first. If you write to us, we forward your request to the business without delay and help it fulfill it (details).
4. What data we process
4.1. Website
uppu.net is a static site: it uses no cookies or tracking code and contains no forms. The site is hosted in our own data center in Istanbul; the servers that deliver the pages keep technical logs for each request, such as the IP address, date and time, requested address, browser details and referring page. Some links on the site carry a campaign code (ref) in the address; we use these codes to measure, in aggregate, which pages and campaigns bring visits and sign-ups, and we don't track anyone individually. If you write to us using an email template on the site, this code, which shows the page or campaign you came from, appears in the email's subject line and is kept with your correspondence. If you email or call us, your name, contact details and the content of your request are processed.
4.2. Panel account
- Identity and contact: name, email address and, if you add it to your profile, your phone number; your panel language preference.
- Sign-in data: an irreversible hash of the password; the optional two-factor secret and recovery codes; the public key, name and device type of passkeys; a "remember me" token.
- Team data: company memberships and roles, availability, the limit of conversations that can be claimed at once, invitations and join requests.
- Security and audit logs: who did what and when, with the IP address and browser details of the action. Sign-up, sign-in, sign-out, lockouts, password resets and changes, email changes (old and new address), two-factor and passkey actions and account deletion are recorded. Passwords, verification codes, tokens and secrets are never logged. The time of your last successful sign-in and, if your account was suspended, the time of suspension are also kept on your account.
- Session: the session cookie and technical session data (Cookie Policy).
4.3. Company, contract and billing
Company name, the accepted contract version and time of acceptance, records of the company's channels and settings, and the daily usage counts used as the basis for billing. If the company owner has entered billing details: legal name, tax identification number (for sole proprietorships, the Turkish ID number; for companies billed abroad, a foreign tax or VAT number with its country prefix and the billing country), tax office, billing address and billing email address.
Once the company's billing starts, we also process plan and subscription details, payment requests and payments, and bank transfer notices (the sending account holder's name, bank, amount, date, optional bank reference, receipt and note). Once card payments are enabled, card details are sent directly to the payment institution from the payment page; the card number and security code never reach UPPU's servers and are not kept by UPPU. For a one-off card payment we keep the payment result. If the company owner authorizes saving the card for automatic renewal, we process the card's brand, last four digits and expiry date, the card key issued by the payment institution (encrypted), and the time of the authorization and the phone number and IP address given with it; the payment institution stores the card itself.
Effective date: the sentences of this paragraph on card payments and automatic renewal (from "Once card payments are enabled") take effect on 4 December 2026; UPPU will not enable card payments before then.
If the company has connected its account with Türkiye's Message Management System (İYS) in the panel: the İYS code, brand code, İYS API username and password (the password encrypted), and the time and error code of the last check.
4.4. API and webhooks
Only the SHA-256 digest of API keys, their scopes and the IP address they were last used from; an API request log (method, route pattern, related record IDs, response code and IP address; request bodies and query strings are not logged); the webhook addresses and signing secrets defined by the business (encrypted) and delivery records.
4.5. Meta account and Telegram bot connection
When a user connects a WhatsApp Business account, Facebook Page or Instagram account to UPPU, we store: the connecting user's UPPU identity; a SHA-256 hash of the Facebook user ID (pseudonymized; used to match Meta's deletion requests); the list of permissions granted by Meta; the identifiers of the business assets (WhatsApp Business account, phone number, Page and Instagram account IDs), display name, phone number quality and messaging limit details; message templates and their approval status; and the Page or WhatsApp Business account access token issued by Meta (encrypted). We do not store the Facebook user access token created in the browser during the connection. A diagnostic log of the connection steps (step, error codes and Meta IDs, without codes or tokens) is kept.
We receive this information through Meta's Embedded Signup and Facebook Login for Business flows, with your approval. So that you can choose the account to connect, we read the list of Facebook Pages and Instagram accounts you manage; we do not store the ones you do not choose. You can withdraw the permissions you granted in the Business integrations section on Facebook (steps). Retention periods are in section 9.
When a business connects a Telegram bot, we store: the bot's Telegram ID, username and display name; the bot token obtained from Telegram's BotFather tool (encrypted); only a digest of the secret value that verifies Telegram's webhook requests; and the connecting user's action and confirmation about the bot's privacy policy (in the audit log). The bot token is deleted when the channel is disconnected in the panel.
4.6. Data we process on behalf of businesses
When you write to a business through a channel connected to UPPU, we process the following on the business's behalf:
- Identifiers: on WhatsApp, the business-scoped user ID (BSUID) and your phone number; on Messenger, the page-scoped ID (PSID); on Instagram, the Instagram-scoped ID (IGSID); on Telegram, your Telegram user ID and, if you share your own contact card with the bot, your phone number; on web chat, a randomly generated visitor ID.
- Name: your WhatsApp profile name; on Messenger and Instagram, your name and username where Meta allows it; on Telegram, the first and last name in your profile, or your username if there is none; a display name entered for you by an agent; on web chat, the name you enter (the business may make it mandatory if it has turned on the pre-chat form).
- Pre-chat form: if the business has turned on the web chat pre-chat form, the name, email address and phone number you give in it, and your short first question.
- Messages: what you write and what is sent to you; button and list replies, reactions, reply context, locations you share (latitude, longitude, place name and address), contact cards you share (which may contain other people's names and phone numbers), Instagram story replies and messages you forward on Telegram.
- Media: images, video, audio, documents and stickers you send or receive; file name, type and size.
- Technical data: message IDs; sent, delivered and read times; error codes; a raw, unprocessed copy of the incoming message (for troubleshooting and reprocessing, for at most 90 days).
- Conversation data: status, assigned agent, tags, block status and the version of the privacy notice shown in web chat.
- Consent records: consents and withdrawals recorded by the business for sending you marketing or utility messages; the consent text, source and time.
- İYS check: if the business has connected its İYS account, the consent status in İYS of your number beginning with +90 is checked before a marketing template is sent to you from the panel inbox. The result is cached for at most 15 minutes; the cache uses a digest of the number, not the number itself.
In web chat we do not write the visitor's IP address or browser details to the database. The IP address and browser details of visitors to pages where the chat widget is loaded are, however, written to the access logs of UPPU's servers, even if the widget is never opened; we keep these logs as data controller for our own security (3.1 and 9). The IP address also appears in short-lived rate-limit records used to prevent abuse. The chat widget stores a visitor key and messages not yet sent in the visitor's browser; if the business has turned on the pre-chat form it also stores the form's name, email and phone answers, and if the widget has a language selector, the chosen language (details and periods: Cookie Policy).
4.7. Facebook and Instagram comments
Effective date: this section takes effect on 4 December 2026; UPPU will not enable comment management before then.
If the business has turned on comment management, we process the following on its behalf and on its instructions: comments and replies on posts of the business's Facebook Page and Instagram professional account; the commenter's ID issued by Meta (page-scoped on Facebook, Instagram-scoped on Instagram) and name or username; the comment's text and time; the ID, type and link of the post the comment belongs to and a short excerpt of its caption; and the actions the business takes on a comment (public reply, private reply, hiding, unhiding and deletion). We only count like and reaction notifications. We do not create a separate contact record for a commenter; if the commenter has messaged the business on the same channel, the comment is linked to that contact. Commenters should first send erasure and access requests to the business concerned (details). Retention periods are in section 9.
5. Data received from Meta platforms
UPPU is software that lets businesses use the WhatsApp Business Platform (Cloud API), the Messenger Platform and Instagram messaging and, where the business turns it on, the Facebook Page and Instagram comment interfaces. We process the data received through these channels (what Meta calls "Platform Data") only as follows:
- What we receive: messages and media sent to the business, message statuses (sent, delivered, read, failed), profile names, identifiers and settings of business assets, message templates and quality details; if the business has turned on comment management, comments and replies on its posts (see 4.5, 4.6 and 4.7).
- Why: only to run the messaging and, if turned on, the comment management of the business concerned: showing messages in the inbox, delivering the business's replies, tracking delivery, applying Meta's 24-hour and template rules, passing data to the business's own systems on its instructions; showing, replying to, hiding and deleting comments and replying to a comment by private message.
- What we do not do: we do not sell or rent this data; we do not use it for advertising or marketing targeting; we do not build profiles of people or enrich this data with other data; we do not use it to develop or train AI models; we do not share it with anyone other than the business concerned and the recipients listed in this policy.
- Where we keep it: in our own data center in Istanbul, with access tokens encrypted.
- How long: for the periods in the Retention section. The access token is deleted when the channel is disconnected in the panel (unless another connected channel uses the same Meta account). When UPPU's partner access is removed from a WhatsApp Business account, Meta notifies us, the tokens are deleted and the channel is closed. Removing UPPU from a Facebook Page or Instagram on Meta's side invalidates the token; the stored token is deleted when the channel is disconnected in the panel or when the company's data is purged.
- How to have it deleted: Data Deletion Instructions.
Effective date: the parts of this section about Facebook and Instagram comments take effect on 4 December 2026.
Messages on Meta channels pass through Meta's systems and are subject to Meta's own terms and privacy policy. Web chat data is never sent to Meta.
6. Purposes and legal grounds
For processing where we are the controller, the main purposes and the legal grounds under Article 5 of Law No. 6698 (KVKK) are:
| Data | Purpose | Legal ground (KVKK Art. 5/2) |
|---|---|---|
| Panel account and team data | Opening the account, authentication, providing the service, team management, service emails (verification, password reset, invitations, alerts) | (c) conclusion and performance of a contract (the user who creates the company and accepts the agreement); (f) legitimate interest (invited users: providing the service to our customer's team) |
| Security and audit logs | Information security, preventing abuse, evidence in possible disputes | (ç) legal obligation (the data security measures of KVKK Art. 12); (f) legitimate interest; (e) establishment, exercise or protection of a right |
| Contract and billing data | Performing the contract, invoicing, collecting payments and reviewing bank transfer notices, tax and accounting obligations | (c) contract; (ç) legal obligation (tax and commercial law) |
| Legal names and representatives' contact details of customer businesses | Keeping the customer list required by Meta's terms for technology providers and giving it to Meta if Meta asks | (f) legitimate interest |
| Meta and Telegram connection data | Setting up and maintaining channel connections; handling Meta's deletion and access removal notices | (f) legitimate interest; (c) contract where the connecting person is a party to the agreement |
| Platform server logs | Operating the platform securely, preventing abuse, troubleshooting; keeping security logs for 12 months and reviewing them regularly under the payment card industry security standard (PCI DSS) | (f) legitimate interest |
| Website server logs | Operating the site securely; measuring in aggregate, by the campaign codes in our addresses, the visits that pages and campaigns bring (no individual tracking). As the site is hosted in our own data center, these logs are not transferred to a hosting provider; they are kept for 30 days for operating the site (9) | (f) legitimate interest |
| Email and phone correspondence | Answering requests, preparing quotes | (c) directly related to concluding a contract; (f) legitimate interest |
| KVKK applications and deletion requests | Concluding the application, forwarding the request to the business concerned | (ç) legal obligation (KVKK Art. 13); (e) evidence of the application |
We do not use your data for marketing without your consent. Mandatory service notices, such as security notices, contract changes or service interruptions, are not marketing messages.
For data we process on behalf of businesses, the business as data controller determines the purpose and legal ground. Obtaining the consents required for marketing messages and recording them in Türkiye's Message Management System (İYS) are duties of the business that sends the message; UPPU's İYS connection does not relieve the business of these duties and does not cover sends through the customer API.
7. Who we share data with
- Meta Platforms: when a business connects a WhatsApp, Messenger or Instagram channel, the messages and media it sends, recipient identifiers, read receipts and template definitions are sent to Meta, and incoming messages are received from Meta. On Messenger and Instagram, the person's ID is sent to Meta when the person's name is requested. If the business has turned on comment management, comments and post details are received from Meta, and the business's public and private replies to comments and its hide, unhide and delete instructions are sent to Meta. In addition, under Meta's terms for technology providers, we may give Meta the names and contact details of the businesses that are our customers if Meta asks. Meta processes this data under its own terms.
- Facebook JavaScript SDK: loaded only on the WhatsApp, Messenger and Instagram connection pages of the panel, for the user who opens these pages. While the SDK loads, Meta receives the user's IP address and browser details; when the Facebook Login window opens, Meta uses its own cookies.
- Telegram (Telegram Messenger Inc.): when a business connects a Telegram bot, the messages and files in the bot's private chats are received through Telegram's Bot API, and the business's replies, buttons and files and the recipient's Telegram ID are sent to Telegram. Telegram processes this data under its own terms and privacy policy. UPPU is not affiliated with or endorsed by Telegram.
- İleti Yönetim Sistemi A.Ş. (İYS): if the business has connected its İYS account in the panel, the recipient's phone number beginning with +90 is sent to İYS on the business's instructions and with its İYS credentials, to check its consent status before a marketing template is sent from the panel inbox. This check is not made for messages sent through the customer API.
- Payment institution (PayTR): once card payments are enabled, the company's legal name, billing address, email address, the phone number entered on the payment page, the payer's IP address, the amount and the order number are sent to PayTR so that the payment can be made; card details are entered directly with PayTR, and PayTR stores any card saved for automatic renewal.
- Email service provider (mail.uppu.net): to send verification, password reset, invitation, alert, export and billing emails and to receive emails sent to us.
- The business's own systems: data sent to the webhook addresses defined by the business and data retrieved with the business's API keys; the business decides the recipient.
- The business concerned: if a KVKK application or deletion request about a business reaches us, it is forwarded to that business so that it can be fulfilled.
- Competent authorities: where required by law and on a duly made request.
Effective date: the sentence on comments in the Meta Platforms item and the Payment institution (PayTR) item take effect on 4 December 2026.
We use no third-party analytics, advertising, tracking, error-tracking or CAPTCHA services. Platform data is kept on our own servers, not with a cloud provider.
8. Transfers abroad
Platform data is stored in Türkiye, in our data center in Istanbul. On WhatsApp, Messenger and Instagram, messages pass through the systems of Meta companies abroad, such as WhatsApp LLC, Meta Platforms Ireland Ltd. and Meta Platforms, Inc., because that is how these channels work. On Telegram, for the same reason, messages pass through the systems of Telegram (Telegram Messenger Inc.) abroad.
- Data we process on our own behalf: Meta connection data, the customer details Meta asks for and the information the Facebook SDK passes to Meta on the connection pages reach Meta companies abroad, in order to provide the service and to comply with Meta's platform terms. These transfers are subject to Article 9 of the KVKK; the basis on which they are made will be stated in this section once the legal review is complete.
- Businesses' messages on Meta and Telegram channels: for these messages, the legal basis of the transfer and informing the people concerned are the responsibility of the business as data controller (Data Processing Annex E.8).
9. Retention
Expired data is deleted automatically every night. Each deletion is documented by a destruction record containing only the number of records deleted.
| Data | Period |
|---|---|
| Conversations and messages | 365 days from the conversation's last activity; the older messages of a conversation that stays active are kept with it. The business can change the period to anything between 30 and 730 days. |
| Contact records with no conversations left | Together with their identifiers, once the person's last activity is older than the retention period |
| Raw copies of messages | 90 days (or the business's retention period, if shorter) |
| Meta notifications not routed to any company (raw) | 7 days |
| Incoming media files | At most 90 days after receipt; earlier, together with the conversation, if the business's retention period deletes it first |
| Media uploaded by the business for sending | 90 days after its last use; the file's record 30 days after the file is deleted |
| Facebook and Instagram comments and replies (if the business has turned on comment management) | The business's retention period (the same as for conversations), counted from the last activity; post records with no comments left are deleted too. If the business turns off receiving comments for a channel or in its plan, the stored comments are deleted 7 days later. |
| Deletion markers of erased comments (only the comment's Meta ID and the time of deletion) | 10 days |
| Comment action records whose comment was deleted, reduced to IDs | 30 days |
| Raw copies of comment and post notifications (received while the feature is off, events that are not processed, like and reaction notifications) | 7 days; notifications delivered together with other events 90 days |
| API request log | 30 days |
| Webhook records | Delivery records 30 days; event contents 7 days after delivery completes (at most 30 days); the event skeleton (ID, type and time) 35 days |
Events that can be pulled from the API (GET /v1/events) | 7 days |
| Meta error records | 30 days |
| Meta connection record (hash of the Facebook user ID, permissions granted, connecting user, asset identifiers) | While the company account remains open; deleted 365 days after the company is closed. The PIN is deleted when the channel is disconnected; the access token when the disconnection completes, unless another connected channel uses the same Meta account. |
| Telegram bot record (the bot's ID, username and display name) | While the company account remains open; deleted together with the data of the closed company. The bot token is deleted when the channel is disconnected in the panel. |
| Meta connection diagnostics | 90 days |
| Records of incoming messages that could not be processed | 90 days after the problem is resolved |
| Access, error, application, system and security logs of the platform servers (IP address, request time, requested address and browser details; in application error logs, data about the request in which the error occurred; administrator access records; details in KVKK Privacy Notice 3.7) | Copied every day into an integrity-protected security log archive and kept there for 396 days (12 months plus a margin); during that period individual entries in the archive cannot be corrected or deleted, and the archive is deleted automatically at the end. They stay in the current files on the server for a shorter time: application logs 30 days, the server's system journal at most 3 months. Detailed web application firewall logs are kept for 30 days and detailed intrusion detection alerts for 90 days; they are not archived. |
| Accounts whose email was never verified | 72 hours |
| Panel account | Until the account is deleted |
| Data of a closed company | Deleted 365 days after closure. A company with connected channels cannot be closed; its channels are disconnected before closure. This purge deletes the tax office, address and billing email from the billing details and, where the number is a Turkish ID number (sole proprietorship), the legal name and number too. In payment requests and credit notes, the legal name, number, address and email of a buyer registered with a Turkish ID number are anonymized. Bank transfer receipts are deleted, and sender names and notes are cleared. The following are not deleted in this purge and are currently kept indefinitely: the company record (name); the legal name and number of companies and buyers registered with a tax identification number or a foreign tax number; payment requests and amounts; the accepted contract version; setup steps and audit logs. The legal records will be destroyed after 10 years (Tax Procedure Law No. 213 and Turkish Commercial Code No. 6102), the audit logs after 10 years. |
| Security and audit logs | At least 3 years; currently not deleted automatically (upper limit: 10 years) |
| Invoices and accounting records | 10 years (Tax Procedure Law No. 213 and Turkish Commercial Code No. 6102). The payment requests and payment records in UPPU are currently not deleted automatically. |
| Bank transfer notices | The receipt is deleted 90 days after the review decision. When the company is closed, the closed company's purge deletes all receipts and clears sender names and notes; the record of the notice remains. |
| Card saved for automatic renewal (brand, last four digits, expiry date, card key, authorization record) | When the card is removed, the card key is deleted; once the payment institution has deleted the card, the phone number and IP address given with the authorization are deleted too. The brand, last four digits, expiry date and time of authorization are deleted in the closed company's purge; the card's removal stays in the audit log with the brand and last four digits. |
| Payment notifications from the payment institution | The content of the notification is deleted after 90 days; the payment result remains. |
| Website server logs | 30 days for operating the site. |
| Email and phone correspondence | 2 years |
| KVKK applications and deletion requests | 3 years after the application is closed |
Effective date: the four rows of the table on Facebook and Instagram comments and the rows "Card saved for automatic renewal" and "Payment notifications from the payment institution" take effect on 4 December 2026.
Deleted data remains in database and media backups for at most 7 more days. It is also kept in the database change logs (binary logs) to be deleted after 7 days; because a log file can only be deleted once it has been closed, this period may be exceeded.
10. Security
Our main technical and organizational measures:
- TLS-encrypted connections on all our domains;
- AES-256-GCM encryption of Meta access tokens, Telegram bot tokens, WhatsApp PINs, İYS API passwords, webhook addresses and secrets, using a rotatable key ring separate from the application's general encryption key (APP_KEY); each encrypted value is bound to its company and record;
- storing only digests of API keys; keys that can be limited by scope, channel, IP range and expiry;
- 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;
- isolation of each company's data, access based on roles and explicit permissions, and masked phone numbers for agents;
- logging of data changes and security events in an audit log;
- only the necessary ports open on our servers, administrative access by key and from restricted addresses, and automatic security updates;
- nightly database backups and regular restore tests.
No system is perfect. If a breach affects data for which we are the controller, we notify the Personal Data Protection Board and the people concerned under Article 12(5) of the KVKK. For data we process on behalf of businesses, we notify the business concerned without undue delay and help it make its own notification to the Board and to the people concerned (Data Processing Annex E.10).
11. Your rights
Under Article 11 of the KVKK you have the right to learn whether your personal data is processed; to request information if it is; to learn the purpose of processing and whether data is used for that purpose; to know the third parties in Türkiye or abroad to whom it is transferred; to request correction of incomplete or inaccurate data; to request erasure or destruction; to request that correction and erasure be notified to the third parties the data was transferred to; to object to a result against you that arises solely from automated analysis; and to claim compensation for damage caused by unlawful processing.
How to apply, with an application template, is explained in the KVKK Privacy Notice. Applications are concluded within 30 days at the latest and generally free of charge; if the action involves an additional cost, the fee set in the tariff of the Personal Data Protection Board may be charged.
Panel users can delete their account themselves in their profile settings. Businesses can export and erase people's data in the panel.
People in the European Economic Area and the United Kingdom: if your data is processed on behalf of a business, please first contact that business, which is the controller, to exercise your rights under the GDPR or UK GDPR; we help the business respond. For data we process on our own behalf, write to kvkk@uppu.net. Where these laws apply to you, you may also lodge a complaint with the supervisory authority of your country.
12. Deleting your data
The Data Deletion Instructions explain step by step how to make a deletion request depending on who you are. In short: if you wrote to a business, ask the business or us; if you are a business user, use the panel or ask us. In every case you can write to kvkk@uppu.net.
13. Children
UPPU is a service for businesses. You must be at least 18 years old to open a panel account; our website is not directed at children.
14. Changes
We update this policy when our services or the law change. The date at the top of the page changes with each update. We notify company owners of significant changes by email before they take effect.
Update of 20 November 2026: the parts about Facebook and Instagram comments (sections 2, 3.2, 4.7, 5, 7 and 9) and about card payments and automatic renewal (sections 4.3, 7 and 9) take effect on 4 December 2026; the other changes take effect on 20 November 2026. UPPU will not enable comment management or card payments before 4 December 2026.
15. Contact
Alone AI Teknoloji Ltd. Şti.
Cumhuriyet Mah. Kartal Cad. Kalay Plaza No:65/1-2, Kartal / İstanbul, Türkiye
KEP: aloneai@hs01.kep.tr
Personal data: kvkk@uppu.net
General: info@uppu.net