← Back to Home

Privacy Policy | LiveSpend

Effective date: September 12, 2026

LiveSpend ("LiveSpend," "we," "us," or "our") provides a service that helps you track spending using (a) transaction alert emails read through the Gmail API or Microsoft Graph with your permission, and (b) transactions you enter manually (the "Service").

This Privacy Policy explains what information we collect, how we use it, and the choices you have. If you have any questions, contact us at support@livespend.app.

1) Information we collect

A. Account information

When you create an account, we collect and store:

  • Email address (required)
  • Account identifiers, including a Clerk user identifier and internal identifiers used to connect your account with LiveSpend features and billing

Authentication and account profile details are handled through Clerk.

B. Transaction information

LiveSpend stores only the transaction details needed to provide the Service. This may include:

  • Merchant name
  • Transaction amount
  • Currency
  • Transaction date
  • Category (if assigned)
  • Transaction source (e.g., connected-email sync, manual entry)
  • Spending source/card nickname (if you set one with multiple cards)
  • Creation and deletion status for transaction records

You can provide transaction information in the following ways:

  1. Gmail API connection (optional): You connect a Gmail account and authorize LiveSpend to read messages using the Gmail API. LiveSpend checks new messages to identify bank transaction alerts and extracts transaction details from alerts it recognizes. The Gmail access, temporary processing, storage, and automated extraction involved are described in Sections 1D, 1F, and 1G below.
  2. Microsoft email connection (optional): You connect a supported personal Microsoft or eligible Microsoft 365 work or school account and authorize LiveSpend through Microsoft Graph. LiveSpend checks new messages to identify recognized bank transaction alerts. The Microsoft access, temporary processing, storage, and automated extraction involved are described in Sections 1E, 1F, and 1G below. An organization administrator may restrict or need to approve this connection.
  3. Manual entry: You can manually enter transactions with similar fields.

C. Spending targets, preferences, and notifications

LiveSpend also stores information you create or configure in the Service, such as spending targets, cycle settings, categories, category rules, spending sources/card nicknames, time zone, onboarding status, notification preferences, generated insights, and app progression state.

If you enable notifications, LiveSpend may store notification preferences, sent notification records (including the recipient, subject, message, destination link, provider, and delivery identifier), browser push subscription details, iOS/device push tokens, and related delivery information.

D. Gmail API data (Gmail connection only)

If you choose to connect Gmail, LiveSpend accesses your Gmail data through the Gmail API after you grant permission. LiveSpend is designed to minimize persistent storage, but the ongoing sync path may need to inspect a newly added message before it can determine whether the message is a bank transaction alert the Service can use.

  • Permission: LiveSpend requests the Gmail gmail.readonly permission. This allows LiveSpend to read messages but does not allow it to send, edit, or delete email.
  • What we temporarily process: For a message being checked, LiveSpend may fetch the full Gmail API message and hold its headers, timestamp, snippet, and decoded text or HTML body in application memory while determining whether it is a transaction alert and extracting transaction details. A regular catch-up sync narrows messages by configured bank sender domains. During ongoing Gmail history/watch sync, LiveSpend may fetch any newly added message before determining that it is unrelated. Unrelated message content is discarded after that check.
  • What we store about the Gmail connection: We store the connected Gmail address, an encrypted OAuth refresh token, whether synchronization is enabled, last-sync timestamps and status, the latest sync error and its timestamp, a Gmail history cursor, and watch-expiration information.
  • What we store for each processed message: We retain the Gmail message ID, a one-way SHA-256 hash derived from the connected Gmail address, processing status (pending, non-transaction, or transaction created), and record timestamps. This minimal tracking record is retained even when a message is determined to be unrelated, so LiveSpend can avoid reprocessing the same message and keep sync reliable.
  • What we store for a transaction alert: If a message produces a transaction, we store the extracted transaction information described in Section 1B and link it to the message's tracking record.
  • What we do not persist: LiveSpend's database does not store email bodies, subjects, senders, recipients, full headers, snippets, or attachments from Gmail. It does not retain the content of unrelated email after the temporary check described above.

E. Microsoft Graph data (Microsoft email connection only)

