P2P Learning SessionSesi P2P Learning

Authority RequestsAuthority Requests

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.

1
Recognise what counts as an authority requestKenali apa yang termasuk authority request
2
Route and handle it with the right team and wordsArahkan dan tangani ke tim yang tepat dengan kata-kata yang tepat
3
Spot red flags and know when to escalateKenali red flag dan tahu kapan harus eskalasi
4
Apply the right scope — service, plan, or accountTerapkan scope yang benar — service, plan, atau account

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

01 · Foundation01 · Dasar

What counts as an authority request?Apa yang termasuk authority request?

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.

✓ Counts✓ Termasuk
  • Police and cybercrime unitsPolisi dan unit cybercrime
  • Government agencies asking for account dataInstansi pemerintah yang minta data akun
  • Court orders, subpoenas, legal noticesPerintah pengadilan, subpoena, pemberitahuan hukum
  • Regulator hotlines (e.g. RRT Lithuania, CYSEC)Hotline regulator (mis. RRT Lithuania, CYSEC)
  • UDRP / ADNDRC decisions from ICANN-approved providersKeputusan UDRP / ADNDRC dari provider yang disetujui ICANN
✗ Does not count✗ Tidak termasuk
  • Private cybersecurity companies (e.g. Proofpoint) — they are third-party reportersPerusahaan cybersecurity swasta (mis. Proofpoint) — mereka pelapor pihak ketiga
  • Informal emails "from the police" with no official documentsEmail nggak resmi yang ngaku "dari polisi" tanpa dokumen resmi
  • Individuals claiming to represent a government body, with no proofOrang yang ngaku mewakili instansi pemerintah, tanpa bukti
  • Anti-phishing feeds (APWG, Spamhaus, etc.)Feed anti-phishing (APWG, Spamhaus, dll.)
Key rule: a formal request for customer or account data through official or legal channels = authority request. Unsure? Route to 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.
Analogy — the bank vault: a bailiff with a court paper delivered through official channels gets taken seriously. A stranger who says "I work with the bank's partner" doesn't get a peek at anyone's account, however polite or well-connected they sound. Analogi — brankas bank: juru sita dengan surat pengadilan lewat jalur resmi ditanggapi serius. Orang asing yang bilang "saya kerja sama partner bank" nggak boleh lihat akun siapa pun, sesopan atau sekoneksi apa pun dia.
02 · Types and owners02 · Jenis dan penanggung jawab

Different request, different ownerBeda permintaan, beda pemilik

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 / pemerintahAccount info, logs, backupsInfo akun, log, backupComplianceDepends on the orderTergantung order
Police suspension requestPermintaan suspend dari polisiSuspend a domain/account for fraud, CSAM, phishingSuspend domain/akun karena fraud, CSAM, phishingAbuseNo (fraud / CSAM)Nggak (fraud / CSAM)
Court order — domain transferCourt order — transfer domainUDRP, ADNDRC, trademark ordersUDRP, ADNDRC, order merek dagangCompliance / DomainsDepends on scopeTergantung scope
Court order — suspensionCourt order — suspendSports-broadcast and IPTV piracy ordersOrder pembajakan siaran olahraga dan IPTVAbuseDepends on categoryTergantung kategori
GDPR / privacy-law requestPermintaan berdasarkan GDPR / UU privasiSMTP and access logsLog SMTP dan aksesComplianceLogs only, not backupsLog saja, bukan backup
Regulatory hotline reportLaporan hotline regulatorRRT Lithuania (CSAM), CYSEC (financial fraud)RRT Lithuania (CSAM), CYSEC (fraud finansial)Abuse (immediate action)Abuse (tindakan langsung)NoNggak
Analogy — hospital triage: the triage nurse doesn't treat anyone. She sorts patients by type so each one lands with the right specialist. Your first job is the same: sort, then hand over. Analogi — triage rumah sakit: perawat triage nggak mengobati siapa pun. Dia mengelompokkan pasien berdasarkan jenisnya supaya masing-masing sampai ke spesialis yang tepat. Tugas pertama kamu sama: pilah dulu, baru serahkan.
03 · The handling flow03 · Alur penanganan

Route it, don't open itTeruskan, jangan dibuka

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.

1
Identify the requester and the type. Official body or private organisation? Data, suspension, or domain transfer?Kenali peminta dan jenisnya. Badan resmi atau organisasi swasta? Minta data, suspend, atau transfer domain?
2
Share nothing. No account details, user info, or internal review notes — whoever the requester claims to be.Jangan bagikan apa pun. Tanpa detail akun, info user, atau catatan review internal — siapa pun yang diklaim si peminta.
3
Route to the right team.Arahkan ke tim yang tepat.
  • Data request → requester emails compliance@hostinger.com with official documentsPermintaan data → peminta kirim email ke compliance@hostinger.com dengan dokumen resmi
  • Suspension only → Abuse team handles it directlySuspend saja → tim Abuse menangani langsung
  • Suspension + data → Abuse suspends first, then hands over to ComplianceSuspend + data → Abuse suspend dulu, lalu serahkan ke Compliance
  • Phone call → never give information by phone; ask them to email support@hostinger.comTelepon → jangan kasih informasi lewat telepon; minta mereka email ke support@hostinger.com
