Quick exit: leave this site now

#16DAYS of Activism against Gender-Based Violence

16 days. 16 conversations. Safer platforms for women, girls & children.

Code for Dignity is a 16-day hybrid hackathon running alongside the daily #16DAYS conversations. It turns community dialogue into open-source digital infrastructure built to defend women and girls online.

When
November 25 to December 10, 2026
Daily at
12:00 PM ET
Where
X Spaces + Discord

Ensure Justice · Protect Survivors · End Impunity

The problem

Digital violence is scaling faster than moderation can handle.

Tech-Facilitated Gender-Based Violence (TFGBV), including targeted doxxing, deepfake generation, and bot-driven hate campaigns, is scaling faster than standard content moderation can handle. Victims are routinely gaslit by tech interfaces, while corporate frameworks fail to provide actionable, localised protection or legally sound evidence mechanisms.

The campaign

#16DAYS OF ACTIVISM against Gender-Based Violence is an annual international campaign. It kicks off on 25 November, the International Day for the Elimination of Violence against Women & Girls, and runs until 10 December, Human Rights Day.

Lianna Adams has hosted it for the past four years to create awareness and hold solution-finding conversations that challenge violence against women and girls.

Code for Dignity runs in sync with those conversations. Each daily conversation is a live user-research module. Its last 15 minutes deliver a Dignity prompt that hackathon participants use to iterate, prototype, and build.

What to build

Anything small that reduces digital harm.

Build anything small that reduces digital harm to women, girls or children, or makes a tool safer by design. Improving a build you already have counts.

  • A reporting flow
  • A safety check-up
  • An evidence organiser
  • A support finder
  • Safer default settings
  • A plain-language explainer

How it works

From conversation to public good.

  1. Nov 25 to Dec 10

    Conversation

    Daily conversations covering the four tracks of the #16DAYS OF ACTIVISM campaign.

  2. Nov 25 to Dec 10

    Prompt

    Each conversation ends with a 15-minute Dignity prompt on the day's topic.

  3. Any time

    Build

    One small build in any no-code or low-code tool.

  4. Dec 8

    Submit

    The build, a 3-minute demo, and a one-page safety note.

  5. Dec 8 to 9

    Select

    Builds are selected to be presented on December 10.

  6. Dec 10

    Showcase

    Live demos and showcase.

  7. Dec 10

    Gallery

    A public gallery, a briefing pack to platforms, and an archive in the Code for Dignity Commons.

The 16 days

Every day: a conversation, a prompt, a build.

12:00 PM ET on X Spaces + Discord . Open a day for its conversation angle, Dignity prompt, 10-minute task and solution-building prompt. Join the Discord server to take part.

Block 1 Protect Survivors

Day 1Wed 25 NovThe State of Digital Violence: From “Online Drama” to Structural Harm

Digital abuse is not a communications problem; it is a rights, safety, and equality problem. Explore how harassment, stalking, image abuse, doxxing, and gendered disinformation converge into offline risk.

Dignity prompt“What would a digital world look like if a woman’s safety did not depend on her willingness to disappear from it?”

10-minute task

Map one survivor journey across platforms, devices, services, and offline consequences; mark every point where harm can escalate.

Solution-building prompt

Build a TFGBV harm map: a shared, privacy-preserving taxonomy that helps teams identify abuse patterns, escalation risks, and affected groups without collecting identifiable survivor data.

Day 2Thu 26 NovDigital Footprints: Who Can Find You, Track You, and Reconstruct Your Life?

Move beyond “use strong passwords.” Examine metadata, shared calendars, tagged photos, delivery records, fitness apps, public registries, and cross-platform inference.

Dignity prompt“What is the minimum amount of my life that an app truly needs to know?”

10-minute task

Audit a common app or service: list data collected, inferred, retained, shared, and visible to another account holder.

Solution-building prompt

Prototype a footprint minimiser: a checklist or browser extension that flags high-risk exposures, suggests privacy actions, and never requires uploading personal data.

Day 3Fri 27 NovSurvivor-Centred Security: Protection Without Surveillance

Safety tools often recreate coercive control by monitoring survivors “for their own good.” Ask: who holds the power, who can see the data, and who can turn the tool off?