If you connect a Microsoft inbox, LiveSpend accesses data for the signed-in account through Microsoft Graph after you grant permission. Personal Outlook.com, Hotmail, and Live accounts are supported, as are eligible Microsoft 365 work or school accounts.

  • Permissions: LiveSpend requests delegated openid, profile, offline_access, User.Read, and Mail.Read permissions. These let LiveSpend identify the signed-in user, maintain the connection, and read that user's mailbox. LiveSpend does not request permission to send, edit, or delete email.
  • What we temporarily process: LiveSpend checks new messages in visible inbound and custom mail folders. It excludes junk, deleted, drafts, sent, and outbox folders. It first uses message metadata such as sender, subject, received date, message identifiers, and parent folder. For a message that appears to be a supported bank alert, it may then temporarily process the message body, body preview, and internet headers to extract transaction details. LiveSpend does not fetch attachments and does not import messages from before you connected the account. Temporary message content is discarded after processing.
  • What we store about the Microsoft connection: We store the connected email address or user principal name, Microsoft user identifier, encrypted OAuth refresh token, synchronization start time and status, last-sync and error information, Microsoft Graph subscription identifier and expiry, a one-way hash of subscription verification data, visible folder identifiers and display names, folder synchronization cursors, and related timestamps.
  • What we store for a candidate message: We may retain the Microsoft Graph message identifier, internet message identifier, a one-way SHA-256 hash derived from stable Microsoft and mailbox identifiers, processing status, limited retry information, and record timestamps. We do not retain message identifiers for messages that fail the initial supported-bank metadata check.
  • What we store for a transaction alert: If a message produces a transaction, we store the extracted transaction information described in Section 1B and link it to its minimal tracking record.
  • What we do not persist: LiveSpend's database does not store Microsoft email bodies, body previews, subjects, senders, recipients, full headers, or attachments. It does not retain the content of unrelated email after the temporary check described above.

F. OAuth tokens (connected email only)

For Gmail and Microsoft connections, LiveSpend stores only an encrypted refresh token, which is used to obtain temporary access tokens when needed. Access tokens are not stored persistently and are generated and used only transiently during synchronization. You can revoke access through your Google or Microsoft account settings, which prevents future access. Disconnecting a provider inside LiveSpend removes the email address and encrypted refresh token from that provider's active connection record.

G. Automated parsing, categorization, and insights

LiveSpend uses the OpenAI API for limited, user-facing features:

  • Ambiguous bank alerts: If a message comes from an authenticated sender at a bank LiveSpend works with, but LiveSpend's standard parser cannot confidently interpret it, LiveSpend may send OpenAI the bank name, email subject, email date, and up to 12,000 characters of extracted body text to determine whether it is a transaction alert and, if so, extract the amount, direction, date, and merchant.
  • Merchant categorization: LiveSpend may send a transaction's merchant name and your category names to suggest a reusable merchant rule and category.
  • Weekly insights: LiveSpend may send an aggregated weekly metrics brief containing period dates, spending totals and counts, merchant and category summaries, time-of-day and weekday/weekend patterns, comparisons with recent periods, and budget context. The brief does not contain raw individual email messages or a list of raw transaction records.

LiveSpend does not separately save the raw OpenAI prompt or raw response in its database. It does store the resulting transaction, category or rule, and generated insight needed to show these features in the Service. OpenAI may temporarily retain API inputs and outputs according to LiveSpend's API configuration and OpenAI's applicable data policies. LiveSpend does not opt in to using this data to train generalized AI models. For current provider retention details, see OpenAI's API data controls.

H. Billing and subscription information

New subscriptions are available only in the iPhone app and are processed through Apple In-App Purchases. Once subscribed, use the same LiveSpend account on iPhone and the web. If you have a legacy web subscription, it is processed through Stripe. References to Stripe and web subscriptions in this policy apply to legacy web subscriptions, if any. Apple or Stripe, as applicable, will collect and process your payment information directly.

We do not collect or store your credit card number, CVV, or full payment credentials.

We may receive and store limited billing-related information from Apple or Stripe, such as:

  • Subscription status, such as active, cancelled, past due, expired, refunded, or revoked
  • Apple or Stripe customer, subscription, transaction, or receipt identifiers
  • Plan, billing period, purchase or expiration dates, cancellation status, and related entitlement status
  • Apple billing verification data needed to validate and manage iOS subscriptions

This information is used solely to manage your account and provide the Service. For details on how Apple or Stripe handle payment data, see Apple's applicable payment and privacy terms and Stripe's Privacy Policy.

I. Support communications

If you email us for support, we will receive and store the contents of your message and your contact information (such as your email address) to respond and help resolve your issue.

J. Technical, usage, and analytics data

We may collect technical and usage data such as IP address, device/browser information, timestamps, page views, referral source, UTM parameters, diagnostic events, and limited product or website interaction events for security, abuse prevention, troubleshooting, analytics, and product improvement.