4
Act within the exact scope of the request (next slide).Bertindak sesuai scope persis dari permintaannya (slide berikutnya).
5
Log it. Add every request to the Register of Information Provided for Institutions (mandatory) and note your reasoning in the CRM.Catat. Masukkan setiap permintaan ke Register of Information Provided for Institutions (wajib) dan tulis alasan keputusanmu di CRM.
When the customer pushes back: use the approved predefines #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.
Analogy — the receptionist: take the envelope, send it to the right desk, write it in the logbook. Never open the filing cabinet for a visitor, however official their badge looks. Analogi — resepsionis: terima amplopnya, kirim ke meja yang tepat, catat di buku log. Jangan pernah membuka lemari arsip untuk tamu, seresmi apa pun kelihatan badge-nya.
04 · Suspension scope04 · Scope suspend

Do exactly what the request saysLakukan persis seperti isi permintaannya

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.

The authority names the scopeAuthority menyebut scope-nya
  • Only the domain → suspend only the domainHanya domain → suspend domain saja
  • Whole account → suspend the whole accountSeluruh akun → suspend seluruh akun
  • "Don't inform the customer" → don't notify"Jangan beri tahu customer" → jangan diberi tahu
  • Court orders → only the domains listedCourt order → hanya domain yang tercantum
Our default for clear abuseDefault kita untuk abuse yang jelas
  • Fraud, phishing, illegal content → the reported service + the whole hosting planFraud, phishing, konten ilegal → service yang dilaporkan + seluruh hosting plan
  • Account looks fraudulent → the whole accountAkun terlihat fraud → seluruh akun
  • Unsure which applies → ask Compliance and note it in the CRMNggak yakin yang mana → tanya Compliance dan catat di CRM
Related accountsAkun terkait
  • Suspend only if they show the same abuse patternSuspend hanya kalau menunjukkan pola abuse yang sama
  • Check dates and content — a device match alone isn't enoughCek tanggal dan konten — kecocokan device saja nggak cukup
  • Request goes beyond the reported account (e.g. by phone/device)? Escalate to Compliance firstPermintaan melebar dari akun yang dilaporkan (mis. lewat telepon/device)? Eskalasi ke Compliance dulu
✗ Real mistake✗ Kesalahan nyata
A piracy court order listed a few domains. The team blocked transfers on every domain in the account, and the customer had to keep pointing out legitimate ones were stuck.Court order pembajakan hanya mencantumkan beberapa domain. Tim memblokir transfer semua domain di akun, dan customer harus berulang kali bilang domain legitimnya ikut tertahan.
✓ Correct handling✓ Penanganan benar
Cross-check the domain list in the order. Restrict only those; unlock everything else and let the customer transfer it normally.Cocokkan daftar domain di order. Batasi hanya yang tercantum; buka semua sisanya dan biarkan customer transfer seperti biasa.
Analogy — a search warrant: it names one room. Officers can't search the whole building because they're already inside. Analogi — surat perintah penggeledahan: isinya menyebut satu ruangan. Petugas nggak boleh menggeledah seluruh gedung cuma karena sudah masuk.
05 · Backups and data delivery05 · Backup dan pengiriman data

Who gets a backup — and how it travelsSiapa yang dapat backup — dan cara mengirimnya

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?

SituationSituasiBackup?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
Police backup delivery protocolProtokol pengiriman backup untuk polisi
  • Archive is AES-256 encryptedArsip terenkripsi AES-256
  • Upload to the abuse-department S3 bucket — never a public oneUpload ke bucket S3 abuse-department — jangan pernah yang publik
  • Send the download URL and the password link separatelyKirim URL download dan link password secara terpisah
  • Password via pwpush: 4 views / 90 days — never open it to testPassword lewat pwpush: 4 kali lihat / 90 hari — jangan dibuka untuk ngetes
  • Provide SHA512 checksums; police may also ask for an MD5 of the encrypted fileSertakan checksum SHA512; polisi juga bisa minta MD5 dari file yang terenkripsi
  • Do not notify the site ownerJangan beri tahu pemilik situs