Dignity prompt“How do we protect someone without making them feel watched, managed, or disbelieved?”

10-minute task

Redesign a hypothetical “safety app” around consent: what must be optional, encrypted, local-only, time-limited, or survivor-controlled?

Solution-building prompt

Build a consent-first safety profile: local, encrypted templates for trusted contacts, check-in preferences, emergency escalation, and automatic data expiry.

Day 4Sat 28 NovDigital Safe Houses: Access, Anonymity, and Low-Bandwidth Safety

A safe digital space is not only a website; it must work for people with shared devices, limited data, fear of discovery, disability, or unstable connectivity.

Dignity prompt“What does safety look like when privacy cannot be assumed at home?”

10-minute task

Sketch three user contexts: shared phone, no personal email, low bandwidth. Identify failure points in a typical support-service journey.

Solution-building prompt

Prototype a low-friction digital safe-house entry point: pseudonymous access, quick exit, minimal data, offline-capable resources, and clear “what happens to what I type” notices.

Block 2 Ensure Justice

Day 5Sun 29 NovWeaponised Narratives: Gendered Disinformation and Coordinated Harassment

Abuse is often narrative warfare: reputational attacks, false accusations, sexualized rumors, and coordinated pile-ons designed to silence women in public life.

Dignity prompt“How do we counter a lie without amplifying it or putting the targeted person on trial?”

10-minute task

Analyze a fictional coordinated-harassment scenario. Identify signals of coordination versus ordinary disagreement, and the risks of automated labeling.

Solution-building prompt

Build a narrative-risk toolkit: detection of coordinated patterns, draft response templates, evidence-preservation guidance, and support pathways, without publishing accusations or identifying targets.

Day 6Mon 30 NovSynthetic Violence: Deepfakes, NCII, and the Right to Be Believed

Synthetic media turns humiliation into scalable abuse. The issue is not only detection; it is rapid takedown, evidence preservation, victim support, and preventing re-victimization.

Dignity prompt“If a fake image of me appeared tomorrow, what would I need in the first hour, day, and week?”

10-minute task

Create a first-72-hours response map: document, report, request removal, seek support, and protect mental health, without requiring the survivor to repeatedly explain the abuse.

Solution-building prompt

Prototype a synthetic-abuse response companion: consent-based evidence capture, platform-report preparation, takedown tracking, and links to legal/psychosocial support.

Day 7Tue 1 DecSafety by Design: Build for the Worst User, Not the Ideal User

Most products are designed for a calm, well-resourced user. Ask what happens when a user is panicked, stalked, coerced, or using a device controlled by someone else.

Dignity prompt“What does this product do when the person using it is afraid?”

10-minute task

Threat-model one feature: who could misuse it, who could be harmed, what data could be exposed, and what default would reduce that risk?

Solution-building prompt

Produce a safety-by-design checklist and apply it to a prototype: risk assessment, privacy defaults, abuse scenarios, human escalation, and transparency.

Day 8Wed 2 DecDigital Evidence: Justice Without Re-Traumatisation

Survivors are often asked to become forensic investigators. Explore how evidence can be preserved credibly while reducing repeated disclosure, disbelief, and institutional harm.

Dignity prompt“What would justice feel like if I did not have to prove my humanity before my case?”

10-minute task

Map the evidence journey from disclosure to court. Identify where evidence is lost, where the survivor must repeat themselves, and where bias may enter.

Solution-building prompt

Build a digital-evidence preservation prototype: timestamped, hash-verified, exportable evidence bundles with survivor-controlled sharing and clear legal-context guidance.

Block 3 End Impunity

Day 9Thu 3 DecWhen Platforms Fail: Content Moderation as a Public Safety Issue

Moderation is not just deletion. Failures include under-enforcement, over-removal, opaque appeals, language bias, and inconsistent treatment across regions and identities.

Dignity prompt“What would fair moderation look like if the person reporting had the same standing as the person reported?”

10-minute task

Compare three moderation outcomes for the same abusive content: removal, no action, and account restriction. Identify transparency and appeal gaps.

Solution-building prompt

Prototype a moderation accountability layer: structured reports, plain-language decisions, appeal tracking, and anonymised pattern reporting for civil-society oversight.

Day 10Fri 4 DecWellbeing of Survivors and Responders: Care Is Infrastructure

