lake.

Lake Financial: Privacy Policy

Effective November 15, 2026 at 00:00 UTC. This policy replaces the Privacy Policy effective October 5, 2026. Earlier versions are available on request. This policy does not replace the Terms of Service. The separate Apple Membership Supplement addresses native purchases without changing existing arbitration or other rights.

Effective date: November 15, 2026
Last updated: November 15, 2026

This revision describes the native iPhone app’s authentication, Apple purchases, local reminders, optional measurement, feedback and deletion controls; clarifies profile images, transaction-location metadata, provider requests and retention. It does not introduce advertising inside the native app or replace the Terms of Service. The August 31 revision history below is retained for context.

Revision note (August 31, 2026): this revision replaces the July 24, 2026 policy, whose source and SHA-256 hash are archived. It adds disclosures for Vercel Web Analytics, Google Analytics 4, the Meta Pixel on the public funnel pages, the first-touch campaign-attribution cookie, the HubSpot customer-relationship system, the in-product accuracy survey, the free trial, and marketing email, and it corrects the July version's statement that the Service used no analytics or advertising technology, which stopped being accurate when advertising measurement launched in August 2026. Because the prior policy understated actual practice, this revision was published on an accelerated schedule rather than after a 14-day notice window; the notice describing the change is shown in the Service. Review by outside counsel is recommended and pending; publication was directed by the owner.

Revision note (October 26, 2026): Lake no longer uses HubSpot. Feedback, survey answers, campaign labels and lifecycle records are kept only in Lake's own database, and the HubSpot recipient is removed. This removes a recipient and expands no collection, so it is a non-material change that takes effect when posted. Feedback sent from the public feedback page without an account is now deleted after 12 months. Feedback tied to an account is deleted with the account, as before.

Revision note (October 30, 2026): this revision adds a Cookie Notice and a U.S. state privacy rights section (Section 11) that lists the categories of personal information Lake collects, where it comes from, who receives it, and how to use your rights, including through an authorized agent and by appeal. It discloses Vercel Speed Insights, which measures page performance without cookies and receives page addresses only after the same clean-up Lake applies for Vercel Web Analytics. It adds commitments that Lake does not use your information to train generative AI models, does not buy personal information about you from data brokers, and does not use sensitive information to infer characteristics about you. It explains how Lake treats Global Privacy Control and Do Not Track signals. Privacy requests and notices go to support@lakefin.net only. These changes add protections and describe existing practice. They do not expand collection, add a recipient outside Lake's existing providers, reduce your choices or lengthen retention, so under Section 9 they take effect when posted.

Revision note (October 30, 2026): Lake now sends its marketing email, including the emails about your account's progress described in Section 2, through Loops, an email delivery provider listed in Section 3.1. Loops receives only your email address, your Lake account identifier, the name of the account event that triggers an email and, for the trial-ending email, your trial end date. Loops also records whether you open these emails or click a link in them. It never receives your name, balances, bank names or accounts, merchants or transactions. Deleting your Lake account also deletes the contact Loops holds. Marketing email was already a purpose of this policy, and an email delivery provider was listed as a recipient until October 26, 2026, so Lake treats naming the provider that now does that work as a non-material change. Under Section 9 it takes effect when posted.

Revision note (October 30, 2026): the Lake iPhone app is adding optional journal entries, which are the reflections you choose to save next to a place, month or goal: a rating of whether a place was worth it, a rating for a month, up to four enjoyment tags, and notes of up to 280 characters. Section 1.1 describes what Lake stores, Section 2 how it is used, Section 5 how long it is kept and Section 6 how to delete it. Lake stores journal entries in its own database under your account, encrypts the note text, shows entries only to you, and does not send them to Google Analytics, the Meta Pixel, Loops, any notification or any AI service. The policy already covers notes and labels you give Lake, and this adds no recipient and no longer retention, so Lake treats it as a non-material change. Under Section 9 it takes effect when posted.

Revision note (November 15, 2026): the Lake iPhone app now saves your app settings with your account so they follow you to a new phone or a new sign-in. These are your appearance and navigation choices, whether the weekly check-in is on and its day and time, whether you want goal-result notifications, which prompts you dismissed, an optional display name, and the avatar and boat you pick. Section 1.1 describes what Lake stores, Section 4 how it is protected, Section 5 how long it is kept and Section 6 how to delete it. The display name is encrypted. These settings are not sent to Google Analytics, the Meta Pixel, Loops, any notification or any AI service. Nearby-reminder places, coordinates and addresses still stay on your device and Lake does not receive them. Lake does not have a self-service export of everything it holds about you; a request for a copy is fulfilled by hand, as Section 6 describes. This revision is effective November 15, 2026, the release date of the app version that adds these settings.

This Privacy Policy explains how Rieper LLC, an Indiana limited liability company doing business as Lake Financial ("Lake," "we," "us"), collects, uses, protects, shares, and deletes information when you use www.lakefin.net and the Lake application (the "Service").

Lake exists to show you your own money clearly, so handling your financial data carefully is central to the work. This policy is written to be read, not skimmed past.

The short version

The rest of this document is the detail behind those statements.

1. Information We Collect

1.1 Information you give us

