How to recognise, route, and act on requests from police, courts, and regulators — without leaking customer data or overreaching. Gimana mengenali, meneruskan, dan menindaklanjuti permintaan dari polisi, pengadilan, dan regulator — tanpa bocorin data customer atau bertindak kelewatan.
Audience: CS Specialists · Based on the Internal Wiki and real cases (customer details removed) · Use ← → to navigate Audiens: CS Specialist · Berdasarkan Internal Wiki dan kasus nyata (detail customer dihapus) · Pakai ← → untuk navigasi
A formal request from an official body asking us to act on a customer account or hand over customer data. The messenger matters as much as the message. Permintaan formal dari badan resmi yang minta kita bertindak pada akun customer atau menyerahkan data customer. Siapa yang meminta sama pentingnya dengan apa yang diminta.
compliance@hostinger.com. Not an authority? Handle it as a normal abuse report and never share account-level data — general standards for what makes a report actionable are fine to share.
Aturan utama: permintaan formal atas data customer atau akun lewat jalur resmi/hukum = authority request. Ragu? Arahkan ke compliance@hostinger.com. Bukan authority? Tangani sebagai abuse report biasa dan jangan pernah bagikan data tingkat akun — standar umum soal laporan yang actionable boleh dibagikan.
Identify the type first — who handles it and whether a backup is possible both follow from that. Kenali jenisnya dulu — siapa yang menangani dan boleh nggaknya backup, dua-duanya tergantung ini.
| TypeJenis | ExamplesContoh | Handled byDitangani oleh | Backup?Backup? |
|---|---|---|---|
| Police / gov data requestPermintaan data polisi / pemerintah | Account info, logs, backupsInfo akun, log, backup | Compliance | Depends on the orderTergantung order |
| Police suspension requestPermintaan suspend dari polisi | Suspend a domain/account for fraud, CSAM, phishingSuspend domain/akun karena fraud, CSAM, phishing | Abuse | No (fraud / CSAM)Nggak (fraud / CSAM) |
| Court order — domain transferCourt order — transfer domain | UDRP, ADNDRC, trademark ordersUDRP, ADNDRC, order merek dagang | Compliance / Domains | Depends on scopeTergantung scope |
| Court order — suspensionCourt order — suspend | Sports-broadcast and IPTV piracy ordersOrder pembajakan siaran olahraga dan IPTV | Abuse | Depends on categoryTergantung kategori |
| GDPR / privacy-law requestPermintaan berdasarkan GDPR / UU privasi | SMTP and access logsLog SMTP dan akses | Compliance | Logs only, not backupsLog saja, bukan backup |
| Regulatory hotline reportLaporan hotline regulator | RRT Lithuania (CSAM), CYSEC (financial fraud)RRT Lithuania (CSAM), CYSEC (fraud finansial) | Abuse (immediate action)Abuse (tindakan langsung) | NoNggak |
Your role is to identify, protect the data, and route — then log it. Not to investigate or negotiate with the requester. Peran kamu: mengenali, melindungi data, dan meneruskan — lalu mencatat. Bukan menyelidiki atau bernegosiasi dengan si peminta.
compliance@hostinger.com with official documentsPermintaan data → peminta kirim email ke compliance@hostinger.com dengan dokumen resmisupport@hostinger.comTelepon → jangan kasih informasi lewat telepon; minta mereka email ke support@hostinger.com#abuse-permanent-police-request (permanent, non-negotiable, no reinstatement or backup) and #abuse-permanent-police-request-insist (confidential report from a higher authority; no reinstatement, transfer out, or backup). Never name the authority or describe the report.
Kalau customer ngotot: pakai predefine yang sudah disetujui: #abuse-permanent-police-request (permanen, non-negotiable, tanpa reinstatement atau backup) dan #abuse-permanent-police-request-insist (laporan rahasia dari pihak berwenang; tanpa reinstatement, transfer out, atau backup). Jangan pernah menyebut nama authority atau menjelaskan isi laporannya.
No more, no less. Too little leaves abuse live; too much hits innocent customers and creates legal risk. Nggak lebih, nggak kurang. Terlalu sedikit = abuse tetap jalan; terlalu banyak = customer nggak bersalah kena dan muncul risiko hukum.
Two questions: is a backup allowed at all, and if so, how do we deliver it safely? Dua pertanyaan: boleh nggak ada backup, dan kalau boleh, gimana kirimnya dengan aman?
| SituationSituasi | Backup?Backup? |
|---|---|
| Police/gov — fraud or phishingPolisi/pemerintah — fraud atau phishing Non-negotiable. No backup, no transfer out.Non-negotiable. Tanpa backup, tanpa transfer out. | NoNggak |
| CSAM Zero tolerance. Immediate permanent suspension.Zero tolerance. Langsung suspend permanen. | NoNggak |
| Police/gov data request with a legal orderPermintaan data polisi/pemerintah dengan order hukum Via Compliance, encrypted export, logged in the Register.Lewat Compliance, export terenkripsi, dicatat di Register. | YesYa |
| Account hijackAkun di-hijack Unintentional, so backups should be provided.Nggak disengaja, jadi backup harus diberikan. | YesYa |
| Copyright court order, failed KYC, related account with no abuseCourt order hak cipta, KYC gagal, akun terkait tanpa abuse Check what the order says; otherwise follow the Suspension Table; related accounts → Compliance.Cek isi order; kalau nggak disebut, ikuti Suspension Table; akun terkait → Compliance. | DependsTergantung |
abuse-department S3 bucket — never a public oneUpload ke bucket S3 abuse-department — jangan pernah yang publikNot every authority request deserves the same speed. Two real cases sit at opposite ends. Nggak semua authority request butuh kecepatan yang sama. Dua kasus nyata ini ada di dua ujung yang berlawanan.
→ Don't transfer. Escalate to Legal to verify authenticity.→ Jangan transfer. Eskalasi ke Legal untuk verifikasi keaslian.
In the real case, asking the regulator for extra proof delayed action and hurt trust with them.Di kasus nyata, minta bukti tambahan ke regulator menunda tindakan dan merusak kepercayaan mereka.
Eleven real cases from Slack. Pick one, read what happened, and ask yourself: what would I have done at each step? Sebelas kasus nyata dari Slack. Pilih satu, baca apa yang terjadi, lalu tanya dirimu: apa yang akan kulakukan di tiap langkah?
Eight questions that would have prevented the real mistakes from our cases. Tap each one as you go through it. Delapan pertanyaan yang bisa mencegah kesalahan nyata dari kasus-kasus kita. Tap satu per satu sambil kamu baca.