Security & privacy

The product exists to keep sensitive data on your machine. The design follows from that.

Where data goes

The companion binds to localhost by default. Your prompts are processed in-process on your machine.
We operate no servers in the data path. The only thing that reaches a cloud AI tool is the cleaned, regenerated prompt — which is the entire purpose.
The storefront (this website) sees your email, name, and payment via Paystack. It never sees a prompt.

The audit log

Each scan appends one JSON line: entity types, counts, the AI tool, timing. Original values are hashed with a per-install salt (128-bit truncation) and never written in clear. The line is safe to forward to a SIEM; it cannot be reversed into the data it protected. Keep the per-install salt on the machine — do not ship it alongside the log.

The redaction corpus

Used by the admin workbench. Stores the synthetic replacement (which is fake by construction), the recogniser, the score, and the surrounding sentence with every detected span masked. Original values are salted hashes. It never leaves the machine.

Licence integrity

Purchased licences are signed with our private Ed25519 key, held only on the storefront backend. The desktop app embeds the matching public key and verifies the signature offline. The app cannot forge a licence and we cannot read your data — the keypair only proves a licence is genuine and untampered.

Fail-closed guarantees

Companion unreachable → the extension blocks the send.
Licence missing/expired/seat-exceeded → blocked with a clear reason.
Prompt box can't be located after a site redesign → blocked, not passed through.

The product never trades a silent leak for convenience.

Reporting an issue

Security reports to hello@raphaelamponsah.com. We respond within five working days.

Need a hand? hello@raphaelamponsah.com