WhatDetailRequired?
Account identityEmail address and sign-in identifiers handled through Clerk; any name, username or profile image you provide or make available through a connected sign-in providerEmail and sign-in identity are required; name, username and profile image are optional
Optional profileBirth year you choose to provide, plus any legacy gender value you provided before that field was removedOptional: birth year is used only for an age-group comparison based on published public benchmarks; stored profile fields are encrypted at rest and separately deletable
Your labels and notesBudget and category names, goal names and targets, account nicknames, colors and icons, transaction notes, custom merchant categorization rulesOptional
AttachmentsReceipts and documents you attach to transactions (up to 4 MB per file, 5 per transaction)Optional
Support and feedbackSupport emails, including the sender address and any message, attachment, and email metadata you choose to send; answers you submit through in-product feedback prompts; in-app thumbs up, thumbs down, and dismissals on Insights, together with the Insight/template/instance context, relevant merchant, category, budget, or goal label, wording variant, and timestampOptional
How you heard about LakeIf you answer the optional setup question about where you heard about Lake, your choice from a short list and, if you choose "Something else", a short note of up to 60 characters. Lake stores it with your account, in our own database, to understand which channels bring people to Lake. It is not sent to Google Analytics, the Meta Pixel or any other advertising or analytics providerOptional
Journal entriesIf you choose to write them in the iPhone app, the reflections you save next to a place, month or goal: whether a place was worth it this month (Worth it, Okay or Not really); a rating for a month (Good, Mixed or Rough) and whether the month was worth it; up to four enjoyment tags for a place (Time with people, Time to myself, A treat, Part of my routine); and notes of up to 280 characters. Each entry is saved with the place, month or goal it belongs to, when it was saved and your account. Lake stores it in our own database, encrypts the note text, shows it only to you, and uses it to show your entries back to you and to show you patterns drawn from your ratings, tags and spending. It is not sent to Google Analytics, the Meta Pixel, Loops, any notification or any AI serviceOptional
App settings and profileIf you use the iPhone app, the settings you choose: appearance (system, light or dark) and navigation (tab bar or dial); whether the weekly check-in is on and its day and time; whether you want goal-result notifications; which prompts you have dismissed; an optional display name of up to 30 characters; and the avatar and boat you pick. Lake stores them in our own database under your account, encrypts the display name, shows them only to you, and uses them so your settings match on every device you sign in on. They are not sent to Google Analytics, the Meta Pixel, Loops, any notification or any AI service. Notification permission and the places you save for nearby reminders stay on your deviceOptional
Accuracy surveyIf you answer the one-time in-product survey about the spending summary ("the reveal"), your multiple-choice answers about accuracy and usefulness and any free-text notes about what surprised you or looked wrongOptional
Plan and trial statusYour plan, billing interval, subscription status, and, if you start the free trial, the trial's start and end datesCreated when you subscribe or start a trial

1.2 Financial information from your linked accounts

When you link a financial institution, Plaid Inc. facilitates the connection with that institution and provides us with account data on an ongoing basis. Depending on the institution and the accounts you select, this includes:

We do not receive or store your online banking credentials. You enter them through Plaid Link or authorize access through your financial institution's OAuth flow. Lake receives an access token, which is encrypted before it is stored and is used solely to fetch the data above.

Information handled by Plaid during connection. New bank connections in the native app request Plaid’s Transactions product. Its connection scope includes account-owner contact information, which may include name, email, phone number and address. This is separate from the transaction-location fields described above. Lake’s current native integration does not request Plaid Identity or Identity Verification and does not receive those owner-contact fields through its Transactions response.

Plaid also offers an optional returning-user flow. If you choose to be remembered, Plaid can collect and verify a phone number and associate it with saved bank connections for future use. Lake does not prefill a phone number or receive it from that flow. This is Plaid’s feature, separate from Lake sign-in and optional usage measurement. See Plaid’s returning-user explanation and its end-user privacy policy.

1.3 Information we generate

1.4 Information collected automatically

The web analytics, advertising pixel and campaign-cookie descriptions in this section concern the website and web application. Section 1.6 describes the native iOS app. A website you choose to open from the app is also subject to that website's processing. Authentication and bank-return callback pages do not load Lake marketing or analytics scripts. The Cookie Notice lists each cookie and browser-storage item the website uses, how long it lasts and how to control it.

Signed-in application pages do not use advertising cookies, advertising pixels, session recording, or cross-site behavioral trackers; the Meta Pixel described above runs only on the public funnel pages. Vercel states that Web Analytics does not use cookies and stores page-view data in anonymized, aggregated form rather than associating it with an individual or IP address. Vercel also states that its visitor-identification hash is reset every 24 hours; that statement does not mean page-view records are deleted within 24 hours. See Vercel's Web Analytics privacy documentation at vercel.com/docs/analytics/privacy-policy.

1.5 Your account record

Lake keeps a record for each account in its own database, keyed to your account and email address. It can include: your lifecycle stage with Lake (signed up, activated, trialing, subscribed, or churned, with timestamps); your trial start and end dates; the first-touch campaign labels described in Section 1.4; and your answers to in-product feedback prompts and the accuracy survey. Lake does not automatically copy linked-account records, balances, transactions, merchants, holdings, liabilities or derived spending information into that record. Feedback you submit is included as written, so do not add financial details that support does not need. Native and web account lifecycle updates share this record. Native operational updates include signup, first completed bank sync, trial dates and verified paid-access status. Submitted native feedback includes the text and app context you reviewed; optional native screen-view events are not copied into this record. Lifecycle updates do not add financial or merchant details. This record is not sent to a customer-relationship service. To send the emails described in Section 2, Lake gives its email provider, Loops, only the details listed for Loops in Section 3.1, never the rest of this record. Section 6 describes how it is deleted with your account.

1.6 Native iOS app information

Account name and images. The signed-in app displays an available name or username and profile image from your Clerk account. These can originate from a connected sign-in provider. The app requests the profile image from its HTTPS image address. Merchant images currently come from Plaid-provided logo addresses; the current native financial endpoints do not generate Logo.dev fallback requests. Image hosts receive the requested image address and ordinary network information, including the requesting device’s IP address. A merchant-image address can identify the merchant. Lake does not attach your account token, balance or transaction amount to these image requests. A missing or rejected image displays a local symbol or initials.

Authenticator setup. Clerk currently requires multi-factor authentication. During authenticator enrollment, Clerk creates the setup secret and verifies the code you enter. The app displays that setup information. Backup codes are not currently enabled. If you choose to open an authenticator app, iOS passes the setup address, including its secret and account label, to the app handling that address. That app handles the information under its own terms. Lake does not send these secrets to its financial backend or analytics, or persist them in its own device store; leaving setup or changing account clears the enrollment state. Any copy you save yourself remains where you save it.

