Skip to content

Privacy Policy.

Last updated: 20 November 2026

Foliopeak is owned by Rackel Ltd, a company registered in England and Wales (company number 14567038), and registered with the Information Commissioner's Office (registration number ZC283586) (“Foliopeak”, “we”, “us”). This policy explains what information we collect when you use Foliopeak, why we collect it, who we share it with, and the rights you have over it.

At a Glance

What We Collect

  • Your name and email address

    To run your account. We never store your password.

  • The figures you add

    We never connect to your bank or ask for a bank login. A screenshot you scan is read on your device and not kept.

  • Messages you send us

    Kept for 12 months, then deleted.

  • Your IP address, briefly

    To stop abuse. Hosting logs are deleted within 7 days.

What We Don't Do

  • No selling your data

    And we don't use it for advertising.

  • No advertising cookies

    Only cookies the site needs, or that remember your choices.

  • No tracking across other sites

    Visits are counted as totals only, and you can turn that off.

Where It's Held

  • Your database is in London

    Backed up every night, also in London.

  • A short list of named providers

    Each works on our instructions, under a written agreement.

  • Legal safeguards for anything sent abroad

    For example Cloudflare and Stripe, under UK-approved safeguards.

Your Rights

  • See, correct or delete your data

    Email us and we reply within one month.

  • Download or delete everything yourself

    Any time. A few records are kept for a while, listed below.

  • Complain to the ICO

    The UK's data protection regulator, if you're unhappy with our answer.

Information We Collect

Account information