Moderators, helpline workers, and activists absorb trauma. Burnout is not a personal failing; it is a design and staffing failure.

Dignity prompt“Who cares for the people who hold other people’s pain?”

10-minute task

Design a shift protocol for a responder: intake limits, debrief prompts, escalation rules, and boundaries for after-hours contact.

Solution-building prompt

Build a responder wellbeing module: caseload signals, debrief prompts, peer-support routing, and configurable boundaries, without exposing sensitive case content.

Day 11Sat 5 DecProtecting Girls Before Harm: Cyberbullying, AI Manipulation, and Digital Resilience

Prevention must not put responsibility on girls to avoid abuse. Focus on age-appropriate agency, trusted adults, platform accountability, and education that does not shame victims.

Dignity prompt“How do we teach girls to navigate digital spaces without teaching them that abuse is their fault?”

10-minute task

Rewrite a victim-blaming safety message into an agency-based, rights-based message for a specific age group.

Solution-building prompt

Prototype an age-appropriate digital resilience toolkit: scenario-based learning, trusted-adult connection, reporting support, and privacy controls designed with young people.

Day 12Sun 6 DecBystanders and Community Response: From Watching to Safe Intervention

Bystanders often want to help but fear retaliation or do not know what helps. Explore bystander power, collective documentation, and support that does not endanger the target.

Dignity prompt“What can a community do in ten minutes that makes a targeted person less alone?”

10-minute task

Design a bystander decision tree: witness, assess risk, support privately, document safely, escalate, or disengage.

Solution-building prompt

Build a community response toolkit: private support messages, safe documentation prompts, resource routing, and coordination features that avoid public pile-ons.

Block 4 The Safety Net

Day 13Mon 7 DecPrevention and Educational Impact: Measuring What Actually Changes

A hackathon can accidentally reward flashy demos. Ask how to measure reduced harm, increased confidence, improved reporting, better institutional response, and survivor trust.

Dignity prompt“What evidence would tell us this tool made someone safer, not merely that people used it?”

10-minute task

Define one outcome, one indicator, one data source, and one ethical guardrail for a prototype.

Solution-building prompt

Create an impact measurement canvas: safety outcomes, survivor experience, accessibility, privacy, unintended harms, and community accountability.

Day 14Tue 8 DecData in the Machine: AI, Bias, and the Politics of Training Data

AI trained on the internet inherits gendered stereotypes, victim-blaming narratives, and unequal language coverage. Ask who is represented, who is misclassified, and who bears the error.

Dignity prompt“If this system makes a mistake about me, who will notice, who will correct it, and who will be harmed?”

10-minute task

Audit a proposed AI feature: inputs, training assumptions, error cases, human oversight, appeal path, and data-minimization requirements.

Solution-building prompt

Build an AI harm and bias review card: intended use, excluded uses, known biases, human-in-the-loop requirements, data retention limits, and redress process.

Submissions are due today: the build, a 3-minute demo, and a one-page safety note.

Day 15Wed 9 DecFrom Prototype to Policy: Ending Impunity Through Design and Accountability

Technology cannot substitute for law, enforcement, platform accountability, and survivor-led policy. Ask how code can create evidence, visibility, and pressure for institutional change.

Dignity prompt“What must change outside the app for justice inside the app to be possible?”

10-minute task

Translate one prototype into a policy ask: what rule, standard, disclosure, or duty would make the intervention systemic rather than heroic?

Solution-building prompt

Produce a prototype-to-policy brief: problem, evidence gap, recommended safeguard, responsible institution, implementation steps, and survivor-informed success measures.

Day 16Thu 10 DecLive Demos Showcase: From Prototypes to Public Goods

Human Rights Day. All builders present their build and receive live feedback and questions from the audience.

Prepare a responsible showcase

Problem, users, safety assumptions, data practices, limitations, maintenance plan, and community governance.

After the demos

A public gallery, a briefing pack to platforms, and an archive in the Code for Dignity Commons.

December 10 · Live Demos Showcase

How builds are evaluated.

Submit by December 8: the build, a 3-minute demo, and a one-page safety note. Selected builders present live on December 10.

