Last updated: October 4, 2026
My Move browser storage
My Move stores the move date, five-digit ZIP code, homeowner or renter selection, completed tasks, dismissed tasks, and tasks added from guides, and public Internet provider names saved to My Move in the current browser’s local storage. No account is required, and this data is not synced to MoveIn or another device. Clearing browser storage, using a private browsing session, or resetting My Move removes saved progress. If browser storage is blocked, the checklist can still work during the current visit but may not be available later.
MoveIn measures aggregate My Move interactions such as starting a checklist, completing a task category, adding a task, resetting, printing, or viewing a move phase. MoveIn does not send the move date, checklist text, notes, exact street address, names, account information, or other personally identifying checklist details to Google Analytics.
Saved Internet comparisons
The Internet comparison tool can store up to four public provider names, technology labels, official links, review dates, and an optional five-digit ZIP in this browser. It does not store a street address, email, phone number, provider account, price, or personal note. The list is not synced to MoveIn and can be cleared from the comparison page or with browser controls.
ZIP searches
MoveIn does not save ZIP searches to its application database or associate them with a name or email. The web server and reverse proxy may retain ordinary short-lived request logs, including IP addresses, for security and operations. The lookup does not collect a street address.
Coverage requests
The Request My ZIP Code page does not ask for an email, name, phone number, account, or street address. When analytics is available, MoveIn sends the requested five-digit ZIP and the request page as an anonymous event so aggregate demand can guide future coverage. Invalid ZIP entries are not sent. Browser privacy controls or blocking tools may prevent the event.
Corrections
A correction requires a ZIP code, issue type, and description. Provider name, supporting URL, and reply email are optional. Reports are stored separately from verified provider records and never update public data automatically.
Google Analytics
MoveIn uses Google Analytics 4 to understand aggregate website usage. It measures page visits and interactions such as successful ZIP lookups, county and guide navigation, printable use, My Move task categories, unsupported ZIP requests, renter guide and kit views, calculator starts and completions, and clicks to official provider information.
The move-in calculator does not save entered dollar amounts or send them to Analytics. Renter events use only public route names, coarse task categories, audience type, and counts such as the number of expense categories used. MoveIn does not send rent, deposit, fee, insurance, or moving amounts; lease details; utility account information; exact street addresses; email addresses; move dates; complete checklist text; notes; submitted correction descriptions; or other correction-form content to Google Analytics. Successful lookup events use aggregate context such as county, state, coverage status, and provider-category count rather than the entered ZIP code. The only ZIP-specific custom event is an explicit unsupported-coverage request.
Visitors may use browser privacy controls, Global Privacy Control, Do Not Track, or content-blocking tools to limit analytics tracking. Analytics being unavailable never prevents the site, lookup, calculator, printables, or My Move from working.
Sign-in and private households
MoveIn uses your email address to send single-use sign-in links, not marketing. The account database stores a stable user ID, email, verification state, and account timestamps, along with the authentication library’s required identity fields. We do not offer profiles or avatars. Sessions store an expiry, token, timestamps, and may retain IP address and browser information for access and security. A private household membership connects your account to the purchase records you confirm. Session cookies are HTTP-only, use SameSite protection, and require HTTPS in production. Signing out revokes the current session. Sign-in, receipt, and My Home pages do not send page views or private information to analytics.
Authentication has been implemented for local testing and has not been deployed. Local sign-in links appear in the developer terminal only when explicitly enabled. Production will require an explicitly configured email service to deliver sign-in links.
Receipts and My Home
Receipt processing and household inventory have not been deployed to production. With the Ollama extractor selected, JPG and PNG receipt photos are read by a locally installed vision model on the same machine running MoveIn. Receipt bytes are sent only to a configured loopback Ollama server, not an external API. Original files are processed in memory and discarded rather than stored in a permanent image library. Real PDF extraction is not enabled. An explicitly selected demo provider instead returns labeled sample purchases without reading the document.
Only purchase information you confirm and selected inventory items are saved in the local SQLite database. Authenticated records belong to your private household. An explicit development test mode retains a separate seeded household shared by local browsers; new accounts never inherit those legacy records. They are separate from My Move browser storage. Receipt and inventory queries are household scoped. Real JPG and PNG uploads are limited to 8 MB and 20 megapixels and decoded in memory before inference. Short-lived hashed IP and household keys enforce production upload limits; these limits reset when the app restarts. Receipt images and raw model responses are not logged. Analytics is disabled in local development. Private pages and APIs require a verified session and household membership. Authentication fails closed if production email and session configuration are missing. These local-processing statements apply to this Ollama implementation; any future cloud provider will need its own privacy policy.
Other sensitive information
MoveIn does not collect utility account credentials, Social Security numbers, identification documents, payment information, leases, closing documents, or My Move notes. Household inventory is private and has not been deployed publicly.
Data sales
MoveIn does not sell ZIP searches or personal information. Contact hello@movein.guide with privacy questions.