When you create an account, we collect your name, your email address and, if you choose one, a password. Foliopeak receives your password briefly, to screen it against known breaches and to pass it to our authentication provider, Neon Auth. We never store it, log it or write it to a database. Neon Auth keeps only a salted one-way hash of it (a scrambled version that can't be turned back into your password), never the password itself, and our application code never reads that hash. Before a password is set, a one-way hash of it is calculated and only the first five characters of that hash are sent to Have I Been Pwned, so a password already known from a breach cannot be used; the password itself is never sent to them, and nothing is stored from the check. If you sign in with Google instead, no password is involved and the OAuth exchange (the handshake with Google that signs you in) is handled by Neon Auth.

Signing in with Google, and Google Sheets. If you choose Continue with Google, Google tells us, through Neon Auth, your name, your email address and whether Google has confirmed it, the link to your Google profile picture, and an ID for your Google account. We use these only to create your Foliopeak account, sign you in and show your name. We never receive your Google password, and we can't see your Gmail, Drive, contacts or anything else in your Google account. If you connect Google Sheets to keep a live copy of your accounts, you give Foliopeak permission to create and update spreadsheets: it only ever writes to the one sheet it created for you, never reads your other spreadsheets, and keeps the connection's access tokens (the keys for that connection) encrypted so the sync can run. We don't sell Google user data, use it for advertising, or share it with anyone except the providers named on this page who run Foliopeak for us. It is deleted when you disconnect Google Sheets or delete your account, and you can remove Foliopeak's access at any time at myaccount.google.com/permissions. Foliopeak's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Notion. If you connect Notion to keep a live copy of your accounts, debts, goals and bills, Notion asks which pages to share with Foliopeak. Foliopeak writes three tables under the page you choose, never reads anything else in your Notion, and keeps the connection's access token (the key for that connection) encrypted so the update can run. It is deleted when you disconnect Notion or delete your account, and you can remove Foliopeak's access at any time in Notion, under Settings, Connections.

You can also sign in, or sign up, with a link we email you instead of a password. Neon Auth makes the link and we send it. If you sign up this way, we keep the name and email address you gave, and any referral code, until the link has made your account, and for no more than two days.

If you turn on two-factor authentication, we store the information needed to verify your one-time codes, plus a set of one-way-hashed backup codes. The plaintext (readable) backup codes are shown to you once, at setup, and never stored.

If you add Face ID, a fingerprint or a security key (a passkey) as your second step, we store its public key and ID, a counter your device sends with each use, how it connects (for example USB or built in), a name for it worked out from your browser and the kind of key (for example "iPhone" or "YubiKey"), and when it was added and last used. We never receive anything biometric: your face or fingerprint is checked by your device and does not leave it, and the device only tells us the check passed. Adding or using a passkey also stores a random one-time challenge, which stops working after five minutes. Passkeys are removed when you remove them, turn two-factor off or delete your account.

To warn you about sign-ins from somewhere new, we keep a short record of each device your account signs in from: the browser and system (for example "Chrome on Windows"), a rough location worked out from your connection (a town and country), and when it was first and last used, plus any name you give it. Each signed-in session is linked to its device, so Settings shows which session is which; that link is deleted when the session ends. We never keep your IP address for this. The record is used only for those emails and that list, and is deleted with your account.

Financial information you enter yourself

Foliopeak does not connect to your bank, broker, or pension provider, and never asks for your banking credentials. Every account, holding, transaction, balance and goal in Foliopeak is information you've added yourself - typed in, imported from a file or read from a screenshot. We store it so we can show it back to you - as your dashboard, your tax-year tracking, your net worth history, and your calculators.

Screenshots and photos. When you add accounts, debts or a balance from a screenshot or photo, or show Cairn a picture, it is read in your browser, on your device, by Tesseract (free text-reading software that Foliopeak serves from its own site). The picture is not sent to Foliopeak or to any other company, and it is not kept once it has been read. You see what it found and can change it, and only the names and amounts you then save are stored, like figures you type.

If you use the business tools, we also store the figures you save there - your income for the year, expected turnover and expenses, whether you pay Scottish income tax, whether it's your first Self Assessment year, and your company's year end. If you import your business accounts, or type them in, we store the figures you confirm - turnover, expenses, profit, cash at bank, retained profit, a director's loan and Corporation Tax owed - with the period they cover and which accounting software they came from. The report file itself is read in your browser and never uploaded. When you log a payment against your tax reserve, we store what you were paid and what you set aside; and which company year-end checklist items you have ticked.

To build your net worth history, we save a daily record of your net worth (and a breakdown by account type) once a day when you visit, or on demand if you use the "Save today's figures" button - both are stored the same way as everything else above.

If you use the Retirement overview, we also store the year you were born, the age you plan to retire, your State Pension forecast, what you pay into pensions, your expected retirement spending and any retirement income you add. They are used to show that page and to fill in Good and Bad Years when you open it from there.

If you use the household feature, we also store what you choose to share for a combined view - your ownership share of joint accounts, and (if you invite a partner) their email address, sent by us so they can join. A Partner member's invite also carries an invite code to the site, labelled with the inviter's name and linked to the partner's account once they join. Everyone in a household sees the others' accounts, debts, budget and tax-year allowance figures, and any family map entries they choose to share, read-only, until they leave it. If you choose to share an employer share grant with them, they see its company and vested value, not its units, prices, notes or vesting schedule. That sharing stops when anyone joins or leaves the household.

If you use the family map (part of Household, on the Partner plan), we store what you add to it: where accounts, pensions, policies, property and documents are held or kept, reference numbers, notes, and the names and contact details of people you list, such as a solicitor. It is for where things are, not how to get into them, and it turns away entries that look like a password, PIN, recovery code or card number. A household partner sees only the entries you choose to share with them. Someone you share your portfolio with sees your whole map, including executor notes on your accounts, only if you include it in that share. Your note to your family is stored encrypted with the rest of your family map. It is seen by you, by someone you share your portfolio with if you include the map, and by your trusted contact if your map is released - never by a household partner.

Saved calculator figures

If you save a calculator's figures under a name, we store that name, the figures in the boxes, the results as the page showed them and the date, so you can open them again or compare them. We never save whether you ticked Blind Person's Allowance, because that is information about your health. Remove a saved set at any time; they are deleted with your account.

Learning Hub progress

If you use the Learning Hub, we save which articles you've finished and whether you got full marks, and, for the daily review question, which questions you've answered and when each is next due. It's stored with your account so your progress follows you between devices, and it isn't used for anything else.

We also save which parts of Today you did on each day, your last Find My Gaps result (your level on each topic and the guides it suggests), and the Expedition checks you have ticked. Play Together saves nothing unless you both choose Keep it. If you do, we store that one result with your account: the two names shown on it and what each of you picked. You can remove it there at any time. Text you paste into the Jargon Decoder stays in your browser and is not sent to us.

Information you send us directly

If you use the contact form, we receive whatever name, email address, and message you provide, and any screenshot you attach, so we can reply to you. If you use Contact support inside the app, we receive your message, your email address, the page you were on and any screenshot you attach.

Contact support also has a box, unticked unless you tick it, saying we may quote your message on the Foliopeak website. If you tick it, we store that and the first name and town you give, and we may then show your words, or part of them, on the website with that name and town and nothing else about you. Email us and we take a quote down; the message itself goes after 12 months, like any other.

Technical information

We process your IP address for security purposes - specifically, to rate-limit sign-up and sign-in attempts (limit how often they can be tried) and reduce automated abuse. We don't use it for tracking or profiling.

Cloudflare, which hosts Foliopeak, keeps a short log of requests and errors so we can find and fix what breaks: the page asked for (never anything after the "?" in its address), when, details such as your IP address, and any error. It is deleted automatically after no more than 7 days.

How We Use Your Information

We use the information above to:

  • Provide and run your Foliopeak account - your dashboard, calculators, tax-year tracking, and goals
  • Authenticate you and keep your account secure, including two-factor authentication and rate-limiting
  • Send account-related emails - email verification, password reset, sign-in links, and (if you invite one) a household partner invite
  • Respond to you when you contact us
  • Process payments and manage your subscription, if you're on a paid plan (Solo or Partner)
  • Meet our own legal and accounting obligations
  • Count how Foliopeak is used, as totals that never identify you, so we can improve it

We do not use your information for advertising, and we do not sell it to anyone.

If You Connect an AI Assistant (Cairn)

Cairn lets you connect an AI app you already use - Claude, or other AI apps that can connect to it - to your Foliopeak data, so you can ask about your own numbers in plain English. It is off unless you turn it on. Cairn is read-only by default. You can choose to create a key with write access, which can only propose changes - new balances, new accounts, bills, journal entries, allowance payments, trades, goals, family map entries or fixes for your notifications. It cannot move money, delete data or change account settings, and nothing changes until you approve it inside Foliopeak. Any key, read-only ones too, can also suggest keeping one of Cairn's live tools on your Tools page. That changes none of your figures, and it is kept only when you approve it in Foliopeak.

A key with write access works through Cairn and through Foliopeak's API, and both can only propose a change. It waits in Foliopeak, showing exactly what would change, until you approve or decline it while signed in, and expires after 7 days. You can't approve it if anything it relies on has changed since it was proposed. Revoke a key in Settings and it stops working immediately.

How the write side is held back, control by control:

  • A key that can make changes can only suggest them. Every write tool - balances, new accounts, bills, journal entries, allowance payments, trades, goals, family map entries, fixes for notifications - creates a proposal, and so does keeping a tool on your Tools page. Several at once arrive as one batch. The key applies nothing itself.
  • You approve inside Foliopeak. You approve every change inside Foliopeak, while signed in. If anything it relies on has changed since Cairn suggested it, the change is turned down and nothing is saved. Changes that arrive together are approved or turned down together.
  • Suggestions expire, and only so many can wait. A proposal expires after 7 days, and at most 20 can wait at once. Past that the tools answer with a message to approve or decline some first, so a runaway or hijacked assistant fills one card, not your account.
  • Making changes has to be switched on. Only a key you create in Settings, choosing write access, can propose changes to your figures. Connecting an assistant with one click issues a read-only key, which can only suggest a tool to keep on your Tools page, and no assistant can raise its own permission.
  • A limit each hour. A key may propose at most 30 changes an hour.
  • Everything is logged. Every request a key makes is in the Cairn request log, and every approval and decline is in your account's audit log.
  • Switched off in one click. Revoking a key in Settings stops it immediately.

We do not see your conversation. We receive only the request your AI app sends, such as “summarise my portfolio”, and any text it asks us to save, such as a journal entry you asked for.

We keep a log of those requests - which one, when, and whether it succeeded, including any balance it updated - and show it back to you on the Cairn page. It exists so you can see what left your account and when, which is the thing worth being able to check after connecting a third party to your finances. Entries are deleted automatically after 12 months, and revoking the API key stops any further access immediately.

The data your assistant receives goes to whichever AI provider you chose, under their terms and their privacy policy, not ours.

Our Legal Bases for Using Your Information

UK data protection law requires us to have a specific reason for each thing we do with your information, and to tell you what it is. Ours are:

  • Running your account - Performance of a contract. You asked us to provide Foliopeak; storing the accounts, investments and goals you enter is how we do that.
  • People you list on the family map - Our legitimate interests (a reason the law allows when it is needed and fair to you) in you being able to record who to contact. We store the names and contact details you add, show them to you and anyone you share the map with, and delete them with your map or your account.
  • Taking payment for a paid plan - Performance of a contract, for the subscription itself. Keeping the resulting records is a legal obligation - UK tax law requires us to retain them.
  • Account security email - Performance of a contract, and our legitimate interests. Password resets, verification, sign-in links and sign-in codes are not optional extras; an account you cannot recover is not a usable account.
  • Keeping the service working and preventing abuse - Our legitimate interests. Rate limiting, the bot check on sign-up, and blocking fraudulent payments protect every other user, and none of it requires knowing anything about you beyond what we already hold.
  • Children's accounts you add - Our legitimate interests in you being able to track money you hold for a child. We store the child's name you give with the account's figures, and delete them with the account or yours.
  • Our customer list - Our legitimate interests in knowing who is waiting for Foliopeak and who is using it. We keep your name, email address, where you signed up from, your plan and the date you joined on a list in our own database - never your figures.
  • Quoting a support message - Consent. Only if you tick the box on Contact support. Email us and we take the quote down.
  • Counting how Foliopeak is used - Our legitimate interests in knowing whether Foliopeak works for the people using it. We count things like how many people signed in this month or saved a goal, as totals only. For the shared Partner pages (Household, the Family Map, the Couples Tax Plan and Retirement for Two), we keep only when you last opened each one, so we can count how many households use them; it is deleted with your account. When you start a paid plan, we keep which page you went to Billing from on the plan at Stripe, and count it - with checkouts opened, plans paused, plans kept after cancelling and any reason you give for cancelling - as totals with no account on them, so we know which features people pay for. We keep when you first saw What Changed or your Monthly Review, to count how long setting up takes (not if you turned off Count my visits), and, during a free trial, your answer if you choose to answer our one question about which feature you'd pay for - both counted as totals only. No one is followed around the app, and no cookie or tracking script is used for it.
  • One free trial per card - Our legitimate interests in stopping the same card being used for free trial after free trial. If you start a free trial, we keep a scrambled code made from your card (never the card number itself), so each card gets one free trial.
  • Optional emails - Consent. Monthly Review reminders, Tax Year Reminders and the newsletter are off unless you turn them on. Turn any of them off in Settings, or with the unsubscribe link in the email, and that consent is withdrawn straight away. If you tell us why you unsubscribed, we keep your answer, any note you add and the month for 13 months, not linked to your account or email address.
  • The Cairn request log - Performance of a contract, and our legitimate interests in you being able to audit what an assistant you connected has read. Only kept if you use Cairn at all, and deleted after 12 months.
  • Your trusted contact - Performance of a contract, at your request: you choose who we write to if you die, what they get, and whether they can see your account read-only for a year. We use their name and email address for that alone, and delete them when you remove the contact or your account.

Where we rely on legitimate interests, we have considered whether our reason is outweighed by your rights, and we think it is not - but you can object, and we will look at it properly.

Who We Share Information With

We use a small number of service providers to run Foliopeak. Each only receives what it needs to do its specific job:

  • Neon - our database and authentication provider. Hosts your account details and everything you enter into Foliopeak.
  • Amazon Web Services - keeps the nightly backups of the database, and copies of any documents you attach to accounts, in London, in an account kept apart from the rest of Foliopeak. The site can add a backup but cannot change or delete one. New backups are encrypted before they reach AWS, with a key AWS does not hold. Documents are only ever copied encrypted.
  • Cloudflare - hosts the application itself and handles web traffic.
  • Resend - sends emails on our behalf. This includes account security emails (password resets, email verification, sign-in links and codes), contact-form messages, household and portfolio-share invites, payment receipts and failed-payment notices for paid plans, and any notifications you have turned on. Security emails contain a one-time link or code tied to your account. No email we send contains your figures - balances, holdings, amounts, rates or allowances - or the names of your accounts, goals, debts, providers or companies, or where you are: an email says that something has happened or needs a look, and links to the page in Foliopeak where the detail is, behind your sign-in.
  • Stripe - processes Solo and Partner subscription payments. We never see or store your card details; Stripe's own checkout page handles that directly.
  • Google - if you choose to sign in with Google, or connect Google Sheets to export your data, the relevant exchange happens directly with Google under your control.
  • Notion - if you choose to connect Notion, Foliopeak writes the accounts, debts, goals and bills you pick to the Notion page you pick, under your control.

Each of these acts as our processor: they handle your information on our instructions and for no purpose of their own, under a written data processing agreement (a contract setting out how they may handle your data). We remain responsible for it either way. You can read each agreement: Neon, Amazon Web Services, Cloudflare, Stripe and Resend.

Stripe is also a controller (a company that decides for itself why and how personal data is used) in its own right for parts of what it does - fraud prevention and meeting its own financial-services obligations - which it explains in its own privacy policy.

Foliopeak's calculators and news pages also call market-data and currency providers (for share prices, exchange rates, and headlines), public news feeds and, for a property value estimate, HM Land Registry. These only ever receive a ticker symbol or ISIN, a currency code, a postcode, or a request for general headlines - never your name, your balances, or anything that identifies you. They are not our processors (companies that handle your data for us), because they get nothing about you.

Where prices and company figures come from. Share and fund prices come from Yahoo Finance and Massive (a market data service), and a fund's ISIN (its ID code) is matched to its ticker with OpenFIGI (Bloomberg's free list of these codes). Exchange rates come from Massive, central banks' official rates through Frankfurter, Yahoo Finance, ExchangeRate-API and HMRC. Crypto prices come from CoinGecko. Past prices for the “What If I'd Invested?” tool, and US companies' results dates, come from Financial Modeling Prep. Prices can be delayed. The Stock Screener's figures come from each company's own yearly accounts: for US companies, as filed with the SEC (the US regulator, the Securities and Exchange Commission); for UK and European companies, as collected by filings.xbrl.org. A company name in another alphabet is shown in English from GLEIF (the Global Legal Entity Identifier Foundation, the public register of company IDs). Where a company is based comes from the SEC, GLEIF and the company's own yearly report, and what it does from Wikipedia (found through Wikidata). Its stock market values, dividend yields and P/E figures come from Yahoo Finance, and so do the companies of other countries, which have only those figures. These sources are sent nothing about you.

