Email aliasing, self-hostable, crypto accepted.
Safing SPN
Portmaster and SPN privacy network using per-connection multi-hop routing, priced in cards, Bitcoin or Monero.
safing.io
- KYC: light
- AT
- Evidence and facts →
Portmaster and SPN privacy network using per-connection multi-hop routing, priced in cards, Bitcoin or Monero.
Evidence and facts
Evidence and facts
Specs
Review analysis, source material, related services, and history
Analysis
Safing's Portmaster and SPN network route each connection through multiple hops with per-app routing, built by Safing ICS Technologies GmbH in Vienna and funded through EU NGI/NLnet, Netidee and FFG grants rather than venture capital.
This is not a no-account service: the privacy policy records account, tax-country and payment data, and while Bitcoin or Monero payment reduces exposure, it does not remove account metadata.
A match for people wanting per-app multi-hop routing from an Austrian, grant-funded provider who accept some retained account and payment metadata.
Corporate identity
Registry-sourced, not audited. The facts below come from cited web research rather than a direct registry query. Each claim links its own source.
- LEGAL ENTITY
- Safing ICS Technologies GmbHsource ↗
- REGISTRATION NO.
- FN 464654ssource ↗
- INCORPORATED IN
- Austriasource ↗
- INCORPORATED ON
- 2017-01-13source ↗
- REGISTERED ADDRESS
- Heinrich Bablik-Straße 17a/4, 2345 Brunn am Gebirge, Austriasource ↗
- ULTIMATE OWNER
- Nicholas Pestellsource ↗
Frequently Asked Questions
Is identity verification required?
The recorded KYC level is "light". Account/payment metadata exists for paid SPN/Portmaster Pro. Privacy policy lists username, email for some payment/account contact paths, country/calling code for Austrian tax, and payment data; BTC/XMR payments reduce but do not remove account metadata.
Which payment methods are accepted?
Please check the provider site for accepted payment methods.
Where is it available?
Recorded availability: GLOBAL.
Is the operator based in a Five Eyes country?
No. The recorded jurisdiction is AT, which is not a Five Eyes country. This is jurisdiction context and does not by itself establish that a service is safer or less safe.
How are identity, operator, and evidence fields reported?
Identity exposure is level 1 of 4. Hosted operator data has not been established. Jurisdiction is shown as context, not a safety verdict. Source coverage is verified evidence, last reviewed 2026-08-25, and recorded risk is standard.
Sources and history
Terms and privacy policy
No changes to the documents we watch since we started checking on 9 Aug 2026. Last checked 9 Aug 2026.
Evidence basis: Claims on this page are linked to published sources for comparison, not certification, audit, endorsement, or recommendation; read the methodology and coverage map before relying on an entry.