Personal Finance OS
On this page
  1. Who we are
  2. Summary
  3. Information we collect
  4. What we do not collect
  5. Product analytics
  6. How we use your information
  7. Who we share information with
  8. Where your data is stored
  9. How long we keep your data
  10. Early-access and waitlist emails
  11. Your rights and choices
  12. State privacy notices
  13. Children's privacy
  14. Security
  15. Changes to this policy
  16. Contact

Privacy Policy

Last updated: November 21, 2026 · Effective: June 14, 2026

liway ("we", "our", or "us") provides a personal-finance tool that helps you see how much money is safe to spend before your next paycheck. This Privacy Policy explains what information we collect, how we use it, who we share it with, where it is stored, how long we keep it, and the choices you have. By creating a liway account or using the liway website or mobile apps, you agree to the practices described here.

If you have questions, contact connect@liway.app.

Who we are

liway is operated by Liway LLC, a Colorado limited liability company. We can be reached at connect@liway.app for any privacy questions, data requests, or general support. The product is currently available only in the United States.

Summary

If you want the short version:

  • We collect your email, a hashed password, what you tell us about your money (or what your bank tells us via Plaid, or what your iPhone shares from Apple Wallet if you connect Apple accounts), and limited operational metadata.
  • We use that information to compute your leeway — how much room you have between now and payday — and to keep your account secure.
  • We do not sell, rent, or share your data with advertisers or data brokers. We do not run ads, and we use no advertising or cross-site tracking SDKs. The liway web and mobile apps use first-party product analytics (PostHog) to understand feature usage — aggregate, pseudonymous, and never including your financial data, and you can opt out in Settings.
  • If you subscribe, we record which plan you are on and whether it is active — never your card. Apple and Google take the payment; no card detail ever reaches us.
  • You can edit, export, or delete everything we hold about you at any time. Deletion is immediate and cascades across every system we use, apart from two deliberate exceptions described under When you delete your account.
  • All production data lives in the United States with SOC 2 Type II service providers.

Detailed disclosures follow.

Information we collect

We collect only what we need to compute your leeway and operate the service. There are eight categories.

1. Account information

  • Email address (your login identifier and the address we send transactional emails to)
  • Your name (used to personalize the app and your emails)
  • A bcrypt hash of your password (we never store the plain-text password)
  • Account creation timestamp and email-verification status

2. Financial inputs you enter

  • Current account balance
  • Paycheck amount and date
  • Upcoming bills (name, amount, due date, account)
  • Estimated spending until your next paycheck

These values are editable from inside the app at any time.

3. Bank account data (when you connect a bank via Plaid)

If you choose to link a bank account, our integration partner Plaid handles the bank login on our behalf. Plaid returns the following to liway:

  • Account names and types (checking, savings, etc.)
  • Current account balances (read-only)
  • A Plaid-issued access token that lets liway refresh balances later
  • Transaction history — see below

We never see, store, or transmit your bank login credentials. Those go directly from your device to Plaid. See Plaid's End User Privacy Policy at plaid.com/legal for how Plaid handles bank credentials.

How liway uses Plaid Transactions

We access your bank-account transaction history through Plaid for two purposes: to automatically detect the recurring patterns that drive the leeway calculation, and to show you your own activity.

  • Recurring paychecks — date, amount, and cadence of incoming deposits, so you don't have to enter your paycheck manually.
  • Recurring bills — name, amount, due date, and account of outgoing recurring debits, so you don't have to enter your bills manually.
  • Average discretionary spending — a rolling daily average computed from non-bill outflows, used to forecast the runway between now and payday.
  • Your own activity — Your Activity and Your Spending show you the transactions behind those numbers: date, payee or merchant name, amount, and category, so the leeway is something you can check rather than take on trust.

Your transactions are shown only to you. They are never used for advertising, profiling, or shared with any third party. The transactions table stores the rows needed to show you that history and to re-run detection if Plaid sends an update; nothing else is done with that data.

Where a purchase happened. For some transactions your bank also reports the merchant's address or website. We keep that with the transaction so the transaction's detail can show it to you. Together with the date, a merchant's address can say where you were, so it gets the same protection as the rest of your transactions: it is shown only to you, and only when you open that transaction. Open in Maps hands the address to the maps app you choose (Apple Maps or Google Maps) only when you tap it; no map service receives it before then. This is the merchant's location as your bank reports it, never your device's location: liway never asks for location permission.

You can disconnect your bank at any time (Settings → Disconnect). On disconnect we revoke the Plaid connection at Plaid before removing the local record.

4. Apple Wallet data (when you connect Apple accounts on your iPhone)