We use PostHog for limited website and product analytics. On our public landing page, we configure PostHog in cookieless mode, so PostHog is not intended to store analytics identifiers in cookies, local storage, or session storage. PostHog may collect page views, referral and campaign information, and interactions such as clicks on download, sign-up, or other call-to-action buttons.

On our production landing page, we also use the Meta Pixel to send Meta Platforms a page-view event when the page loads. The event may include the page URL, timestamp, referral and campaign information, IP address, browser or device information, and Meta cookies or identifiers. We use this information to measure and attribute visits from Facebook and Instagram ads and to optimize our Meta advertising campaigns. We do not send connected-email content, transaction details, merchant names, transaction amounts, bank credentials, or payment credentials through the Meta Pixel.

In the iOS app, we use the Meta SDK to share app installs and app events (such as launches, completed registrations, first transaction syncs, and in-app purchases) with Meta Platforms for advertising measurement; we do not share bank transaction details or collect the device advertising ID.

Product and backend analytics sent to PostHog are limited to high-level funnel and status events, such as whether an account was created, onboarding steps were completed, an email provider was connected, a spending source was added, a spending target was set, or a first transaction was received. For signed-in users, these analytics events may be associated with Clerk and internal account identifiers, the account creation time, plan, app environment, and relevant high-level event status. We do not send PostHog connected-email message content, email subjects, email bodies, raw transaction descriptions, merchant names, transaction amounts, bank or payment credentials, or other sensitive financial details.

Landing-page PostHog analytics is configured so PostHog is not intended to store its analytics identifiers in cookies, local storage, or session storage.

K. Information we do not collect

LiveSpend is designed to avoid collecting sensitive banking and payment credentials. We do not collect or store:

  • Bank logins, passwords, or credentials
  • Access to your bank account portal
  • Full card numbers
  • CVV codes
  • Payment card expiration dates

2) How we use information

We use the information we collect to:

  • Provide, operate, and maintain the Service
  • Create and manage your account
  • Process and display your transaction history and summaries
  • Create and manage spending targets, categories, category rules, spending sources, preferences, insights, and notifications
  • Sync transactions from a connected Gmail or Microsoft email account (if enabled)
  • Temporarily inspect newly added messages in your connected inbox to identify bank transaction alerts the Service can process and avoid processing the same message twice
  • Use OpenAI for the user-facing transaction parsing, merchant categorization, and weekly insight features described in Section 1G
  • Manage subscription status, billing records, and subscription access
  • Send notifications if you enable them
  • Respond to support requests and communicate with you about the Service
  • Protect the security and integrity of the Service (e.g., preventing abuse and troubleshooting)
  • Measure landing page performance, understand which sources and campaigns lead to downloads or sign-ups, improve onboarding, and understand high-level product funnel drop-off

We do not sell your personal information. We do not use connected-email content, transaction details, merchant names, transaction amounts, bank credentials, or payment credentials for advertising. We do not use Gmail- or Microsoft-derived content for advertising, resale, surveillance, credit or lending decisions, or training generalized AI/ML models. We use limited landing-page technical and usage data through the Meta Pixel for advertising measurement, attribution, and campaign optimization as described in this Privacy Policy. Some service providers may process basic operational, security, diagnostic, analytics, or delivery data under their own policies.

3) How connected email syncing works

A. Gmail

If you connect Gmail, LiveSpend uses read-only Gmail API access to check new messages for bank transaction alerts it can use and extract transaction details. This feature can be disabled by you. As explained in Section 1D, an ongoing sync may temporarily inspect a newly added message before determining that it is unrelated.

Most bank alerts LiveSpend can use are handled by its standard parsers. Some ambiguous alerts from authenticated bank senders may be analyzed through the OpenAI API as described in Section 1G.

  • You control whether Gmail sync is enabled.
  • You can revoke LiveSpend's Gmail access at any time in your Google account permissions.
  • If access is revoked or expires, syncing may stop until you reconnect.
  • Disconnecting Gmail inside LiveSpend stops future Gmail syncing and removes the active Gmail address and OAuth token. It does not automatically delete transactions already imported or the minimal per-message tracking records described in Section 1D.

B. Microsoft email

