Privacy Policy
Last updated: November 12, 2026
LEGAL-4 in monetization-readiness.md).1. What we collect
Account information: name, email address, and (for credentials sign-in) a hashed password. If you sign in with Google, we receive your name and email from Google.
Client information you enter: if you use the Service to manage your own real-estate clients, we store the names, emails, budgets, and financing details you enter about them. This data belongs to you and your business relationship with your client — see our Terms of Service for your responsibilities regarding it.
Usage data: properties you search, the number of analyses you run each month (to enforce plan quotas), and general application logs.
Final results of your analyses: when every comparable behind an analysis has been confirmed, we keep a record of its final figure — the property address, the date, the suggested value or rent and its range, and the comparables it rests on — under a unique reference number that is also printed on your report. The record does not include your clients' names. While your account exists it is linked to your account.
Analytics and cookies: we sort the cookies and similar tools we use into two groups, and you decide about the second one.
- Essential — always on. The cookies that keep you signed in (a session cookie, plus
next-auth.csrf-tokenandnext-auth.callback-url), the record of your cookie choice (ws_consent, kept for 180 days), and the limits on repeated sign-in attempts and requests that protect accounts from abuse. The Service cannot work without them, so there is nothing to switch off. - Analytics — off until you accept. Google Analytics and its cookies (
_ga,_ga_*), a first-visit cookie of ours (wisesquire_utm) that remembers the campaign that brought you to the site so a later signup can still be credited to it, the usage events our servers send to Google Analytics about what you do (signing up, running an analysis, exporting a report), and page-speed measurements of the site.
Nothing in the Analytics group runs, and nothing is sent to Google, until you choose "Accept analytics" on the cookie banner. "Essential only" is just as easy to choose, and the Service works the same either way. If your browser sends the Global Privacy Control signal and you have not chosen, we treat that as "Essential only" and do not ask; pressing Accept afterwards overrides it.
Once you accept, Google Analytics receives the path of the page you are on (never the property address or a client's details), the campaign tags of the link you arrived by, the page title, the site that referred you, and which product actions you take. For events sent from our servers, your account is represented by a keyed code — not your email address or account number. Google's advertising features (Google signals and ad personalization) are switched off. We don't sell this data or use it to build an advertising profile of you.
You can change your mind at any time: "Cookie settings" at the bottom of every page reopens the choice. Choosing "Essential only" deletes the Google Analytics and campaign cookies from your browser and stops anything further being sent; when you are signed in the choice is also saved to your account, so you are not asked again on another browser. Data Google Analytics has already received stays there until it expires; contact us (see section 8) if you want it removed. You can also block cookies in your browser settings, or use Google's Analytics opt-out browser add-on, without losing access to the Service.
Billing information: if you subscribe to a paid plan, payment details are collected and processed directly by Stripe — we never see or store your full card number.
2. How we use it
- To provide and operate the Service (run your analyses, save your client list and search history)
- To authenticate you and secure your account
- To send transactional email (email verification, password reset, billing receipts) — never marketing email without separate consent
- To enforce plan quotas and prevent abuse
- To improve the Service and diagnose issues
We do not sell your personal information. We do not use your account details, your clients' details, your searches or your results to train artificial-intelligence or machine-learning models, and we do not give them to anyone else for that purpose.
3. Third-party services and sub-processors
We use the outside services below to run the Service. This is the full list of those that receive information from you or about you, and each entry says what it receives, why, and when. Your clients' names, emails, budgets and financing details are kept on our hosting provider and in the encrypted backups; none of the other services below receives them.
Hosting and backups
Where the Service runs and where its copies are kept.
Railway
Receives: Everything you store in the Service — your account, your clients, your searches and your results — because the Service and its database run on Railway's servers.
Why: Hosts the application and its database.
When: Always.
Cloudflare R2
Receives: An encrypted copy of the database, taken every hour. The copy is encrypted with a key Cloudflare does not have before it leaves our server, so Cloudflare cannot read it.
Why: Disaster recovery — restoring the Service if the database is ever lost.
When: Always. It is not used for anything you see.
Property data and addresses
What we look up when you run an analysis.
RentCast
Receives: The property address you analyze, and the search criteria built from it (such as bedrooms, size and distance). Never your name or your clients' details.
Why: Property records, valuations, rent estimates, comparable listings and market statistics — the core data the Service is built on.
When: Whenever you run an analysis.
RealtyAPI
Receives: The address of the property and of its comparable properties.
Why: Confirms facts such as garage and basement that other property data does not carry.
When: Analyses on the Pro plan only.
US Census Geocoder
Receives: The address you type.
Why: Puts the address in its standard postal form so the same property is always looked up the same way.
When: Whenever you run an analysis.
OpenStreetMap Nominatim
Receives: The address you type, once when you submit an analysis.
Why: Checks that the address exists and flags a likely typing mistake.
When: Whenever you run an analysis.
Sign-in, payment and email
What it takes to have an account.
Google (sign-in)
Receives: Your sign-in request. Google gives us your name and email address.
Why: Lets you sign in with your Google account instead of a password.
When: Only if you choose Sign in with Google.
Stripe
Receives: Your name and email address, and the payment details you enter on Stripe's own page — which we never see.
Why: Takes payment for a paid plan and manages the subscription (receipts, changing your card, cancelling).
When: Only if you subscribe to a paid plan.
Resend
Receives: Your email address and name, and the text of the email.
Why: Delivers the emails we send you, such as address verification and password reset.
When: Whenever the Service emails you.
Have I Been Pwned (Pwned Passwords)
Receives: The first five characters of a one-way scramble of the password you choose — never the password itself, and not enough to identify it.
Why: Refuses passwords that have appeared in known data breaches.
When: When you create or reset a password.
Analytics and error tracking
Off, or limited, unless you or we choose otherwise.
Google Analytics
Receives: What section 1 describes: the path of the page you are on (never a property address or a client's details), the campaign tags of the link you arrived by, the page title, the site that referred you, a keyed code instead of your account number or email address, and which product actions you take.
Why: Understanding how the Service is used.
When: Only after you choose “Accept analytics”.
Sentry
Receives: Technical details of an error: the path of the page (property addresses and client ids removed), your browser, and the error itself. Page-speed traces too, but only if you accepted analytics. No recordings of your screen.
Why: Finding and fixing errors.
When: Only if we switch error tracking on.
Loaded by your browser
Your browser contacts these directly when a page shows the map.
OpenStreetMap map servers
Receives: Your browser's request for map images: your IP address, your browser's details and which part of the map you are looking at.
Why: The background of the map of comparable properties.
When: Only on a page that shows the map.
Federal Reserve Bank of St. Louis (FRED). The Service looks up the current 30-year mortgage rate from FRED. That request carries nothing about you or your clients.
Links that open another website, such as a listing on Zillow or a location in Google Maps, do nothing until you click them.
4. Data retention and security
We retain your account and client data for as long as your account is active. Property and valuation data fetched from RentCast is cached to reduce redundant lookups and cost. Passwords are hashed (never stored in plain text). The database is backed up hourly to off-site storage. We take reasonable measures to protect your data but cannot guarantee absolute security.
5. Your rights
You can review and update your account information from your account page. From that same page, you can export a copy of your data — your profile, clients, their search history, your usage log, and the final results you have validated — as a JSON file, and permanently delete your account and the data associated with it at any time. Deletion takes effect immediately and cannot be undone. One exception: the records of final results described in section 1 are not erased when you delete your account — the link to you is removed, so they no longer show your name, your email address or your account, and the rest of the record is kept. If you need help with a data request that isn't covered by those self-service controls, contact us at the address below.
6. Children's privacy
The Service is intended for licensed real estate professionals and investors and is not directed at children. We do not knowingly collect information from anyone under 18.
7. Changes to this policy
We may update this Privacy Policy from time to time. Material changes will be reflected by updating the "Last updated" date above.
8. Contact
Questions about this policy or a data request? Contact us at support@wisesquire.com.