No charge
The intention is for GhostLayer to be available at no charge if it reaches a usable release. No memberships, premium privacy tiers, usage caps, or paid unlocks.
GhostLayer started from a simple question: if browsers, websites, ad networks, analytics systems, and applications are constantly exchanging signals, can a privacy tool reduce how much of that information is useful without making the computer unusable?
Give normal users meaningful privacy controls without forcing them to understand every protocol, cookie, tracker, domain, or fingerprinting API. The system should explain itself and make privacy decisions visible.
Fewer unnecessary tracking connections, less cross-site linkability, clearer information about what applications are contacting, and strong local control without GhostLayer collecting a new profile of its own.
Protection settings, rules, activity history, statistics, and privacy profiles should stay on the user’s device unless a future feature explicitly requires otherwise and the user knowingly enables it.
A privacy tool nobody can leave enabled is not very useful. GhostLayer should offer strict protection while making broken sites or programs easy to diagnose and temporarily allow.
GhostLayer is a personal project created by Bow. Bow is a one-person operation and works hard on every project, from the initial idea and research through design, coding, testing, documentation, and updates.
Please have patience as I work through what is possible and try to make sure things work as intended. There is no set release date for GhostLayer. This concept may take time, change direction, or discover technical limitations along the way.
This site serves as both project notes and a proof of concept. It shows what I would like GhostLayer to achieve and how those ideas might work, but it should not be read as a guarantee that every proposed feature is possible or will be released.
The intention is for GhostLayer to be available at no charge if it reaches a usable release. No memberships, premium privacy tiers, usage caps, or paid unlocks.
The project should not deliberately hold back protection to encourage payment. The purpose is to help people hide and protect their information, not monetize how much privacy they can afford.
The code is intended to be available for people to inspect, edit, learn from, and reuse for free. A clear software license can be included when code is published so those permissions are unambiguous.
Visit Potter Service Projects to explore more of Bow's personal projects and experiments.
While this project is in development, the website should always make clear whether something is a goal, prototype, experimental feature, or tested protection. Privacy software depends on trust, and the product should earn that trust by being clear about its limits.