On an iPhone, you can choose to connect your Apple accounts: Apple Card, Apple Cash and Apple Savings. The data comes through FinanceKit, Apple's own framework for sharing Wallet data with apps you approve. iOS shows you a permission screen listing the accounts, and liway reads only what you approve there. There is no login involved and no credentials change hands: the data is read on your device, with your permission, and your iPhone then sends it to liway's servers. What arrives is the same shape as bank data:

  • Account names and types (card, cash, savings)
  • Current balances (read-only)
  • Transaction history, used exactly as described under How liway uses Plaid Transactions: detecting recurring patterns and showing you your own activity

Once stored, Apple Wallet data is protected and used the same way as bank data from Plaid: encrypted at rest, shown only to you, and never used for advertising, profiling, or shared with any third party. It takes part in the same leeway, bill, spending and forecast calculations, and shows on iOS, the web and Android.

Because the data is read on your iPhone, it refreshes when the liway app runs there: liway's servers cannot reach Apple Wallet on their own. The app shows how fresh each Apple account's data is.

You can disconnect your Apple accounts at any time (Settings → Disconnect), which deletes the stored data, and you can withdraw the permission itself in your iPhone's Settings. Apple receives no data from liway.

5. Operational metadata

We log a small set of operational events to keep the service secure and observable. None of this is sold or shared for advertising; it stays inside our hosting providers' logs:

  • Server-side access logs (from our hosting platform) — request method, path, response status, timestamp; request bodies are not logged.
  • Authentication audit logs — sign-in, sign-out, password change, account-deletion attempts (success and failure), with the associated user ID and a coarse timestamp.
  • Plaid item-status events — connection created, refreshed, expired, revoked.
  • Email-send audit (from our transactional-email provider) — recipient address, template name, delivery status.

6. Push notification tokens (only if you turn notifications on)

Notifications are off until you enable them. If you do, your device gives us a push token — the address the operating system uses to deliver a message to that one installation of the app. We store it alongside the platform (iOS or Android) and the time we last saw it, linked to your account so we know where to send your alerts. We do not attach a device identifier to it.

A push token is not an advertising identifier and cannot be used to follow you across other apps or websites. We remove it when you turn notifications off, when you delete your account, and automatically when Apple or Google tells us the app is no longer installed.

Notifications never contain amounts. An alert tells you something needs attention; the figures stay inside the app, behind your lock screen.

Who gets a notification, and when, is decided only by your notification settings, never by your financial data, Apple Wallet data included.

7. Subscription status (only if you subscribe)

Check In is free, and if you never subscribe there is nothing in this section to collect. If you do subscribe to Full liway, we record what we need to know whether your account currently has access:

  • Which plan you are on, whether it is active, in a trial, in a billing grace period or expired, and the date it next renews or ended.
  • A reference the store gives us for your subscription, so a renewal or cancellation can be matched back to your account.
  • An append-only log of the events behind it — purchased, renewed, cancelled, expired, restored — so we can tell what happened and when if something looks wrong.

This is linked to your liway account, because its entire purpose is to decide what your account can open.

We never see your card. Apple and Google take the payment under their own terms; no card number, expiry or billing address ever reaches liway. We cannot charge you, refund you, or cancel your subscription — those all happen at the store.

Subscription records are deleted with your account, along with everything else. One exception, described under When you delete your account: we keep a one-way fingerprint of your email address so a single free trial cannot be claimed repeatedly. It cannot be reversed to recover your address.

8. Sign-up and sign-in records

When you create an account, we keep a short record of where the sign-up came from. Each time you sign in after that, we keep a smaller record of the network you signed in from. We use these records for two things: keeping test and automated accounts out of liway's numbers, and spotting abuse. Only liway's operators can see them.

A sign-up record holds:

  • Your IP address, and the host name it resolves to (its reverse-DNS name)
  • Who owns that network (for example, your mobile carrier or internet provider), and whether it is a cloud or hosting network
  • The country and region your IP address points to. This is approximate and comes from the address itself; liway never asks for your device's location
  • Which app you used (iPhone, Android or the web), and its version and build number
  • In the iPhone and Android apps: the device model (for example "Pixel 9"), its operating-system version, and whether it is an emulator or a Google test device (Firebase Test Lab)
  • In the Android app: the Play Store's install referrer, which says which link or campaign, if any, led to the install
  • How you signed in (Google, Apple or email)
  • On the web only: the first page you visited, the website that linked you there, and any campaign tags in that link (utm tags). A first-party cookie remembers these for up to 30 days, until you sign up

