Cashvy Not out yet

The app’s own privacy policy

Privacy

This is the same text Cashvy shows under Menu → Privacy policy, read from the one file the app ships, so the two cannot differ.

Last updated 12 October 2026

Cashvy does not collect anything, because there is nowhere for it to go.

That is about the app. Signing up to test Cashvy before release is separate. The form asks for your name, where the invitation should go, what you will test it on, and how you split bills today — and it records the sentence you agreed to, word for word, rather than a tick. It keeps no IP address, no browser details, and no cookie.

We hold those answers until the beta ends. beta.cashvy.app lists every one of them and the date they are deleted, and that page is the authority on the beta programme rather than this one.

Who we are

Cashvy is made by Soul Archive Limited, a company registered in England and Wales, company number 16186654. Its registered office is 71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ. On this page, "we" and "us" mean that company.

What leaves your device

Nothing, unless you send it.

There is no analytics SDK, no crash reporter, no advertising identifier, and no telemetry of any kind in this app. There is no Cashvy account and no Cashvy server holding your ledger. We do not know that you installed it.

These are all the ways data leaves, and each one is something you tap:

  • sending someone a trip as a file, by AirDrop, mail or a message
  • letting a friend read a trip in their browser, from a code you showed them
  • connecting a friend's copy of Cashvy to yours, by reading them six words or letting them scan a code on your screen
  • handing a trip to a device at the same table, with no internet at all
  • saving or sending an export, or a Cashvy backup file, wherever you choose
  • opening a payment app or a payment link to pay somebody back
  • emailing us

And one that keeps going after you tap it, once. When you have connected a friend, new entries pass between the two of you without either of you doing anything. That is the only thing in Cashvy that moves data on its own, it is described in full under Connecting a friend, and there is a switch for it in Menu → Keep shared trips up to date.

Three of these are worth spelling out.

Email opens your own mail app, prefilled with the app's version number and your platform and nothing else — no device id, no person id, nothing from your ledger — and no message is sent unless you send it.

A payment link or handle opens the app that address belongs to. Cashvy fills in the details and never moves money, and what happens after that is between you and that app.

Showing yourself to people nearby is the one thing here that is a broadcast rather than a send: while it is on, anything in radio range can hear it, which is how being findable works on every device you own. So it is worth saying exactly what it says. It announces that this device speaks Cashvy, a version number, and two words picked at random each time you turn it on — that is the whole of it. Not your name, not your device, not a trip, not an amount, and nothing that is the same twice. It is off until you turn it on, and it stops when you turn it off, leave the screen, or put the app in the background.

What is stored, and where

WhatWhere
Trips, people, expenses, settlementsA SQLite database in the app's private storage
Money lent between two people, and anything repaid against itThe same database
Who may add expenses to a trip, and who has approved whatThe same database
Who hosts each trip, and which name in a trip each device answers toThe same database
Exchange rates you set for a tripThe same database
Payment details you or a friend typed — a handle, a link, a trip's own payment noteThe same database
Photos you attach, and any text read off a receiptFiles and rows in the app's private storage
The full history of every changeThe same database, as an append-only log
Devices you have connected to, their keys, and how far each one has caught upThe same database
A record of unlocks, refused files, and codes you issuedThe same database
Theme, currency, haptics, lock, reminder noteThe app's key-value store

All of it is inside the app's own container. Other apps cannot read it.

One row in that table travels further than the rest, and you should know which one. Payment details are the only thing here meant to be read by somebody else: share a trip and the handles in it go with it, because that is what they are for. Everything else stays on the device unless you send it.

None of it is in your device's system backup. The ledger, the photos you attach, the avatars and any trip file handed to the app are all deliberately excluded, so a new device starts empty. That is not an oversight: the key that decrypts the ledger never leaves the device it was made on, so a copy of the database in iCloud or on a computer could not be opened by anything, including Cashvy. Leaving it there would cost you storage and give you nothing back.

The only copy that exists outside the device is a Cashvy backup you make yourself, from Settings. It is one encrypted file, opened by eight words that are shown to you once and stored nowhere. Cashvy cannot open it for you.

A backup holds the ledger and not the pictures. Every trip, expense, settlement, loan and change is in it; the photos you attached and the avatar you picked are not, because they are files beside the ledger rather than entries in it. Restore onto a new device and the numbers all come back with the pictures missing.

A backup also brings back the trips you host. It holds a key that lets the device you restore onto take hosting back from the device you lost; the other people in the trip see that it moved. Which means anybody with the file and its eight words could do the same, so keep the two apart. After a restore, make a new backup: the one you used brings the ledger back again, but not the hosting.

Start over removes all of it — the ledger, the photos, the settings and the keys. Nobody else's copy is touched, and there is no way back except a Cashvy backup.

Deleting a trip erases it from your device: its expenses, settlements, photos and history, and anybody you know only through that trip. Nobody else's copy is touched and nothing is sent to them. Their devices may go on sending updates for it, and yours throws them away without keeping them; to do that it keeps one line, the trip's random identifier, which says nothing about the trip. A Cashvy backup made before you deleted it still contains it, and is the only way back.

