mirror of
https://github.com/Such-Software/smirk-backend-core.git
synced 2026-10-17 07:21:32 +02:00
- tools/secret-scan.sh now also flags nsec1 Nostr secret keys and *_PEPPER/*_SALT/*INTEGRITY_SECRET hex assignments, the secret classes this backend actually handles (previously only PEM/seed shapes). - .gitignore: *.hex + admin-key* so an operator running inside the checkout cannot commit the raw admin key (create-admin-wallet --out). - PRIVACY.md pointing to the canonical smirk.cash/privacy, framed for self-hosting operators as independent data controllers.
29 lines
1.5 KiB
Markdown
29 lines
1.5 KiB
Markdown
# Privacy Policy
|
|
|
|
The canonical Smirk privacy policy lives at **https://smirk.cash/privacy** and
|
|
describes the data practices of the instance operated by Such Software LLC
|
|
(api.smirk.cash).
|
|
|
|
## For operators who self-host
|
|
|
|
This backend is open source and self-hostable. **If you run your own instance, you
|
|
are an independent data controller for it** and the Such Software policy does not
|
|
speak for you. What your instance receives from wallets that connect to it:
|
|
|
|
- **Monero/Wownero view keys** (to scan for users' incoming funds; a view key
|
|
cannot spend) and their scan/registration state.
|
|
- **Public addresses** for BTC/LTC balance lookups and **signed transactions** to
|
|
broadcast. Recipient address and amount are not sent on broadcast.
|
|
- A one-way **seed fingerprint** (SHA-256) as a non-reversible wallet identifier.
|
|
- If enabled: the **username to npub** mapping published in your NIP-05 directory,
|
|
and, for the relay, encrypted message envelopes (ciphertext only).
|
|
- IP addresses only as a **salted one-way hash**, for rate-limiting.
|
|
|
|
Private keys and seed phrases are never transmitted to the backend.
|
|
|
|
If you offer your instance to others, publish your own privacy policy describing
|
|
how you handle this data, your retention, and your jurisdiction. The knobs that
|
|
affect retention and data exposure (login-event and audit retention, erasure,
|
|
relay retention, landing-page exposure) are documented in
|
|
[docs/operations/CONSOLE.md](docs/operations/CONSOLE.md) and the root `.env.example`.
|