If you connect Microsoft email, LiveSpend uses delegated Microsoft Graph access to check new messages for supported bank transaction alerts and extract transaction details. It does not request permission to send, edit, or delete email. The temporary processing and minimal records are described in Section 1E. Some eligible alerts may be analyzed through the OpenAI API as described in Section 1G.

  • You control whether Microsoft email sync is enabled.
  • You can revoke LiveSpend's access to a personal Microsoft account at Microsoft's app permissions page. Work or school users can review or revoke access through the My Apps portal, subject to their organization's controls.
  • If permission is revoked, expires, or is restricted by an organization administrator, syncing may stop until you reconnect or the administrator permits access.
  • Disconnecting Microsoft email inside LiveSpend stops future syncing, removes the active Microsoft connection record, and attempts to remove the Microsoft Graph subscription. It does not automatically delete transactions already imported or minimal candidate-message tracking records described in Section 1E.

LiveSpend uses Microsoft API data only to provide and improve the user-facing transaction tracking features you authorize. LiveSpend does not use Microsoft-derived content for advertising, resale, surveillance, credit or lending decisions, or training generalized AI/ML models.

Google API Limited Use

LiveSpend's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including the Limited Use requirements. LiveSpend uses Gmail-derived data only to provide or improve user-facing transaction tracking features that you authorize.

4) Sharing of information

We do not sell your personal information.

We may share information only in the following limited circumstances:

A. Service providers (to operate the Service)

We use trusted third parties to run LiveSpend, such as:

  • Clerk (authentication)
  • Apple (iOS subscription billing through In-App Purchases)
  • Stripe (billing and payment processing for legacy web subscriptions, if any)
  • Resend (email notification delivery)
  • Apple Push Notification service and browser push providers (push notification delivery)
  • Railway (hosting and database infrastructure)
  • Google (Gmail API access, only if you connect Gmail)
  • Microsoft (Microsoft Graph access, only if you connect a Microsoft email account)
  • OpenAI (limited transaction-alert parsing, merchant categorization, and weekly insight generation as described in Section 1G)
  • PostHog (limited website and product analytics, including high-level funnel events; session replay is disabled)
  • Meta Platforms (Meta Pixel for production landing-page advertising measurement, attribution, and campaign optimization; Meta iOS SDK for app-install attribution and in-app event measurement)

These providers process data as needed to provide their services to us and support operation, security, analytics, and reliability of the Service. OpenAI may temporarily process or retain the limited data described in Section 1G in accordance with LiveSpend's API configuration and OpenAI's applicable data policies. Gmail- and Microsoft-derived content is not used by LiveSpend for advertising, resale, surveillance, credit or lending decisions, or training generalized AI/ML models. We do not share connected-email message content, raw transaction details, transaction amounts, merchant names, bank credentials, or payment credentials with PostHog.

B. Legal and safety

We may disclose information if we believe it is reasonably necessary to:

  • Comply with applicable law, regulation, or legal process
  • Protect the rights, safety, and security of LiveSpend, our users, or others
  • Detect, prevent, or address fraud, abuse, or security issues

C. Business changes

If LiveSpend is involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, information may be transferred as part of that transaction. If that happens, we will take reasonable steps to ensure your information remains protected.

5) Data retention

We keep information only as long as necessary to provide the Service and for legitimate operational needs (such as security, dispute resolution, and compliance).

  • Transactions and account data are retained while your account exists unless deleted or changed through the Service, subject to limited retention for legal/security purposes. Deleted transactions may be removed from active views while some records are retained for operational integrity.
  • Spending targets, categories, rules, preferences, spending sources, insights, and notification records are retained while your account exists unless deleted or changed through the Service.
  • Gmail API sync: LiveSpend does not persist full Gmail message content in its database. The Gmail connection data, extracted transactions, and per-message tracking records described in Section 1D are retained while your LiveSpend account exists. Disconnecting Gmail removes the active Gmail address and encrypted refresh token, but does not delete imported transactions or the per-message tracking records. Deleting your LiveSpend account deletes those records from LiveSpend's primary application database, subject to the limited exceptions described below.
  • Microsoft Graph sync: LiveSpend does not persist full Microsoft message content in its database. Microsoft connection data, extracted transactions, folder synchronization state, and the candidate-message tracking records described in Section 1E are retained while your LiveSpend account exists. Disconnecting Microsoft email removes the active connection record, including the email address and encrypted refresh token, but does not delete imported transactions or candidate-message tracking records. Deleting your LiveSpend account deletes those records from LiveSpend's primary application database, subject to the limited exceptions described below.
  • OpenAI processing: LiveSpend does not separately save raw prompts or raw responses in its database. OpenAI may temporarily retain API inputs and outputs according to LiveSpend's API configuration and OpenAI's applicable data policies.
  • Billing data (subscription status and Apple or Stripe identifiers) is retained as long as your account exists and for a reasonable period after account deletion as required for accounting, tax, and dispute resolution purposes.
  • Analytics data is retained only as long as reasonably needed for analytics, product improvement, security, and troubleshooting, or according to our analytics provider settings. Session replay is disabled.