Sign in with Apple. Clerk provides account sign-in. If your Lake account is linked to Apple and Lake has no stored revocable grant for that Apple identity, the native app asks you to confirm Apple authorization before entering the main app. This one-time enrollment lets Lake revoke its Apple sign-in authorization when you delete your account. Lake checks the saved grant on later visits; sign-out and account deletion remain available while enrollment is unfinished.

Lake receives an Apple user identifier, identity token and authorization code, and binds the confirmation to your current Lake identity and session using a short-lived challenge. Lake verifies the identity token and exchanges the authorization code with Apple for a refresh token. The grant journal stores a one-way hash of the code, encrypted identity/session and challenge details, an encrypted refresh token, ownership hashes, state and timestamps. It does not retain the raw authorization code or identity token. If Apple returns tokens but Lake cannot finish verifying the exchange, Lake retains those refresh or access tokens encrypted solely to revoke them during cleanup; they do not grant access to Lake. These records support authentication, account ownership, replay prevention and deletion, independently of your optional measurement choice. Section 5 describes their retention.

Apple purchases. When you buy through the App Store, Apple handles your payment method. Lake receives verified purchase information needed to provide access and handle billing changes: product and transaction identifiers, original transaction identifier, purchase and expiry dates, renewal status, refund or revocation status, Apple environment and verification timestamps. Lake creates an account token that links an Apple purchase to the Lake account that made it. Lake does not receive your full card number or Apple Account password. These billing records support entitlement checks, restoration, reconciliation and abuse prevention; they are not sent as optional screen-view events or advertising postbacks. For specifically admitted beta and review accounts, Lake also stores an account-specific Sandbox-access expiry and the intended Apple environment of a pending purchase. Admission lasts at most 30 days per grant and can be withdrawn earlier. Verified test purchases remain distinct from real paid access and are not reported as revenue. The admission field is removed with the Lake account; verified purchase history follows the billing-record retention described in Section 5.

TestFlight beta testing. Apple automatically shares crash logs, usage information and device/build and invitation details with Lake; your name and email may be included. Lake's optional usage setting does not disable this TestFlight collection. If you submit TestFlight feedback, Apple shares your comments, screenshots and accompanying diagnostics with Lake. This is separate from Lake's in-app feedback form. We use TestFlight reports to diagnose and improve the beta. We review them only in App Store Connect, do not download or export them, and do not copy or share them with third parties. See Apple's TestFlight privacy notice and Section 5.

Optional usage measurement. This account choice applies to Lake's website and native iOS app and is off by default. If you turn it on, Lake receives an event when you view your spending summary or the membership screen, together with an event identifier, event name, Lake account identifier, timestamp, platform, app version and build number. This first-party measurement helps us assess those two product experiences. It includes no merchant name, account balance, transaction amount, financial account detail, free-text answer, advertising identifier or general tap history. The events remain in Lake's database and are not sent to advertising networks or other third parties. We derive return counts from views of your spending summary on at least two distinct UTC calendar days within the retained history; this creates no additional event payload and does not establish that a session was useful to you. When the saved account preference permits measurement and the client has confirmed consent without a pending local refusal, Lake also records whether a newly created goal came from iOS or the website. Goal creation still works when this optional context is withheld. This optional platform field contains no goal name, merchant, target or financial amount. Missing, historical or expired origin stays unknown. Turning measurement off stops these events and clears the optional events and goal-origin fields once the server confirms the change. Necessary account, billing, security and support processing and the separate web practices in Section 1.4 continue.

If saving a refusal fails, the app remembers a one-way hash of the existing Clerk account identifier in app-only preferences so measurement remains paused for that account across sign-out and relaunch. This value is not a new device or installation identifier and is not transmitted for analytics. It is removed when the refusal is confirmed by the server or account deletion begins or completes.

The website uses browser local storage for the same protection: a one-way hash of the existing Lake account identifier and a random marker for the pending change. The marker prevents an older response from clearing a newer refusal; it is not a device identifier and is not sent to Lake. The local pause survives navigation and reload until a confirmed off save, a successful later opt-in, or clearing that browser's site storage. Other devices continue to use the saved account preference until the server applies the change. If the browser blocks this preference storage, these optional events are withheld.

Bank-link continuity. To return from a bank’s authorization page, the website temporarily saves a Plaid Link token, a timestamp and the connection flow, with the originating Lake account identifier for a new link or a connection identifier for reconnecting in browser local storage. A new-connection flow may also include existing Lake connection identifiers, public institution identifiers, bank names and connection status so Lake can warn before adding another connection to the same bank. It does not store bank login credentials or the successful exchange token there. Lake rejects and clears this continuation when it is next read after 30 minutes, and clears it when the flow finishes or is canceled. If you abandon the flow and never return, it can remain until you clear that browser’s site storage.

Saved deletion checks. Before submitting account deletion, the native app saves a signed status receipt in this device's Keychain. It contains a one-way identity hash, validity and expiry times and a signature; the app also stores a local receipt identifier, an account hash and the latest status/dates. It includes no raw account identity, email, bank token or financial details. The receipt permits only a check of this request's pending, next-retry, completed or unavailable status, including after sign-out or removal of the authentication account. It does not grant access to financial data or start another deletion. New receipts expire within 30 days; a receipt issued after completion expires no later than 30 days after completion. Earlier 90-day receipts keep their original expiry, but cannot recover completion records already removed under Section 5. The app keeps at most 16 saved checks and does not silently evict an older pending check to make room; completed or unavailable checks can be dismissed. Keychain access is limited to this device. A next-retry time is not a promised completion date, and an unavailable or expired receipt does not prove deletion finished.

Lake also counts goal creations and settled goal results from the records needed to provide those features. These internal reports contain aggregate counts, separated from optional platform context; they do not add merchant names, spending limits, visit counts or financial amounts to analytics or any third party. Pending results are not treated as failures, and a settled result does not establish that you viewed it.

