Skip to content

Instantly share code, notes, and snippets.

@oppianmatt
Created March 12, 2026 10:02
Show Gist options
  • Select an option

  • Save oppianmatt/8f25c4769de7eb7819998c73b1eca3da to your computer and use it in GitHub Desktop.

Select an option

Save oppianmatt/8f25c4769de7eb7819998c73b1eca3da to your computer and use it in GitHub Desktop.
Lunchbox Rewind - Privacy Policy

Privacy Policy — Lunchbox Rewind

Last updated: 2026-03-09

What data does Lunchbox Rewind collect?

Lunchbox Rewind collects and stores the following data locally on your device in Chrome's extension storage and IndexedDB:

  • Lunch Money API token — used to authenticate with the Lunch Money API to fetch and update transactions
  • Transaction snapshots — before/after copies of transactions you edit, used to compute undo payloads
  • Undo action history — a record of edits you've made so you can revert them
  • Extension preferences — settings like undo stack size, UI visibility, and button position

Where is data stored?

All data is stored locally in your browser using Chrome's chrome.storage.local API and IndexedDB. No data is stored on external servers.

What data is transmitted?

Lunchbox Rewind communicates only with the Lunch Money API (api.lunchmoney.dev) to:

  • Fetch transaction details (to create before/after snapshots)
  • Update transactions (to revert changes when you click Undo)

No data is sent to any other server, analytics service, or third party.

Data sharing

Lunchbox Rewind does not:

  • Sell or transfer user data to third parties
  • Use data for advertising, analytics, or profiling
  • Use data to determine creditworthiness or for lending purposes
  • Collect personally identifiable information beyond what Lunch Money's API returns

Data retention

All data remains on your device until you:

  • Remove the extension
  • Clear extension data via Chrome settings
  • Delete a budget from the extension's settings

Contact

For questions about this privacy policy, contact: matt@oppian.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment