|
|
2nd Semester · Focus: Data Structures in C · Reverse Engineering · Privacy by Design
Computer Science undergrad at FIAP. I build small, hard, focused software — most of it never reaches a public repo.
My day-to-day sits between backend systems, reverse engineering and data privacy as a first-class design constraint, not an afterthought.
If it isn't in RAM, it doesn't exist.
Disposable email built on the opposite principle of every disposable email service: nothing on disk, no analytics, no plaintext tokens. Mailboxes, messages and attachments live only in volatile memory, behind 512-bit cryptographic tokens. A reboot wipes the entire service. By design.
Native Windows tooling, built in stealth mode.
A small portfolio of native Windows software under one umbrella, sharing the same design philosophy:
native performance, zero telemetry, no on-disk surprises, ship as a single signed binary.
One product is free and open-source; the others are proprietary and paid.
Most of what I build assumes someone is going to try to take it apart.
So I do that part first.
snwvlr@fiap:~$ systemctl status snwvlr.service
● snwvlr.service — building things that aren't supposed to leak
Loaded: stealth (proprietary; vendor preset: paranoid)
Active: online (running) since boot
Tasks: orlixys/optimizer, orlixys/orbit, orlixys/photon, korppi-mail, reverse-engineering
Contact: snwvlr@orlixys.com
Memory: volatile — wipes on reboot, by design