Ending a trip is not deleting it. It is a fact about the trip, so it reaches everybody in it: the trip moves to Past trips on every device, keeps its history and its balances, and anybody in it with the app can reopen it.

Deleting an expense is different, because an expense belongs to everybody in the trip. It is removed from everyone's totals, on every device in the trip, and the record of it stays in the trip's history.

Your name in a trip

When you join a trip that already has your name in it — a friend added you before you had the app — Cashvy asks which one is you. Your answer is how you appear in that trip and nowhere else. Your own name and picture, the ones you set up in Cashvy, stay exactly as they were, and every other trip goes on showing you as you.

Everybody in the trip can see which device took which name. That is what makes the answer safe to give with one tap, and it is also why a wrong tap is easy to see. If you picked the wrong one, That's not me on the trip takes it back from your own device, without asking anybody, and lets you pick again.

Two names are not yours to take this way. The host's name can never be taken. And a name another device already holds — your own, on a device you replaced — only moves to your new device if the trip's host approves it; the device it moved from is told.

Who hosts a trip

The device that starts a trip hosts it. The host can hand hosting to somebody else in the trip, who has to accept it, and everybody in the trip sees who hosts now. Nobody can remove the host from a trip until hosting has moved; a backup can bring hosting back, as described above.

The camera, and photos

Cashvy asks for the camera at the moment you point it at something, and uses it for two things: photographing a receipt, and scanning a friend's pairing code. Both are read on the device. Nothing is uploaded, and there is no service behind either feature — which is why they work with the aeroplane mode on.

Reading a receipt uses text recognition that runs on the device — on iPhone and iPad, the same one your photo library uses to find words in your own pictures. The picture is not uploaded, the text is not uploaded, and neither is sent anywhere to be read.

A picture you attach — an avatar, a receipt, a payment screenshot — is copied into the app's storage and resized. The original stays in your photo library untouched. Cashvy asks for photo access at the moment you pick a picture, not at launch, and never reads your library on its own.

Reminders

A reminder is a notification your own device schedules and shows. There is no push token, no notification server, and nothing to send one to. The words you set as your reminder note are kept on the device and appear in the notification, which a locked screen will show unless you have turned previews off.

When you end a trip that still has money open, Cashvy offers once to remind you in three days. It is the same kind of reminder: it names the trip and no amount, and it goes away by itself if the trip is settled first.

Widgets

The Cashvy widget shows what you are owed and what you owe in each currency, and the name and position of your current trip. It shows no names of people and no expenses. To draw it, the app writes those few figures to a small file that only Cashvy and its own widget can read, protected so that it cannot be read while your device is locked. The widget never opens your ledger, and nothing is sent anywhere.

If you turn on the Face ID lock, the widget shows only "Cashvy · Locked", with no amounts and no trip name, unless you also turn on "Show amounts on widgets" in Menu. That setting is off until you turn it on.

Siri, Shortcuts and the app icon

Asking Siri or a shortcut to add an expense, scan a receipt or open a trip, or choosing one from the app icon, only opens Cashvy on that screen. Face ID comes first if you have turned the lock on, and nothing is saved until you tap Save. Nothing is sent to us. Siri handles your request the way it handles any request to open an app, under Apple's own privacy terms. To list your trips in Shortcuts, Cashvy keeps their names in the same protected file as the widget; with the Face ID lock on and amounts hidden, that list is empty.

Trip summaries

A trip summary is a PDF made on your device. It goes wherever you send it from the share sheet, and nowhere else.

Connecting a friend

There are two different things called connecting, and they disclose different amounts, so they are described separately.

A friend reading a trip in their browser. You show a code; their browser and your device exchange encrypted messages. The introduction is made by a relay that never holds the key and therefore cannot read anything it passes on — it sees an anonymous session identifier and a stream of ciphertext, and it keeps nothing once you disconnect. The messages that set the connection up are sealed too, so the relay does not learn how either device is connected to the internet.

Connecting their copy of Cashvy to yours. This is the six words, and the code on your screen is the same six words drawn as a QR, so reading them out and letting a friend scan them are the same act. The words are the secret. The first two are the address the two devices meet at; the other four are never sent anywhere, in any form, including a form the relay could work backwards from — so a relay that watched the whole exchange cannot work out the code or read a word of what passed. A code works once, stops working when you leave the screen that shows it, and tells nobody anything about you: it is six words drawn at random and nothing else. One wrong attempt spends it, and you make a new one.

What that one exchange leaves behind is permanent on purpose: each device keeps the other's key. That is what lets a later trip travel without another code, and it is the thing the switch in Settings turns off.

How often your device looks. While Cashvy is open: with a trip on your screen it checks every fifteen seconds for the first five minutes; otherwise it checks every thirty seconds and slows down, as far as every twelve minutes or so, while nothing arrives. Pulling down on a list checks at once.