Goal-result notifications. Only if you enable them, Lake admits a random installation identifier for the signed-in account and registers an Apple Push Notification service (APNs) token, with the app topic, environment, ordered registration revision and expiry. The admission has a random generation identifier and a fixed 90-day expiry; token updates do not extend that period. Lake encrypts the token and retains a one-way token hash. A revocation capability is kept in the app's device-only Keychain so an earlier permission can be withdrawn even after sign-out; Lake stores its hash with the admission and replay-protection records described in Section 5. Notification content is limited to a generic Lake update and an opaque event identifier. It contains no bank, merchant, amount, goal name or reward details. Opening a notification requires the appropriate Lake account to retrieve the actual result. Notification permission does not affect your points, paid access or measurement choice. Delivery is not guaranteed.

Optional nearby and weekly reminders. Nearby reminders are off by default. You choose a merchant and search an area, such as a street, town or ZIP code. The search sends the merchant name and the area you enter to Apple Maps; displaying a map also uses Apple’s map service. Lake does not send your current device coordinates as the search query. Apple processes its service requests under its Maps privacy notice.

If you save a place and enable nearby reminders, iOS checks entry into an approximately 350-foot area around it. Location and notification permissions are requested separately when needed; background matching requires the corresponding iOS permission. Lake keeps up to five selected place names, addresses, coordinates and merchant identifiers, an account-binding hash, reminder preferences and delivery timestamps in protected storage on this device. Lake does not upload your saved places, their coordinates or addresses, or a device-location history to its backend, analytics or any third party. It does not continuously record a location trail. Local notifications contain generic text; opening one retrieves the signed-in account’s spending context. The independent weekly check-in is a local scheduled notification and does not require location permission; whether it is on, and its day and time, are saved with your account so a new device can schedule it once you allow notifications on that device. Turning either reminder off cancels its monitoring or schedule but retains its saved setup. Sign-out, account change and account deletion clear the local reminder setup. iOS controls delivery, which is not guaranteed.

Feedback you submit. The native feedback form contains four optional answer fields, with at least one answer required to submit and a limit of 300 UTF-16 units per answer; some emoji use more than one unit. Before submitting, you can review the text and the included app version, build number and iOS version. The form sends a submission identifier and this context under your authenticated Lake account. It uploads no attachments, bank records or automatic diagnostics. Lake saves the submission, encrypted, in its own database under your account, and acknowledges it as delivered once it is saved. It is not sent to another service, and a saved submission does not mean support has read it. Retried submissions are deduplicated. Please omit financial details and other sensitive information that support does not need; we do not automatically add them to your answers. Your answers are submitted as written, so information you choose to type is included even when it describes your finances.

Sharing Lake. If you choose Share Lake, the iOS share sheet shares the public Lake home-page link. It does not include your account, bank data, referral identifier or a conversion claim. The destination app or service you choose handles the share under its own terms. Lake does not upload your contacts or record an attributed referral from this action.

The support screen also lets you choose to share the app version, build, iOS version and notification status displayed there. Those details are included only in the diagnostics share you initiate, without bank data, account identifiers or saved deletion receipts.

The native app has no advertising SDK, IDFA collection or cross-app tracking integration. Clerk's optional native SDK telemetry is disabled; required authentication processing and provider security records still apply. These statements do not change the separate web practices described in Section 1.4.

2. How We Use Your Information

We use your information only for these purposes:

  1. To provide the Service: automatically track spending from linked accounts; identify and display repeat-place or repeat-category habits, usual spend, visit frequency, recent visits, and matched spending-limit context; display accounts, balances, transactions, and selected liability indicators; receive and maintain supported investment holdings and liability details; and run budgets, goals, snapshots, reports, exports, and Insights; and save and show back the journal entries you choose to write.
  2. To authenticate you and secure your account: verify who you are, detect and prevent fraud and abuse, and protect the integrity of the Service.
  3. To process payments and administer plans: create and manage subscriptions, one-time purchases, and free trials, and determine which features your plan entitles you to.
  4. To communicate with you about the Service: service, security, billing, trial-status, and account notices; responses to your support requests. These operational messages are part of the Service and are sent to all accounts.
  5. To send marketing communications: with the limits in Section 6, we may send you product news, feature announcements, and offers by email, and emails about your account's progress: a welcome, a reminder to connect a bank, a note before your free trial ends, a note after your first payment, and a message after a free trial or subscription ends. Lake chooses these emails from your account, bank-connection, trial and subscription status, and Loops delivers them (Section 3.1). Every marketing email includes a working unsubscribe link, and unsubscribing never affects your account, your data, or the operational messages in purpose 4.
  6. To measure our advertising and understand usage: the web analytics and advertising-measurement processing described in Section 1.4, campaign attribution as described there, the optional answer to where you heard about Lake described in Section 1.1, and the optional first-party usage measurement described in Section 1.6.
  7. To improve and personalize the Service: diagnose errors, fix calculations, rank Insights, select among Insight phrasing variants after enough feedback, honor Insight dismissals, and evaluate whether the spending summaries we show are accurate and useful, using your survey and feedback responses.
  8. To comply with law: meet legal, tax, and regulatory obligations, and respond to lawful requests.

We do not use your financial data to build advertising profiles, to train models for sale or licensing to third parties, or for any purpose unrelated to operating Lake for you.

No AI training. Lake does not use your financial data, notes, attachments, feedback or other personal information to train, fine-tune or develop generative AI models, and does not sell or license it to anyone for that purpose. Lake does not buy personal information about you from data brokers.

Aggregated and de-identified data. We may create aggregated operational statistics that cannot reasonably be linked to an individual and use them to operate and improve the Service. Lake's current age-group comparison uses published Federal Reserve survey benchmarks, not pooled Lake-user financial data. We do not re-identify de-identified data or license it to third parties.

3. Who We Share Information With