Property value estimates. If you ask for an estimate of a property's value - on a property account or with the property value calculator - the postcode you enter is sent to HM Land Registry's public Price Paid Data service, to find past sales at that postcode. The local council area of the matching sale is then sent to its UK House Price Index, to see how prices there have moved since. The same postcode is sent to the government's register of Energy Performance Certificates (EPCs, the energy rating every home has to have when it is sold or let), and then the number of the matching certificate, to show the home's energy rating and floor area. The house number or name you type is matched against those results on our own server and is never sent. Nothing that identifies you goes with any of these requests, and we don't keep the postcode. HM Land Registry and the EPC register are public open-data services, not our processors (companies that handle your data for us): they answer the lookup and receive nothing else from us.

If you choose to have a property follow house prices, its postcode is sent to HM Land Registry once, to find its local council area. We keep that area with the property, not the postcode, and once a week ask the UK House Price Index for the area's latest figure; the area's name is all that request carries. Stop following and the area is removed.

We don't share your information with anyone else, and we don't sell it. If that ever changes for a specific new feature, we'll update this policy first. The exceptions are ones you make yourself: a household partner, someone you share your portfolio with, and a trusted contact you name - who gets only what you chose, and only when it is released, as set out under How long we keep your information.

Where Your Information Is Held

Your database is in the UK. Everything you enter into Foliopeak - your accounts, holdings, transactions, goals, journal entries and family map - is stored in a Neon database hosted in London (AWS eu-west-2), and backed up every night to Amazon Web Services, also in London, in an account kept apart from the rest of Foliopeak.

Some of the services around it do operate internationally, and we would rather say so than imply otherwise:

  • Cloudflare - Serves the site from whichever data centre is nearest to you, so request data (such as your IP address) may be processed outside the UK. Also holds any document you attach to an account, your profile picture if you add one, and any screenshot you attach to a message to us, in private storage in Western Europe. Covered by the UK Addendum to the EU Standard Contractual Clauses (the UK's approved safeguards for sending personal data abroad) in its data processing agreement.
  • Stripe - US-based. Certified under the UK Extension to the EU-US Data Privacy Framework, which is a transfer mechanism (a safeguard for sending personal data abroad) the UK government recognises.
  • Resend - US-based. Also certified under the UK Extension to the EU-US Data Privacy Framework.
  • Google - Only involved if you choose to sign in with Google or connect Google Sheets, and only for that exchange.
  • Notion - US-based. Only involved if you choose to connect Notion, and only for what Foliopeak writes to the page you pick.

Cookies and Local Storage

Cookies. Foliopeak sets only cookies of its own that the site needs or that remember a choice you made:

  • Signing in - a small number that keep you signed in and remember that you've passed two-factor verification for your current browser session. Some last only a few minutes, while you sign in with Google, confirm your email or change it.
  • New device emails - one that recognises this browser as a device you've signed in from before, for up to 400 days, so we can email you when your account is signed into from somewhere new.
  • Invite-only access - while the site is invite-only, one that remembers you've come in with an invite code (for up to 30 days from your last visit, re-checked every hour so a withdrawn code stops working) or with the site's access password (for up to 30 days). If an AI assistant's sign-in sends you to the invite page, another remembers that sign-in for up to 15 minutes, so you can carry on after.
  • Connecting a service - while you connect Google Sheets or Notion, one that lasts up to 10 minutes and checks that the reply comes from the connection you started.
  • Roadmap votes - if you press "I want this" on the Roadmap page, one that holds a random number so you can take your vote back, for up to 400 days. We keep only a scrambled copy of that number (a hash) with the vote, and nothing that says who you are.
  • Your settings - ones that remember the colour theme, text size and "hide balances" choice you picked, whether you turned off Count my visits (below), whether you opened Foliopeak as an installed app, and whether you chose Not now on Summit's goal step.
  • This visit only - one that remembers the logo animation has already played, so it doesn't play again, until you close the browser, and one that shows a thank-you for a minute after a Support Foliopeak payment.

When you sign in, sign up or send us a message, Cloudflare runs a quick security check (called Turnstile) to stop automated sign-ups.

Local storage. Your browser's own storage keeps a few settings on this device so the app remembers how you left it: which cards and sections you've folded shut, your chosen Learning Hub layout, whether you've already seen today's question, whether game sounds are muted, and which AI assistant you picked on the Cairn page. It also keeps a copy of your Learning Hub progress so the Hub loads instantly - the progress itself is saved to your account, as described under "Learning Hub progress" above. If you turn on the biometric lock, it also keeps an identifier for the passkey your device created - Foliopeak never receives your fingerprint or face data, which stays with your device's own biometric system. Apart from that Learning Hub copy, these settings are used by the app in your browser, are not sent to us, and are never used to track you.

When you pay, you do it on Stripe's own checkout page, which sets its own cookies for payment security and fraud prevention under Stripe's privacy policy.

Because all of this is either strictly necessary or remembers choices you have made, there is no cookie banner. We don't use advertising cookies or tracking scripts. The one analytics script is Cloudflare Web Analytics, from the company that already hosts the site: it counts page views and load times, sets no cookie, stores no personal data and does not follow you across sites. If you'd rather not be counted, turn off the switch below: it remembers your choice on this device with one small cookie, and the script is left out of every page from then on. Signed in, the switch is also saved to your account, so it follows you to every device you sign in on. The same switch is in Settings, under Preferences.

Clearing your browser's data for foliopeak.com removes everything above; signing out removes the sign-in cookies.

The Early-Access List

While Foliopeak is invite-only, the page you reach without an invite code offers to tell you when it opens. If you use it we store the email address you give us and whether you asked for the monthly newsletter as well, and when you confirmed it - no name, no tracking, and nothing else.

We use it to email you once to say you're on the list (or, if you ticked the newsletter box, to send the confirm link instead), to email you once when Foliopeak opens, and, only if you ticked that box and then pressed the confirm link we email you, the monthly newsletter on how Foliopeak is being built. If an email to the address bounces for good or is reported as spam, Resend tells us, we note that against the address, and no more optional emails go to it. Our legal basis is your consent, which you can withdraw at any time: every one of those emails has an unsubscribe link, and one click is enough. The address is held in our database in London, where we keep track of who is waiting, and sent through Resend, the email provider named above. It is never sold, and never passed to anyone beyond Resend.

If you have an account and turn the newsletter on in Settings, that choice is stored in the same list. It is removed, or switched off, when you delete your account.

We keep it until Foliopeak opens or until you ask us to delete it, whichever comes first. Email hello@foliopeak.com to see what we hold, correct it, or have it deleted.

How Long We Keep Your Information

We keep your account and the information you've entered for as long as your account is active, so Foliopeak can keep working the way it's meant to. You can delete your account and data yourself at any time, from Settings - or email hello@foliopeak.com and we'll do it for you.

If a Free account isn't used for 3 years (no sign-in, and no use through the iPhone app or an AI app you linked), we email you twice, a month apart, and then delete it on the date the emails give. Signing in before then keeps it. Accounts with a paid plan, a household or a trusted contact are not deleted this way.

Deleting your account removes your login and everything attached to it - accounts, holdings, transactions, goals, journal entries, family map, daily net worth records, household membership, Learning Hub progress and API keys. Three things survive, and it is only fair to say so: we keep your email address and the reason you gave, as a short record that the deletion happened and why, for 12 months, after which it is deleted automatically; our audit log keeps its record of security events on the account, such as API keys being created, by an internal ID rather than your name or email, for 24 months; and your data remains inside existing backups until those age out, which is about three months. Ask us and the exit record goes sooner. If you were paying, the plan is cancelled when you ask to delete and ended in Stripe when the account goes; Stripe keeps its own record of the payments you made, which it and we are required to keep for tax and accounting.

Free trials. If you start a free trial, our audit log keeps a record that you had one, with a scrambled code made from your card (never the card number itself), for 24 months - even if you delete your account. This is so each person and each card gets one free trial. After 24 months it is deleted automatically.

Messages you send us - through the contact form or Contact support - are kept for 12 months so we can follow up, then deleted automatically. Any screenshot you attach is deleted after 7 days. Deleting your account deletes your Contact support messages and screenshots straight away; the contact form isn't linked to an account, so a message sent there goes at 12 months, or sooner if you ask.

Sign-ups never confirmed. If someone starts an account but never confirms their email address, never signs in and adds nothing, we delete it automatically after 24 hours.

Your trusted contact. If you name a trusted contact in Settings, we keep their name and email address, the note you leave for them (encrypted), the word you choose for them (scrambled) and the choices you make. Nothing is sent to them while you're alive. It is released in one of two ways: when someone sends us a death certificate and we have checked it, after 14 days' notice to your email address, during which signing in stops it; or, if you choose, after the period without a sign-in you set (6 or 12 months), with warnings to your email address first. We then email them a link. They see your note once they confirm it's them, with a code we email to them and the word you chose for them, if you set one (we keep only a scrambled form of that word, which can't be turned back into it). If you chose to let them see where your money is held, they see it read-only, through their own account, for 12 months - it is not put in the email - and then your account is deleted. If you turned on read-only access, they can also see your Foliopeak, read-only, through their own account, and download your export, for 12 months - never with your login - and then your account is deleted, sooner if they ask. If they get only your note, your account is deleted 12 months after it is sent. If it was sent because you hadn't signed in, we write to your email address 30 days before your account is deleted. Removing your trusted contact, or deleting your account, deletes all of this.

When you delete something - an account, a holding, a trade, a debt, a goal, a bill, a planned spend, a journal entry or a share grant - or change a debt's balance, we keep a copy of what it was in your activity history, so you can undo it. Undo works for 30 days, and the history is deleted automatically after 90. Documents attached to a deleted account are kept for those 30 days so an undo can bring them back, then deleted. Text that is encrypted stays encrypted in the history. It is included in your data export, cleared by Clear all my data, and deleted with your account.

Backups are written daily to Amazon Web Services in London, in their own account, so that a failure is recoverable rather than final. Each is kept for about three months, then deleted automatically.

Your Rights

Under UK data protection law, you have the right to:

  • Ask what personal information we hold about you, and get a copy of it
  • Ask us to correct information that's wrong or incomplete
  • Ask us to delete your information
  • Ask us to restrict or object to certain uses of your information
  • Receive your information in a portable format

To exercise any of these, email hello@foliopeak.com. We'll respond within one month.

Making a Complaint

If you're unhappy with how we've handled your personal information, you can complain to us by emailing hello@foliopeak.com. Putting "Data protection complaint" in the subject line helps it reach the right place quickly. We'll acknowledge your complaint within 30 days, look into it, and tell you what we found and what we're doing about it without undue delay.

If you're not happy with our response, you can complain to the UK's data protection regulator, the Information Commissioner's Office (ICO).

Children

Foliopeak isn't intended for anyone under 18. We don't knowingly collect information from children. If we become aware that we have, we'll delete it.

If you add a child's account, such as a Junior ISA, we store the child's name you give and its figures, only to show them to you and anyone you share with. We use them for nothing else, and delete them with the account.

Security

We use industry-standard measures to protect your information, including encryption in transit (HTTPS, which encrypts data while it travels between you and us) and access controls on our systems. The free text you write, such as journal entries, notes and family map details, is also encrypted with a key kept outside the database before it is stored, as are your two-factor secret and any Google Sheets or Notion connection tokens; your numbers are not, because totals and charts need them. Your account, and the accounts, figures and notes you enter into Foliopeak, are stored in a UK data centre and backed up nightly to another, also in the UK. Documents and pictures you attach are held by Cloudflare in Western Europe. Some processing does happen outside the UK - Cloudflare serves the site from the data centre nearest you, and Stripe is US-based - which is set out in full under Where your information is held above, along with the legal mechanism covering each. No method of storage or transmission is completely secure, but we work to keep your information as safe as reasonably possible and to improve on that over time.

Changes to This Policy

We may update this policy as Foliopeak changes. We update the date at the top each time. If we make a change that matters, we'll email account holders before it applies.

Contact Us

Questions about this policy or your information? Email hello@foliopeak.com.