Salto never asks for your phone number or email, keeps no server able to read you, seals every message with post-quantum encryption and hides who talks to whom. With no network at all, nearby phones carry it. Try it right here: cut the connection, write, bring a relay within range.
Next Switch 1: cut the internet. Your real connection is not touched.
This switch is part of the demo. Your real connection is not touched.
Your browser right now: online Real reading. Turn your own Wi-Fi off: this page keeps working.
Cut the internet first.
B is a phone that agreed to relay. It cannot read your message.
The sealed envelope goes A to B, then B to C; C's acknowledgement comes back the same way.
Ready
Step 1: cut the internet to start.
Turn the internet back on and choose how the message travels. Content, transport and metadata are protected by different layers, and a reconnection never uploads your local data on its own.
End-to-end encryption: only your contact can read, on every route.
The onion route or tunnel hides your traffic from the local network and your internet provider.
Type a message, pick a route and send it. Each column shows what that party actually receives: your contact reads it, everyone in between handles a sealed block. The sealing below really runs in your browser.
| What is protected | Nearby (no internet) | Private (Tor) | Hardened (mixnet) | Fast (tunnel) |
|---|---|---|---|---|
| Message content | End-to-end encrypted | End-to-end encrypted | End-to-end encrypted | End-to-end encrypted |
| Who you talk to | Hidden: nearby devices carry a sealed envelope | Hidden from your network and from relays | Hidden, even from a global observer | Hidden from your network; sealed sender at the relay |
| Your IP address | Not used | Hidden from the relay | Hidden from the relay | Hidden from the relay; known to the exit operator |
| When you send | Depends on who is nearby | Visible to someone watching both ends | Blurred by mixing and cover traffic | Visible to the exit operator |
| Delay | Minutes to hours | About a second | Seconds to minutes | Lowest |
| Where it works | Within Bluetooth or local Wi-Fi range | Most networks; bridges where Tor is blocked | Where the mixnet is reachable | Most networks; easier to block |
As designed. The Salto app is in development; this demo seals your text with AES-GCM in your browser to show the size and look of what relays carry.
End-to-end encryption. Each message is sealed on your phone for your contact's devices only, whatever the route. Relays, servers and networks carry a block they cannot open.
Keys. Keys are created on your device and never leave it. Each message uses a fresh key (forward secrecy), and the conversation recovers after a compromised key at the next exchanges (post-compromise security). You verify a contact by scanning their code in person.
Post-quantum. The first key exchange is designed as a hybrid of X25519 and ML-KEM, as in PQXDH, so traffic recorded today does not help a future quantum computer. Post-quantum protection of every later message is a research track.
Identity. No phone number and no email. Each relationship uses its own identifier, so two contacts cannot link you by comparing IDs.
Metadata. Sealed sender hides who sends a block; padding hides its length; the Private and Hardened routes hide your address, and the mixnet also hides when you send. The Fast route protects content, but its exit operator sees your address.
| What is protected | Salto (as designed, in development) | Signal | Telegram |
|---|---|---|---|
| End-to-end encryption by default | Every message, every route | Yes, all messages and calls | No: cloud chats use client-server encryption; secret chats are opt-in and one-to-one |
| Group chats end to end | Yes | Yes | No |
| Phone number to sign up | No | Yes; optional usernames hide it from others | Yes, or a number bought on Fragment |
| Post-quantum protection | Hybrid X25519 + ML-KEM key exchange; later messages: research track | PQXDH since 2023; SPQR post-quantum ratchet rolling out since October 2025 | Not documented: classical Diffie-Hellman in secret chats |
| Sender hidden from the server | Sealed sender | Sealed sender; the server still sees the recipient | No: the service keeps cloud messages and contacts, and IP and device data for up to 12 months |
| Works with no internet at all | Nearby delivery over Bluetooth or local Wi-Fi (demo on this site) | Not documented: needs an internet connection | Not documented |
Sources · checked 4 Nov 2026 Signal: PQXDH ↗ Signal: SPQR ↗ Signal: sealed sender ↗ Signal: usernames ↗ Telegram FAQ ↗ Telegram: secret chats ↗ Telegram privacy policy ↗
Salto is in development: these tables compare its design with services available today, on stated criteria, from the sources listed (checked on 4 November 2026). They claim no advantage that has not been demonstrated.
After the envelope, the bigger picture: how relays, storage and computing take part across regions. Pick a layer, touch a region, pause to inspect, then open the full Atlas.
Synthetic data generated for this demonstration and published with the same rules as production: regional aggregation only, at least 20 participants per published cell, complementary suppression of device types, rare flows between regions removed, the latest period withheld, values rounded to tens. In production the observation window and the last refresh are shown here.
To protect participants, SALTO keeps the exact locations of relays, nodes and devices private. The Atlas shows delayed regional activity. Animated connections represent aggregated flows or clearly identified simulations. Areas with too few participants are grouped or hidden.
Regions
Switch between an ordinary messenger and Salto. Each line is something a server, a network observer or a stolen database could learn about you, with the layer Salto uses to take it away.
Ordinary messenger: how messaging services commonly work. Salto: the layer that removes each item.
Required to sign up and linked to every chat.
Never asked. Your identity is a key pair created on your phone.
Ed25519 + ML-DSA identity keys →Readable by the operator on some apps, or in cloud backups.
Sealed end to end with post-quantum keys, on every chat and every group.
PQXDH · Triple Ratchet · MLS →Visible to the server on every message.
Sealed sender: relays route envelopes without knowing who sent them.
Sealed sender →Seen by the server and by your internet provider.
Hidden behind onion or mixnet routes. Offline mode opens no internet route at all.
Tor (Arti) · Nym mixnet →Timing alone reveals relationships.
Cover traffic and mixing delays blur the timing.
Loopix cover traffic →Length gives away photos, voice notes and keywords.
Padded to fixed size buckets: 1, 4, 32 or 256 KB.
Padmé padding →Uploaded to find friends.
Never uploaded. Contacts are added by QR code or in person, then checked by key transparency.
Key transparency →Copied to every service that asks.
Checked once, then only zero-knowledge proofs: over 18, eligible country, one real person.
Salto Pass · zk-SNARKs →With a connection, Salto never falls back to an ordinary messenger. Your message passes seven protections before and after it leaves the phone. Press play and follow it.
Your text is padded to a fixed size bucket, so its length gives nothing away.
Padmé padding · 1 / 4 / 32 / 256 KB
First contact uses PQXDH: X25519 and ML-KEM-1024 combined, so a conversation recorded today cannot be opened by a future quantum computer.
PQXDH · ML-KEM-1024 · HKDF-SHA-256
Every message gets a fresh key from the Triple Ratchet (Double Ratchet + SPQR). One stolen key opens one message, never the past and never the future.
Double Ratchet · SPQR · forward secrecy · post-compromise security
XChaCha20-Poly1305 encrypts and authenticates the envelope. Your identity travels inside, never on the outside.
XChaCha20-Poly1305 · sealed sender
The envelope is wrapped in onion layers. Each relay removes one and only learns the next hop: none knows both you and your contact.
Tor (Arti) · Nym Sphinx packets · cover traffic
It waits, still sealed, in a mailbox. Your contact fetches it with private information retrieval, so the mailbox cannot tell whose mail was read.
PIR · rotating mailbox IDs
Your contact opens it and signs an acknowledgement that comes back the same hidden way. Only then does your phone show Received.
Signed acknowledgement · hop receipt
| Default behaviour | Salto | Signal | Telegram | |
|---|---|---|---|---|
| Sign up without a phone number | Yes | Beta option | No | No |
| End-to-end encryption on every chat, groups included | Yes | Yes | Yes | No: Secret Chats only, one to one |
| IP address hidden by built-in onion or mixnet routing | Yes | No | No | No |
| Cover traffic against timing analysis | Yes | No | No | No |
| Messages travel with no internet, phone to phone | Yes | No | No | No |
| Identity checks with zero-knowledge proofs | Yes: Salto Pass | No | No | No |
Defaults compared from each provider's public documentation, November 2026. Trade names belong to their owners.
Seven layers of open, state-of-the-art cryptography, woven into one seamless app. Pick a layer to see what protects you.
Defence in depth: each ring is an independent layer around your message.
Phones find each other and hop messages along, with no network at all.
Every message is sealed end to end, with group keys that refresh and post-quantum key exchange.
When you go online, you choose how: fast tunnel, onion routing or a mixnet that hides timing.
Salto Pass proves who may do what, with one unlinkable pseudonym per service and nothing else revealed.
Handovers, entitlements and tasks are proven precisely, without revealing who you are.
Four assets, named networks, and keys that sign on a device that never goes online.
An assistant that runs on your device, with remote tasks bounded by a policy engine.
Established primitives on one side, SALTO protocols on the other. Tap a term to see the problem it solves and where it works in the app.
Salto Pass is a private KYC for the whole Salto network. Your documents are checked once; from then on, services receive mathematical proofs, never your identity.
proof: age ≥ 18 ✓proof: eligible country ✓proof: unique person ✓pseudonym for this serviceNever your name, photo, document number or address.
Used for card access, payouts, fair campaign rewards and partner onboarding, wherever a check is required.
Salto means "jump" in Spanish and in Italian. In the demo, every time your message passes from one device to the next, that is literally a salto: A to B is the first jump, B to C the second.
Run the demo above: each hop you trigger is a salto.
Secure Asynchronous Local Transport Overlay: the transport layer at the heart of Salto. Each word maps to something you just saw.
Follow a message off-grid. See what a relay can learn. Verify a file for yourself.
What you just saw Two halos in turn: the relay accepts the envelope, then the recipient confirms delivery.
Private conversations, nearby or far
What you just saw Traffic enters the tunnel and follows the route you chose. When the route breaks, sending pauses instead of leaking.
Protect a connection
What you just saw Fragments are stored and checked; one fragment fails its recovery check and is refused.
Put your devices to work
What you just saw The request is handled on the phone. The remote branch opens only after you approve the mission.
Local and connected assistant
What you just saw A payment is prepared field by field, signed on your device, then broadcast through a private route.
BTC, ETH, USDT, USDC wallet
What you just saw The transaction travels to an offline signer by QR code, gets signed there and comes back sealed.
Cold storage for your keys
What you just saw The daily limit slides down, then the card is frozen with one tap.
Physical or virtual crypto card
What you just saw An alias is created for one service, counts down, then expires on its own.
Email aliases, SMS numbers, profiles
What you just saw The internet signal disappears, your library stays lit, a pack arrives from a nearby device and its source opens.
Your offline knowledge library
What you just saw Two devices pair, the tunnel lights up to the gateway, then stops when the quota is reached or the session is revoked.
Share a connection nearby
What you just saw A kiosk broadcasts, a phone without app reads, a ticket waits, the guide arrives verified.
Public documents without an app, guides on request
What you just saw A file becomes a fingerprint and a seal; change one byte and the seal breaks.
Check files, receipts and approvals yourself
What you just saw Three proofs are checked - age, country, one real person - while the document itself stays hidden.
One private KYC for the whole network
What you just saw Two aggregated regions light up, an arc appears and a pulse travels along an aggregated link (demo data).
The world network, aggregated
Write a message, cut the internet, bring a relay within range, then the recipient. The panel shows what the relay can actually observe in this scenario, and what encryption keeps from it.
Simulated The radio route is simulated: nothing leaves this browser tab. Sizes and times come from the scenario, not from a real network.
Write a message, then cut the internet.
Salto turns trust into something you can check. Every handover, every task and every payment leaves a precise proof that anyone involved can verify.
Install Salto, add a friend by QR and send your first message, even with no signal.
Install Salto, add a contact by scanning their QR code and send a message. No account, no phone number and no internet needed for nearby chat.
Each hop covers the Bluetooth or Wi-Fi range of a phone. With relays in between, your message jumps from device to device to reach people well beyond your own range.
No. Relays carry sealed envelopes that only the recipient can open. Per-relationship identities and Hardened mode keep what the network can observe to a minimum.
Storage fragments are encrypted and unreadable to the node that holds them. Compute tasks run isolated, and only with the data you choose to send.
It works for calls, SMS and most sign-ups. Some banks and platforms only accept long-term carrier numbers for one-time codes.
No. It is optional, free and run by a separate company. Salto works fully without it, and it never sees your conversations, keys, VPN routes or location.
No. It stays in this browser tab, is not stored, and disappears when you reset or close the page.
English, French, Italian, Spanish, Chinese, German and Portuguese.
Follow a message from your keyboard to its recipient, then go deeper into the radios, the encryption, the routes and the proofs that make Salto work without internet.
Salto shows exactly where your message is. A relay's receipt and the recipient's acknowledgement are never confused.
Your draft is sealed for one recipient and signed, with a unique ID against duplicates and a time to live.
Waiting for a neighbour, handed to a relay, or on its way. A relay's signed receipt proves the handover.
The recipient opens it and signs an acknowledgement. Retries and duplicates never create two visible copies.
Restart, low battery or a suspended app: messages stay sealed on the device and pick up where they left off.
This runs in your browser with Web Crypto: authenticated encryption, the same family Salto applies to every envelope. Nothing leaves this page.
Demo engine: AES-256-GCM and SHA-256 from your browser. The app uses XChaCha20-Poly1305 for the payload, with keys from PQXDH and the Triple Ratchet.
Web Crypto is not available in this browser.
Relays move envelopes they cannot open. Here is what is inside one.
Exact algorithms and Salto parameters, layer by layer.
Every action in Salto rides on proven, open technology. Here is what powers each moment.
When you press Send with the internet off
When you send a voice note or a photo nearby
When you let relay B carry your message
When you switch Salto VPN to Fast
When you choose Private mode
When you send a message that can wait
When you let two Salto services talk peer to peer
When you prove you hold a plan without showing your account
When you approve a payment from your vault
When you translate a note in airplane mode
When you look at the public Atlas
Seven layers of open, state-of-the-art cryptography, woven into one seamless app. Pick a layer to see what protects you.
Defence in depth: each ring is an independent layer around your message.
Phones find each other and hop messages along, with no network at all.
Every message is sealed end to end, with group keys that refresh and post-quantum key exchange.
When you go online, you choose how: fast tunnel, onion routing or a mixnet that hides timing.
Salto Pass proves who may do what, with one unlinkable pseudonym per service and nothing else revealed.
Handovers, entitlements and tasks are proven precisely, without revealing who you are.
Four assets, named networks, and keys that sign on a device that never goes online.
An assistant that runs on your device, with remote tasks bounded by a policy engine.
Choose a layer to light up the established terms it uses and the Salto proofs built on top of it. Every chip opens its definition.
Salto layers the most advanced open cryptography available today: post-quantum keys, zero-knowledge proofs, mixnets and threshold signatures. Here is what each one does, and where Salto uses it.
Defence in depth: several independent layers protect every action, so one alone is never the only safeguard.
Used inMulti-hop relay and delayed deliveryMeetups and local mutual aidLocal classifiedsLimited proximity walletOccasional phone relayPermanent mesh beaconsGuide packs from nearby devicesSALTO Bulletins
Used inMulti-hop relay and delayed deliveryVoice notes and file sharing, sized to the linkPrivate callsTransfer between your devicesOccasional phone relayPermanent mesh beaconsGuide packs from nearby devicesShare a connection nearbySALTO GuestSALTO Bulletins
Used inPermanent mesh beaconsLoRa with extra hardwarePersonal boxes and beacons
Used inPrivate and group messagesPrivate callsQR contacts and limited-use invitationsTransfer between your devices
Used inPrivate and group messagesVoice notes and file sharing, sized to the linkDisappearing messages and screenshot shield
Used inPrivate and group messagesTemporary private spacesPublic channels with participant privacyGames, polls and shared listsCollaborative documents with conflict handlingTeam and business plans
Used inPrivate and group messagesMulti-hop relay and delayed deliveryEncrypted mailboxVoice notes and file sharing, sized to the linkTemporary private spacesTransfer between your devicesNotes and documents vaultCollaborative documents with conflict handlingZero-knowledge encrypted backupTemporary private inboxesPasswords, passkeys and TOTP, isolated from AIPrivate file dropRevoke future accessDuress PIN and decoy spaceEncrypted mailboxes on your nodeStorage sharing: encrypted, fragmented, auditedLoRa with extra hardwareOffline guide librarySALTO FieldOptical transfer
Used inMulti-hop relay and delayed deliveryEncrypted mailboxOne identity per relationshipSealed senderMeetups and local mutual aidOccasional phone relayEncrypted mailboxes on your nodeSALTO DispatchSALTO Field
Used inPrivate callsForums and blogs that survive outagesBlockchain nodeTransaction relay
Used inPublic channels with participant privacySealed senderTransaction relay
Used inPrivate credentials for access or reputationSalto Pass: zero-knowledge KYCSalto Card, physical or virtual
Used inPublic channels with participant privacyLocal classifiedsGames, polls and shared listsPrivate credentials for access or reputationSubscriptions with unlinkable authorisationsSalto Pass: zero-knowledge KYCConfidential payments via compatible protocolsRewards for verified service onlyCard revenue sharingCapped referral on paying customersPrivate group consultations
Used inOne identity per relationshipEmail alias per serviceSeparate profilesSalto Pass: zero-knowledge KYCCapped referral on paying customersPrivate group consultations
Used inQR contacts and limited-use invitationsKey transparency
Used inNotes and documents vaultZero-knowledge encrypted backupPasswords, passkeys and TOTP, isolated from AISalto Card, physical or virtualTeam and business plansPrivacy API and SDK
Used inSecondary temporary numbers and SMSSubscriptions with unlinkable authorisationsSalto token and credits, apart from earningsRewards for verified service onlyPersonal plansPay-as-you-go storage and AIPrivacy API and SDKCommunities funded by an organiserCompromised password check
Used inStorage sharing: encrypted, fragmented, auditedVerifiable capacity reservationHost Survival packs
Used inShared compute for suitable dataVerifiable capacity reservationConfidential compute with attestation
Used inBTC, ETH, USDT and USDC walletPrepared, signed, broadcast, confirmedCold signer
Used inConfidential payments via compatible protocolsPayment requests and invoicesStealth and silent-payment addresses
Used inConfidential payments via compatible protocolsPayment requests and invoicesStealth and silent-payment addresses
Used inThreshold recovery with trusted peopleMultisignature and conditional paymentsThreshold wallet across your devices
Used inLimited proximity walletClosed-loop wallet for a partner venue
Used inMetadata removal and local blurLocal AITranslation and transcriptionSearch in your authorised documentsAI on your personal computerOffline assistant with sourcesMask before AI
Used inLocal AIPermissions and shared data dashboardCards per merchant or per mission, with AI limitsAI on your personal computerControlled VPN exit pointsMini-apps and automations marketplaceMask before AI
Used inPrivate and group messagesOne identity per relationshipDisappearing messages and screenshot shieldLocal AINotes and documents vaultSeparate profilesPasswords, passkeys and TOTP, isolated from AISalto Pass: zero-knowledge KYCDuress PIN and decoy spaceBTC, ETH, USDT and USDC walletCold signerThreshold wallet across your devicesOffline assistant with sources
Used inForums and blogs that survive outagesOffline maps and travel folderVerifiable app releasesSalto Pass: zero-knowledge KYCKey transparencyDistribution of signed AI models and public contentOptical transfer
Used inMulti-hop relay and delayed deliveryEncrypted mailboxSealed sender
Used inEncrypted mailboxEmail alias per serviceTemporary private inboxesPrivate file dropEncrypted mailboxes on your node
Used inPrivate credentials for access or reputationSalto Pass: zero-knowledge KYC
Used inPrivate credentials for access or reputationRevoke future accessSalto Pass: zero-knowledge KYC
Used inPrivate contact discovery
Used inSearch in your authorised documentsPrivate contact discoveryCompromised password check
Used inForums and blogs that survive outagesZero-knowledge encrypted backupPrivate file dropStorage sharing: encrypted, fragmented, auditedGuide packs from nearby devicesHost Survival packsSALTO Dispatch
Used inZero-knowledge encrypted backupThreshold recovery with trusted people
Used inBTC, ETH, USDT and USDC walletPrepared, signed, broadcast, confirmedCold signerBill splittingAutomatic conversion for card top-upsPersonal plans
Used inBill splittingMultisignature and conditional payments
Used inThreshold wallet across your devicesShared compute for suitable dataConfidential compute with attestation
Used inOffline maps and travel folderShare a connection nearby
Used inVerifiable app releasesDistribution of signed AI models and public contentMini-apps and automations marketplacePersonal boxes and beaconsOffline guide libraryGuide packs from nearby devicesHost Survival packsSALTO GuestSALTO DispatchSALTO Bulletins
Ten services, every capability in one place. Each one tells you what works offline, what goes online and which protocols protect it.
Follow a message off-grid. See what a relay can learn. Verify a file for yourself.
What you just saw Two halos in turn: the relay accepts the envelope, then the recipient confirms delivery.
Private conversations, nearby or far
Messages are sealed end to end on your phone and hop between nearby phones over Bluetooth or local Wi-Fi. A relay signs a receipt when it accepts an envelope; only your contact's own acknowledgement confirms delivery.
Try it: Send a message with the internet off →What you just saw Traffic enters the tunnel and follows the route you chose. When the route breaks, sending pauses instead of leaking.
Protect a connection
One switch opens a tunnel: WireGuard to one exit (Fast), three Tor relays (Private) or a mixnet with cover traffic (Hardened). A kill switch is designed to block traffic whenever the tunnel drops.
Try it: Connect, switch modes, cut the network →What you just saw Fragments are stored and checked; one fragment fails its recovery check and is refused.
Put your devices to work
Your device offers a quota you set. Reserved space is checked with recovery challenges, and stored files are split into encrypted fragments so that any 10 of 30 bring them back.
Try it: Remove devices, recover the file →What you just saw The request is handled on the phone. The remote branch opens only after you approve the mission.
Local and connected assistant
Models run on your device first. A task that needs more power becomes a mission you approve, with a budget, a destination and a way to revoke it.
Try it: Follow the data →What you just saw A payment is prepared field by field, signed on your device, then broadcast through a private route.
BTC, ETH, USDT, USDC wallet
Keys stay on your phone. You choose the asset and the network, check the address, see the fee, sign on the device and follow the confirmations.
Try it: Send and receive with fictional assets →What you just saw The transaction travels to an offline signer by QR code, gets signed there and comes back sealed.
Cold storage for your keys
A second device that stays offline holds the keys and signs. The online phone only carries the payment to sign and the signature, by QR code.
Try it: Sign with a cold device →What you just saw The daily limit slides down, then the card is frozen with one tap.
Physical or virtual crypto card
Limits and freezing are set in the app. Card payments travel on the card network, so the issuer and the network see them as with any card.
Try it: Set your card rules →What you just saw An alias is created for one service, counts down, then expires on its own.
Email aliases, SMS numbers, profiles
Each sign-up gets its own alias, number or profile that you can expire or revoke. Passwords, passkeys and one-time codes stay in the encrypted vault on your device.
Try it: Create and revoke an alias →What you just saw The internet signal disappears, your library stays lit, a pack arrives from a nearby device and its source opens.
Your offline knowledge library
Packs are signed and versioned. The assistant answers from local passages it shows you, and a missing guide comes from a nearby device and is checked before it opens.
Try it: Find a guide without internet →What you just saw Two devices pair, the tunnel lights up to the gateway, then stops when the quota is reached or the session is revoked.
Share a connection nearby
A neighbour shares a connection for a set time and amount, through a tunnel to a managed gateway. The person sharing cannot read your traffic and can stop at any moment.
Try it: Share a connection nearby →What you just saw A kiosk broadcasts, a phone without app reads, a ticket waits, the guide arrives verified.
Public documents without an app, guides on request
A kiosk serves public documents to any browser on its local Wi-Fi. A request for a missing guide is carried by relays and fetched from an authorised source.
Try it: Follow a guide request →What you just saw A file becomes a fingerprint and a seal; change one byte and the seal breaks.
Check files, receipts and approvals yourself
Your browser computes the file's SHA-256 fingerprint, checks the publisher's signature and a Merkle path to an anchored root. Change one byte and the check fails.
Try it: Verify a file yourself →What you just saw Three proofs are checked - age, country, one real person - while the document itself stays hidden.
One private KYC for the whole network
An accredited verifier checks you once. Your device then gives each service a zero-knowledge proof tied to a pseudonym that exists only for that service.
Try it: Pick a service, get a pseudonym →What you just saw Two aggregated regions light up, an arc appears and a pulse travels along an aggregated link (demo data).
The world network, aggregated
Devices are counted per region. A figure is published only when enough participants share a cell, after a delay, rounded, and never with a device position.
Try it: Open the Atlas control room →Every Salto service in six families. Each one tells you what it is for, what works offline, what goes online and which protocols protect it. Every service has its own link to share.
Showing 91 of 91 options
Messages, groups, relays and contacts that keep working when the network does not.
UseTalk one to one or in groups with contacts you verified in person.
Protected byPQXDHDouble Ratchet · SPQRMLS · RFC 9420XChaCha20-Poly1305Secure Enclave · StrongBox
UseReach someone out of your range through consenting devices in between.
Protected byBluetooth Low EnergyWi-Fi Aware · MultipeerSealed SenderUniform paddingXChaCha20-Poly1305
UseLeave a message for someone who cannot be reached right now.
Protected byOnion servicesSealed SenderXChaCha20-Poly1305Uniform padding
UseSend voice notes and small files; size adapts to the available speed.
Protected byWi-Fi Aware · MultipeerDouble Ratchet · SPQRXChaCha20-Poly1305
UseCall a contact privately.
Protected byWi-Fi Aware · MultipeerPQXDHTor · Arti
UseOpen a short-lived group for an event, a trip or a project.
Protected byMLS · RFC 9420XChaCha20-Poly1305
UseAdd someone by scanning a QR code face to face.
Protected byPQXDHKey Transparency
UseShow a different identity to each contact or context.
Protected byScoped nullifiersSealed SenderSecure Enclave · StrongBox
UseFollow or publish to a public channel without exposing its members.
Protected byMLS · RFC 9420Nym mixnet · Sphinxzk-SNARKs · PLONK · Halo2
UsePublish posts that keep spreading during network cuts.
Protected byML-DSA · FIPS 204Reed-Solomon erasure codingTor · Arti
UseMove your conversations to a new phone.
Protected byPQXDHWi-Fi Aware · MultipeerXChaCha20-Poly1305
UseStrip location and camera data and blur faces before sharing.
Protected byllama.cpp
UseHide who sent a message from relays and servers.
Protected bySealed SenderUniform paddingNym mixnet · Sphinx
UseSet messages to vanish after a chosen time, and block screenshots on supported phones.
Protected byDouble Ratchet · SPQRSecure Enclave · StrongBox
UseRead a kiosk's public documents from any phone browser, without an app or an account.
Protected byWi-Fi Aware · MultipeerReproducible builds · Sigstore
UseAsk for a public document nobody nearby has; get it later through a relay.
Protected bySealed SenderReproducible builds · SigstoreReed-Solomon erasure coding
UsePublish a signed local notice, correct it or cancel it.
Protected byReproducible builds · SigstoreBluetooth Low EnergyWi-Fi Aware · Multipeer
UseProve you belong to a group and contribute once, without revealing which member you are.
Protected byzk-SNARKs · PLONK · Halo2Scoped nullifiers
Tools that run on your device, with or without a connection.
UseAsk an assistant that runs on your own device.
Protected byllama.cppOpen Policy AgentSecure Enclave · StrongBox
UseTranslate a message or transcribe a voice note.
Protected byllama.cpp
UseFind a phrase across the documents you choose to index.
Protected byllama.cppPrivate Information Retrieval
UseKeep private notes and documents encrypted on your device.
Protected byXChaCha20-Poly1305Secure Enclave · StrongBoxPasskeys · FIDO2
UseCarry maps, tickets and travel documents for places without signal.
Protected byH3 hexagonal gridML-DSA · FIPS 204
UseArrange to meet or ask people nearby for help. Not a replacement for emergency services.
Protected byBluetooth Low EnergySealed Sender
UsePost or browse small ads around you.
Protected byBluetooth Low Energyzk-SNARKs · PLONK · Halo2
UsePlay, vote or keep a shared list with people around you.
Protected byMLS · RFC 9420zk-SNARKs · PLONK · Halo2
UseEdit a document together, even while disconnected.
Protected byMLS · RFC 9420XChaCha20-Poly1305
UseBack up chats, notes and keys, encrypted with a key only you hold.
Protected byXChaCha20-Poly1305Shamir secret sharingReed-Solomon erasure codingPasskeys · FIDO2
UseCheck that your Salto app is exactly the published, signed code.
Protected byReproducible builds · SigstoreML-DSA · FIPS 204
UseSearch and read guides stored on your device, with every radio off.
Protected byXChaCha20-Poly1305Reproducible builds · Sigstore
UseGet a guide you lack from a phone, computer or NAS nearby, with its owner's consent.
Protected byBluetooth Low EnergyWi-Fi Aware · MultipeerReproducible builds · SigstoreReed-Solomon erasure coding
UseAsk a question; the answer lists the passages it used.
Protected byllama.cppSecure Enclave · StrongBox
UseFill inspection or inventory forms offline and send them encrypted.
Protected byXChaCha20-Poly1305Sealed Sender
UseMove a small object from a screen to a camera with animated QR frames.
Protected byXChaCha20-Poly1305ML-DSA · FIPS 204
UsePreview and mask names, emails, numbers and wallet references before a remote mission.
Protected byllama.cppOpen Policy Agent
Separate identities, aliases and credentials, under your control.
UseSign up with a unique alias, set its expiry and revoke it at any time.
Protected byScoped nullifiersOnion services
UseUse a disposable inbox for a short exchange.
Protected byXChaCha20-Poly1305Onion services
UseRent a second number for sign-ups and calls you want to keep separate.
Protected byPrivacy Pass · RFC 9576
UseKeep work, family and other activities apart.
Protected byScoped nullifiersSecure Enclave · StrongBox
UseStore passwords and passkeys and generate one-time codes.
Protected byPasskeys · FIDO2Secure Enclave · StrongBoxXChaCha20-Poly1305
UseProve a right or a reputation without revealing who you are.
Protected byBBS signaturesW3C Verifiable Credentials 2.0zk-SNARKs · PLONK · Halo2Cryptographic accumulators
UseUse a paid service without tying each use to your billing identity.
Protected byPrivacy Pass · RFC 9576zk-SNARKs · PLONK · Halo2
UseSee what each service or mission can access, where data goes and until when.
Protected byOpen Policy Agent
UseRecover your vault with shares held by several people you trust.
Protected byShamir secret sharingFROST threshold signatures
UseShare a file through a time-limited link.
Protected byXChaCha20-Poly1305Onion servicesReed-Solomon erasure coding
UseStop new downloads of anything you shared, instantly.
Protected byCryptographic accumulatorsXChaCha20-Poly1305
UseVerify once, then prove only what a service needs (adult, eligible country, unique person) without ever sharing your documents.
Protected byBBS signaturesW3C Verifiable Credentials 2.0zk-SNARKs · PLONK · Halo2Scoped nullifiersCryptographic accumulatorsSecure Enclave · StrongBoxML-DSA · FIPS 204
UseFind which of your contacts use Salto without uploading your address book.
Protected byOPRF · Private Set IntersectionPrivate Information Retrieval
UseYour app automatically checks that every contact's key is genuine.
Protected byKey TransparencyML-DSA · FIPS 204
UseA second PIN opens a harmless decoy space or wipes the data you choose.
Protected bySecure Enclave · StrongBoxXChaCha20-Poly1305
UseCheck whether a password appears in a known leak, without sending it.
Protected byPrivate Information RetrievalPrivacy Pass · RFC 9576
A self-custody wallet, a cold vault and a card, with every step visible.
UseHold, send and receive the four assets, with the network named every time.
Protected bySecure Enclave · StrongBoxPSBT · BIP-174EIP-712 typed signing
UseAlways see which step a payment has reached.
Protected byPSBT · BIP-174EIP-712 typed signing
UseSign on a separate device that never goes online.
Protected byPSBT · BIP-174EIP-712 typed signingSecure Enclave · StrongBox
UseReduce on-chain exposure where a protocol supports that asset and network.
Protected byzk-SNARKs · PLONK · Halo2Silent Payments · BIP-352Stealth addresses · ERC-5564
UseRequest a payment with an address or invoice specific to the context.
Protected bySilent Payments · BIP-352Stealth addresses · ERC-5564
UseShare a bill and track who has paid.
Protected byEIP-712 typed signingTaproot · MuSig2
UseRequire several signers or a condition before funds move.
Protected byTaproot · MuSig2FROST threshold signatures
UseSpend your crypto with a card, wherever the card is accepted.
Protected byPasskeys · FIDO2BBS signatures
UseA card locked to one merchant or one AI mission, with a spending cap.
Protected byOpen Policy Agent
UseTop up your card from BTC, ETH, USDT or USDC; Salto converts when needed.
Protected byEIP-712 typed signing
UseHand over a small, capped value to someone nearby.
Protected byChaumian ecash · CashuBluetooth Low Energy
UseSpend limited credits at an event or venue.
Protected byChaumian ecash · Cashu
UseSee each balance on its own: credits, rewards and Salto tokens.
Protected byPrivacy Pass · RFC 9576
UseShare one address publicly; every payment lands on a fresh, unlinkable address.
Protected bySilent Payments · BIP-352Stealth addresses · ERC-5564
UseSplit your key across phone, computer and a trusted contact; any two can sign.
Protected byFROST threshold signaturesMulti-party computationSecure Enclave · StrongBox
Phone, computer, mini-PC, NAS or server: your device, your roles, your limits.
UseLet your phone carry other people's sealed envelopes now and then.
Protected byBluetooth Low EnergyWi-Fi Aware · MultipeerSealed Sender
UseInstall an always-on relay in a fixed place.
Protected byBluetooth Low EnergyWi-Fi Aware · MultipeerLoRa
UseHold sealed envelopes for recipients who are absent.
Protected byOnion servicesSealed SenderXChaCha20-Poly1305
UseRent out space on your phone, computer or NAS for encrypted fragments you cannot read.
Protected byXChaCha20-Poly1305Reed-Solomon erasure codingProofs of retrievability
UseServe verified copies of models and public files to nearby devices.
Protected byML-DSA · FIPS 204Reproducible builds · Sigstore
UseRun larger models on your own computer for your own devices.
Protected byllama.cppOpen Policy Agent
UseRun other people's tasks in an isolated sandbox.
Protected byTEE remote attestationFully homomorphic encryptionMulti-party computation
UseRun a node for a supported chain.
Protected byTor · Arti
UseCarry a signed transaction until it reaches a connected device.
Protected byTor · ArtiNym mixnet · Sphinx
UseSend short text over long distances with a dedicated radio.
Protected byLoRaXChaCha20-Poly1305
UseOptionally let VPN traffic exit through your connection. Never automatic.
Protected byWireGuard · RosenpassOpen Policy Agent
UseReserve capacity that is checked to really exist.
Protected byProofs of retrievabilityTEE remote attestation
UseEarn only for service that was requested and delivered, never for self-generated traffic.
Protected byPrivacy Pass · RFC 9576zk-SNARKs · PLONK · Halo2
UseRun sensitive tasks only on nodes that prove, in hardware, which code they run.
Protected byTEE remote attestationMulti-party computation
UseKeep verified packs on your device and deliver them to nearby people who ask.
Protected byReed-Solomon erasure codingProofs of retrievabilityReproducible builds · Sigstore
UseShare a real internet connection with people you accept, within limits you set.
Protected byWi-Fi Aware · MultipeerWireGuard · RosenpassH3 hexagonal grid
Free to start, with plans and partner options when you need more.
UseFree, Plus and Premium. The free core works offline.
Protected byPrivacy Pass · RFC 9576EIP-712 typed signing
UseSeats, access control and devices for a team, in self-service.
Protected byPasskeys · FIDO2MLS · RFC 9420
UsePay for the storage or AI you actually use.
Protected byPrivacy Pass · RFC 9576
UseAdd small apps and automations with explicit permissions.
Protected byOpen Policy AgentReproducible builds · Sigstore
UseBuild Salto's privacy services into your own product.
Protected byPrivacy Pass · RFC 9576Passkeys · FIDO2
UseReady-made hardware to run a node or beacon.
Protected byLoRaReproducible builds · Sigstore
UseCommunities and partners that bring card users share in card revenue, under their agreement.
Protected byzk-SNARKs · PLONK · Halo2
UseRecommend Salto through the optional partner program, run by a separate company. Free to join; never paid for sign-ups.
Protected byScoped nullifierszk-SNARKs · PLONK · Halo2
UseAn organiser or publisher funds Salto for their community.
Protected byPrivacy Pass · RFC 9576
No option matches. Clear the filters to see all 91.
Four modes, chosen per service. Salto always shows which route carries your traffic, and never switches it behind your back.
Press once to connect. Pick a mode to trade speed for privacy, then cut the network to see the protection the Salto VPN is designed to keep. Simulation in your browser: no real tunnel is opened.
Disconnected. Your traffic goes out directly, as usual.
Mode
WireGuard tunnel to one exit server
Illustrative values: real speed and reach depend on your network and country. The Salto VPN is in development; this shows the behaviour it is designed to have.
| What is protected | Salto VPN (as designed, in development) | Proton VPN | ExpressVPN |
|---|---|---|---|
| Kill switch | Blocks traffic when the tunnel drops (see the demo above) | Yes, on every plan; permanent kill switch on Windows and Linux | Network Lock blocks IPv4, IPv6 and DNS if the VPN drops |
| More than one hop | Private mode: three Tor relays; Hardened mode: mixnet | Secure Core through Switzerland, Iceland or Sweden (paid plans) | Not offered, by design |
| Hiding when you send | Hardened mode adds cover traffic and mixing | Stealth disguises the tunnel as HTTPS; it does not add cover traffic | Not documented in the sources reviewed |
| Post-quantum tunnel | Not specified so far | Announced, not shipped as of April 2026 (press report) | Hybrid ML-KEM in Lightway (January 2025) and in WireGuard on iOS, Android and Windows (August 2025) |
| Independent no-logs audits | No service to audit yet | Securitum audits each year since 2022 | KPMG assurance as of February 2025; RAM-only servers |
Mullvad's DAITA, for comparison, adds constant packet sizes and cover traffic on selected servers.
Sources · checked 4 Nov 2026 Proton VPN: kill switch ↗ Proton VPN: Secure Core ↗ Proton VPN: Stealth ↗ Proton VPN: no-logs audits ↗ Proton VPN roadmap (Tom's Guide) ↗ ExpressVPN: ML-KEM in Lightway ↗ ExpressVPN: post-quantum WireGuard ↗ ExpressVPN: Network Lock ↗ ExpressVPN: no multi-hop ↗ Mullvad: DAITA ↗
Salto is in development: these tables compare its design with services available today, on stated criteria, from the sources listed (checked on 4 November 2026). They claim no advantage that has not been demonstrated.
No internet route is opened. Messages wait for a nearby device.
Hides your address from destinations and your destinations from your network. Bridges where Tor is blocked.
Adds delays and cover traffic to resist timing analysis.
Everyday protection on untrusted Wi-Fi with low overhead.
Salto only, or the whole device where the system allows it. The screen always names the exit that receives your traffic and how to turn it off.
"Tunnel active" and "local network working" are shown apart, so a nearby chat never hides a dropped tunnel.
If the route you chose fails, traffic that requires it stops and waits. Nearby local exchanges keep working.
Leak-protected on every platform: DNS, IPv6, Wi-Fi changes and wake from sleep.
Your request is locked three times on your phone. Each relay opens only its own lock and learns only the next hop. The exit sees the destination, never you.
Every action in Salto rides on proven, open technology. Here is what powers each moment.
When you switch Salto VPN to Fast
When you choose Private mode
When you send a message that can wait
When you let two Salto services talk peer to peer
Research tracks: T06 · Traffic-analysis defence (Maybenot, DAITA)
Phones relay nearby, computers and NAS store and compute, servers carry the heavy loads. You set the roles, the limits and the hours.
Carries nearby envelopes now and then, within your battery and data limits.
Share part of your free space for encrypted fragments, while charging on Wi-Fi.
Light tasks while charging on Wi-Fi, if you allow it.
An always-on relay at a fixed spot: a shop, a boat, a building.
Encrypted mailbox for recipients who pass by later.
Not designed for compute. Optional LoRa radio with extra hardware.
Relay and mailbox during the hours you choose.
Encrypted fragments within the disk quota you set, with recovery checks.
CPU or GPU tasks in an isolated sandbox. Local AI for your own devices.
A durable mailbox for your household or team.
Larger encrypted fragment storage with recovery audits and repair.
Light compute and a cache for signed models and public content.
Connected relay and mailbox; optional blockchain node or transaction broadcaster.
High-capacity fragments and verifiable reserved capacity.
CPU and GPU jobs with agreed limits and result criteria.
Pause any time
Which roles, disk and data limits, energy budget, hours, end date and pause.
VPN exit, blockchain node and transaction broadcasting each need their own consent. Nothing turns on automatically.
Earn for the service your device actually delivers: relaying, storage and compute, measured and verified before every payout. Never for idle presence or self-generated traffic.
Storage fragments are encrypted and unreadable to the host. Compute tasks run isolated in a sandbox.
A file is encrypted on your phone, then split with Reed-Solomon into 30 fragments spread over different devices. Switch devices off: as long as 10 fragments remain reachable, the file comes back whole. No device ever holds a readable piece.
Tap a device to switch it off or on.
The mechanisms SALTO is designing, the privacy and security question each one answers, and the established primitives they build on: blind signatures, Privacy Pass, zero-knowledge proofs, PIR, MPC, FHE, TEE and post-quantum cryptography.
SALTO is designing protocols for private message handoffs, verifiable storage and permission-bound AI tasks. Each one answers a precise question: did a relay accept the message, can a storage provider recover the requested data, is an AI agent still authorised to act?
Built on established primitives
The established cryptography Salto builds on, and exactly where each idea lives in the app.
Your Salto Pass holds a secret that never leaves your phone. Each service receives a pseudonym derived from that secret and from its own name: same person, unrelated identifiers, and no service can link them.
Choose a service
Derived here with SHA-256 so you can watch it change; the app uses Poseidon inside a zero-knowledge circuit.
Choose a layer to light up the established terms it uses and the Salto proofs built on top of it. Every chip opens its definition.
Each card names the observer it would limit, the concrete use, what it protects, its limit, the maturity of the standard and the test that would move it forward. These are research tracks, separate from SALTO's own protocols and from features in the app.
Research tracks T01 to T14 are distinct from the 14 cross-cutting requirements of the original matrix. None is an app feature today.
Where Salto is active, region by region, published with privacy built into every step.
Synthetic data generated for this demonstration and published with the same rules as production: regional aggregation only, at least 20 participants per published cell, complementary suppression of device types, rare flows between regions removed, the latest period withheld, values rounded to tens. In production the observation window and the last refresh are shown here.
To protect participants, SALTO keeps the exact locations of relays, nodes and devices private. The Atlas shows delayed regional activity. Animated connections represent aggregated flows or clearly identified simulations. Areas with too few participants are grouped or hidden.
Pick a sparse region and filter on NAS only. If the filter could single out an operator, the Atlas hides the figure and says why.
The public API returns the same published data: GET /api/atlas. No coordinates finer than a region, no device, no IP, no identifier, no route.
Salto Atlas shows where the network is active, region by region. Participation is voluntary, publication is delayed and sparse regions stay hidden, so the map never reveals a person. Your own devices live in your private space.
Move the threshold. A region is published only when enough devices are active in it, so a published cell never points to a single person.
Research tracks: T03 · Distributed aggregation (DAP, Prio3)
Use it, power it, or recommend it. Each path is independent, and the first one is free.
The Salto web app opens at saltonetwork.com/dashboard and the mobile and desktop apps follow. Until then, every button that needs the app brings you here: what each access will do, where it will live and what you can already try.
Your Salto space in the browser: your devices, node settings, plans and receipts, without a phone number or an email.
Opens at saltonetwork.com/dashboard
Messaging without internet, the VPN, Survival packs and the wallet live in the app, on iOS, Android and desktop.
Choose the roles, limits and hours of a phone, computer or NAS, pause it or set it to zero at any time.
Membership, licences and partner tools are handled in the partner program's own dashboard, run by a separate company with its own terms. Using Salto never requires it.
Partner dashboard opening soon
This site keeps no sign-up list and asks for no email. When the dashboard opens, the buttons of this page and of the whole site will lead to it directly.
Using Salto, contributing a device and joining the partner program are independent. You can use Salto, buy a plan and share resources without ever opening a partner account.
Messaging works offline from the first minute, with no account, no financial profile and no sign-up. Start free and upgrade when you need more connected capacity.
Try the offline demo →Choose roles, limits and hours for your phone, computer or NAS, pause any time, and earn for the service your device actually delivers.
Configure a node →Optional and free, run by a separate company with its own sign-up, terms, accounts and admin. Rewards apply only to eligible paid sales, never to sign-ups. Partner administration has no access to messages, keys, VPN routes or user location.
Open the partner portal →Install Salto, add a contact by scanning their QR code and send a message. No account, no phone number and no internet needed for nearby chat.
Each hop covers the Bluetooth or Wi-Fi range of a phone. With relays in between, your message jumps from device to device to reach people well beyond your own range.
No. Relays carry sealed envelopes that only the recipient can open. Per-relationship identities and Hardened mode keep what the network can observe to a minimum.
Storage fragments are encrypted and unreadable to the node that holds them. Compute tasks run isolated, and only with the data you choose to send.
It works for calls, SMS and most sign-ups. Some banks and platforms only accept long-term carrier numbers for one-time codes.
No. It is optional, free and run by a separate company. Salto works fully without it, and it never sees your conversations, keys, VPN routes or location.
No. It stays in this browser tab, is not stored, and disappears when you reset or close the page.
English, French, Italian, Spanish, Chinese, German and Portuguese.
Salto AI translates, transcribes, summarises and searches on your device, even without internet. When a task needs more power, it prepares a mission you can inspect, trim, redirect or refuse.
Translate or rephrase a message, transcribe a voice note, summarise a document, search authorised notes and files, with the model available on the device.
Translate the demo message in airplane mode above.
For a task beyond the device, Salto prepares a mission with the selected data, the tools needed, the executor, a duration and an optional budget.
Remove a passage, change the destination, then refuse or revoke.
Explains why a message is waiting, why a node paused its contribution or why a task exceeds a quota, from the state you allow it to read.
Pick a situation below and read the explanation.
A personal computer or compatible node can run authorised tasks. The assistant also helps an operator understand a failure, a receipt or an order status.
Compare phone, computer and remote node in the table.
The same message in three situations. At every step you see what stays on the device, what would leave, to whom, for how long and how to cancel. Refusing never blocks offline messaging.
Meet at the north gate at 6.
If the local model is not installed, Salto says so and offers to download it over Wi-Fi. Nothing is sent elsewhere in the meantime.
Mission Capsule · Mission-Bound Authority · Proof of Bounded Execution · Proof of Local Processing
Your phone dropped below the battery floor you set, so Salto paused its relay and storage roles. Nothing is lost: envelopes it holds stay sealed. Suggestion: resume automatically when the phone is charging.
Your free space fell under the minimum you protect, so Salto stopped accepting new fragments. Suggestion: lower the shared quota by 2 GB or free space; committed fragments are moved to other devices first.
This summary needs more computing than your daily quota allows. Suggestion: run it on your paired computer tonight, or split the document into two parts.
| Criterion | Phone | Personal computer | Remote node |
|---|---|---|---|
| Availability | Always with you; limited by battery and model size | When it is on and paired | When the node is online and accepted the mission |
| Data the executor can access | Everything stays on the phone | Only the task data, over the local network | Only the approved passages, for the capsule's lifetime |
| If interrupted | Resumes on the phone | Resumes when the computer is back | Resumed or reassigned by the orchestrator; the capsule still bounds it |
Runs open models on phones and computers, without internet.
Design choiceOrchestrates multi-step assistant tasks.
Design choiceResumes connected tasks after a disconnection or a restart.
Design choiceChecks every action against your authorisations, independently of what the model writes.
Design choiceMission Capsule, Mission-Bound Authority, PBE and PLP are explained in SALTO Protocols. Inside SALTO Protocols →
Salto AI can advise, prepare and run a non-financial action you explicitly delegate. Private keys, recovery phrases, vault signatures, treasury approvals and payout decisions stay out of its reach. In the private partner portal the assistant only explains versioned rules, finds an authorised receipt or prepares a file for human review, and the two companies' data stay separate.
Before a remote mission, Salto detects names, emails, numbers and wallet references, replaces them with temporary aliases and shows the exact text that would leave. The alias table stays on your phone and expires.
Your text (fictional)
Exactly what would leave
-
Alias table (on this phone only, expires in 1 hour)
SALTO is designed to let you share spare storage or computing capacity. Eligible contributions may earn rewards when your device delivers a verified service.
Salto means jump in Italian and in Spanish. Watch your message jump from one device to the next, then read the five words hidden in the name.
Each time the envelope passes from one device to the next, that is a salto. Hover a word to see which part of the scene it names.
Salto means "jump" in Spanish and in Italian. In the demo, every time your message passes from one device to the next, that is literally a salto: A to B is the first jump, B to C the second.
Run the demo above: each hop you trigger is a salto.
Secure Asynchronous Local Transport Overlay: the transport layer at the heart of Salto. Each word maps to something you just saw.
Prepare a payment, sign it on a device that never touches the internet, check what each observer can learn, and set your card limits. Every step is shown, nothing moves without your approval.
Choose an asset and a network, then follow the payment step by step. Each step says who acts and what is checked.
Your phone prepares the transaction; an independent signer that never touches the internet approves it. Change anything after signing and the signer must approve again.
Prepare a transaction, then carry it to the cold signer by QR code.
Pick an asset, a network and an observer. Each layer shows what that observer can learn and which Salto protection applies.
On transparent blockchains, amounts and addresses are public. Salto reduces what links them to you; it cannot hide what the chain itself publishes.
| Design | Amount on chain | Sender to recipient link | Network origin |
|---|---|---|---|
| Salto Pay on BTC or ETH | Visible | Reduced: fresh, stealth or silent-payment addresses | Hidden by a private route |
| Shielded-pool coins | Hidden when fully shielded | Hidden when fully shielded | Depends on the wallet |
| Ring-signature coins | Hidden | Obscured among decoys | Depends on the wallet |
| Chaumian ecash for nearby use | Not on chain | Unlinkable to the issuer (blind signatures) | Works offline |
Reference designs for comparison only. Purchases on Salto use BTC, ETH, USDT and USDC.
Set a daily limit, choose where the card works, freeze it in one tap, and see exactly what the card provider can access.
The card is issued by a regulated card partner in eligible countries. Card identity, commercial profile and messaging pseudonym stay separate.
Fictional assets, real checks. Pick an asset and a network, receive to a fresh address, or send with every check a careful wallet makes. Balances and confirmations are demo data; the address checksum and the signature are computed in your browser.
Your receive address (fictional)
-
-
| What is protected | BTC, ETH (Salto wallet, as designed) | USDT, USDC | Zcash, fully shielded |
|---|---|---|---|
| Sending and receiving addresses | Public on the chain; a fresh address per payment limits linking | Public on the chain | Hidden |
| Amount | Public | Public | Hidden |
| Memo | None on chain | None on chain | Hidden |
| Fee and time | Public | Public | Fee public; timing observable |
| Your IP address when broadcasting | Visible to network peers unless sent through a private route | Visible to network peers unless sent through a private route | Not hidden by the protocol; Tor recommended |
| Who can freeze funds | Nobody: you hold the keys | The issuer can freeze an address | Nobody |
Zcash privacy holds only for fully shielded transfers: moving funds into or out of the shielded pool reveals the amount. Salto's wallet does not make BTC or ETH payments private on its own; Silent Payments (BIP-352, specification complete, not in Bitcoin Core) and stealth addresses (ERC-5564) are research tracks.
Sources · checked 4 Nov 2026 Zcash: addresses and privacy ↗ Zcash: privacy best practices ↗ Bitcoin: protect your privacy ↗ Ethereum: transactions ↗ USDC terms ↗ USDT terms ↗ BIP-352 ↗ ERC-5564 ↗
Salto is in development: these tables compare its design with services available today, on stated criteria, from the sources listed (checked on 4 November 2026). They claim no advantage that has not been demonstrated.
Research tracks: T07 · Silent Payments (BIP 352) T13 · Payjoin v2 and stealth addresses
Create an alias for one sign-up, let it expire on its own, revoke an app's access in one tap and share a file for a day. Your real address and number stay out of it.
Create an email alias for one service and choose when it expires. Mail reaches you; the service never sees your real address.
-Some services refuse secondary numbers for one-time codes.
Prepare your guides while you are online. When the network goes down, search them, read them and ask questions that cite their sources. A guide you lack can come from a nearby device, checked before it opens.
Turn the internet off, search for a power-outage guide, and watch a nearby NAS share a verified copy over the mesh. Then disconnect the NAS: your copy stays readable.
Everything runs in your browser. Sizes and names are illustrative.
Your guides are on this phone. Turn the internet off, then search.
Source: public emergency-preparedness guide, section 2.3 · Public domain · Pack 2026.10 · Signed manifest verified on this phone
Salto tells you what this device can do before you need it.
Search your local guides, open documents and, if your device runs a compatible model, ask a question and see the passages used for the answer.
Search and reading stay available offline. The screen shows which functions work on this device, the size of each pack and the space left.
With its owner's consent, a phone, computer or participating NAS shares the pack over the mesh. You see size, language, version and provenance before accepting; Salto checks the signed manifest and every fragment, then keeps the copy.
You can separately allow a question, or selected passages, to be sent to that computer. The screen names the recipient, the data sent and how long the permission lasts.
Beyond strict survival: outage preparation, off-grid travel, repairs, technical documentation, maps and checklists. Every pack shows who published it, when, in which language, its size, whether it may be shared and how it was verified.
| Pack | Publisher | Date | Language | Size | Sharing between devices | Verification |
|---|---|---|---|---|---|---|
| Power outage preparation | National emergency agency (public domain) | 2026-09 | English | 18 MB | Allowed | Signed manifest · official source linked |
| First aid basics | Humanitarian organisation (non-commercial licence) | 2025-11 | English, French | 42 MB | Free sharing only, never rewarded hosting | Signed manifest · official source linked |
| Off-grid travel maps | Open map community (share-alike) | 2026-10 | All | 640 MB | Allowed with attribution | Signed manifest |
| Repair guides | Community wiki (non-commercial licence) | 2026-08 | English | 1.1 GB | Free sharing only, never rewarded hosting | Signed manifest |
| Technical documentation | Your own files | - | Yours | Your choice | Never shared unless you choose | Stays on your devices |
| Offline checklists | Salto (open licence) | 2026-10 | 7 languages | 2 MB | Allowed | Signed manifest |
Illustrative For high-risk topics (medicine, electricity, chemicals) the official source is always one tap away. When no document in your library is reliable enough, the assistant says so instead of guessing.
On a compatible device the assistant runs locally. On a phone that cannot run it, you can ask a nearby computer, only with a permission you grant for that question.
Keep verified packs and deliver them to nearby people who ask.
Run the assistant for nearby people who send a question.
Accept questions from people you approve. Separate from compute: you can compute without seeing who asked.
Three separate permissions. Turning one on never turns on another.
Passages used
Rewards Eligible contributions may earn rewards when a requested service is delivered and verified.
When one person nearby still has internet, they can choose to share it: for a set time, a set amount of data and only with the people they accept. Traffic goes through an encrypted tunnel to a managed gateway, never out of their own address.
Only the third needs someone nearby with a real connection who chooses to share it.
No internet needed
Your envelope hops between nearby devices until it reaches your contact.
Try the offline messaging demo →No internet needed
A guide or file already on a mesh device is delivered to you, checked before it opens.
Find a guide without internet →Needs a real upstream connection and the owner's consent
A neighbour with a connection lets you use it, within limits they set, through a tunnel to a managed gateway.
Share a connection nearby →The nearby link and the permission to share are one problem; the tunnel is another. Each layer is chosen for its own job.
| Criterion | WireGuard | MASQUE CONNECT-IP (RFC 9484) |
|---|---|---|
| Threat model | Authenticated peers with static keys; small attack surface | IP over HTTP/3 through a proxy; looks like ordinary web traffic |
| Compatibility | Kernel or user-space on every major platform | Needs an HTTP/3 stack on client and gateway |
| Metadata visible on the path | A UDP flow to the gateway | An HTTPS flow to the gateway |
| Battery | Very low idle cost | Higher cost from the HTTP/3 and QUIC stack |
| Throughput | High | Good; depends on QUIC tuning |
| Recovery after a cut | Fast: roams across addresses | Fast: QUIC connection migration |
| Maintenance | Small, audited code base | Newer standard; fewer mature implementations |
Start with WireGuard; use CONNECT-IP where a network blocks plain UDP tunnels and an HTTP proxy path gives a concrete advantage. Both carry Salto's post-quantum key exchange on top.
| Platform | Local link set up by Salto | Sharing internet | Device check |
|---|---|---|---|
| iPhone and iPad | Peer-to-peer link between nearby devices | Personal Hotspot, turned on by the user in Settings; depends on the carrier plan | To verify on real devices |
| Android | Local-only hotspot: nearby devices talk, with no internet on that network | System hotspot setting, turned on by the user | To verify on real devices |
| Computer | Local Wi-Fi or wired link | Windows Mobile Hotspot can be driven by an app with the right permission; on Mac, Internet Sharing is a system setting | To verify on real devices |
Salto never bypasses a system setting. Before any rewarded pilot, the carrier terms on sharing a connection are checked market by market.
Rewards Eligible contributions may earn rewards when a requested service is delivered and verified.
A kiosk's documents in any browser, a guide fetched while you are away, notices you can trust, forms that travel encrypted, screen-to-camera transfers and private group consultations.
A passenger joins the ship's kiosk Wi-Fi in a browser, asks for a guide the kiosk does not have, keeps an ephemeral ticket and leaves. A relay later reaches an authorised source. Back on board, the passenger opens the guide and checks where it comes from.
Simulated Kiosk, relays and source are simulated in this tab. The ticket lives in this page only.
You are on board, no internet. Join the kiosk Wi-Fi in your browser.
An organiser publishes a signed bulletin over the mesh. Readers see who issued it, when it was last known and whether it is still fresh, even offline.
Drafts stay protected on the phone. A finalised form is encrypted for the organisation, carried by any device, and imported once.
Draft protected on this device. Nothing leaves until you finalise.
A small object (an invitation, an attestation, a signing request) travels as a sequence of QR frames. Missed frames are rebuilt from the extra ones.
Bluetooth and Wi-Fi off. Play the frames.
Any camera that sees the screen can copy a visible QR: sensitive objects are encrypted for their recipient. Size is limited; large guides use Wi-Fi or the mesh. Frames here are illustrative.
A fictional association runs a consultation. A member proves membership and submits one contribution per consultation, without revealing which member did.
-Fictional group. A proof of membership does not prove a person holds only one membership; the issuer of memberships matters. Not meant for high-stakes public elections.
Only fictional examples here. The check sends a short prefix of the fingerprint, gets a padded list back and compares the rest on the device.
Never type a real password or a recovery phrase on a website. This demo accepts no input.
-Fingerprints and signatures run on your device. Inclusion and freshness need the chain. Each step says who sees what and what works offline.
Pick one. Each step happens in a different place, is seen by different parties, and needs a connection or not.
This check really runs in your browser: SHA-256 fingerprint, the publisher's signature over the manifest, the version policy and the path to a timestamp commitment. Each result names exactly the property it verifies.
-First bytes (hexadecimal)
Computed in your browser The fingerprint, signature and path are computed on this device with the Web Crypto API. The publisher key is a test key; the anchor is a test fixture.
Press Verify. Then change one byte and verify again.
A merchant receives a payment request, goes offline and comes back later. Each step is separate: signed intent, broadcast, inclusion, confirmations or finality, reconciliation with the invoice.
Test data Test data only. A real check needs a node or a light client you trust; this offline demo uses fixtures and says so.
Choose an asset and a case, then come back online.
Scenarios with fictional data. Treasury operations stay in the companies' private spaces.
The chain documents money movements; SALTO proofs document delivery. Neither replaces the other.
Instead of a test transfer, the owner signs a one-time challenge that names its purpose, a nonce and an expiry.
A proof of control gives no permission to spend. The exact withdrawal still needs human approval. Custodial addresses that cannot sign follow another procedure.
Each company controls its own treasury. An outgoing payment needs two different approvers; nobody approves their own request.
No promise of free payments and no coverage of every chain.
What exists today, honestly. A screen or a fictional value is not a network integration.
| Function | In the memo | Web demo (fixtures) | Native build | Testnet verified | Production verified |
|---|---|---|---|---|---|
| Salto Pay (BTC, ETH, USDT, USDC) | Yes | Yes: #pay | No | No | No |
| Salto Vault (cold signing) | Yes | Yes: #vault | No | No | No |
| Salto Shield (who sees what) | Yes | Yes: #shield | No | No | No |
| Invoices paid in BTC, ETH, USDT, USDC | Yes | Yes: #receipt | No | No | No |
| Settlement reconciliation | Yes | Yes: #receipt | No | No | No |
| Blockchain nodes on Salto Node | Yes | Listed: #nodes | No | No | No |
| Transaction broadcast through a private route | Yes | Yes: #pay | No | No | No |
| Timestamp anchor of public pack versions | Proposal | Yes: #verify-file | No | No | No |
| Utility token | Later track | No | No | No | No |
Audit of the code delivered on 3 Nov 2026: no network connector, no contract address and no RPC endpoint exists in the site or its server. Every chain value shown is a test fixture.
Accepted for purchases: BTC, ETH, USDT and USDC only, on networks explicitly enabled. Your personal wallet is non-custodial: no company approver ever holds its keys.
What this website processes today, what the app will process, and your rights.
This website, saltonetwork.com, is published by the company that operates Salto: to be completed (legal name, registered address, registration number).
Contact for any privacy question or request: to be completed (email address).
The site is made of static pages and demonstrations that run in your browser. It has no account, no sign-up form, no newsletter, no comment field, and no analytics or advertising tool.
What you type in a demonstration stays on your device and disappears when you reload or close the page.
Like any website, each request reaches our hosting provider with technical data: your IP address, the page requested, date and time, your browser's user agent and, if your browser sends it, the referring page.
The site's own code does not record these requests. Cloudflare, Inc., which hosts and protects the site, processes them to deliver the pages and to protect the service against abuse, under its own policies (cloudflare.com/privacypolicy).
Our hosting dashboard shows us aggregated traffic figures (number of requests, countries, threats blocked). They do not identify you.
On this site, Ask Salto searches a list of answers that is loaded with the page. Your question is not sent anywhere.
If a connected assistant is added later, this policy will say so before it is switched on, with its provider and how long questions are kept.
We process the technical data above only to deliver the site and keep it secure, which is our legitimate interest in operating a secure website. We do not use it for profiling or advertising and we do not sell it.
We keep no visitor data ourselves. Our hosting provider keeps operational logs for the limited periods set out in its own policies. Aggregated statistics contain no personal data.
Cloudflare operates a global network, so a request may be processed outside your country, including in the United States, under the safeguards described in Cloudflare's data processing terms. We share no visitor data with anyone else.
The Salto app is not available yet. As designed, messaging works without a phone number or an email; keys are created and kept on your device; relays carry sealed envelopes they cannot read; plans are paid in BTC, ETH, USDT or USDC and each payment is reviewed by a person; the partner program is run by a separate company with its own policy.
A dedicated privacy notice for the app will be published before it opens. Nothing described in this section is collected through this website today.
Depending on where you live, for example under the EU General Data Protection Regulation or the UAE Personal Data Protection Law, you may have rights to access, correct, delete, restrict or object to the processing of your personal data, and to complain to a data protection authority.
As the site itself stores no visitor data, most requests concern data held by our hosting provider. Write to to be completed and we will help you.
We update this page when the site or the app changes and show the date of the last update at the top.
Also read: Terms & Conditions · Cookie Policy · Legal notice
The rules for using this website and its demonstrations.
These terms govern your use of saltonetwork.com, published by to be completed. By using the site you accept them.
The site presents the Salto project, its services and the stage of each one.
Demonstrations are simulations or calculations run in your browser with demo data. They show how a service is designed to behave; they are not the service itself. Figures in Atlas and in the demos are demo data.
Nothing on the site is an offer, a solicitation, or financial, legal or investment advice. Financial services (wallet, payments, card) are in development and are not offered on this site; their availability will depend on the law of each country.
Each service shows its stage. Research tracks are studies, not commitments. Descriptions may change as the product is built.
Do not try to disrupt the site, bypass its security, copy it at a rate that harms its availability, or use it for unlawful purposes.
The Salto name and logo, the texts, illustrations and code of this site belong to their owners and may not be reused without permission, except short quotations with attribution. Names of third-party products and standards belong to their owners.
Links to standards, research papers, NEO AI and other sites are given for information. We are not responsible for their content.
The site is provided as is. To the extent permitted by law, we are not liable for indirect losses arising from its use or from decisions taken on the basis of its content.
The partner program is operated by a separate company under its own terms, which will be published in its own dashboard. These terms do not cover it.
Governing law and competent courts: to be completed.
Contact: to be completed.
Also read: Privacy Policy · Cookie Policy · Legal notice
No tracking, no banner needed, and why.
This site sets no cookie of its own and uses no analytics, advertising or tracking technology. It stores nothing in your browser's local storage either.
Our hosting provider, Cloudflare, may place one strictly necessary security cookie (for example cf_clearance) only if your connection is asked to complete a security check.
It records that the check was passed, holds no profile and expires on its own, after 30 minutes on this site.
Strictly necessary security cookies do not need consent, and the site uses no other cookie, so there is nothing to accept or refuse.
If this ever changes, a preferences panel will be added here before any optional technology is used.
Demonstrations keep their state in the page's memory only. Reloading the page resets them.
You can block or delete cookies in your browser. The site works without them; a security check may simply be shown again.
Also read: Privacy Policy · Terms & Conditions · Legal notice
Who publishes this website and who hosts it.
Website published by: to be completed (company name, legal form, registered address, registration number and registering authority).
Publication director: to be completed. Contact: to be completed.
Salto is operated by the Salto product company. The partner program is operated separately by the Salto partner company. Their legal details: to be completed.
Technology developed by NEO AI (lilineo.com).
Hosted by Cloudflare, Inc., 101 Townsend Street, San Francisco, CA 94107, United States (cloudflare.com).
Demonstrations use demo data and show the intended behaviour of services, several of which are in development. Each service shows its stage.
Also read: Privacy Policy · Terms & Conditions · Cookie Policy