We share information only in the circumstances below. We do not sell personal information, and we never share your linked-account or financial data with advertisers. The Meta Pixel measurement on our public funnel pages (Sections 1.4 and 3.1) may constitute "sharing" for cross-context behavioral advertising under some state privacy laws; Section 6 describes how to opt out, and the pixel is suppressed automatically for browsers sending the Global Privacy Control signal. It is the only such sharing Lake engages in.

3.1 Service providers who process data for us

ProviderRoleWhat it receives
Plaid Inc.Bank account connections and merchant imagesCredentials or authorization entered through Plaid Link or your financial institution's OAuth flow, never through Lake, plus authorized financial data and account-owner contact information used by Plaid during connection. Plaid may also collect a phone number when you choose its returning-user flow (Section 1.2). Its image service receives merchant-logo requests and ordinary network information as described in Section 1.6. Plaid's handling is governed by its end-user privacy policy.
ClerkAuthentication and identityEmail address, sign-in identifiers, login/session and security information, optional name/username/profile image, and authenticator enrollment information. A connected sign-in provider may supply profile fields you make available. Profile-image hosting receives image requests as described in Section 1.6.
Apple Inc. (Sign in with Apple, App Store, TestFlight, APNs and Maps)Native authorization/revocation, purchases, beta testing, optional notifications and place search/mapsLake and Apple exchange the sign-in, token-revocation, purchase/account-token, beta-testing and notification information described in Section 1.6. Optional place searches send merchant and entered-area text to Maps. Apple handles payment details and its own account, authentication, billing, maps and delivery records under its terms.
Stripe, Inc.Web payment processingYour payment method and billing details, entered directly with Stripe. Lake never receives your full card number. We store only Stripe's customer and subscription identifiers, your plan, and its status.
NeonDatabase hostingAll data described in Section 1 that we store, as our hosting infrastructure
Vercel Inc. (hosting)Application hosting, scheduled jobs, and server/security loggingRequests and application data processed in transit, plus the request and log information described in Section 1.4
Vercel Inc. (Web Analytics)Cookie-free route and page-view analyticsThe analytics information described in Section 1.4. Lake sends no custom events and normalizes the two sensitive detail-route values described there before transmission.
Vercel Inc. (Speed Insights)Cookie-free page-performance measurementThe performance information described in Section 1.4, with the two sensitive detail-route values normalized before transmission
Trove (Headline)Transaction enrichmentFor each transaction we enrich: the description, amount, date, and a pseudonymous Lake user identifier. Not your name, email, bank-account numbers, or balances.
Logo.devWebsite merchant logosRequests are made from your browser, exposing its IP address and the merchant domain requested. Lake does not attach your account identifier, balance or transaction amount. The current native financial endpoints do not generate this fallback. Logo.dev describes API request logs in its privacy policy.
Google Workspace / GmailReceiving support email sent to support@lakefin.netSender address, recipient address, subject, message body, attachments, and email routing metadata included with the message
LoopsSending Lake's marketing email, including the emails about your account's progress in Section 2Your email address, your Lake account identifier, the name of the account event that triggers an email (for example, that you signed up or that your free trial ends in three days) and, for the trial-ending email, your trial end date. Loops keeps a contact record with these details and the delivery and unsubscribe status of each email. Loops also records whether you open an email or click a link in it. Never your name, balances, bank names or accounts, merchants, transactions or other financial data.
Google LLC (Google Analytics 4)Site-wide usage analytics (measurement only; Google Signals and ad-personalization disabled)First-party analytics cookies (including `_ga`), IP address, browser and device information, and pages visited with sensitive detail URLs normalized to route placeholders before transmission. Never linked-account data, balances, or transactions. Governed by Google's privacy policy at policies.google.com/privacy.
Meta Platforms, Inc.Advertising measurement via the Meta Pixel, on public funnel pages onlyCookie identifiers (including `_fbp`), IP address, browser and device information, referrer, and which of the landing, sign-in, sign-up, or welcome pages was visited, including a signup-completed event. Never your identity as a Lake member, and never linked-account data, balances, or transactions. Suppressed entirely for browsers sending Global Privacy Control. Governed by Meta's own privacy policy at facebook.com/privacy.

Lake uses these providers for the roles listed above. Their agreements and published terms govern their processing, and some providers may have independent legal obligations or expressly permitted uses, including billing recordkeeping or use of de-identified or aggregated data. They are independent companies with their own security programs; we do not control them.

Support messages. Google Workspace / Gmail receives support and legal notices sent to support@lakefin.net. Native feedback submitted inside Lake is saved encrypted in Lake's own database, as described in Section 1.6. The native feedback flow adds no artificial-intelligence drafting service. Replies are written by us. Support correspondence is retained as described in Section 5 and is deleted on request.

3.2 Other disclosures

Other than the funnel-page Meta Pixel measurement described in Sections 1.4 and 3.1, we do not disclose your information to data brokers, advertising networks, or credit reporting agencies.

4. How We Protect Your Information

No system is perfectly secure. We cannot guarantee that unauthorized access will never occur. Protect your side of it too: use a strong, unique password, enable multi-factor authentication where offered, keep your email account secure, and tell us at support@lakefin.net if something looks wrong.

If we discover a breach affecting your personal information, we will notify you and any required authorities as required by applicable law, without unreasonable delay.

5. How Long We Keep Information

