Loading…
Loading…
> Last updated: October 10, 2026_
If you register for an event as a guest, without a KrackedDevs account, we collect two things: a display name and an email address. Providing them is voluntary, but we cannot register you for an event without them.
We use them for three purposes: to record your registration, to email you about that registration (a confirmation email containing a link to manage or cancel it), and, for the display name only, to show who is attending on the event's public page. The name field is labeled as publicly displayed at the point you fill it in; providing it is your consent to that display.
Guest email addresses are never used for marketing. No newsletter enrollment, no promotional email, and no marketing contact profile is created from a guest registration.
If you do not confirm your registration via the emailed link (following it and confirming on the page it opens), the registration record is deleted after 7 days. Guest registrations, whatever their status, are anonymized (display name and email address removed) 90 days after the event ends, unless you have claimed the registration into a KrackedDevs account. Email delivery logs follow the same schedule: guest email addresses are removed from delivery logs 90 days after the event.
Transactional emails to guests are sent through Resend, our email delivery provider, which processes your email address on our behalf for delivery only. Resend may process this data on servers outside Malaysia.
Every email we send you about a registration contains a link to manage or cancel it. Cancelling withdraws your consent: your name is removed immediately and you receive no further emails about that registration. Your email address is retained solely to honor the stop request and to prevent the cancelled registration from being re-created, and is removed on the same 90-day post-event schedule. If you no longer have the email, contact us at hello@krackeddevs.com or through our contact page and we will cancel it for you.
You may request access to, or correction of, your guest registration data the same way, by email or through the contact page.
If you opt in, you consent to KrackedDevs sharing specific parts of your builder profile — your name, email address, role and experience level, skills, Malaysian state, projects-showcased count, and startups-listed count — with our ecosystem grant partners, for the sole purpose of matching you to grants, programmes, and funding opportunities you may be eligible for.
“Ecosystem grant partners” means Malaysian (and, where relevant, regional) startup-ecosystem grant agencies, government-linked programme operators, accelerators, and funding bodies. Each partner that receives your data is a separate, independent data controller, responsible for its own handling of that data under applicable law. You can see the current list of partners we share with, updated as it changes, in the “Current partners” note below.
Sharing happens only if you have opted in, and only within the purpose and partner category described above. If you have not opted in, we do not share your profile with any partner for these purposes. You may withdraw your consent at any time from your account settings, with no effect on your KrackedDevs account. We do not sell, trade, or rent your personal data.
We are not currently sharing builder profiles with any partner. When we begin sharing with a specific partner, we will name them here. Any sharing takes place only under a signed data-sharing agreement with that partner.
If you choose to, you can tell us three things about yourself on your profile: your age band, your gender, and your occupation status (for example student, working, or founder). All three are optional. You can skip them, answer only some of them, or choose Prefer not to say, and nothing about your KrackedDevs account changes either way.
We use these answers for three purposes: to understand who our community is, to plan classes and programs, and to report overall community statistics to sponsors and partners. Sponsors and partners only ever receive totals, such as the percentage of members who are students. Your individual answers are never displayed on your profile, member card, or any public page, and are never shared with any third party.
Answers are only ever counted in aggregate, and any group smaller than ten members is hidden even from our own admin reports. This is designed so that no combination of statistics points to one person. We collect age as a coarse band, never a date of birth. Members under 18 appear only inside the same aggregate totals and are never singled out or targeted.
You can change or clear your answers at any time from your profile. Clearing them removes the data. Your answers are stored only as long as your account exists and are deleted with it. To request access to, correction of, or deletion of your data, contact us through our contact page.
Jika anda mahu, anda boleh memberitahu kami tiga perkara tentang diri anda pada profil anda: lingkungan umur, jantina, dan status pekerjaan (contohnya pelajar, bekerja, atau pengasas). Ketiga-tiganya adalah pilihan. Anda boleh melangkaunya, menjawab sebahagian sahaja, atau memilih Tidak Mahu Nyatakan, dan akaun KrackedDevs anda tidak terjejas sama sekali.
Jawapan ini digunakan untuk tiga tujuan: memahami komuniti kami, merancang kelas dan program, dan melaporkan statistik keseluruhan komuniti kepada penaja dan rakan kongsi. Penaja dan rakan kongsi hanya menerima jumlah keseluruhan, contohnya peratusan ahli yang merupakan pelajar. Jawapan individu anda tidak akan dipaparkan pada profil anda, kad ahli, atau mana-mana halaman awam, dan tidak dikongsi dengan mana-mana pihak ketiga.
Jawapan hanya dikira secara agregat, dan mana-mana kumpulan yang kurang daripada sepuluh ahli disembunyikan walaupun daripada laporan pentadbir kami sendiri. Reka bentuk ini bertujuan supaya tiada gabungan statistik boleh menunjuk kepada mana-mana individu. Kami mengumpul umur sebagai lingkungan sahaja, bukan tarikh lahir. Ahli bawah 18 tahun hanya muncul dalam jumlah agregat yang sama dan tidak akan disasarkan secara berasingan.
Anda boleh menukar atau memadamkan jawapan anda pada bila-bila masa melalui profil anda. Jawapan anda disimpan hanya selagi akaun anda wujud dan dipadamkan bersamanya. Untuk akses, pembetulan, atau pemadaman data anda, hubungi kami melalui halaman hubungi kami.
Some services let you connect your KrackedDevs account to them, for example by pressing a “Connect with KrackedDevs” button on that service. When you do, KrackedDevs shares only the details listed on the consent screen you approve at that moment. For a basic connection this is your KrackedDevs username and member ID. The screen names the service, the details, and what the service uses them for; nothing outside that list is shared.
Connecting is always your choice. You can disconnect a service at any time from your profile dashboard. Disconnecting stops that service from receiving anything further from KrackedDevs and immediately invalidates the credentials it held. Details the service already saved into its own records are governed by that service's privacy policy, which is linked on the consent screen.
We keep a record of each connection and disconnection, including the exact version of the consent text you approved, so we can show what was agreed and when. Each connected service is responsible in its own right for the details it receives, under its own privacy policy.
Sesetengah perkhidmatan membolehkan anda menyambungkan akaun KrackedDevs anda kepadanya, contohnya dengan menekan butang “Sambung dengan KrackedDevs” di perkhidmatan itu. Apabila anda berbuat demikian, KrackedDevs hanya berkongsi butiran yang disenaraikan pada skrin persetujuan yang anda luluskan ketika itu. Untuk sambungan asas, butiran tersebut ialah nama pengguna dan ID ahli KrackedDevs anda. Anda boleh memutuskan sambungan pada bila-bila masa dari papan pemuka profil anda; selepas itu perkhidmatan tersebut tidak lagi menerima apa-apa daripada KrackedDevs. Kami menyimpan rekod setiap sambungan dan pemutusan, termasuk versi teks persetujuan yang anda luluskan.
If you apply to KD Labs, we keep the answers you give on the application form. These are your project's name, where it is today, what it does and who pays for it. They also include your repository and live links, your team, the hours you can give each week and why you are applying now. Applying is your choice. The repository link, live link and team are optional. The other answers are needed, and so is ticking the box to accept the KD Labs rules. Without them, you cannot send the form. If you name teammates or customers, name only people who are happy to be named. We also keep when you sent your application, when you last edited it and when you accepted the rules.
To apply, you need a KrackedDevs (KD) account that is active and not banned, with a GitHub account linked to it. KD Labs is for members who are 18 or older. You confirm this when you accept the rules. When you send, we record the username and ID of that GitHub account. Then we ask GitHub four things about it. When was the account made? How many contributions did you make in the last 90 days? On how many days did you make a contribution, in the last 30 days and in the last 90? How many public repositories did you commit to this month?
We ask with our own GitHub key, not through your GitHub sign-in. So GitHub shows us only your public work, plus a count of private contributions if you have chosen to show them on your GitHub profile. To read these facts, we do not ask GitHub for the names or the code of your repositories. If we cannot get these facts from GitHub when you send, your application still goes in, and a panelist may ask GitHub again while it is open.
We also add your KD level, when you joined KD and, if you listed a startup on KD as its founder, the stage of the newest active one.
We count how many days in the last 30 you made a contribution. From that count we give the panel a hint: strong for 5 days or more, borderline for 1 to 4 days, and weak for none. The hint sets the order of the panel's list of applications waiting for a decision. If we could not get the facts from GitHub, the hint says not read. Your application then sits after those with a hint until a panelist gets the facts. The hint is not shown on your application page, krackeddevs.com/labs/apply. It never decides. A panelist does.
We use all of this to decide your application and to tell you the decision. If you get a seat, we also use it to keep a record of your seat and to show your seat on the public KD Labs page, krackeddevs.com/labs. Before we give anyone a seat, we check that their KD account is active and not banned.
Your application is read by the KD Labs panel, which is every KrackedDevs admin. No other KD member can open it. The panel sees your answers, the facts above, the hint, and your name and username on KD. Panelists can write notes on it for each other. Those notes are not shown on your application page. If a panelist applies, another panelist decides. On the panel's pages, the panelist who applied cannot add notes to their own application or see its hint or the panel's notes on it. None of this is shown on any public page.
When the panel decides, or a panelist seats you without an application, we send you a notification on KD and an email to the confirmed email address on your KD account. The email can include your project's name, your seat number and a note the panel writes to you. That note can also show on your application page. If your account is banned or not active, we send no notification and no email. We also skip the email if earlier email to that address bounced or was marked as spam.
Our service providers handle this data only on our behalf. Among them, Supabase stores it, Vercel runs the KD website, Resend delivers the decision email and Sentry records site errors. Sentry's error reports and logs can include your KD account ID and IP address. To read the facts, we send your GitHub username to GitHub, and your GitHub ID if your username has changed. GitHub and some of these providers store or process data on servers outside Malaysia.
If you hold a seat, the public KD Labs page shows your seat number and that the seat is held. Once you have accepted the rules, it also shows when the lab starts and your name, initials, username and avatar, with a link to your KD profile. If you applied, you accepted the rules when you sent your application, so your name shows as soon as the panel gives you a seat. If a panelist seats you without an application, your seat shows as reserved, with no name, until you accept the rules on your application page. If your profile is set to stay out of the member directory, or you have no KD username, your seat shows as “A KD Labs builder”, with no name, username or avatar. If your KD account is banned or not active, your seat shows as open.
The public KD Labs page never shows your location, your email address, your application, the hint or the panel's notes. It is built fresh on every visit, so a change shows the next time it loads. We cannot remove copies that search engines or others have already saved.
In My Lab you can add up to three lab projects. If you connect a GitHub repository to a project through the KD GitHub App, we keep the repository's GitHub ID, its name, whether it is private and the App installation it sits under. When GitHub tells us about a push or a merged pull request made by your GitHub account on a connected repository, we record which project it was for and when it arrived. We never keep its content in your Labs record: no code, commit titles, messages, links or branch names. Repository names are shown only to you in My Lab and to KD admins, and no public page ever names a repository. If GitHub fails to deliver one of these notices to us, we keep that delivery's GitHub ID and the repository's GitHub ID in KD's admin log, so that a lost delivery is looked for and resent before your seat is judged.
GitHub sends KD a notice for every repository you let the KD GitHub App see, not only the one you connect. Each notice first lands in KD's delivery queue, which holds what GitHub sent until it has been processed. That can include the repository's owner and name, the branch, the GitHub IDs of the accounts involved, the first line and link of each commit, the title and link of any pull request or issue, the names of the repositories you gave the App, and the account the App is installed on. We delete a processed notice from the queue 90 days after it was processed. A notice that could not be processed is kept as evidence of the failure. We do not use those commit lines in KD Labs.
If you connect Dr Rick, the KD Labs bot on Telegram, we store your Telegram chat ID and username on your seat so that Rick can message you, and the reminder hours you choose. Your messages with Rick pass through Telegram, which handles them under its own privacy policy and may process them on servers outside Malaysia. You can disconnect Rick in My Lab at any time. That clears the chat ID and username from your seat, and they are cleared on their own after your seat reopens.
When you check in with Rick, your messages, your first name, your hex state and streak, whether your seat is on leave, which day of the ladder you are on, how many entries you have posted today, today's counts of pushes and merged pull requests on each of your lab projects, and the names of your lab projects are sent to the AI model service KD uses to run Rick, so that it can draft your entry, together with the entry drafted so far, including any launch link. The service is the DeepSeek V4.1 Flash model, which KD runs on Microsoft Azure in KD's own account and reaches through KD's own gateway, so DeepSeek, the company, does not receive it. Microsoft's abuse checks may select a sample for review by automated systems and, if flagged, by its authorised staff. No repository name is sent. The reasons you give for grace are never sent, but anything you type to Rick in an ordinary message is, whatever it is about. Nothing else from your account is sent. The service has no access to KD's database. It may process this data on servers outside Malaysia. KD keeps the conversation for 30 days, then deletes it. Nothing Rick drafts is published until you press the button.
The entries you confirm, which are the story of a code day, a launch with its link, or a sales step, appear on krackeddevs.com/labs with the project's name, the time and the name on your builder card. If you have chosen to stay out of the member directory, the page shows “A KD Labs builder” and “A lab project” instead of your name and your project's name. Staying out of the member directory hides your name and any launch link, not what you write: the text of your entries stays public. Your hex shows its state, your streak and when you last shipped, to anyone. If you are in the member directory, your profile also shows your lab projects with their stage and your longest streak, and keeps showing them after your seat reopens. We never show your location or your email address. Describe a customer by company or role, never by a person's name: the panel hides any entry that names a person. The panel can strike or hide an entry and tells you why. If your seat reopens, your entries stay on the ledger as the record of your time in the lab.
Every KD admin can read your check-ins, including hidden and struck ones, your grace requests and their reasons, whether Rick is connected and your Telegram username, and the names of your connected repositories and whether they are private. We delete the reason you give for grace, and the panel's note on it, 90 days after the panel decides, you withdraw the request, or it lapses, so please do not share medical details in it. The copy of the panel's note in the notice we send you in the app is deleted with your other KD notifications, after 180 days at most. The request's dates and outcome stay with your seat record. A check-in draft you never post is deleted 30 days after it was started.
We tell you about your seat in the app, by email and on Telegram when Rick is connected. We keep a record of which notice went out on which channel for 90 days, so that none goes out twice, and then delete it. KD's scheduled jobs for the lab, which decide seats and send these notices, run on Trigger.dev on KD's behalf, which may process this data on servers outside Malaysia.
If your KD account is deleted, your seat, your lab projects, their ship records and your entries are deleted with it. Our admin log also keeps a line, with ids and dates only, when a repository is connected, disconnected or lost, when you connect or disconnect Rick, when a grace request is granted, declined or lapses, when an entry is struck, hidden or shown again, when a seat reopens or is held back, and when GitHub fails to deliver a notice or a lost one is recovered. These lines stay too, as do the log lines described above, even if your KD account is deleted.
If your application is declined, or you withdraw it, we delete it 30 days after that. If it stays on the waitlist, we delete it 210 days after the panel put it there. An accepted application is kept while you hold your seat and deleted 30 days after the seat closes. A seat closes when you go five days without a ship, counted from the lab's start, the day you are seated, the end of a grace, or your last ship; when a seat given to you without an application is not accepted within a week of the lab starting or of your being seated, whichever is later; or when your KD account is banned or not active. The panel can give you grace for up to four weeks, and your seat waits. Your seat record stays while you have a KD account: the seat number, how, when and by whom you were seated, and when you accepted the rules. If a panelist seats you without an application, the record also keeps their reason, which is not sent to you. We delete that reason 30 days after the seat closes.
A few short records stay after your application is deleted. Our admin log keeps a line for each decision, and for each time a panelist seats a member without an application. Each line holds your KD account ID, the outcome, when, which panelist and your seat number if you got one. It never holds your answers or any note. Our email log keeps your email address and a line saying whether a KD Labs email was sent to it. We do not delete these lines on a schedule, and they stay even if your KD account is deleted. Your notification on KD only says that the panel has decided. We delete it once it is 90 days old and you have read it, and after 180 days in any case.
While your application waits for a decision, you can edit your answers on your application page. An edit replaces your earlier answers. Once it is on the waitlist, you cannot edit it. While it waits for a decision or is on the waitlist, you can withdraw it there, and we delete it 30 days later.
To see what your application page does not show, such as the hint or the panel's notes, contact us through our contact page. Use the same page to ask us to correct or delete what we hold about you in KD Labs, or to ask a question or make a complaint. If you want to give up your seat, or do not want a seat a panelist gave you, tell us there too. To take your name off the public KD Labs page, ask us there to set your profile to stay out of the member directory. That also takes you out of the directory and other KD member lists. Anyone you named in your application can contact us the same way.
Jika anda memohon untuk menyertai KD Labs, kami menyimpan jawapan yang anda berikan dalam borang permohonan. Jawapan itu ialah nama projek anda, peringkat projek itu hari ini, apa yang projek itu lakukan dan siapa yang membayar untuknya. Jawapan itu juga termasuk pautan repositori dan pautan projek anda yang sedang beroperasi, pasukan anda, jumlah jam yang boleh anda peruntukkan setiap minggu dan sebab anda memohon sekarang. Memohon adalah pilihan anda. Pautan repositori, pautan projek yang sedang beroperasi dan pasukan tidak wajib diisi. Jawapan lain wajib diisi, dan kotak untuk menerima peraturan KD Labs wajib ditanda. Tanpa semua ini, anda tidak dapat menghantar borang itu. Jika anda menamakan ahli pasukan atau pelanggan, namakan hanya mereka yang rela dinamakan. Kami juga menyimpan masa anda menghantar permohonan, masa anda terakhir menyuntingnya dan masa anda menerima peraturan.
Untuk memohon, anda perlu mempunyai akaun KrackedDevs (KD) yang aktif dan tidak disekat, dengan akaun GitHub yang dipautkan kepadanya. KD Labs adalah untuk ahli yang berumur 18 tahun atau lebih. Anda mengesahkannya apabila anda menerima peraturan. Apabila anda menghantar permohonan, kami merekodkan nama pengguna dan ID akaun GitHub tersebut. Kemudian kami bertanya empat perkara kepada GitHub. Bilakah akaun itu dibuat? Berapa banyak sumbangan yang anda buat dalam 90 hari yang lalu? Pada berapa hari anda membuat sumbangan, dalam 30 hari yang lalu dan dalam 90 hari yang lalu? Dalam berapa banyak repositori awam anda membuat commit pada bulan ini?
Kami bertanya menggunakan kunci GitHub kami sendiri, bukan melalui log masuk GitHub anda. Oleh itu, GitHub hanya menunjukkan hasil kerja awam anda kepada kami, serta jumlah sumbangan persendirian jika anda memilih untuk memaparkannya pada profil GitHub anda. Untuk membaca fakta ini, kami tidak meminta nama atau kod repositori anda daripada GitHub. Jika kami tidak dapat memperoleh fakta ini daripada GitHub semasa anda menghantar permohonan, permohonan anda tetap dihantar, dan ahli panel boleh bertanya kepada GitHub sekali lagi selagi permohonan anda masih terbuka.
Kami juga menambah tahap KD anda, bila anda menyertai KD dan, jika anda menyenaraikan syarikat pemula di KD sebagai pengasasnya, peringkat syarikat pemula aktif anda yang terbaharu.
Kami mengira pada berapa hari dalam 30 hari yang lalu anda membuat sumbangan. Daripada kiraan itu, kami memberi panel satu petunjuk: “Strong” (kuat) untuk 5 hari atau lebih, “Borderline” (sederhana) untuk 1 hingga 4 hari, dan “Weak” (lemah) jika tiada. Petunjuk ini menentukan susunan senarai permohonan yang menunggu keputusan dalam paparan panel. Jika kami tidak dapat memperoleh fakta daripada GitHub, petunjuk itu ialah “Not read” (tidak dibaca). Permohonan anda kemudian diletakkan selepas permohonan yang mempunyai petunjuk sehingga ahli panel memperoleh fakta tersebut. Petunjuk ini tidak dipaparkan pada halaman permohonan anda, krackeddevs.com/labs/apply. Petunjuk ini tidak pernah membuat keputusan. Keputusan dibuat oleh ahli panel.
Kami menggunakan semua maklumat ini untuk membuat keputusan tentang permohonan anda dan untuk memaklumkan keputusan itu kepada anda. Jika anda mendapat tempat, kami juga menggunakannya untuk menyimpan rekod tempat anda dan untuk memaparkan tempat anda pada halaman awam KD Labs, krackeddevs.com/labs. Sebelum memberi sesiapa tempat, kami menyemak bahawa akaun KD mereka aktif dan tidak disekat.
Permohonan anda dibaca oleh panel KD Labs, iaitu setiap pentadbir KrackedDevs. Tiada ahli KD lain boleh membukanya. Panel melihat jawapan anda, fakta di atas, petunjuk tersebut, serta nama dan nama pengguna anda di KD. Ahli panel boleh menulis catatan pada permohonan itu untuk dibaca oleh ahli panel lain. Catatan tersebut tidak dipaparkan pada halaman permohonan anda. Jika ahli panel memohon, ahli panel lain yang membuat keputusan. Dalam paparan panel, ahli panel yang memohon tidak boleh menambah catatan pada permohonannya sendiri, dan tidak boleh melihat petunjuk atau catatan panel padanya. Tiada satu pun daripada maklumat ini dipaparkan pada mana-mana halaman awam.
Apabila panel membuat keputusan, atau ahli panel memberi anda tempat tanpa permohonan, kami menghantar pemberitahuan kepada anda di KD dan e-mel ke alamat e-mel yang telah disahkan pada akaun KD anda. E-mel itu boleh mengandungi nama projek anda, nombor tempat anda dan catatan yang ditulis oleh panel kepada anda. Catatan itu juga boleh dipaparkan pada halaman permohonan anda. Jika akaun anda disekat atau tidak aktif, kami tidak menghantar pemberitahuan mahupun e-mel. Kami juga tidak menghantar e-mel itu jika e-mel terdahulu ke alamat tersebut melantun atau ditanda sebagai spam.
Penyedia perkhidmatan kami mengendalikan data ini hanya bagi pihak kami. Antaranya, Supabase menyimpannya, Vercel menjalankan laman web KD, Resend menghantar e-mel keputusan dan Sentry merekodkan ralat laman. Laporan ralat dan log Sentry boleh mengandungi ID akaun KD dan alamat IP anda. Untuk membaca fakta tersebut, kami menghantar nama pengguna GitHub anda kepada GitHub, dan ID GitHub anda jika nama pengguna anda telah berubah. GitHub dan sesetengah penyedia ini menyimpan atau memproses data pada pelayan di luar Malaysia.
Jika anda memegang tempat, halaman awam KD Labs memaparkan nombor tempat anda dan bahawa tempat itu sudah dipegang. Setelah anda menerima peraturan, halaman itu juga memaparkan bila KD Labs bermula, serta nama, huruf awal nama, nama pengguna dan avatar anda, berserta pautan ke profil KD anda. Jika anda memohon, anda telah menerima peraturan semasa menghantar permohonan, jadi nama anda dipaparkan sebaik sahaja panel memberi anda tempat. Jika ahli panel memberi anda tempat tanpa permohonan, tempat anda dipaparkan sebagai “Reserved” (dikhaskan), tanpa nama, sehingga anda menerima peraturan pada halaman permohonan anda. Jika profil anda ditetapkan supaya dikecualikan daripada direktori ahli, atau anda tiada nama pengguna KD, tempat anda dipaparkan sebagai “A KD Labs builder”, tanpa nama, nama pengguna atau avatar. Jika akaun KD anda disekat atau tidak aktif, tempat anda dipaparkan sebagai “Open seat” (tempat kosong).
Halaman awam KD Labs tidak pernah memaparkan lokasi anda, alamat e-mel anda, permohonan anda, petunjuk atau catatan panel. Halaman ini dibina semula pada setiap lawatan, jadi sebarang perubahan dipaparkan pada kali seterusnya halaman itu dimuatkan. Kami tidak dapat memadamkan salinan yang telah disimpan oleh enjin carian atau pihak lain.
Dalam My Lab anda boleh menambah sehingga tiga projek makmal. Jika anda menyambungkan repositori GitHub kepada sesuatu projek melalui Aplikasi GitHub KD, kami menyimpan ID GitHub repositori itu, namanya, sama ada ia persendirian dan pemasangan Aplikasi tempat ia berada. Apabila GitHub memberitahu kami tentang push atau pull request yang digabungkan oleh akaun GitHub anda pada repositori yang disambungkan, kami merekodkan projek yang berkaitan dan bila notis itu sampai. Kami tidak pernah menyimpan kandungannya dalam rekod Labs anda: tiada kod, tajuk commit, mesej, pautan atau nama cabang. Nama repositori hanya dipaparkan kepada anda dalam My Lab dan kepada pentadbir KD, dan tiada halaman awam yang menamakan sebarang repositori. Jika GitHub gagal menghantar salah satu notis ini kepada kami, kami menyimpan ID GitHub penghantaran itu dan ID GitHub repositori dalam log pentadbir KD, supaya penghantaran yang hilang dicari dan dihantar semula sebelum tempat anda dinilai.
GitHub menghantar kepada KD satu notis bagi setiap repositori yang anda benarkan Aplikasi GitHub KD melihat, bukan hanya yang anda sambungkan. Setiap notis mula-mula sampai ke baris gilir penghantaran KD, yang menyimpan apa yang GitHub hantar sehingga ia diproses. Ini boleh termasuk pemilik dan nama repositori, nama cabang, ID GitHub akaun yang terlibat, baris pertama dan pautan setiap commit, tajuk dan pautan mana-mana pull request atau isu, nama repositori yang anda berikan kepada Aplikasi, serta akaun tempat Aplikasi dipasang. Kami memadamkan notis yang telah diproses daripada baris gilir itu 90 hari selepas ia diproses. Notis yang tidak dapat diproses disimpan sebagai bukti kegagalan. Kami tidak menggunakan baris commit itu dalam KD Labs.
Jika anda menyambungkan Dr Rick, bot KD Labs di Telegram, kami menyimpan ID sembang dan nama pengguna Telegram anda pada tempat anda supaya Rick boleh menghantar mesej kepada anda, serta jam peringatan yang anda pilih. Mesej antara anda dan Rick melalui Telegram, yang mengendalikannya mengikut dasar privasinya sendiri dan mungkin memprosesnya pada pelayan di luar Malaysia. Anda boleh memutuskan sambungan Rick dalam My Lab pada bila-bila masa. Ini mengosongkan ID sembang dan nama pengguna daripada tempat anda, dan kedua-duanya dikosongkan dengan sendirinya selepas tempat anda dibuka semula.
Apabila anda mendaftar masuk bersama Rick, mesej anda, nama pertama anda, keadaan hex dan rentetan hari anda, sama ada tempat anda sedang bercuti, hari anda berada pada tangga, bilangan catatan yang anda hantar hari ini, bilangan push dan pull request yang digabungkan hari ini pada setiap projek makmal anda, serta nama projek makmal anda dihantar kepada perkhidmatan model AI yang digunakan oleh KD untuk menjalankan Rick, supaya ia boleh merangka catatan anda, bersama catatan yang telah dirangka setakat ini, termasuk pautan pelancaran jika ada. Perkhidmatan itu ialah model DeepSeek V4.1 Flash, yang dijalankan oleh KD di Microsoft Azure dalam akaun KD sendiri dan dicapai melalui get laluan KD sendiri, jadi DeepSeek, syarikat itu, tidak menerimanya. Semakan penyalahgunaan Microsoft mungkin memilih satu sampel untuk disemak oleh sistem automatik dan, jika ditanda, oleh kakitangannya yang diberi kuasa. Tiada nama repositori dihantar. Sebab yang anda berikan untuk tempoh tangguh (grace) tidak pernah dihantar, tetapi apa-apa yang anda taip kepada Rick dalam mesej biasa dihantar, walau tentang apa pun. Tiada apa-apa lagi daripada akaun anda dihantar. Perkhidmatan itu tidak mempunyai akses kepada pangkalan data KD. Ia mungkin memproses data ini pada pelayan di luar Malaysia. KD menyimpan perbualan selama 30 hari, kemudian memadamkannya. Tiada apa-apa yang dirangka oleh Rick diterbitkan sehingga anda menekan butang.
Catatan yang anda sahkan, iaitu kisah hari kod, pelancaran beserta pautannya, atau satu langkah jualan, dipaparkan di krackeddevs.com/labs bersama nama projek, masanya dan nama pada kad pembina anda. Jika anda memilih untuk dikecualikan daripada direktori ahli, halaman itu memaparkan “A KD Labs builder” dan “A lab project” sebagai ganti nama anda dan nama projek anda. Mengecualikan diri daripada direktori ahli menyembunyikan nama anda dan sebarang pautan pelancaran, bukan apa yang anda tulis: teks catatan anda kekal awam. Hex anda memaparkan keadaannya, rentetan hari anda dan bila kali terakhir anda menghantar, kepada sesiapa sahaja. Jika anda berada dalam direktori ahli, profil anda juga memaparkan projek makmal anda dengan peringkatnya dan rentetan hari terpanjang anda, dan terus memaparkannya selepas tempat anda dibuka semula. Kami tidak pernah memaparkan lokasi atau alamat e-mel anda. Huraikan pelanggan mengikut syarikat atau peranan, bukan nama seseorang: panel menyembunyikan mana-mana catatan yang menamakan seseorang. Panel boleh membatalkan atau menyembunyikan catatan dan memberitahu anda sebabnya. Jika tempat anda dibuka semula, catatan anda kekal pada lejar sebagai rekod masa anda di makmal.
Setiap pentadbir KD boleh membaca daftar masuk anda, termasuk yang disembunyikan atau dibatalkan, permintaan tempoh tangguh (grace) anda beserta sebabnya, sama ada Rick disambungkan beserta nama pengguna Telegram anda, dan nama repositori anda yang disambungkan serta sama ada ia persendirian. Kami memadamkan sebab yang anda berikan untuk tempoh tangguh, dan catatan panel padanya, 90 hari selepas panel membuat keputusan, anda menarik balik permintaan itu, atau permintaan itu luput, jadi sila jangan kongsi butiran perubatan di dalamnya. Salinan catatan panel dalam notis yang kami hantar kepada anda di aplikasi dipadamkan bersama pemberitahuan KD anda yang lain, selepas 180 hari paling lama. Tarikh dan hasil permintaan itu kekal bersama rekod tempat anda. Draf daftar masuk yang tidak anda hantar dipadamkan 30 hari selepas ia dimulakan.
Kami memaklumkan anda tentang tempat anda dalam aplikasi, melalui e-mel dan di Telegram apabila Rick disambungkan. Kami menyimpan rekod notis mana yang dihantar melalui saluran mana selama 90 hari supaya tiada notis dihantar dua kali, kemudian memadamnya. Tugas berjadual KD untuk makmal, yang memutuskan tempat dan menghantar notis ini, dijalankan oleh Trigger.dev bagi pihak KD, yang mungkin memproses data ini pada pelayan di luar Malaysia.
Jika akaun KD anda dipadamkan, tempat anda, projek makmal anda, rekod penghantarannya dan catatan anda turut dipadamkan. Log pentadbir kami juga menyimpan satu baris, dengan ID dan tarikh sahaja, apabila repositori disambungkan, diputuskan atau hilang, apabila anda menyambung atau memutuskan Rick, apabila permintaan tempoh tangguh diluluskan, ditolak atau luput, apabila catatan dibatalkan, disembunyikan atau dipaparkan semula, apabila tempat dibuka semula atau ditahan, dan apabila GitHub gagal menghantar notis atau notis yang hilang dipulihkan. Baris ini kekal, seperti baris log yang diterangkan di atas, walaupun akaun KD anda dipadamkan.
Jika permohonan anda ditolak, atau anda menarik baliknya, kami memadamkannya 30 hari selepas itu. Jika permohonan anda kekal dalam senarai menunggu, kami memadamkannya 210 hari selepas panel meletakkannya dalam senarai itu. Permohonan yang diterima disimpan selagi anda memegang tempat anda dan dipadamkan 30 hari selepas tempat itu ditutup. Tempat ditutup apabila anda tidak menghantar apa-apa selama lima hari, dikira dari permulaan makmal, hari anda diberi tempat, tamatnya tempoh tangguh, atau penghantaran terakhir anda; apabila tempat yang diberikan kepada anda tanpa permohonan tidak diterima dalam masa seminggu selepas makmal bermula atau selepas anda diberi tempat, mengikut yang lebih lewat; atau apabila akaun KD anda disekat atau tidak aktif. Panel boleh memberi anda tempoh tangguh (grace) sehingga empat minggu, dan tempat anda menunggu. Rekod tempat anda kekal selagi anda mempunyai akaun KD: nombor tempat, bagaimana, bila dan oleh siapa anda diberi tempat, serta bila anda menerima peraturan. Jika ahli panel memberi anda tempat tanpa permohonan, rekod itu juga menyimpan sebab yang diberikan oleh ahli panel tersebut, yang tidak dihantar kepada anda. Kami memadamkan sebab itu 30 hari selepas tempat itu ditutup.
Beberapa rekod ringkas kekal selepas permohonan anda dipadamkan. Log pentadbir kami menyimpan satu baris bagi setiap keputusan, dan bagi setiap pemberian tempat tanpa permohonan. Setiap baris menyimpan ID akaun KD anda, hasil, masa, ahli panel yang terlibat dan nombor tempat anda jika anda mendapat tempat. Log ini tidak pernah menyimpan jawapan anda atau sebarang catatan. Log e-mel kami menyimpan alamat e-mel anda dan satu baris yang menyatakan sama ada e-mel KD Labs telah dihantar ke alamat itu. Kami tidak memadamkan baris ini mengikut jadual, dan baris ini kekal walaupun akaun KD anda dipadamkan. Pemberitahuan anda di KD hanya menyatakan bahawa panel telah membuat keputusan. Kami memadamkannya apabila usianya mencapai 90 hari dan anda telah membacanya, dan selepas 180 hari dalam apa jua keadaan.
Semasa permohonan anda menunggu keputusan, anda boleh menyunting jawapan anda pada halaman permohonan anda. Suntingan menggantikan jawapan anda yang terdahulu. Setelah permohonan itu berada dalam senarai menunggu, anda tidak boleh menyuntingnya lagi. Semasa permohonan anda menunggu keputusan atau berada dalam senarai menunggu, anda boleh menarik baliknya di halaman itu, dan kami memadamkannya 30 hari kemudian.
Untuk melihat apa yang tidak dipaparkan pada halaman permohonan anda, seperti petunjuk atau catatan panel, hubungi kami melalui halaman hubungi kami. Gunakan halaman yang sama untuk meminta kami membetulkan atau memadamkan maklumat yang kami simpan tentang anda dalam KD Labs, atau untuk bertanya soalan atau membuat aduan. Jika anda mahu melepaskan tempat anda, atau tidak mahu tempat yang diberikan oleh ahli panel, beritahu kami di halaman itu juga. Untuk mengeluarkan nama anda daripada halaman awam KD Labs, minta kami di halaman itu untuk menetapkan profil anda supaya dikecualikan daripada direktori ahli. Ini juga mengeluarkan anda daripada direktori itu dan senarai ahli KD yang lain. Sesiapa yang anda namakan dalam permohonan anda boleh menghubungi kami dengan cara yang sama.