6) Your choices and rights

A. Account deletion

For instructions and support, see how to delete your LiveSpend account.

You can delete your account. Account deletion cancels an active legacy web subscription, if you have one, attempts to revoke the Gmail connection, removes any active Microsoft email connection and Graph subscription, and deletes the account's transactions, email message tracking records, settings, and other associated user records from LiveSpend's primary application database. Limited billing, security, webhook, analytics, or provider-held records may remain where reasonably necessary for legal compliance, accounting, dispute resolution, fraud or abuse prevention, or under the applicable provider's retention settings. Deleting your LiveSpend account does not cancel an Apple In-App Purchase subscription; that subscription must be cancelled through your Apple account or App Store settings. You may also withdraw connected-email access without deleting your LiveSpend account by disconnecting the provider or revoking access through Google or Microsoft.

B. Access and correction

You can access and update certain account details through your account settings. If you need help accessing, correcting, or deleting information, contact us at support@livespend.app.

C. Connected-email access revocation

If you connected Gmail, you can disconnect it inside LiveSpend or revoke access in your Google account settings. After revocation, LiveSpend will no longer be able to sync Gmail messages unless you reconnect. Revoking access through Google does not by itself delete LiveSpend's local Gmail connection record, imported transactions, or per-message tracking records. Disconnecting inside LiveSpend removes the active Gmail address and token, but imported transactions and per-message tracking records remain until your LiveSpend account is deleted.

If you connected Microsoft email, you can disconnect it inside LiveSpend, revoke a personal account connection through Microsoft account permissions, or use the My Apps portal for a work or school account. After revocation, LiveSpend can no longer sync Microsoft messages unless you reconnect. Revoking through Microsoft does not itself delete LiveSpend's local Microsoft connection record, imported transactions, or candidate-message tracking records. Disconnecting inside LiveSpend removes the active Microsoft connection record and attempts to remove its Graph subscription, but imported transactions and candidate-message tracking records remain until your LiveSpend account is deleted.

D. Subscription cancellation

You can cancel your LiveSpend subscription at any time according to the platform where you subscribed: through your Apple account or iOS App Store subscription settings for subscriptions purchased through Apple In-App Purchases, or through your account settings or the Stripe customer portal if you have a legacy web subscription. Subscription access after cancellation is described in the Terms of Service. Your transaction data and account information will not be deleted upon subscription cancellation.

E. Notifications

You can enable or disable email and push notifications in your account settings. You can also control push notifications through your browser or device settings.

F. Website analytics and advertising choices

On our landing page, we configure PostHog analytics in cookieless mode, so PostHog is not intended to store its analytics identifiers in cookies, local storage, or session storage. Session replay is disabled. The Meta Pixel may use cookies or similar identifiers as described in Meta's Privacy Policy. You can manage how Meta uses activity from advertising partners in your Meta ad preferences. You can also limit or block website analytics and advertising technologies using browser privacy settings, browser extensions, or other tools that block these scripts. If we provide additional analytics opt-out controls, you may also use those controls. Blocking analytics or advertising scripts may prevent measurement features from working, but should not prevent you from viewing the landing page.

G. Data export

Data export is not currently available, but may be added in the future.

7) Security

We use reasonable administrative, technical, and organizational safeguards designed to protect your information. However, no method of transmission or storage is 100% secure, so we cannot guarantee absolute security.

8) International users

LiveSpend is currently operated from Canada. If you access the Service from outside Canada, your information may be processed and stored in locations where our service providers, including hosting, analytics, authentication, billing, and automated model providers, operate. By using the Service, you understand that your information may be transferred to and processed in other jurisdictions.

9) Children's privacy

LiveSpend is not intended for children under 13 (or the minimum age required in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has provided us information, please contact support@livespend.app.

10) Changes to this Privacy Policy

We may update this Privacy Policy from time to time. If we make changes, we will update the "Effective date" above. If changes are material, we may provide additional notice within the Service or by email.

11) Contact us

If you have questions about this Privacy Policy or our privacy practices, contact us at:
Privacy Officer, LiveSpend
support@livespend.app