Safety & Privacy by Design

  • Does the tool respect user data privacy?
  • Is there any risk that this tool could be weaponised by abusers if misused?
  • Are there safety fallbacks, such as a quick-exit button?

Trauma-Informed UX

  • Is the interface calm, accessible, and easy to use under high stress?
  • Does the language avoid cold, clinical, or re-traumatising terms?

Feasibility & Impact

  • Can this solution realistically be deployed in the next 3 to 6 months?
  • Does it solve a real gap mentioned in the daily conversations?

Technical & Execution

  • How functional is the prototype, or how well thought out is the no-code/low-code design?
  • Is the logic solid and ready for development?

Design principles for builders

Six rules every build carries.

  1. Do no additional harm

    No scraping, public shaming, location exposure, facial recognition, or retention of sensitive evidence without explicit, revocable consent.

  2. Survivor control

    Survivors decide what is stored, shared, escalated, or deleted.

  3. Safety by design

    Assess risks before features; make privacy and safety defaults, not optional add-ons.

  4. Intersectionality

    Design for girls, disabled women, LGBTQ+ people, migrants, rural users, low-bandwidth users, and people facing multiple forms of discrimination.

  5. Accountability over automation

    AI can triage or explain; it should not make final decisions about a person’s safety, credibility, or case.

  6. Open but protected

    Open-source the non-sensitive infrastructure, while keeping survivor data, threat intelligence, and case details closed.

Mentors

People in your corner.

  • Shazeeda Bhola

    Strategy Director, Firsthand

  • Stephanie Stranko

    Founder & CEO, ikwe.ai

  • Nidhi Srivastava

    Founder & CEO, DigiArmorX

  • Maria Fernanda

    Social Protection Specialist

  • LeeLoo

    Founder, LeeLoo AI and École H (AI school for neurodivergent kids). Works at the intersection of public & international law (FR-US).

Questions

Code for Dignity, in short.

What is Code for Dignity?
Code for Dignity is a 16-day hackathon that runs alongside the daily #16DAYS of Activism against Gender-Based Violence conversations. Each conversation ends with a 15-minute Dignity prompt, and participants use it to build small tools that reduce digital harm to women, girls and children.
When is Code for Dignity?
Code for Dignity runs from November 25 to December 10, 2026. Conversations take place every day at 12:00 PM Eastern Time. Builds are due on December 8 and the live demos showcase is on December 10, Human Rights Day.
Where does Code for Dignity take place?
It takes place online, on X Spaces and on the Code for Dignity Discord server.
Do I need to know how to code to take part?
No. A build can be made in any no-code or low-code tool, and improving a build you already have counts. You can also come only to listen to the conversations.
What can I build?
Anything small that reduces digital harm to women, girls or children, or makes a tool safer by design. Examples include a reporting flow, a safety check-up, an evidence organiser, a support finder, safer default settings, or a plain-language explainer.
What do I submit, and by when?
Submit by December 8, 2026: the build, a 3-minute demo, and a one-page safety note. Selected builders present live on December 10.
How are builds evaluated?
Builds are evaluated on four criteria: safety and privacy by design, trauma-informed user experience, feasibility and impact, and technical execution.
What is #16DAYS of Activism against Gender-Based Violence?
It is an annual international campaign. It starts on November 25, the International Day for the Elimination of Violence against Women and Girls, and runs until December 10, Human Rights Day. Lianna Adams has hosted #16DAYS conversations for the past four years.
What is tech-facilitated gender-based violence (TFGBV)?
Tech-facilitated gender-based violence is abuse carried out through digital tools, including targeted doxxing, deepfake generation and bot-driven hate campaigns.
How do I join Code for Dignity?
Register your interest below and join the Discord server. You can choose to listen to the conversations, build in the hackathon, or both.

Join in

Register your interest for Code for Dignity.

Come to listen, come to build, or both. Conversations run daily at 12:00 PM ET on X Spaces + Discord, November 25 to December 10.

I would like to

What happens to what I type
  • Only what you type above is stored, with the time you sent it. Your IP address and device details are not stored.
  • It is kept in private storage that only the organiser can open. It is not shown on this site.
  • It is used to contact you about Code for Dignity and #16DAYS, and nothing else.
  • To have your details deleted, email lianna.adams@gmail.com.

Contact