DataRetention
Account and financial dataFor as long as your account is open
Data for a disconnected institutionDeleted from Lake's active database when you remove that institution from Settings, subject to the backup and provider rules below
Optional profile (birth year and any legacy gender value)Until you delete it from Settings or delete your account, subject to the backup rule below
Active Lake database records linked to your userDeleted from the active Service when you delete your account, subject to the exceptions below (see Section 6)
Neon database backups and point-in-time recovery historyOur database's configured point-in-time recovery window is currently six hours (verified September 17, 2026); deleted rows leave recovery history when that window lapses. If we lengthen the window, it will not exceed 30 days, and this policy will be updated.
Trove enrichment request dataTrove receives enrichment requests as described in Section 3.1 and handles them under its own agreements and policies; a fixed retention period has not been confirmed. We will update this row when that information is established. The requests never contain your name, email, or account numbers.
Journal entries (ratings, tags and notes)Retained with the active Lake account until you edit or delete the entry or delete your account, then deleted from the active database, subject to the Neon backup rule above
In-app Insight feedback, accuracy-survey answers, and feedback-prompt recordsRetained with the active Lake account and deleted from the active database when the account is deleted, subject to the Neon backup rule above
Support correspondenceRetained in our support mailbox until deleted manually; deleted on request (Section 6). Not deleted automatically when you delete your Lake account.
Loops email contactCreated when Lake first sends you an email through Loops. Kept while your account is open, including after you unsubscribe, so your unsubscribe keeps working. When you delete your account, Lake asks Loops to delete the contact and shows deletion as pending until Loops confirms. Loops' own logs and backups follow its terms.
Billing and transaction records held by Stripe or AppleRetained by the billing provider under its terms and applicable recordkeeping obligations, independent of your Lake account. Local Apple purchase/account-token records are removed with your Lake account; deletion does not cancel the provider subscription.
TestFlight beta reportsApple retains beta feedback for one year and may retain crash and usage data until bugs are resolved. Lake keeps no separately downloaded or exported copies. Apple-held installation and other records follow its privacy notice.
Vercel server and security logsRetained or made available under Lake's then-current Vercel plan and configuration and Vercel's applicable terms; reporting availability is not necessarily the same as deletion
Vercel Web AnalyticsRetained or made available under Lake's then-current Vercel plan and Vercel's applicable terms. The 24-hour visitor-identification-hash lifecycle described in Section 1.4 is not a page-view deletion period.
Vercel Speed InsightsRetained or made available under Lake's then-current Vercel plan and Vercel's applicable terms
Campaign attribution cookie (`lake_utm`)Expires from your browser after at most 90 days; the copied campaign labels on your account record are kept until you delete your account
How you heard about Lake (optional setup answer)Retained with the active Lake account and deleted from the active database when the account is deleted, subject to the Neon backup rule above
Optional first-party web/native usage events and goal originView events expire after 90 days. The optional iOS/web goal-origin field is cleared 90 days after goal creation. Confirmed withdrawal or account deletion removes both earlier. Derived later-day return counts use only retained consented view history. Scheduled cleanup enforces expiry; necessary goal/result records follow their existing retention and are not deleted by a measurement choice.
Minimal verified billing lifecycle events in Lake's business serviceExpire after 90 days or are removed on account deletion; they are separate from optional usage events and provider-held billing records.
Feedback (website popup, public feedback page and native app)Feedback answers and app context are encrypted at rest. Feedback tied to your account, whether sent from the website or the native app, is deleted with your account. Feedback sent from the public feedback page without an account is deleted after 12 months. Native feedback still waiting in the older delivery queue is moved into this storage; a queued submission that is not moved within 90 days has its ciphertext cleared, and terminal deduplication records expire 90 days after completion or failure.
Pending account deletionThe encrypted Clerk identity, email, the Lake account identifier needed to delete your Loops contact, Plaid cleanup credentials and verified Apple subject/client revocation results are kept only while needed to finish the requested cleanup. During deletion, Lake also retrieves an available Apple web sign-in access token from Clerk when needed for revocation and saves it only in the encrypted cleanup instructions. Apple-confirmed revocation clears that token. Each completed step removes the data it no longer needs. Once cleanup completes, Lake removes the ciphertext and original Lake account identifier and keeps a one-way identity hash, any manual Apple-revocation flag, and limited request/retry timestamps and count for 30 days to prevent replay or accidental account recreation. Scheduled cleanup removes that completed record. Unresolved provider outcomes remain pending for reconciliation rather than being reported as completed deletion.
Native Apple sign-in grants and pending token cleanupThe encrypted refresh token and grant binding remain while needed to provide account access and revoke the authorization on deletion. Returned tokens whose exchange could not be verified remain encrypted solely for cleanup. Confirmed revocation clears each retained token. The ownership-hash binding is removed when account deletion completes. An unresolved exchange or revocation remains pending for reconciliation, without a fixed completion deadline.
Native Apple authorization challenges and replay recordsA challenge can be used for five minutes; its encrypted identity/session binding, identity hash and use/expiry times become eligible for scheduled cleanup 30 days after expiry. The grant journal keeps authorization-code, identity and Apple subject/client hashes, challenge identifiers, state, timestamps and encrypted binding details. Unexchanged, rejected or revoked attempts become eligible for scheduled cleanup 30 days after their last update. Active grants and unresolved exchanges are excluded from that expiry rule and follow the preceding row. These security periods are Lake choices, not claims that a law requires retention.
Bank-exchange recovery recordsA one-way public-token hash, owner identifier, state and timestamps support retries. An exchanged access token and item identifier, any explicit confirmation of an existing connection at the same institution, and a cleanup reason are encrypted until the bank connection is durably saved or removed. Unused or terminal attempts expire after 30 days; unresolved receipts remain only while needed for connection recovery or deletion. Account deletion removes the associated attempts once cleanup is possible.
Native request-limit windowsOne-way scope hashes, counters and expiry times are kept for one minute and removed on subsequent request admission. No raw address or identity is stored in these windows.
Optional notification registration and deliveryRegistered devices expire with their admission, 90 days after that admission is issued; a token update does not extend it. Result events and delivery eligibility expire after 32 days for date-anchored goals. Legacy calendar-month results keep their next-month-first-day 14:00 UTC cutoff, at most 32 days after creation. Cleanup removes expired records. Withdrawal removes the owned device/token and delivery records, and account deletion removes owned notification records.
On-device nearby reminder setupSelected places, account binding, preferences and delivery timestamps stay in protected storage on this device while saved. Turning reminders off retains the setup; removing a place removes its saved selection. Sign-out, account change and account deletion clear the setup and cancel monitoring. Lake holds no server copy of it.
On-device snapshot cache and remembered sign-in emailThe latest account snapshot Lake loaded (the accounts, balances, goals, places and spending shown on Home), with its fetch time and your Clerk account and session identifiers, is saved in a file on this device that uses iOS Data Protection and is excluded from device backups. Lake shows it while the app refreshes, deletes it after 7 days, and deletes it on sign-out, when your sign-in ends, on account change and account deletion, and whenever Lake cannot confirm Apple authorization. It is not sent anywhere. If you sign in with an email address, the sign-in screen may remember that address on this device after sign-out, in app preferences that device backups can include; Lake holds no server copy of it.
Weekly check-in choice and other app settingsWhether the weekly check-in is on and its day and time, your appearance and navigation choices, your goal-notification choice, dismissed prompts, display name, avatar and boat are kept with your account. Sign-out leaves them in place so they return when you sign in again. Account deletion removes them with your account records.
Notification admission and replay protectionThe random installation and admission-generation identifiers, account identifier, hashed revocation capability, revision, last action and fixed expiry prevent old registrations from being replayed. Withdrawal retains this record until the admission expires, without the APNs token. Account deletion removes account-owned admissions; expired admissions and legacy unowned replay records are removed in bounded cleanup batches. Expired or earlier admission generations cannot register again. Re-admission creates a new generation with a new 90-day period. These are security records, not a claim of anonymous data or legally required retention.
Saved native deletion checksNew signed status capabilities expire within 30 days and no later than 30 days after an already completed request. Earlier 90-day capabilities retain their signed expiry. Device-only Keychain retains the account hash, local receipt ID and latest status until you dismiss a completed or unavailable check. At most 16 checks are stored, with no silent eviction. The server stores no separate receipt table: it reads the limited deletion record above, retained for 30 days after completion. A legacy check can become unavailable before its receipt expires. Receipt expiry does not stop unfinished cleanup or prove completion.
Saved website deletion checkA necessary HttpOnly cookie holds one signed status receipt for up to 30 days, never beyond 30 days after an already completed request. A later prepared deletion replaces this browser's saved check. Lake stores no separate receipt table; it reads the same limited deletion record retained for 30 days after completion. Cookie expiry or removal does not stop pending cleanup or prove completion.
Browser pending measurement refusalBrowser local storage keeps a hash of the existing Lake account ID and a per-change random marker until confirmed off, successful explicit later opt-in, or clearing site storage. These values are not transmitted for analytics.
On-device pending measurement refusalAn app-only hash of the existing Clerk account identifier is retained across sign-out/relaunch until the server confirms the refusal or account deletion begins or completes. It is not sent for analytics.
Aggregated, de-identified statisticsMay be retained indefinitely, as they no longer identify you

