PROJECT · CRYPTOGRAPHY

BiuCrypt.

The proposed BiuCrypt would make file and folder protection clearer through guided operations and integrity checks. The current code is experimental planning work.

Future concept · experimental code · no product release

STATUS FUTURE CONCEPT
FORMAT DESKTOP UTILITY
FOCUS FILE PROTECTION
LAST UPDATEDOCT 2026
CONCEPT SUMMARY

Protection with clear boundaries.

BiuCrypt explores how file protection can feel understandable and deliberate, with a workflow that keeps the user informed before, during, and after an operation.

PLANNED FEATURES

Security in the workflow.

Guided protection

Planned capability: A focused flow keeps important choices visible and reduces ambiguity around each operation.

Integrity-aware handling

Planned capability: Protected content is handled with validation and clear feedback throughout the process.

Controlled operations

Planned capability: Progress and cancellation states help keep longer file and folder tasks understandable.

THE USER JOURNEY

A useful problem comes first.

Who would use it?

People who need a clear file-protection workflow and an understandable way to restore their own data.

The problem to solve

Encryption choices can hide recovery risks. A useful interface must explain the selected file, output location and consequences of losing access information.

A proposed everyday flow

Choose a file, confirm a safe output location, protect it and verify a restoration copy before removing the original.

NEXT IMPLEMENTATION STEPS

A plan to validate, then build.

Proposed milestones, not completed deliverables.

  1. Define the file and recovery model

    Describe failure handling, metadata and the boundaries of the proposed protection.

  2. Use established implementations

    Prototype using maintained cryptographic libraries rather than inventing a new algorithm.

  3. Validate round trips and interruptions

    Test corruption, wrong keys and interrupted writes while preserving originals.

Project status: This page is a future product plan. Repository code is experimental and does not represent a released, validated, or deployment-ready application.