Analogy — lock and key: you'd never post a locked box and its key in the same envelope. Two channels, so one leak isn't a breach. Analogi — gembok dan kunci: kamu nggak akan mengirim kotak terkunci dan kuncinya dalam satu amplop. Dua jalur, jadi satu kebocoran nggak langsung jadi pelanggaran.
06 · Speed vs verification06 · Kecepatan vs verifikasi

Know when to verify and when to act nowTahu kapan verifikasi dan kapan langsung bertindak

Not 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.

Slow down: an unusual court order to transfer a domainPelan dulu: court order transfer domain yang janggal
Red flags in a real case:Red flag di kasus nyata:
  • Hostinger not named in the order, though we are the registrarHostinger nggak disebut di order, padahal kita registrar-nya
  • Power of Attorney from 2021, with an email that doesn't match the official bar recordPower of Attorney tahun 2021, emailnya nggak cocok dengan data resmi bar association
  • The requesting domain/email is brand newDomain/email si peminta baru banget dibuat

→ Don't transfer. Escalate to Legal to verify authenticity.→ Jangan transfer. Eskalasi ke Legal untuk verifikasi keaslian.

Act now: CSAM from a government hotlineLangsung bertindak: CSAM dari hotline pemerintah
  • Hotlines such as RRT Lithuania verify content before they submitHotline seperti RRT Lithuania memverifikasi konten sebelum melapor
  • Don't ask for more proof — every hour of delay is real harm and legal riskJangan minta bukti tambahan — setiap jam penundaan itu bahaya nyata dan risiko hukum
  • Immediate permanent suspension, no backup; then check related accountsLangsung suspend permanen, tanpa backup; lalu cek akun terkait
  • Auto relation-tracking can miss links (e.g. payment methods without unique IDs), so check manuallyRelation tracking otomatis bisa melewatkan hubungan (mis. metode pembayaran tanpa ID unik), jadi cek manual

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.

Analogy — fire alarm vs. odd parcel: when the fire department rings the alarm, you evacuate first and ask questions later. When a parcel arrives with strange paperwork, you check before you open it. Analogi — alarm kebakaran vs. paket aneh: kalau pemadam kebakaran membunyikan alarm, kamu evakuasi dulu, nanya belakangan. Kalau ada paket dengan dokumen janggal, kamu cek dulu sebelum dibuka.
07 · Real cases07 · Kasus nyata

Sample cases from the teamContoh kasus dari tim

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?

08 · Expert habits08 · Kebiasaan expert

Your pre-action checklistChecklist sebelum bertindak

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.

Is the requester an official body — not a private organisation or a feed?Apakah peminta itu badan resmi — bukan organisasi swasta atau feed?Case: private cybersecurity firmKasus: perusahaan cybersecurity swasta
Does the request name exactly what to suspend, transfer, or provide?Apakah permintaan menyebut persis apa yang harus di-suspend, ditransfer, atau diberikan?Case: piracy order, wrong domains blockedKasus: order pembajakan, domain yang salah terblokir
Court order: is Hostinger named, does the paperwork match official records, is the requester's domain/email new?Court order: apakah Hostinger disebut, apakah dokumennya cocok dengan data resmi, apakah domain/email peminta baru?Case: suspicious transfer orderKasus: order transfer yang mencurigakan
Did the requested service ever exist here, and is the data still retained (e.g. email logs: 180 days)?Apakah service yang diminta pernah ada di sini, dan datanya masih disimpan (mis. log email: 180 hari)?Case: logs for a cancelled email serviceKasus: log untuk email service yang sudah dibatalkan
Related account: do the dates, content, and abuse pattern really match — not just a device ID?Akun terkait: apakah tanggal, konten, dan pola abuse benar-benar cocok — bukan cuma device ID?Case: mass suspension, abuse pre-dated the customerKasus: suspend massal, abuse terjadi sebelum customer ada
UDRP/ADNDRC transfer: did I update the registrant email to the winner's before starting?Transfer UDRP/ADNDRC: sudah update email registrant ke email pemenang sebelum mulai?Case: FOA went to the losing party, domain lostKasus: FOA terkirim ke pihak yang kalah, domain hilang
Am I keeping the authority's identity and the report details away from the customer?Apakah identitas authority dan detail laporan tetap saya rahasiakan dari customer?Rule: use the approved predefinesAturan: pakai predefine yang disetujui
Is it logged in the Register and are my reasons noted in the CRM?Sudah dicatat di Register dan alasanku ditulis di CRM?Rule: mandatory trackingAturan: pencatatan wajib
0 / 8 checkedtercentang
Analogy — a pilot's pre-flight check: experienced pilots still run the list every time, because the mistakes it prevents are the expensive ones. Analogi — pre-flight check pilot: pilot berpengalaman pun tetap menjalankan daftar ini setiap kali, karena kesalahan yang dicegahnya adalah yang paling mahal.
09 · Knowledge check09 · Cek pemahaman