A sign-in record holds the IP address and its host name, the network's owner, the country and region, the app with its version and build, the device model, operating-system version and emulator or test-device mark, and how you signed in.

We find the network's owner in a database file kept on our own servers. Your IP address is not sent to any other company for this.

How long we keep them is under How long we keep your data.

We do not collect your device's location, contacts, photos, advertising identifiers, or any signal from advertising or cross-site tracking SDKs (we run none), and we do not build a fingerprint of your device to recognize or follow you across apps or websites. The device model, operating-system version and test-device mark described under Sign-up and sign-in records are read only when you sign up or sign in, and are used only to keep test and automated accounts out of liway's numbers. The web and mobile apps do use a first-party product-analytics SDK (PostHog) for aggregate usage events — see Product analytics.

What we do not collect

  • Bank login credentials (Plaid handles these securely; we never see them)
  • Account numbers or routing numbers (Plaid does not surface these to us under the products we use)
  • Biometric data. If you turn on the app lock, Face ID, Touch ID or your device passcode is checked entirely by iOS or Android. Your face or fingerprint never leaves your device and is never sent to us — we only learn whether the check passed.
  • Your device's location — liway never asks for location permission (a merchant's address your bank reports with a transaction is described under How liway uses Plaid Transactions; the approximate country and region of your IP address at sign-up and sign-in are described under Sign-up and sign-in records)
  • Contacts, photos, microphone, camera, or other on-device data. The one exception is Apple Wallet data, which liway reads only if you connect Apple accounts, and only with the permission screen iOS shows you (see Apple Wallet data above)
  • Advertising identifiers (IDFA, AAID) — we don't run ads
  • Advertising or cross-site tracking and attribution signals — no ad networks, no Google Analytics for ads, no advertising SDKs. Our analytics is limited to first-party product analytics on the web and mobile apps, plus cookieless, no-PII page-view and click counts on our public marketing site (see Product analytics). The one link we note is the one that brought a web sign-up to liway, kept with that account only (see Sign-up and sign-in records).
  • Cross-site cookies

Product analytics

To understand how the product is used, the liway web app (my.liway.app) and mobile apps (iOS + Android) use PostHog, a product-analytics service hosted in the United States.

  • We record aggregate usage events only (e.g. a results screen viewed, a bank-connect flow started, the simulator used).
  • Events carry no financial data and no personal information — no balances, amounts, transactions, account or merchant names, email, or name; only non-identifying values like a count or a risk category.
  • You are identified only by a pseudonymous internal id, never your email or name; the mapping back to you lives only in our own database.
  • No session replay. Analytics data is never sold or shared and is used solely to improve liway. You can opt out in Settings.

Separately, our public marketing site (liway.app) uses a cookieless, privacy-friendly analytics tool for aggregate counts only: page views, and taps on our app-store buttons. It sets no cookies, collects no personal information, and does no cross-site tracking or device fingerprinting. It is entirely separate from the product and never sees any account or financial data.

How we use your information

