RentalMath
Storage, Cookies & Offline Caching Notice
How we use browser storage technologies across all tiers.
In This Document
1Overview
RentalMath uses browser-based storage technologies to deliver functionality, enable offline use, and persist your data. Your device is the primary store for deal data whether or not you are signed in; signing in adds Firestore cloud sync on top. This App does not use advertising cookies or third-party tracking cookies.
2localStorage (All Users)
| What | Browser storage that persists on your device until cleared. It is never transmitted automatically the way cookies are; the only value the App deliberately sends is the share-link ownership token, and only when you create or revoke a share link. |
|---|---|
| What is stored | UI state, preferences, dismissed hints, your most recently used property address, the list of share links created in this browser, share-link ownership tokens, calculator hand-off figures, and sync bookkeeping flags. (Full deal records live in IndexedDB; legacy localStorage deal data is migrated automatically.) |
| How to clear | Browser Settings → Clear Site Data, or DevTools → Application → Local Storage. |
3IndexedDB (All Users)
| What | Browser database. The primary on-device store for your saved deal records; also used by Firebase Firestore's offline persistence layer when you are signed in. |
|---|---|
| What is stored | Your saved property records and analysis snapshots (all users). For signed-in users, additionally a local cache of your Firestore data and a queue of pending writes, managed automatically by the Firebase SDK. |
| How to clear | DevTools → Application → IndexedDB. If you are signed out, clearing deletes your saved deals. If you are signed in, cloud copies are unaffected but unsynced local writes may be lost. |
4Service Worker Cache / CacheStorage (All Users)
| What | Caches the App shell and static assets for offline use. |
|---|---|
| What is cached | The App's HTML, JavaScript modules (including firebase-init.js, sync.js, auth-ui.js), Bootstrap CSS/JS, Google Fonts, icons and manifest files. Deal data is NOT stored in the service worker cache. |
| Stale content | You may see a cached version of the App until the service worker updates. We increment the cache version with every App release. |
| How to clear | DevTools → Application → Cache Storage, or clear all site data. |
5Cookies
The App itself does not set cookies, including for its anonymous usage metrics (which use no cookies, identifiers, or fingerprinting). Firebase Authentication may set session-related cookies as part of its SDK behavior. Review Google's privacy policy for details.
6Server-Side Caching
Separate from your browser's storage, our server caches analysis results and upstream data keyed by address or geography (roughly 24 hours for composite analysis results and up to about 30 days per data source) to reduce repeat fetching from data providers. These caches contain property and geography data, not user identities, and are not tied to your browser or account.
7Summary
| Technology | What's Stored | Persistence |
|---|---|---|
| localStorage | UI state, preferences, tokens/flags | Until cleared manually |
| IndexedDB | Deal records (all users); Firestore offline cache (signed-in) | Until cleared manually / managed by Firebase SDK |
| CacheStorage | App shell and static assets | Auto-refreshed on update |
| Cookies | None set by the App directly | N/A |