Ne saklamiyoruz

• Dosya icerikleri
• Sohbet mesaj icerikleri
• Reklam profili veya pazarlama takip verileri
• Zorunlu hesap, telefon numarasi veya rehber verisi

Hangi metadata islenebilir

• Public IP adresleri ve baglanti zaman damgalari
• Gecici oda / oturum kimlikleri ve peer kimlikleri
• CF-Ray gibi Cloudflare talep kimlikleri
• Dosya hash, boyut ve MIME type gibi teknik transfer ozetleri
• User-agent verisinden turetilen hashlenmis cihaz / tarayici imzasi

Neden isliyoruz

• Signaling oturumlarini kurmak ve korumak icin
• Rate limit, room limit ve abuse kontrollerini uygulamak icin
• Dolandiricilik, malware dagitimi, tehdit veya diger suistimal bildirimlerini incelemek icin
• Gecerli makam talepleri veya ihtilaf durumlari icin teknik kayitlari muhafaza etmek icin

Relay ve altyapi notu

ZoriaDrop mumkun oldugunda dogrudan cihazdan cihaza aktarim kuracak sekilde tasarlanmistir. Baglanti kurmak veya surdurmek icin signaling ve gerektiginde TURN relay altyapisi kullanilabilir. Relay kullanilan senaryolarda dahi dosya icerigi ZoriaDrop sunucularinda uygulama icerigi olarak depolanmaz.

Saklama suresi

Guvenlik ve adli audit kayitlari operasyonel ve hukuki ihtiyaca uygun sinirli surelerle saklanir. Mevcut varsayilan teknik saklama hedefi 730 gundur ve bu sure doldugunda ilgili audit kayitlari otomatik olarak imha edilir. Gecerli bir preservation / legal hold talebi varsa yalniz ilgili kapsamda olan kayitlar silinmeye karsi korunur.

Isleyiciler ve aciklama

• Cloudflare gibi altyapi saglayicilari teknik metadata'yi bizim adimiza isleyebilir
• Kayitlar, yalnizca uygulanabilir mevzuat veya gecerli talep varsa yetkili makamlara aciklanabilir
• Dosya icerigi tutulmadigi icin hosted-content teslimi yapilamaz

What we do not store

• File contents
• Chat message contents
• Advertising profiles or marketing trackers
• Mandatory sign-up accounts, phone numbers, or contact lists

What metadata we may process

• Public IP addresses and connection timestamps
• Temporary room / session identifiers and peer identifiers
• Cloudflare request identifiers such as CF-Ray
• Technical transfer metadata such as file hash, file size, and MIME type
• Hashed device or browser signature derived from the request user-agent

Why we process metadata

• To establish and protect signaling sessions
• To enforce abuse controls such as rate limits and room limits
• To investigate fraud, malware delivery, extortion, or other misuse reports
• To preserve technical records for valid authority requests or dispute handling

Relay and infrastructure note

ZoriaDrop is designed for direct device-to-device transfer where possible. Signaling and, when necessary, TURN relay infrastructure may be used to establish or maintain connectivity. Even in relay scenarios, file contents are not stored as application content on ZoriaDrop servers.

Retention

Security and forensic audit records are retained for a limited period aligned with operational and legal needs. The current default technical retention target for audit records is 730 days. Relevant audit records are automatically deleted after that period unless a valid abuse preservation request or legal hold applies to the specific room or transfer.

Processors and disclosure

• Infrastructure providers such as Cloudflare may process technical metadata on our behalf
• Records may be disclosed to competent authorities only when required by applicable law or a valid request
• Because file contents are not stored by the service, they cannot be disclosed as hosted content