6. Your Choices and Rights

Several controls for data in the active Service are available directly in the app; other requests and provider or retention exceptions are described below.

In the app, at any time:

Marketing email. We send marketing email only about Lake itself: product news, feature announcements, offers, and the emails about your account's progress described in Section 2. Loops delivers these emails for us. Every marketing email contains a working unsubscribe link that takes effect promptly, and you can also write to support@lakefin.net to be unsubscribed. Unsubscribing does not affect service, security, billing, or trial-status messages, which are part of operating your account. We do not send marketing on behalf of third parties.

By contacting us at support@lakefin.net, you may also:

We will respond within 45 days, and will tell you if we need more time. We do not charge for these requests, and we will never penalize you, degrade your service, or change your price for making one.

Verification. To protect you, we will verify a request by confirming control of the email address on your account before acting on it.

State privacy laws. Depending on where you live, including under the Indiana Consumer Data Protection Act, the California Consumer Privacy Act, and comparable laws in other states, you may have statutory rights to access, correct, delete, port, and opt out of certain processing, and to appeal a denied request. Some of these laws may not currently apply to Lake because of our size, and some financial data is exempt from them under the Gramm-Leach-Bliley Act. We extend the rights described in this section to all Lake users regardless of whether a statute compels it. If we deny a request, we will explain why and how to appeal; you may also contact your state Attorney General. Section 11 gives the details state laws require.

Opting out of ad-measurement sharing. The only cross-context sharing Lake engages in is the funnel-page Meta Pixel described in Sections 1.4 and 3.1. Lake honors the Global Privacy Control (GPC) signal: when your browser sends it, the pixel does not load and nothing is sent to Meta. You can also prevent the pixel with browser tracking protection or by blocking third-party cookies, limit Meta's use of collected data at facebook.com/adpreferences, or write to us and we will explain what Meta received. It never involves your linked-account or financial data.

Global Privacy Control and Do Not Track. Lake treats a Global Privacy Control signal as a request to opt out of the ad-measurement sharing described above, so the Meta Pixel does not load. The signal does not turn off Google Analytics or Vercel measurement, which Lake uses only to measure its own Service and not for cross-context advertising; the Cookie Notice explains how to block them. The older Do Not Track browser signal has no common standard, so Lake does not change its processing in response to it.

7. Children's Privacy

Lake is intended for users 18 and older. We do not knowingly collect personal information from anyone under 18. If you believe a minor has provided us information, contact support@lakefin.net and we will delete the account and its active Lake records, subject to the provider, support-record, backup, and legal-retention exceptions in Section 5.

8. Location of Processing

Lake is operated from the United States and currently serves users in the United States. Your information is stored and processed in the United States and in other locations where our service providers operate infrastructure. If you access the Service from outside the United States, you understand your information will be processed in the United States, where privacy laws may differ from those in your location.

9. Changes to This Policy

We may update this Privacy Policy. A change is material if it expands the categories of personal information we collect, adds a new category of recipient or a new purpose for sharing, reduces your rights or choices, or lengthens retention of identifiable data. For material changes, we will give at least 14 days' advance notice by a prominent notice in the Service, and by email once we operate a service-email channel, before the change takes effect, and the notice will state the effective date. Non-material changes (clarifications, provider renames, corrections that do not expand collection or sharing) take effect when posted with an updated "Last updated" date. Continuing to use the Service after a change's effective date means you accept it; if you do not accept a change, stop using the Service and delete your account before the effective date. We preserve superseded versions, including the July 24, 2026 original and its hash, and will provide any prior version on request. A revision to this Privacy Policy does not change the arbitration opt-out period in the Terms of Service, which runs from your first acceptance of the Terms.

