Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
148 changes: 148 additions & 0 deletions docs/accelerator/base44-2026/APPLICATION.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,148 @@
---
title: Secure Pride — Base44 Accelerator application
status: draft-not-submitted
prepared: 2026-11-16
cohort: 2
---
# Secure Pride — Base44 Accelerator application

This is a reviewable draft, not a submitted application. Statements about the proposed Base44 desk describe intended functionality until the build and verification record establishes otherwise. Contact information, traction, and commitments require founder confirmation. No real client or participant data is included.

## Positioning

**Security infrastructure for people who cannot fail safely.**

Secure Pride is building practical, open-source security tools for LGBTQ+ organizations. The accelerator project is a security operations desk modeled on the workflow in [mazze93/touchstone](https://github.com/mazze93/touchstone), adapted to nonprofit partnerships, risk assessment, remediation, and evidence review.

The first use is a significant internal tool for Secure Pride: partner intake → scoped engagement → finding → assigned fix → evidence review → closure or explicit unresolved status. A public demonstration must contain fictional data only. Client records, identities, credentials, attack payloads, and private evidence remain outside the demo.

## 1. Your startup

### Startup name
Secure Pride

### Company website
https://securepride.org/

### Describe your startup in one sentence
Secure Pride builds practical, open-source security tools for LGBTQ+ organizations where a privacy failure can put people at risk.

### What are you building?
I’m building Secure Pride, a cybersecurity nonprofit for LGBTQ+ organizations where a privacy failure can expose identity, interrupt care, or undermine trust. Today, our public tools include a manual text scanner with documented limitations and a draft guide to certificate-based Wi-Fi. The next product is a security operations desk modeled on my Touchstone project: partner intake, scoped engagements, prioritized findings, assigned fixes, evidence review, and governance checks. It will help Secure Pride coordinate support without placing client records or attack payloads in a shared dashboard. The Base44 prototype will demonstrate the workflow using fictional data. I want to validate whether this approach helps small teams complete meaningful security improvements and understand what remains unverified.

### Industry or category
Cybersecurity & Privacy

### Startup location
Durham, North Carolina, United States

### Customer type
B2B — organization-facing; not an assertion that paying customers exist.

### Product stage
Publicly launched applies to Secure Pride’s existing public tools. The proposed Base44 desk is not yet built. If the field is interpreted as the desk’s stage rather than the organization’s, select Prototype/MVP and explain this distinction.

### Startup logo
Optional; not uploaded.

### Main goals by April 6, 2027
By April 6, I aim to interview 10 LGBTQ+ nonprofit operators, recruit three pilot organizations, and validate one repeatable security workflow from assessment through a verified fix. I want to measure completion rates, time to remediation, and whether staff understand the tool’s limits. I also want to test a sustainable funding model that keeps essential protections accessible. The program should help me focus the product, build a useful Base44 application, and replace assumptions about demand with evidence from people doing the work.

These are proposed targets, not achieved traction or agreed pilot commitments. Confirm feasibility before submission.

## 2. Your product and pitch

### Base44 app link
Not available. Build is blocked at Base44 sign-in. Do not substitute a ChatGPT Site, the Touchstone repository, or Secure Pride’s public website for the required Base44 app link.

### How are you using Base44?
Building tailored internal tools, workflows or dashboards.

This selection describes the intended initial use. Do not imply that Secure Pride already relies on a deployed Base44 app.

### How does your Base44 app support the core of your business?
I’m building the Base44 app as Secure Pride’s operations desk: the place to track nonprofit partners, scope security engagements, assign remediation, review evidence, and record unresolved risks. This is central to delivering support consistently as the work grows. The demonstration will use fictional operational metadata, with sensitive material kept outside the app. The intended outcome is a repeatable path from a reported risk to a reviewed fix, with an owner, a next action, and an honest record of what was actually verified.

### Product walkthrough
Optional. Record only after the application works. Show intake → finding → blocked closure → evidence review → permitted closure → export. Include the public-demo limitations.

### Founder video
Required; not recorded or uploaded.

#### Proposed 60-second script
I’m Mazze, the founder of Secure Pride. I work across security research, engineering, and design.

I’m building security infrastructure for people who cannot fail safely. For an LGBTQ+ organization, a privacy failure can expose someone’s identity, interrupt care, or make people afraid to ask for help.

Secure Pride already publishes open-source tools with their limits on the record. Next, I’m building a Base44 operations desk, modeled on my Touchstone project, to connect partner intake, security findings, assigned fixes, and evidence review.

The goal is simple: every risk has an owner, every next step is clear, and a completed task is not automatically treated as a verified fix.

During the accelerator, I want to test that workflow with nonprofit operators and find a sustainable way to keep essential protections accessible.

**Recording gate:** Update the build sentence to match what exists when filmed. Read naturally and time it; this script has not been timed in a recording.

### Pitch deck
Required; no deck file or public deck URL exists yet. The following is proposed slide copy, not a claim that a deck was created.

1. **Secure Pride** — Security infrastructure for people who cannot fail safely.
2. **Problem** — Small LGBTQ+ organizations must manage security risks with limited capacity. Exposure can affect identity, access to care, and trust. Validate these needs with operators; do not present the threat-model scenarios as user research.
3. **First workflow** — Partner intake → scoped assessment → finding → assigned fix → evidence review. One owner and one concrete next action for every open issue.
4. **Product** — A Base44 operations desk inspired by Touchstone’s partner, engagement, finding, and governance model. Show only screenshots from a real build, labeled as a synthetic-data demonstration.
5. **What exists today** — Public manual text scanner, draft Wi-Fi guide, public source and threat model. Scanner misses are documented. Touchstone’s source is a reference implementation, not a deployed Secure Pride integration.
6. **Initial users and distribution** — Proposed users: Secure Pride staff and participating nonprofit operators. Proposed recruitment: direct operator interviews, nonprofit networks, and mission-aligned partners. No confirmed pipeline is asserted.
7. **Alternatives and differentiation** — Spreadsheets, generic task boards, and enterprise security platforms. Hypothesis: a smaller desk that separates a claim, its evidence, and the decision to close is easier to use and more accountable. No superiority or performance claim without comparison.
8. **Sustainability** — Explore grants, donations, and sponsor-funded support. Any paid service or institutional funding model requires validation. No revenue or nonprofit registration/tax status is inferred.
9. **Validation plan** — Proposed targets: 10 interviews, three pilots, one end-to-end workflow. Measure completion, remediation time, and understanding of limits. Establish baseline values before claiming improvement.
10. **Founder and accelerator fit** — Mazze: security research, engineering, design. Base44 supports iteration on the core operations desk; mentorship supports product focus, pilot design, and sustainability. No external credentials, CVEs, customer logos, or investor interest are asserted here.

## 3. Your team

| Field | Draft |
| --- | --- |
| Full name | Mazze LeCzzare Frazer |
| Role | Founder — Security Research, Engineering & Design |
| Email | Founder to provide |
| LinkedIn | https://www.linkedin.com/in/mazze-leczzare |
| Phone | Founder to provide |
| WhatsApp | Founder to provide; form says participants are added to a cohort WhatsApp group |
| Country | United States |
| Time zone | America/New_York — confirm in form |
| Lead contact | Mazze, subject to confirmation |
| Headshot | Optional; not uploaded |
| Other participating team members | Unknown; do not invent |

## 4. Traction

The form marks this section optional. Leave user count, annual recurring revenue, total investment, and funding stage empty until the founder confirms the figures. Unknown does not mean zero.

Suggested qualitative answer, if useful:

> Secure Pride has a public website and inspectable open-source tools, including a manual text scanner and a draft Wi-Fi Enterprise guide. The site publishes the scanner’s limitations and a working threat model. These are evidence of published work, not evidence of customer adoption. I have not supplied verified audience, usage, revenue, or funding figures in this application.

## 5. Screening call and submission

- The form describes a 15-minute interview with the Boardy agent.
- Keep “Call right after I submit” unchecked unless the founder wants an immediate call.
- The page states that booking agrees to Boardy’s terms and privacy policy. Obtain action-time confirmation before accepting a legally binding agreement.
- Leave optional application-marketing permission unchecked.
- Do not submit the application until required assets and contact information are complete and the founder has reviewed the final application.
- No application has been submitted.

## Sources and claim boundaries

Inspected 2026-11-16:
- [Base44 application](https://base44.com/accelerator/apply) — six-step form and required materials.
- [Base44 accelerator overview](https://base44.com/accelerator) — applications close December 12, 2026; program January 12–April 6, 2027; Base44 app must be core to the startup, including a significant internal tool.
- [Secure Pride tools](https://securepride.org/tools/) — public scanner, limitations, draft Wi-Fi guide; Rust/WASM scanner described as built but not deployed.
- [Secure Pride founder](https://securepride.org/founder/) — founder’s work across security research, engineering, and design.
- [Touchstone source snapshot](https://github.com/mazze93/touchstone/tree/1bfbef981efe5da63bc65532bc1b837c322ff8d1) — source inspection only. See BUILD.md for the adaptation and limitations.

## Outstanding work

1. Sign in to Base44 and execute BUILD.md.
2. Verify the actual generated app using VERIFICATION.md; preserve failures.
3. Replace this file’s app status and add the exact public demo link only after it exists.
4. Create the deck from the copy above and record the founder video.
5. Confirm contacts, participants, targets, stage, sustainability language, and any traction figures.
6. Review the actual program agreements before submitting.
Loading
Loading