While Cashvy is closed, it asks iOS to wake it now and then so new entries are waiting when you open it. iOS decides when, not us — often overnight or while charging, sometimes not for a day, never in Low Power Mode, and less often if you rarely open Cashvy. A wake does exactly what an open app does: it checks the same mailbox, the same way, and sends nothing else anywhere. Turning off Background App Refresh for Cashvy in Settings stops it, and the app then checks only while it is open. It cannot wake before the first unlock after your device restarts.

When your friend's device is not there at the same time, what they sent waits for you. It waits sealed, at an address that is different every week and that only your two devices can work out, and it is deleted as soon as your device collects it — or after fourteen days if it never does. Nobody can open it but you, including us. Nobody can leave anything in it but a device you have already connected to in person, because an address cannot be worked out any other way.

What this costs, stated plainly. The mailbox can see that *something* was left and later collected, roughly how big it was, when, and from which two internet addresses. It cannot see what, or who, or which trip. That is more than the relay learns, and it is the price of your friend's expenses arriving without the two of you being in the same room. You can turn it off.

Your ledger is never uploaded to it. Menu → Syncing shows you what it has been doing — who it reaches, when it last looked, and what came back. That screen reads the device's own records and asks nothing of anybody.

Addresses, which is the part most policies are vague about. Connecting two devices means two connections, and a connection has an address at each end.

The relay's own code never reads one: it does not log an address, does not store one, and does not count against one — the ceiling that stops the service being flooded counts the whole service rather than any caller, and works without knowing who is calling. The platform it runs on is a different answer and we will not pretend otherwise. Cloudflare sees the address of every request, because that cannot be avoided, and the abuse limits that keep the service standing are applied there, by address. Those are counters inside somebody else's infrastructure, not records we keep or can read — and a VPN changes what they see, where nothing in our software can. The page you signed up for the beta on reads no address at all.

A friend joining from a browser can add one more request, and it goes to the same company. If your device and their browser cannot reach each other on the same network, each asks a public STUN server what internet address it appears to come from, so that they can find a direct route. Cashvy uses Cloudflare's, at stun.cloudflare.com. The request carries that question and nothing else — no code, no key, nothing from your ledger — and Cloudflare sees the address it comes from, as it does for the relay. Connecting two copies of Cashvy, the mailbox, and handing a trip to a device at the same table never send it.

The mailbox changes what that is worth, and this is the one place in Cashvy where coming back regularly costs you something. A relay sees two addresses for the length of one dinner and then there is nothing left to compare it to. A mailbox is somewhere two devices return to, so the same pair of internet addresses shows up again and again — under a different mailbox address every week, which stops one week being linked to the next by its address, and not by its endpoints. Somebody patient enough, with access to the mailbox's own machines, could build a rough picture of who syncs with whom from that alone. Nothing in the software prevents it. A VPN does, and Tor does.

When a camera opens a web page instead of the app

A pairing code drawn as a QR is also an ordinary link, to join.cashvy.app, so that your friend's own Camera app can open it. If they have Cashvy, the link goes straight into the app and nothing is fetched. If they do not, their browser loads a page that tells them so.

Loading that page is a request to a web server, and a web server sees the address it came from. The code itself does not go with it: it rides in the fragment of a link — the part after the hash — which browsers never send. The page sets no cookie, runs no analytics, and loads nothing from anybody else.

What a shared trip says about your device

Every entry Cashvy writes is signed, so that anyone you share a trip with can tell that nothing in it was altered on the way. That signature carries a public key belonging to this device — a random-looking value that says nothing about you, your name, or the device itself, but which stays the same for as long as the app is installed. It is how a friend's copy of Cashvy can recognise your entries as yours. It travels with a trip you share, and only with a trip you share.

A trip also carries the name you chose, the names of everybody in it, what each expense was for and what it cost, and the payment details anybody has typed. That is what sharing a trip means.

It does not carry a single photograph. A receipt you photographed and a picture you set as your avatar stay on the device they were taken on — there is no path in Cashvy that sends an image anywhere, to a friend, to a browser or into a backup. What travels in their place is a filename, which means nothing on anybody else's device, and the house mark you can pick instead of a photo, which is one of a fixed set of drawings the app already ships.

A loan to somebody you are connected to always asks them to accept or decline it, which makes it a trip of its own with the two of you in it. You can cancel it until they accept. A loan to somebody who does not have Cashvy stays on your device, and nobody else sees it.

What we cannot do

Because there is no account, and because nothing we run can read your ledger:

  • We cannot recover your data if you lose your device.
  • We cannot delete your data for you — it is not ours to delete. Removing the app removes it.
  • We cannot tell you which devices have a copy of a trip you shared. Your device can, in the trip's member list.
  • We cannot read, recover or hand over anything waiting in a mailbox. It is sealed to your device and we do not have the key.

Children

Cashvy has no account system, collects nothing, and shows no advertising, so there is nothing to collect from anyone of any age.

Questions

To ask a person, write to hello@cashvy.app. If you have found a flaw in how any of this works, security@cashvy.app goes to a private mailbox rather than a public tracker.