Security and data
Security and data: what we protect, and how.
Everything on this page describes the product as it runs today. We don't claim what we haven't built.
Last reviewed:
Where your data lives
Data stored in UPPU (messages, contacts, media files and backups) is kept on our own servers in our own data center in Istanbul.
WhatsApp, Messenger and Instagram are Meta's services, and their messages pass through Meta's infrastructure. According to Meta's documentation, WhatsApp Cloud API messages are processed in Meta's data centers and kept for up to 30 days for basic functions such as retries; Meta acts as a data processor on behalf of the business for this service. Messenger and Instagram messages are subject to Meta's own terms. Meta also processes these messages in data centers outside Türkiye. Our copy of the messages, media files and backups are in Istanbul. Live chat data never goes to Meta or any other third party, and it doesn't leave UPPU unless you send it to your own systems by webhook.
AI will run here tooComing soonWhen UPPU Bot and the agent assistant launch, the AI model will also run on our own servers in our own data center in Istanbul, and your conversations won't be sent to an AI service outside Türkiye.
Encryption and secrets
- TLS on every domain (Let's Encrypt certificates, HTTP/2): connections are encrypted in transit.
- Meta access tokens and WhatsApp PINs are stored encrypted with AES-256-GCM, and each encrypted value is bound to its workspace and record.
- Your webhook endpoint addresses and signing secrets are stored encrypted too.
- Only a SHA-256 hash of each API key is stored; you see the key itself only when you create it.
- You can give keys scopes, a channel binding, an IP allowlist and an expiry, and rotate or revoke them.
- The
Authorizationheader is never written to any log.
Access and accounts
- Four roles: Owner, Admin, Agent and Auditor. Auditors can only read; retention, API keys and webhooks are owner-only.
- Agents see customers' phone numbers masked (for example +90 *** 2233); owners, admins and auditors see the full number.
- Every user can turn on TOTP two-factor authentication and passkeys.
- UPPU's platform admins have no implicit access to your workspace data, and two-factor authentication is mandatory for their accounts. To run the service they use defined admin screens: company and billing details, user accounts, channel health, usage counts and the audit log.
- To investigate delivery problems, a platform admin can open the raw content of an inbound message: in the panel by entering a written reason (recognized Turkish ID numbers stay masked), or with a server command that records their name. Every opening is written to the audit log, and if the message was routed to your workspace, the record also appears in your workspace's audit log.
- Sensitive pages ask for your password again. Login is limited to 5 attempts per minute, and lockouts are logged.
- A mandatory workspace filter applies to every query, and every route is tested across workspaces and roles.
- Teammates join by invitation; if the owner turns it on, people with your company's verified email domain can also request to join, and the owner or an admin approves by sending an invitation. Free email domains can't use this route.
- Data changes and security events go to the audit log, which is kept for at least 3 years; no upper limit has been set yet, and it isn't deleted automatically today. Passwords, codes, tokens and secrets are never written to any log.
Privacy tools
You are the data controller for your customers' and website visitors' data that UPPU processes on your behalf (for example messages, contacts and media), and UPPU is your data processor. For our servers' access logs (IP address and browser details, including visitors of pages that load the chat widget), UPPU is the controller for its own security, and you need to mention this in your own privacy notice. Details are in our KVKK privacy notice. Built-in tools for your KVKK duties are in the panel.
- The workspace owner chooses a retention period from 30–730 days. Expired data is deleted every day at 07:15 (Istanbul time), and each run writes a destruction log that holds counts only.
- You can export all of a contact's data as JSON or erase it completely from UPPU; to confirm an erasure you type the contact's label. Erased data leaves the nightly backups within 7 days.
- If your workspace has API access, an erasure produces the
contact.erasedevent: it goes to your webhook if you set one up, and stays readable throughGET /v1/eventsfor 7 days. - Marketing templates need a recorded consent. On WhatsApp, a message consisting only of STOP, DUR or İPTAL withdraws it in UPPU's consent ledger. UPPU doesn't pass this withdrawal to İYS today; if the recipient falls under İYS, reporting the opt-out to İYS in time is your company's duty.
- Getting the recipient's consent to commercial messages and recording it in Türkiye's İYS are your duties as the sending business. UPPU sends a marketing template only to people with a marketing consent recorded in UPPU who haven't withdrawn it.
- To send a marketing template from the inbox, the workspace owner either connects the company's İYS account in the panel or declares in the panel that the company meets its İYS duties itself. With İYS connected, the İYS consent of a +90 number is checked before each marketing template, and the template isn't sent without it.
- With the declaration, and for sends through the API, UPPU doesn't check İYS today; before sending a marketing template to numbers in Türkiye (+90), you need to check the recipient's İYS consent in your own system.
Retention periods
These are the product's current settings; when they change, this table changes too.
| Data | Kept for |
|---|---|
| Conversations and messages | 365 days from the conversation's last activity by default; the workspace owner chooses from 30–730 days. Each new incoming or outgoing message restarts the period, and older messages of a conversation that stays active are kept with it. |
| Inbound media files | At most 90 days (if your retention period deletes the conversation earlier, its files go with it) |
| Raw message payloads | 90 days (or your shorter retention period) |
| Unprocessable message records (after closing) | 90 days |
| Meta error events | 30 days |
| Unfinished channel connection attempts | 90 days |
| Meta payloads not routed to any channel | 7 days |
| API request log (no bodies or query strings) | 30 days |
| Webhook delivery records | 30 days; event skeletons 35 days, event bodies 7 days after delivery (up to 30 days for an event that can't be delivered or is held) |
| API event list (GET /v1/events) | 7 days |
| User accounts never verified | 72 hours |
| A closed workspace's data | Deleted 365 days after closure |
| Audit log | At least 3 years; not deleted automatically today |
| Deleted data remaining in nightly backups | Up to 7 days |
| Deleted data remaining in the binary log | 7 days; may be exceeded until the log file is closed |
Reliability
- We test the system end to end every minute, along the real path; if the live chat path fails, our team is alerted within 1.5–2.5 minutes.
- A health check runs every 5 minutes, with a daily report.
- The database is backed up every night and backups are kept for 7 days; a 7-day binary log allows point-in-time recovery.
- We test restoring from backup every month.
Infrastructure
We don't publish our servers' names, addresses or software versions. These are the rules we apply:
- Only the required ports are open to the outside.
- Server management works by key only and from restricted addresses.
- The database and cache aren't reachable from outside.
- Security updates install automatically.
- The staging environment runs separately from production.
- The panel enforces a Content Security Policy (CSP), and HSTS makes browsers connect to it only over encrypted connections.
API and webhook security
- Webhooks are signed with HMAC-SHA256 in the Standard Webhooks format; we recommend refusing any request whose timestamp is more than 300 seconds off.
- Webhook targets pass SSRF protection: nothing is sent to private network ranges, the IP address is pinned, and redirects aren't followed.
- An endpoint goes live only after it passes a test event and a wrong-signature check.
- Webhooks come from 91.216.36.26, and we announce any change 30 days ahead. The real check is the signature.
- Sends require an
Idempotency-Key: retry the same request safely, without duplicate messages. - Browser requests to the API are refused (no CORS); API keys are only used from your servers.
Third parties
- No third-party analytics, ad trackers or CAPTCHA in the panel or the chat widget.
- Facebook's JavaScript library loads only on the panel's WhatsApp, Messenger and Instagram connection pages, as soon as the page opens; Meta receives your IP address and browser details at that point.
- Meta provides the WhatsApp, Messenger and Instagram channels; messages on those channels pass through Meta's infrastructure.
- The system emails UPPU sends (verification, invitations, alerts) never carry your customers' message text.
- This website (uppu.net) sets no cookies and loads nothing, fonts included, from third-party servers.
- The companies we use to provide the service are on our sub-processor list.
Certifications and SLA
Reporting a vulnerability
If you think you've found a security vulnerability, tell us what you found, how to reproduce it and its possible impact: info@uppu.net
Scope: uppu.net, app.uppu.net, messaging.uppu.net and cdn.uppu.net. Please follow these rules:
- Don't try to access, change or delete real customer data; test in your own trial workspace.
- Don't run load or denial-of-service tests that could disrupt the service.
- No social engineering, phishing or physical access attempts.
- Don't share the issue with others before we've fixed it.
We'll review your report and get back to you. We don't run a bug bounty program.
Documents
- Terms of Service and Data Processing AnnexRoles, instructions, security measures and sub-processors
- Sub-processorsThe companies we use to provide the service
- Privacy PolicyWhat data we process, why, and for how long
- KVKK privacy noticeUPPU's notice as a data controller under Turkish law
- Cookie PolicyBrowser storage on the site, in the panel and in the chat widget
- Data deletion instructionsHow Facebook, Instagram and WhatsApp users can delete data