Private mode
Private mode is a choice you make for your household. In a private household, your data is encrypted with a key only you hold, and we can't read it while you're signed out.
That sentence is the whole promise. Three things it does not cover:
- While your household is unlocked, our servers can read it. They have to, to show it to you, sync your banks and answer Sage. The services we use to do that see what we send them (listed below).
- "Signed out" means locked. Your household locks when you lock it, sign out, or stop using it for 15 minutes. See "When it locks".
- Your own devices, a broken-in server, and app updates. An unlocked phone or computer in someone else's hand, or a file you exported, is outside the promise. So is a server that has been broken into while your household is unlocked, and a future update of the app, because whoever can ship the app could ship one that gives the key away. On Android, Google Play signs the app.
Before you go private
- An owner makes it private. A household with more than one member, or with an invitation waiting, can go private: an owner makes it private with its members already in it. See "Sharing a private household".
- A phone or a computer. You go private on whichever you have. On a phone, it's the SageFin app on an iPhone, or on an Android phone with Android 12 or newer that keeps keys in its security chip: either a separate security chip, or a secure area of its processor. An Android phone that can't hold a key says so. On a computer, it's SageFin Desktop on a Mac or a Windows computer: see "Going private on a computer" under "SageFin Desktop". Either one becomes your household's first device, and you can add the other later.
- Where it opens afterwards. On the phones and computers that hold its key. A browser opens only when you approve it on your phone, because a computer never approves a browser. So while your key is only on computers, SageFin opens only in SageFin Desktop, never in a browser.
- How an Android phone keeps its keys. On Android 16 QPR2 and newer, the keys stay inside the phone's security chip, as they stay in an iPhone's Secure Enclave: each use needs your fingerprint, face or screen lock, so an approval that unlocks something asks twice ("Step 1 of 2", "Step 2 of 2"). On older Android, they are protected by the phone's security chip, which opens them only with your fingerprint, face or screen lock, every time. For each approval they are used in the app for at most 30 seconds, then erased. A phone keeps the way its keys were made: one that updates to Android 16 QPR2 goes on using the keys it has, and keys it makes after that (going private, being added to a household, recovering with a code) stay inside the chip. The first time a phone makes keys inside its chip, it uses them once to check they work, which asks for your fingerprint, face or screen lock twice ("Check that this phone can use its new keys"). Some phones make keys there and can't use them; such a phone protects its keys the older way instead, from then on, and nothing else changes. Settings → Security → Devices shows which each device uses: keys that stay inside the phone's security chip, or keys the chip protects that are used in SageFin each time you approve.
- An Android phone's hardware is checked when it's added. Going private, adding the phone or recovering on it, the phone sends its security chip's own signed statement about that key (Google's key attestation; for keys kept inside the chip, one for each key), and SageFin checks it: that the key is in the phone's security chip, that it was made by the SageFin app, that it needs you every time it's used, and that the phone's bootloader is locked. A phone that doesn't pass can't hold a key, and nothing is kept. What Devices shows for that phone is what the check found, not what the phone said. Phones added before this check aren't checked again, and an iPhone's Secure Enclave isn't checked this way.
- Four recovery codes. You write them down when you go private. If you lose every device that holds your key and all four codes, your data can't be opened again, by you or by us. Bank transactions come back if you link your banks again; your notes, splits, categories, rules, budgets and goals do not.
- Banks sync only while it is unlocked, or when you choose Sync and lock. See "While it is locked".
- Some things don't work in a private household: receipts by email, Apple Card updates in the background, and banks connected through Mastercard. Agents, including the SageFin plugin for Claude, read it only for an hour you approve on your phone: see "Agents". Investment prices and fund details are fetched only while it is unlocked, so they can be less up to date. Mail sent to your receipts address is not added. Apple Card updates each time you unlock SageFin on your iPhone.
To go private on a phone, open Settings → Security → Go private in the SageFin app. On a Mac or a Windows computer, choose Make This Household Private… from SageFin Desktop's Household menu (in older versions, its Retailers menu).
Unlocking in a browser
When a private household is locked, the browser shows This household is locked, with a square code and six digits.
- Open SageFin on your phone: an iPhone, or an Android phone that holds the key. (SageFin Desktop never approves a browser.)
- Go to Settings → Security → Approve a browser. If the app on the phone is locked too, tap Unlock a browser instead.
- Point the phone at the square code.
- The phone shows which browser is asking, how long ago, and six digits. Check the six digits match the browser's. If they don't, tap Don't approve.
- Tap Approve with Face ID (or Touch ID, or your passcode, whichever your iPhone uses; on an Android phone, your fingerprint, face or screen lock).
The browser says Approved. Opening… and your page comes back. Other tabs of the same browser open with it. A different browser needs its own approval.
The browser is never sent your key. Your phone sends it to our servers, sealed so that only this one request can open it.
Only approve a code shown on a screen in front of you. If someone sends you a code, or shows you one on their screen, and you approve it, you have unlocked your household for them.
If a code runs out (each lasts two minutes), choose Show a new code. The browser says what went wrong in every other case.
If the phone says This code is from SageFin test (or production), the browser and the app are using different SageFins. Nothing was sent. Open the browser on the same SageFin the app uses, or switch the app to the one it names.
SageFin Desktop
SageFin Desktop shows the same locked page, with one difference: it can be one of your household's devices, so its window opens without reaching for your phone. On a Mac, its key is kept in the Mac's security chip and is used only after Touch ID (or your Mac's password). On a Windows computer, its key is kept in the computer's security chip (the TPM) and is used only after Windows Hello: your face, fingerprint or PIN. Linux computers can't hold a key, so there it unlocks with your phone, as a browser does.
- On a computer that holds the key (one your household went private on, or one added to it), the locked page leads with Unlock with Touch ID on this computer (on Windows, Unlock with Windows Hello on this computer). Press it, and the computer asks you with Touch ID or Windows Hello; approve, and the window unlocks. (An older copy of SageFin Desktop opens its own unlock window first: choose Unlock there.) SageFin Desktop's unlock window also opens by itself when the window comes up locked. The page can ask, but only Touch ID or Windows Hello approves, and the computer asks every time. If you cancel, nothing is unlocked and you can press the button again. To use your phone instead, choose Use your phone instead, and the square code appears.
- On a computer that isn't one of your devices yet, the page shows the square code as usual, and Add this computer below it. That opens the same thing as SageFin Desktop's menu item Use This Computer to Unlock SageFin…: the computer shows a code for your phone to scan (on your phone, Settings → Security → Devices, then Add a device), then twelve characters both screens show. Add it only if they match. On Windows, adding it asks for Windows Hello twice: once to make its key, and once to sign the request.
- Only Touch ID or Windows Hello unlocks it. It unlocks SageFin Desktop's own window, and a Sync and lock when your bank has new activity. It never approves a browser: your phone does that.
If the page offers neither, your copy of SageFin Desktop doesn't do this yet.
Going private on a computer. SageFin Desktop on a Mac or a Windows computer can make your household private and be its first device, as a phone can. You don't need a phone for it.
- In SageFin Desktop, choose Make This Household Private… from its Household menu (in older versions, its Retailers menu). (In its window, Settings → Security offers Make this household private on this computer, which opens the same thing.) It says first whether your household can go private now.
- The computer makes your household's key in its security chip, and shows your four recovery codes once. Write them down, and keep them somewhere safe away from that computer.
- Type one of them back, to show it is written down right.
- Choose Make private. Touch ID or Windows Hello asks twice: once to set up the key, and once to check that it opens your household. Then your household locks, and you unlock it on that computer, as above.
What changes when your key is only on computers:
- SageFin opens only in SageFin Desktop's window, on a computer that holds the key. A computer never unlocks a browser, so a browser shows the locked page and has nothing to scan it with.
- No phone notifications. Nothing reaches a phone: no new-device alerts and no "waiting for a key". SageFin Desktop shows its own notification when your bank has new activity.
- Bank syncs wait until you unlock on that computer, or choose Sync and lock there.
- Losing that computer without your recovery codes loses your household. With a code, you get back in from the SageFin app on a phone (see "Recovery codes, and a new phone"). A recovery code can't set up a computer.
- Adding another computer, or a phone. On a computer that holds the key, choose Add a Device… from SageFin Desktop's menu. Start on the new device (on another computer, Use This Computer to Unlock SageFin…; on a phone, add the phone in the SageFin app) and type the code it shows under its square code. Both screens then show twelve characters; the computer asks you to confirm each group in turn, and Touch ID or Windows Hello asks once before it adds the device. Add it only if every group matches.
- Once you have a phone that holds the key, the phone adds devices, as in any household with one, and a computer no longer can.
- Some changes still need a phone: new recovery codes, going back to standard, and resetting the household. Settings → Security → Devices lists each computer as SageFin Desktop on a Mac or on Windows, with where its key is kept.
What Windows protects, and what it doesn't. Windows has no one place that does what a Mac's Secure Enclave does here, so SageFin Desktop joins two. Its keys are made in the TPM and can't be copied off the computer. The TPM uses them only with a password that is stored nowhere: SageFin Desktop works it out each time from a signature Windows Hello makes only after you approve it. So every unlock asks for Windows Hello, and a program that can't get past Windows Hello can't use the keys. Settings → Security → Devices shows a Windows computer as SageFin Desktop on Windows, with its key in the TPM, opened with Windows Hello. It is weaker than a Mac in these ways:
- The password is briefly in SageFin Desktop's memory each time it unlocks. On a Mac the security chip checks Touch ID itself. Harmful software already running on your Windows account that caught the password then could use the key afterwards without asking you. It still couldn't copy the key off the computer.
- It relies on Windows Hello's signatures staying the same each time, which Microsoft doesn't promise. If that ever changes, SageFin Desktop says it can't open its key, and you add the computer again from your phone. Nothing is lost: your other devices still unlock.
- Resetting or removing Windows Hello removes the key, and the computer unlocks with your phone until you add it again.
- Windows Hello's prompt uses Windows's own words. It doesn't say what you're approving. What you pressed does: the locked page's Unlock with Windows Hello on this computer, or SageFin Desktop's own unlock window behind the prompt. Either way, it only ever unlocks that window or syncs your banks.
- It won't hold a key over Remote Desktop, or where Windows can't show that Windows Hello's own key is in the TPM.
Browsers your phone remembers
- A browser your phone does not remember gets a warning first: "This iPhone does not know this browser." (On Android, "This phone does not know this browser.") Your phone also says when the browser is on a different network from the phone, and in which country, if it can tell. That is normal when your phone is on mobile data. It is a reason to look twice, not proof of anything.
- Approving a browser does not make your phone remember it. Until you say to remember it, each unlock of that browser lasts 15 minutes in all, and your phone warns you first each time.
- When that unlock ends, your phone asks, for example: "Chrome on Windows was unlocked today, 2:10 PM–2:25 PM. Remember it?" Nothing is remembered unless you tap Remember, which asks for Face ID (on Android, your fingerprint, face or screen lock). The question waits in Settings → Security → Unlocked browsers, and an iPhone also gets a notification about it (an Android phone gets none yet). The browser never asks this itself.
- Every time a browser is unlocked, your phones are told: "A browser was unlocked: Chrome on Windows." If it wasn't you, go to Settings → Security → Unlocked browsers and tap Lock beside it. Locking it there also forgets it, so if it asks again, your phone warns you again.
- In a household with other members, they are told too, without your name on their lock screen: "Another member of your household unlocked a browser: Chrome on Windows." Tapping it opens Settings → Security → Unlocked browsers (after Face ID if the household is locked on that phone), where the browser's row says whose it is, for example "Unlocked now: Alex, on a browser". Any member can lock it from there.
Agents
An agent is an AI app you connect to SageFin, with a token or by signing the app in: the SageFin plugin for Claude is one (see Connecting an AI app to your data). In a private household an agent can read your data only for an hour you approve on your phone, an iPhone or an Android phone that holds the key. SageFin Desktop doesn't approve agents. An agent you approve counts as you being signed in, for that hour.
- When the household is locked to it, the agent is told so and SageFin asks you. An iPhone gets a notification: "An agent is asking to read your household." The request also waits in Settings → Security → Agents asking, in case the notification never arrives; an Android phone gets no notifications yet, so look there. It lasts two minutes; the agent asks again if it needs to.
- The first time an agent asks, your phone says "Not one of yours yet", and when the token was made or the app first connected. Only go on if you made that token or connected that app yourself. Sign in and approve asks for Face ID twice: once to sign the agent in on this phone, once to approve it. An Android phone asks for your fingerprint, face or screen lock instead.
- After that, your phone names the agent as it was signed in, for example "Cursor laptop, token sfin_a1b2c3d4, signed in from this iPhone on 3 October", and approving asks for Face ID (or your fingerprint, face or screen lock) once.
When you approve an agent, it can read your household for up to an hour while it is working, and so can our servers, even if you sign out. It stops sooner after 15 minutes without a request from that agent. Only that agent is let in: not a browser, and not another of your tokens. Every phone of the household is told, and the agent is listed in Settings → Security → Unlocked browsers with Lock beside it. Lock now ends it, as it ends everything.
An agent can change your data only as it could before: a token needs permission to make changes, an app needs Can make changes, and the household's own setting still applies. While the household is locked to it, an agent can neither read nor change anything.
If you didn't ask an agent to do anything, tap Don't approve, then revoke the token or disconnect the app in Settings → Integrations. That ends its hour at once and forgets that it was signed in. After you say no, SageFin doesn't ask you about that agent again for 15 minutes.
When it locks
- You lock it. In a browser, open the menu behind your name and choose Lock now, or use Lock now in Settings → Security. On your phone, it is in Settings → Security. With one member, that locks it everywhere: every browser and the phone. In a household shared with other members, Lock now locks only your own browsers, phones and agents, and other members stay signed in; Lock everyone locks it for every member, everywhere. Any member can use either. See "Sharing a private household".
- You sign out. Signing out locks it if no other browser or phone has it unlocked. If SageFin can't be reached as you sign out, it locks 15 minutes later instead.
- You stop using it. After 15 minutes with no typing, clicking, tapping or scrolling, it locks. A page left open does not count as using it.
- 12 hours pass. An unlock never lasts longer than that. An agent's hour is never longer than an hour.
- We update SageFin's servers. Every private household locks. Unlock again as usual.
- You remove a device. The household gets a new key and locks everywhere.
In a shared household, Lock now ends only your own agents' hours; Lock everyone ends every member's.
The unlock belongs to the browser, not the tab. Closing one tab while another is in use locks nothing. On a computer that isn't yours, choose Lock now or sign out before you leave it.
A page you are looking at shows This household is locked as soon as the household locks from somewhere else, such as Lock now on your phone or Lock beside that browser in Settings → Security → Unlocked browsers, and what it was showing is taken off the page. If SageFin can't tell the page straight away (its connection dropped, say), the page checks every 15 seconds instead. A tab in the background checks when you come back to it.
While it is locked
We can't use your bank connections while your household is locked, so no bank is asked for anything new unless you choose to sync. Whatever came in is fetched the next time you unlock, and sorting it into categories and any alerts about it happen then too.
When a bank has new transactions, your iPhone gets one notification: "There's new activity in your household. Open SageFin to catch up." It names no bank and no amount. A card's new statement balance, minimum payment or due date, or new investment prices, wait for your next unlock without a notification. Opening it offers two choices:
- Sync and lock. Your banks sync, and the household locks again within two minutes. While it syncs, our servers can read your data to add the new transactions, and their merchant names go to our AI provider to be sorted into categories. Nothing opens it on a screen.
- Sync and open. An ordinary unlock on your iPhone.
If the household was unlocked somewhere else while it synced, your iPhone tells you it is not locked, instead of saying it locked again.
If the app says This alert is from SageFin production (or test), the notification came from a different SageFin than the one the app is using. Nothing was synced or sent. Switch the app to the one it names to see what is waiting there.
The bell shows the notifications we keep outside your household's data. Alerts about your accounts and spending wait until you unlock. Our email digest says only how many notifications are new and how many of your banks have activity waiting, and nothing about what they are. The top-movers email is not sent.
Just after you go private, each bank's access is replaced at Plaid. That happens while you have the household unlocked; the phone shows Banks still being secured until it is done.
Backups
SageFin backs up a private household while it is unlocked, and once more as it locks, so what you changed that day is copied straight away. A locked household can't be opened, not even to copy it. If the copy as it locks is missed, the next time you unlock SageFin copies the household before it does anything else. Settings → Security says when it was last backed up, on your phone and in a browser that has it unlocked. If something has changed since, it adds: "Changes made since then may not be backed up yet." A household that has just gone private says "Not backed up yet." until its first backup.
Recovery codes, and a new phone
Each of your four codes can be used once, to make a new phone a key to your household: an iPhone, or an Android phone that can hold a key. You type it into the SageFin app on that phone. A code is never typed into a browser, and can't set up a computer. To see how many codes you have left, or to replace them, go to Settings → Security → Recovery codes on your phone. SageFin Desktop can't make or replace codes. In a household with more than one member, each member has four codes of their own: that screen counts only yours, and replacing them leaves the other members' codes as they are. If you have none yet, it says so and offers Make your recovery codes. Where the codes are shown, Copy puts all four on your iPhone's clipboard to paste into your password manager: only on that iPhone, not your other Apple devices, and cleared after 2 minutes. On an Android phone, Copy marks the codes as sensitive, so the phone's copy preview and your keyboard's clipboard suggestions don't show them, and SageFin clears them from the clipboard after 2 minutes (or as soon as it next opens, if it was closed). Android can't keep the clipboard on the phone: some keyboards and phone makers sync it to your other devices, so if yours does, write the codes down instead. An Android phone also blocks screenshots and screen recording while the codes are shown.
Going private, adding or removing a device, replacing or making codes, and giving a member a key need a sign-in from the last 15 minutes. If yours is older, SageFin asks you to Confirm it's you on the same screen: with your passkey (Face ID) if this phone has one, or with a code SageFin emails you. Then it carries on where you were. You stay signed in, so your household stays unlocked, and anything already done on that screen, like the recovery codes you just wrote down, is kept. If you would rather, Sign out and sign in instead still works: signing out locks the household, so you unlock it again, and SageFin then brings you back to the same screen.
If you lose your phone: sign in to SageFin on a new phone and tap Use a recovery code on its locked screen. Then remove the lost phone in Settings → Security → Devices, which gives your household a new key.
To add a second phone: update SageFin on both phones first. On the new phone, tap Add this iPhone (on Android, Add this phone). A phone that isn't one of your household's devices offers this as soon as it opens, before you try to unlock. If your first phone is an iPhone, it gets a notification: "A new device is waiting to be added to your household." On your first phone, go to Settings → Security → Devices, tap Add a device, and scan the code the new one shows. If the camera can't read it, tap Type the code instead and type the code shown under it. Both phones then show twelve characters in three groups. Your first phone asks about one group at a time: check it is the same on the new phone, then tap Same on both. Add with Face ID (or whatever your phone uses) works only after the third group. If any group is different, tap Not the same and don't add the phone.
Each phone adds a random part to the characters that the other can't know in advance. If anyone, us included, swapped in keys of their own, the characters would match only by luck: about one chance in a billion billion.
Device names. A new device is named after its model, such as "iPhone 15 Pro" or "Galaxy A17". To rename one of your devices, unlock the household and tap it in Settings → Security → Devices. A name is only a label: renaming doesn't change the household's key, asks for no Face ID, and locks nothing. You can rename your own devices, not another member's. Devices added before names came from the model keep their names until you rename them.
Sharing a private household
A household can go private with its members already in it, or with one member who invites the others afterwards. Only an owner can make it private, from Settings → Security → Go private on their phone, and every key it makes is that owner's: their phone and their four recovery codes. The other members then see Waiting for a key, and get theirs as a new member does, below. The promise then reads: "Your household's data is encrypted with a key only its members hold, and we can't read it while all of you are signed out." Members aren't hidden from each other. While any of you has it unlocked, our servers can read all of it.
Adding a member. An owner invites them from a browser, as for any household. The invitation then has to be confirmed on an owner's phone, in Settings → Security → Invitations to confirm. After that, any member who holds a key can give the new member theirs.
- The new member accepts the invitation and opens SageFin. A browser, or a phone with no key, says Waiting for a key, and the household stays locked to them. On their phone they tap Ask for a key on this iPhone (on Android, …on this phone) and keep that screen open. Each member who can give them a key gets a notification on their iPhone: "A member of your household is waiting for a key." An Android phone gets no notifications yet, so a member whose only key is on one has to look. A phone that is already another member's key, such as one the owner used before, says so and can't ask: the member it belongs to removes it first, from Settings, then Security, then Devices on their own phone. If their phone asks again, the newer request replaces the older one, so each phone is listed once.
- A member with a key opens Settings → Security → Members waiting for a key on their phone and chooses Give a key. A person who was not invited, or whose invitation an owner has not confirmed, can't be given one. An owner can give a key before confirming the invitation, and the entry offers Confirm the invitation so that the other members can give one too.
- Both phones show twelve characters in three groups. On a call, or side by side, read them to each other one group at a time. The member giving the key taps It matches for each group, and giving the key works only after the third. If any group is different, tap It doesn't match and don't give the key.
- The new member's phone unlocks, and asks them to Make my recovery codes: four of their own. If they skip it, SageFin asks again the next time they open the app, until they have made them.
When a member leaves or is removed. Leaving means deleting your account; an owner can also remove a member. Their access ends at once: they are signed out of the household, and their browsers and agents lose it. But their devices and recovery codes still hold a key until the household is given a new one. The Remove confirmation in Settings → Members says so before you remove anyone from a private household.
- The new key is given at the next unlock on a remaining member's phone. It says who left and when, and asks you to Give it a new key, with Face ID twice. Your banks get a new key at the same time. Then the household locks for everybody, and you unlock it again.
- You can tap Later, and your phone asks again at each unlock. It tells you when it has been a week or more. Until it is done, what is added to the household can still be opened by the person who left, and Settings → Security says so to every member.
- If an owner removes a member from their phone, the new key follows at once.
When the person leaving holds the only keys. If you hold every key and others remain, they would be left unable to open the household. Before your account is deleted, SageFin gives you two choices:
- Give them a key first, if someone is waiting for one.
- Leave, and keep it locked, the default. The others can open it only with one of your recovery codes, if you give them one.
Leaving never deletes the household: it stays with the others. Only its last member can delete it, as "Resetting or deleting a private household" says.
When the last owner leaves, the member who has held a key longest becomes an owner. A household can have several owners, and any of them can do what an owner does here.
Lock now and Lock everyone. Lock now locks your own browsers, phones and agents. Lock everyone locks the household for every member, wherever they are. Any member can use either.
Delete my account is on the locked screen, after "Can't unlock?". In a shared household it opens the choices above, and your account is deleted at once. In a household of one, it deletes your account and the household after 72 hours: see "Resetting or deleting a private household".
Using another member's recovery code. A recovery code is its member's. Someone else's code works only once that member has left the household, or has died: while they are still a member, using it is refused, and they can give you a key instead. If no remaining member holds a key, the locked screen says Nobody here holds a key to this household and offers Use their recovery code. Type one of the departed member's codes into your phone: it becomes your key, and that code is used up. Their other devices and codes can still open the household until it gets a new key, so your phone asks you to Give it a new key next, as when any member leaves. Then make your own four recovery codes in Settings → Security. Every other iPhone of the household's members gets a notification that a former member's recovery code was used to add a phone, so a code used by somebody nobody expected does not go unseen. Without one of their codes, nobody can open it, by you or by us, and it can be deleted and started again.
What we can and cannot see
When your household is locked, our servers hold no key to it, and we can't use your bank connections to fetch it again.
When your household locks, the keys our servers were given are erased at once. Pieces of data the server had already decoded are normally overwritten within about a minute. We can't guarantee that, and the longest they can remain is until we next update SageFin's servers.
Going private doesn't hide the past at once. Our backups from before you went private were made under our key. For about eight days we could still recover your data as it was then from them, with effort; after that, the key that opens them is gone. Merchant names and investment symbols already in our shared lists, and lines already in our logs, from before you went private, are not covered at all.
Your banks. Plaid, which connects your banks, can give us back a bank's access if we ask its support, for example to end a connection after a household is deleted. With it we could, in principle, fetch that bank's data again. It does not open anything else in your household.
What we keep and can read at any time: who you are and how you sign in; your household's name and the names you give your devices and retailer accounts; which banks you have connected, whether each connection works, when it last synced, and whether it has new activity waiting; when your household's data last changed and when it was last backed up (the times, not what changed); which browsers, phones and agents have unlocked it, and when; which agents your phones have signed in; your notification settings; your subscription; what you write to support; and a record of activity without its content, such as when a sync ran and how many transactions it brought, and how much the assistant was used.
Who else sees your data while it is unlocked: Amazon Web Services (where our servers run); Plaid (your bank data); the AI provider Sage uses, or your own if you set one; OpenAI's moderation service (what you type to Sage); Cloudflare (every request, on its way); Clerk (who you are); Resend (email we send you); the fund data services we use (which investments you hold); Brandfetch (which websites' logos you see: merchants' websites, the bank or website you chose for a manual account, and apple.com for Apple Card, Cash and Savings. Your own device asks it for each logo, so it sees those website names and your device's internet address, and nothing else about your household); Plaid's logo service (which merchants, from your own device); Apple (notifications on an iPhone); Google (notifications on Android); Grafana (our logs); Sentry (crash reports from the phone app); and, for an hour you approve, an agent and whoever runs it (what it reads).
Going back to standard
In the SageFin app, on an iPhone or Android phone that holds the household's key, go to Settings → Security → Come back to standard. SageFin Desktop does not offer it. Our servers then hold the household's key again, nothing needs unlocking, and your banks sync on their own. The backups made while it was private become readable to us again. Your phone says so before you confirm. It keeps its keys for 8 days, in case we have to restore from before, then forgets them. You can't go private again until eight days after you last went private.
Resetting or deleting a private household
Reset (Settings → Security → Reset this household, in the SageFin app on a phone that holds the key) deletes every account, transaction, budget and rule, and starts the household again empty. It stays private, with the same devices and recovery codes. Banks have to be linked again. It needs the household unlocked on one of its devices.
Delete (Settings → Security → Account data → Delete account, in the SageFin app on an iPhone or Android phone that holds the household's key, while it is unlocked) deletes your account and everything in the household, and ends your bank connections at Plaid. We email you when it is done. SageFin Desktop can't delete a household, and in a browser Delete account says to do it on a phone that holds the key.
Only the last member can delete a private household. While anyone else is still a member, Delete account names them instead: each has to leave, or be removed by an owner, first. Until then you can leave yourself, which deletes only your account; the household and everything in it stay with the others. If someone joins while a deletion is waiting, it does not go ahead: when its wait is over SageFin ends it, and nothing is deleted.
If you can't unlock it any more, with no device and no recovery code left, choose Can't unlock? Delete my account on the locked screen. Nothing is deleted for 72 hours; then your account and everything in the household are deleted. We email you when you ask, again a day before, and once more when it is done. Unlocking the household in that time cancels it. We can't end your banks' permissions at Plaid without unlocking, so we will ask Plaid to end them. For a bank you linked more than a few minutes before, we ask through your household's own record at Plaid, which needs nothing from your locked household, and Plaid usually ends it within minutes of the deletion. You can end them yourself sooner at my.plaid.com.