We use the information described above to:

  • Authenticate you when you sign in (email verification at sign-up; password at routine login; multi-factor steps for password reset and account deletion)
  • Compute and display your leeway, risk level, and projections
  • Detect recurring paychecks, recurring bills, and discretionary-spending averages from Plaid and Apple Wallet transactions (as described above)
  • Refresh balances from connected accounts (from Plaid when you've opted in, and from your iPhone for Apple accounts)
  • Send you transactional emails — email verification, password reset, account-deletion confirmation
  • Send you an occasional email about liway — news such as a new version, or a personal note from our team — every one carries an unsubscribe link, and unsubscribing never affects sign-in or account emails
  • Send you a service notice when something affects your account or the service (an outage, a change to this policy) — these reach you even if you unsubscribed from news
  • Maintain audit logs of security-sensitive actions (sign-in, password change, account deletion) for breach-investigation and abuse-prevention purposes
  • Keep test and automated accounts out of liway's numbers, and spot abuse, from each sign-up and sign-in record (see Sign-up and sign-in records)
  • Respond to your support requests

We do not use your information for advertising, ad profiling, or selling to third parties. We do use aggregate, pseudonymous product analytics to improve the app — see Product analytics.

Who we share information with

We share information only with the service providers that make liway work. These providers are bound by their own privacy policies and security commitments, and they act as data processors on our behalf. Every provider that handles production user data holds a current SOC 2 Type II report or an equivalent independent security assessment.

We rely on the following categories of providers (and we name the ones you interact with directly, plus the ones the app stores require us to name):

  • Bank connection — Plaid. We use Plaid for bank linking and read-only balance + transaction retrieval. You interact with Plaid directly via the Plaid Link UI when you connect a bank. See Plaid’s End User Privacy Policy.
  • Apple Wallet connection (Apple FinanceKit). If you connect Apple accounts, your iPhone reads the data through Apple's FinanceKit framework with your permission and sends it to liway. Apple is not a data processor for liway and receives no liway-stored user data.
  • App distribution — Apple App Store and Google Play. They receive limited install / purchase metadata per platform policies; they do not receive liway-stored user data.
  • Cloud hosting — runs the liway API and admin dashboard
  • Managed database — stores account, financial, and bank-link data with encryption at rest
  • Transactional email — delivers verification, password-reset, and account-deletion emails, and the occasional news email or service notice (sent from a separate address; it reports whether each one was delivered or bounced, and liway does not track opens)
  • Product analytics — PostHog (US) — receives aggregate, pseudonymous usage events from the web and mobile apps (no financial data, name, or email)
  • Push notifications. Delivers the alerts you turn on, through Apple's and Google's push services. It receives your device's push token and the alert's text, which never contains amounts.
  • Website analytics. Counts visits to our public website (liway.app) without cookies or personal information. It is separate from the app.
  • DNS — resolves liway.app and its subdomains; no user data processed at edge
  • Source control + CI — hosts the codebase and runs deploy workflows; does not hold production user data

A complete, named list of subprocessors — including provider identity, role, data scope, current certifications, and the U.S. region each one operates in — is maintained internally and made available on request to connect@liway.app. We update the internal list whenever a vendor is added, replaced, or removed; this privacy policy does not need to be re-issued for vendor changes.

We do not sell or rent your information to anyone. We do not share it with advertisers, data brokers, or marketing partners. We do not participate in any data co-op, lookalike-audience program, or attribution exchange. This stance also reflects our obligations under the Plaid Developer Policy, which prohibits the sale of data accessed through Plaid.

Where your data is stored

All production data is stored and processed in the United States. Application servers and the primary database both run in U.S. East regions. Email-delivery and DNS providers use globally distributed networks, but neither processes data-bearing user content beyond what is necessary for delivery. Specific region details for each subprocessor are available on request at connect@liway.app.

If you access liway from outside the United States, your data is still transmitted to and stored in the United States.

How long we keep your data

We keep your data while your account is active. Two events cause deletion.

Sign-up and sign-in records

We keep the IP address and host name for 90 days. After 90 days, a sign-in record is deleted completely, and a sign-up record keeps only the network owner's name, the country, and whether it was a cloud or hosting network, along with the app, how you signed in and, on the web, where you came from. A daily job does this. Everything left is deleted with your account.

When you delete your account

You can delete your account from the Settings screen at any time. Deletion is gated by password reauthentication, a one-time email code (six-digit OTP), and a type-to-confirm step. On confirmation, the deletion cascade fires immediately:

  • We revoke your Plaid connection at Plaid (/item/remove) before removing the connection record on our side.
  • We delete every row that references your user ID across the user, financial, prediction, connection (Plaid and Apple Wallet alike), notification (including your push tokens and notification preferences), refresh-token, and verification-token tables.
  • We log the deletion action to an internal audit log (records the timestamp and the fact that a deletion occurred; does not contain your personal data).
  • A trial record survives, and it holds nothing about your money. We keep a one-way fingerprint (a salted hash) of your email address so that a single free trial cannot be claimed again by deleting an account and signing up afresh. It cannot be reversed to recover your address. If an operator had given you a trial of a particular length, that length and a short internal note of the reason are kept beside the fingerprint, so the same trial resumes rather than restarts if you come back.
  • And, only if an email to your address bounced for good or was marked as spam, a one-way fingerprint of that address stays on our do-not-send list, so we never email it again. It cannot be reversed to recover your address. Nothing else about you remains.

There is no recovery window today. We are evaluating adding a 30-day soft-delete grace period in a future release; if added, this policy will be updated.

If you can no longer sign in — you uninstalled the app, or lost the device — you can still have the account deleted. Delete your account explains how to request it by email, and what we verify before acting on it.

Inactive accounts

We do not automatically delete inactive accounts today. If you have not signed in for an extended period and would like your data removed, contact connect@liway.app.

Early-access and waitlist emails

Our website has forms where you can ask for an invite or join a waitlist before you have a liway account: for example, early access to something new we are building, or an invite to the liway web app. This section covers what happens when you use one of them.

  • What we collect. The email address you enter, the date you signed up, and which form you used (for example "early access"). Nothing else.
  • What we use it for. To send you the invite or news you asked for, and occasional news about liway. These are the only uses.
  • Who processes it. The same transactional-email provider that delivers our account emails sends these, under the commitments described under Who we share information with. The address is never sold, rented, or shared with advertisers or data brokers.
  • How to leave. Every email we send the list carries an unsubscribe link, or you can write to connect@liway.app. Leaving removes your address from the list.
  • How long we keep it. While the list is active. When an early-access program closes or the product it was for launches, we delete the addresses of everyone who never created an account. You can leave earlier at any time.

If you later create a liway account with the same address, the rest of this policy applies to your account; the list entry simply records that you asked to hear from us.

Your rights and choices

You have the following rights for as long as you have an account with us. We honor them for all users, regardless of state of residence:

  • Access. Every value liway stores about you is visible inside the app. You can also request a complete export (see "Data portability" below).
  • Edit / correct. Financial inputs, bills, paycheck details, and account info are editable from inside the app at any time. For other changes, contact connect@liway.app.
  • Disconnect your bank or your Apple accounts. From Settings, at any time. We revoke a Plaid connection at Plaid on disconnect; disconnecting Apple accounts deletes their stored data.
  • Delete your account. From Settings; this triggers the immediate cascade described above.
  • Opt out of "sale" of personal information. We don't sell personal information, so there is nothing to opt out of. Our practices on this point apply to everyone, not just California residents.
  • Withdraw consent. Disconnecting your bank, deleting individual records, or deleting your account are all operationally equivalent to withdrawing consent for the affected data.

Data portability

We do not have a built-in data-export feature today. If you would like a complete export of the data we hold about you, contact connect@liway.app; we will fulfill the request manually within 30 days. The export covers all data described under "Information we collect".

Submitting a privacy request

The fastest way to exercise any of the rights above is connect@liway.app. Please indicate (a) the right you are exercising, and (b) the email address on the account. We may ask you to verify the request by clicking a link sent to that email address.

State privacy notices

California (CCPA / CPRA)

liway does not currently meet the revenue or data-volume thresholds that trigger formal CCPA / CPRA applicability. As a posture choice, we honor the underlying consumer rights described above for all users, regardless of California residency. If liway grows past the thresholds, this policy will be updated to add the formal CCPA-mandated disclosures.

If you are a California resident and would like to exercise any of the rights described above, contact connect@liway.app.

Other states

Several states (Colorado, Connecticut, Virginia, Utah, Texas, others) have enacted comprehensive privacy laws. As above, our user-facing rights and operational posture (no data sale, no targeted advertising, full deletion right) apply to all users regardless of state. We update this section as state-specific obligations crystallize.

International users

liway is available only in the United States. We do not knowingly collect data from users outside the U.S. GDPR is not in scope today. If liway expands to the EU or UK, this section is updated before any non-US launch.

Children's privacy

liway is not intended for children under 13. We do not knowingly collect personal information from anyone under 13. If you become aware that a child under 13 has provided us with personal information, please contact connect@liway.app and we will delete it. We do not target advertising to children — we do not run advertising at all.

Security

We take reasonable measures to protect your information:

  • All connections to liway use HTTPS / TLS 1.2 or better; HSTS is enforced on all liway.app subdomains.
  • Passwords are stored only as bcrypt hashes; we never store plain-text passwords.
  • Authentication uses short-lived signed access tokens and longer-lived signed refresh tokens; refresh tokens on mobile are stored in the device's secure enclave (iOS Keychain / Android Keystore).
  • Email verification at sign-up gates access to any authenticated route (including bank linking); the verification link is single-use and time-bounded.
  • Account deletion requires password reauthentication PLUS a one-time email code PLUS a type-to-confirm step (anti-hijack protection).
  • Production data lives in managed cloud-hosting and database providers that operate SOC 2 Type II controls; volume-level encryption at rest is enforced by the database provider.
  • Access to production systems is restricted to authorized personnel with multi-factor authentication enabled on every account.
  • Deploys to production are run only by CI workflows (no human runs deploys locally); branch protection on the main branch blocks force pushes and direct deletions.

No system is perfectly secure. If we discover a breach affecting your personal information, we will notify you in accordance with applicable law, with a target customer-notification time of 72 hours from the time the breach is confirmed.

Changes to this policy

We may update this policy from time to time. Material changes will be communicated by updating the "Last updated" date at the top of this page and, for significant changes, by emailing you at the address on your account before the change takes effect. Older versions are preserved in the project's source-control history.

Contact

For privacy questions, support, or data-rights requests:

connect@liway.app

Liway LLC
Colorado, USA