Security & Privacy

Private pitch-deck handling. Human decisions.

EvalLense keeps pitch decks, workspace access, and report delivery controlled. AI prepares the review. A person decides what happens next.

Why this needs control

Decks and results carry sensitive information

Pitch decks often include strategy, financials, founder details, and selection outcomes. That information should not move freely or leak through open links.

  • Strategy

    A deck can include plans, positioning, and market strategy.

  • Financials

    Revenue, pricing, burn, or fundraising details need controlled access.

  • Founder details

    Team backgrounds and founder details should stay inside the review flow.

  • Review outcome

    Scores, notes, and shortlist decisions can affect funding, selection, and reputation.

  • Controlled workspace

    Each batch stays inside a controlled workspace

    Evaluation runs inside a workspace owned by the organizer. Access is scoped to the people and roles that belong to that project.

    A controlled, private workspace where a batch's decks, scores and reports stay scoped to authorized people
  • Organizer-owned project

    One organizer owns each project in MVP

    In the MVP, each project belongs to one organizer. That organizer owns the decks, evaluations, and reports.

  • Publish gate

    Intake opens only after publishing

    Participants submit through /e/<slug>. The page is public only after the organizer publishes the project. Before that, it returns 404.

Access control

Access is enforced below the UI

Access is not handled only by the interface. Sessions, roles, database policies, and server-only keys decide what each request can see.

GuardrailSession boundary
How it works

Sessions live in httpOnly cookies. Client-side scripts cannot read the token directly.

GuardrailDatabase rules
How it works

Postgres applies row-level security. Organizers can read and write only the projects tied to their account.

GuardrailServer-only keys
How it works

Service-role and AI Gateway keys stay on the server. Admin operations run only after an explicit admin check.

GuardrailPublic gate
How it works

The public /e/<slug> page opens only after the organizer publishes the project. Before that, it returns 404.

Glass illustration: a pitch deck flows through the organizer's authorized workspace into a locked private report
Report delivery

Reports are shared on purpose

Reports should move through the organizer's workspace, not through accidental public access. Participant-facing report sharing is post-MVP.

  • Shared deliberately, not leaked

    A report reaches someone only when the organizer chooses to share it. Participant-facing sharing comes after MVP.

Human-in-the-loop

The final decision stays human

EvalLense prepares the analysis. The organizer reviews it, sets the final scores, and decides how the report is used. AI does not become the final judge.

  • AI analysis is advisory

    AI Total Score is a reference. It does not rank participants by itself.

  • Human owns the final score

    Ranking is built from the organizer's final scores. The organizer decides how the report is used.

An AI-to-human handoff where AI prepares the analysis and a person owns the decision
Get started

Run a controlled pilot on your own decks

Book a demo and see how EvalLense handles decks, access, reports, and final decisions in one controlled flow.