10. Contact Us

Questions, requests, or concerns about privacy:

Rieper LLC (d/b/a Lake Financial)
c/o Registered Agents Inc
5534 Saint Joe Road
Fort Wayne, IN 46835
United States

Email: support@lakefin.net
Web: www.lakefin.net

11. U.S. State Privacy Rights

This section adds the details that California, Colorado, Connecticut, Indiana, Virginia and other states with comprehensive privacy laws ("state privacy laws") require. As Section 6 says, Lake extends these rights to every user, whether or not a state law applies to Lake. Words such as "personal information," "sensitive personal information," "sell," "share" and "targeted advertising" have the meanings those laws give them.

11.1 Notice at collection

Section 1 lists the personal information Lake collects and Section 2 lists why. The table below groups it by the categories California law uses and covers the 12 months before this policy's last update. Section 5 gives the retention period for each kind of record.

CategoryWhat Lake collectsSourcesDisclosed for a business purpose toSold or shared
IdentifiersEmail address, sign-in identifiers, Lake account identifier, Apple user identifier, notification token, IP address and cookie identifiersYou, your browser or device, Clerk and AppleService providers in Section 3.1Cookie identifiers and IP address from the public funnel pages go to Meta for ad measurement unless your browser sends Global Privacy Control. Nothing else.
Customer recordsName, email address and account masks (usually the last four digits)You, Clerk and PlaidService providers in Section 3.1No
Characteristics of protected classificationsOptional birth year and any legacy gender valueYouNeon and Vercel (hosting)No
Commercial informationPlan, trial, subscription and purchase records; transactions from your linked accountsYou, Plaid, Apple and StripeService providers in Section 3.1No
Internet or other electronic network activityPages viewed, funnel events, page-performance measurements, server and security logs, optional first-party usage events, and whether you open Lake's emails or click their linksYour browser or deviceVercel, Google, Loops (email opens and clicks) and, on public funnel pages only, MetaFunnel page visits and the signup-completed event go to Meta unless your browser sends Global Privacy Control
Geolocation dataApproximate location derived from IP address; the merchant location Plaid supplies with a transaction. Nearby-reminder places stay on your device and Lake does not receive themYour browser or device, and PlaidVercel, Google, Neon and, on public funnel pages only, MetaOnly the IP address Meta receives through the funnel-page pixel, unless your browser sends Global Privacy Control
Audio, electronic or visual informationReceipts and documents you attach, and a profile image you provideYou and ClerkNeon, Clerk and VercelNo
Sensitive personal informationFinancial account information (balances, transactions, holdings and liabilities) and account log-in through Clerk. Lake never receives your bank credentialsPlaid, Clerk and youNeon, Vercel, Trove (transaction description, amount and date only) and ClerkNo
InferencesHabits, usual amounts, visit counts, budget pacing and Insights that Lake calculates for youLake's own calculationsNeon and VercelNo
Other information you give usNotes, labels, journal entries, feedback, survey answers and how you heard about LakeYouNeon, Vercel and Google Workspace (support email you send)No

11.2 Sensitive personal information

Lake uses sensitive personal information only to provide the Service you ask for, to secure your account and to meet legal obligations. It does not use or disclose sensitive personal information to infer characteristics about you, and it does not sell or share it. Because Lake limits this use to those purposes, California law does not require a separate "limit the use of my sensitive personal information" link. Linking an account is your choice, and you can disconnect it at any time in Settings.

11.3 Selling, sharing and targeted advertising

Lake does not sell personal information for money. The Meta Pixel on the public funnel pages (Sections 1.4 and 3.1) is the only disclosure that a state privacy law may treat as a sale, sharing or targeted advertising. To opt out, turn on Global Privacy Control in your browser, and the pixel will not load. The pixel works through cookies in your browser, not through your Lake account, so Lake cannot apply an emailed request to it; the browser controls in the Cookie Notice also stop it. You can still email support@lakefin.net and we will explain what Meta received. Lake does not knowingly sell or share the personal information of anyone under 16, and the Service is for adults 18 and older.

11.4 Profiling

Lake does not use personal information for profiling that leads to decisions with legal or similarly significant effects, such as decisions about credit, housing, employment, insurance, education or health care. Habit estimates and Insights are shown to you and decide nothing about you.

11.5 Your rights

Depending on your state, you may ask Lake to:

Lake will not discriminate against you, charge you a different price or give you a different level of service for using these rights.

How to make a request. Use the controls in Settings described in Section 6, or email support@lakefin.net. Lake confirms control of the email address on your account before acting on a request and does not require government identification. We respond within 45 days. If we need more time, we will tell you why within that period and respond within a further 45 days.

Authorized agents. Someone you authorize can make a request for you. Send the request with your signed written permission. We may ask you to confirm your identity or the permission directly with us, unless the agent holds a valid power of attorney.

Appeals. If we decline any part of a request, reply to our response with "Appeal" in the subject line or email support@lakefin.net. We will answer within 60 days and explain the result. If you disagree, you may contact your state Attorney General.

11.6 Other state notices

California "Shine the Light." Lake does not disclose personal information to third parties for their own direct marketing. California residents may ask about this at support@lakefin.net.

Nevada. Lake does not sell covered information as Nevada law defines it. Nevada residents may still send an opt-out request to support@lakefin.net, and we will record it.

De-identified information. Lake keeps de-identified information in a form that cannot reasonably identify you, does not try to re-identify it and does not license it to third parties.

Rieper LLC is an Indiana limited liability company, Business ID 202607202020836, operating under the assumed business name Lake Financial. This Privacy Policy is incorporated into the Lake Terms of Service.