Privacy Policy

This describes what Space.RE (vmodo.com) collects, why, and who we share it with. Space is in active beta — treat this as a description of the product as it exists today, not a permanent promise.

• Account — the email address you sign in with, and a display name/photo if you set one.
• Location — your precise device location, read in two places: when you tap “Verify with location” for Tier 1 verification, and when you tap the location crosshair in the location search on Home or Match. These two paths are handled differently. For Tier 1 verification, your browser rounds that reading to the nearest coarse, city-scale location (roughly a kilometer) before anything is sent — your exact GPS coordinates never leave the device — and only that rounded point goes to our server, which matches it to the nearest known city and saves only the resulting city name (e.g. “Austin, TX”) and a timestamp to your account; no coordinates, rounded or exact, are stored. If your location isn’t close enough to any city we support, verification simply fails and nothing is saved. Locations anywhere in the New York City area — including Brooklyn and Manhattan — are all recorded as “New York, NY”. For the Home/Match crosshair, your browser matches the coordinates to the nearest known city entirely on your device, and the coordinates themselves never leave your device; only the resulting city/state is sent, to fetch listings for that area, and it isn’t saved to your account.
• Content you post — property listings, social posts, comments, direct messages, and photos you upload (see Vercel, below, for how uploaded photos are stored).
• Activity — favorites, saved searches and alert preferences, tour requests, style/preference tags derived from photos you submit for style-tagging, your swipe decisions in Match (liked/super-liked/skipped) and the answers you give during onboarding — both stored as preference signals used to tailor recommendations — and app state like onboarding progress — all tied to your account.
• Waitlist signup — if you join the waitlist on the welcome page or the Invest page, we collect the email address you type in. That form is public and doesn’t require an account, so we may collect this email from people who never sign up for Space, and it isn’t linked to any account record. We keep it until you ask us to remove it.
• Conversations with Agent — your chat messages, and, if you’ve favorited homes, a short summary of your saved cities, property types, and price range, so Agent can tailor its answers.
• Technical data — basic error and performance diagnostics captured automatically if something breaks (see Sentry, below).

To run the marketplace — show your listings and posts to other users, save your favorites and searches, send saved-search alert emails — to enforce the verification tiers, to let Agent answer with relevant context, and to find and fix bugs.

We don’t sell your data. We use a small number of service providers to run Space.RE. A few of them are contacted directly by your browser, not routed through our servers — for example, whenever the app displays an image, product photo, or map tile hosted on their site, or when a diagnostics script posts data straight to its provider’s servers. There’s no proxy in front of these, so that provider’s server sees your IP address, browser user agent, and roughly what you were doing, the same way any web page with a hotlinked image or third-party script works. We call this out specifically below wherever we know it applies, but it’s true of any third-party resource your browser loads from, or sends data to, directly, including ones added after this policy was last updated.

• Neon — hosts our Postgres database. Your account, listings, posts, messages, and everything else in this list lives there.
• Resend — sends your magic sign-in link and account/notification email (saved-search alerts) on our behalf. It also sends an internal notification — containing the address, phone, email, and note you submit — to our own ops inbox when you request full-service listing help, so a person can follow up with you; that notification goes to us, not to you.
• Anthropic — powers Agent, the photo style-tagging feature, and search. Your chat messages, the saved-home summary described above, any photo you submit for style-tagging, and the free-text search queries you type into Search are sent to Anthropic’s API to generate a response. Search queries can be personal (e.g. “near my kid’s school”) — don’t type anything you wouldn’t want sent to a third-party model.
• RapidAPI (us-real-estate) — supplies third-party listing data we blend into search results. We send it a search query (city, state), not your personal account data. If a listing came from this feed, its photos are hosted on the provider’s own photo CDN and loaded directly by your browser rather than through our servers — the same direct-fetch exposure described above.
• Vercel — hosts the app and stores photos you upload through Vercel Blob. Uploaded photos are stored at public URLs — anyone who has the URL can view the file, whether or not they’re signed in. Deleting your account deletes the photo files for any listings you posted — not just the database record that pointed at them — except for the narrow cases spelled out under “Data retention and deletion,” below, which also covers gaps like the fact that there’s no way yet to delete a single listing (or just its photos) on its own, without deleting the whole account.
• Sentry — receives automatic crash/error reports (stack traces, the page you were on) if something breaks, so we can fix it. It also records a sample (about 10%) of performance traces, and default breadcrumbs — recent console logs, the URLs your browser fetched, and what you clicked — leading up to an error, to help us reproduce it. We do not attach your account identity or IP address to that report data. But your browser sends these reports directly to Sentry’s servers — the same direct-fetch exposure described above — so Sentry’s infrastructure does see your IP address at the connection level, even though it isn’t included in the report itself.
• OpenStreetMap Overpass — looks up nearby schools, parks, and shops for a property’s coordinates, and, separately, looks up real local home-services providers (plumbers, electricians, and similar tradespeople) for the Services marketplace. For the property lookup, we send that property’s location, not yours. For Services, we send the centroid of your verified city — the same coarse, city-level location described above under “Location” — not your precise device coordinates, which (as described above) never leave your device. Both lookups are made by our server, not your browser, so Overpass sees our server’s IP address, not yours.
• CARTO — supplies the dark map-tile imagery behind property maps on Home, Search, and each property’s detail page. Unlike Overpass above, your browser loads these tiles directly from CARTO’s servers, so CARTO receives your IP address, browser user agent, and the map area and zoom level you’re viewing.
• Unsplash — some images in the app are loaded directly from Unsplash’s image CDN, which likewise sees your IP address when your browser requests them.
• Curbed, Inman, and Architectural Digest — real-estate and design news feeds shown on Explore › News. We fetch their RSS feeds ourselves, server-side, so the feed content doesn’t expose anything about you to them. Each story’s thumbnail image, however, is loaded directly from that publisher’s own CDN by your browser — the same direct-fetch exposure described above.
• DummyJSON — a free public catalog. When it’s reachable we use its live product data, including photos, for the Shop section instead of our own catalog, so most of what you see there is DummyJSON’s data, not a fixed sample set. We don’t send it your account info or search terms, but your browser loads each product photo directly from DummyJSON’s CDN — the same direct-fetch exposure described above.

Listing a property currently requires only a self-attestation — you check a box confirming who you are. (Services in the Shop section are browse-only today; there’s no way to create a service listing yet, so this tier only gates property listings.) We do not run a third-party background or ID check today. Don’t rely on an “ID verified (self-attested)” badge as proof of anyone’s real-world identity.

Beyond your account data, a few things live only in your browser, on your device:

• space.listingDraft.v1 — the listing wizard autosaves your in-progress draft as you type, so you don’t lose it if you navigate away. This can include the address, agent name/phone/email, contact phone, contact note, and photos you’ve added — photos are stored as raw image data, not just a link to them.
• space.recentSearches.v1 — your last 8 free-text Search queries, so you can tap a recent search again. There’s a Clear button on the Search page that erases these on demand.
• space.tour.seen.v1 and space.tour.replay — flags that record whether you’ve seen the onboarding tour, so it doesn’t show again uninvited.

We also set a few cookies to make sign-in work: __Host-authjs.csrf-token and __Secure-authjs.callback-url are set the moment you load the first page of the site, before you’ve signed in to anything, and __Secure-authjs.session-token is set once you’re signed in, to keep you signed in. (A local development build served over plain HTTP shows these same cookies without the __Host-/__Secure- prefix.) These are strictly functional — none of this is used for advertising or analytics.

Deleting your account does not clear any of this — it lives in your browser, not our database, so we have no way to reach in and remove it. Clear it yourself: use the Clear button on the Search page for recent searches, and your browser’s site-data or cookie clearing (in your browser’s settings, for vmodo.com) for the listing draft, the tour flags, and the cookies above.

Your content stays associated with your account until you delete it or ask us to. Request account deletion by emailing privacy@vmodo.com. Deleting your account removes your profile and cascades to the favorites, saved searches, tour requests, social posts, comments, the message threads you started and every message in them — and to the property listings you posted and any full-service listing requests you filed. One exception on messaging: if you replied inside a thread someone elsestarted, that thread is theirs, so it stays for them — the messages you sent in it remain visible to them, disconnected from your deleted account, the same way an email you sent still sits in the recipient’s inbox after you close your own.

On those last two: deleting your account removes the property listings you posted entirely, not just the agent name/phone/email on them. It also deletes the photo files you uploaded for those listings from Vercel Blob storage (see Vercel, above) — not just the database record that pointed at them — unless that photo is still in use by a listing you don’t own, in which case we leave that file in place rather than break that listing to finish deleting yours. Full-service listing requests are deleted outright from our database, including the address, phone, and email you gave us on them — though a copy of that request was separately emailed to our ops inbox when you submitted it (see Resend, above), and account deletion doesn’t reach that copy. We remove the listing rather than keeping it around with the contact info blanked out: a listing nobody can be reached about isn’t useful market data, it’s just a dead end for whoever finds it. The gaps that remain: there’s no way yet to delete a single listing, or just its photos, without deleting your whole account; a photo can end up with nothing in our database pointing at it, in three ways — another listing you don’t own may still be using that same photo (just described above); the one-time request to delete it from Vercel Blob storage may simply have failed, which we don’t automatically retry and don’t notify you about, leaving the file reachable at its public URL with nothing in our database pointing at it any more; or, separate from account deletion entirely, a photo you add while posting a listing is uploaded to Vercel Blob before the listing itself is saved — if that save is then rejected, fails, or you close the tab first, the photo can be left behind with nothing pointing at it. We re-check your identity verification, fresh, immediately before that upload starts, which prevents the single most common cause of that; we don’t yet have a way to recover a photo that’s already reached Vercel Blob if the save fails for some other reason, or the tab closes before it finishes. And the ops-inbox copy of a full-service request (just mentioned) isn’t touched by account deletion either. All of that still needs a manual request to privacy@vmodo.com.

Waitlist emails (see “Information we collect,” above) are a separate case — they aren’t tied to an account at all, so account deletion doesn’t touch them. We remove a specific one on request to the same address.

The cookies and on-device storage described above (see “Cookies and on-device storage,” above) are a separate case too: they aren’t in our database at all, so account deletion doesn’t touch them — you clear those yourself, as described there.

Space.RE isn’t directed at children under 13, and we don’t knowingly collect data from them.

We use standard safeguards, including encrypted connections and provider-managed database security, but no system is perfectly secure and we can’t guarantee absolute security of your data.

We’ll update the date at the top whenever this changes materially.

Privacy questions or a deletion request: privacy@vmodo.com.

Space Real Estate (sp∆ce) is a product of Vmodo, Inc., doing business as Space Real Estate. This build is a pre-launch demonstration: listings, payments, escrow, and investment flows are simulated or seeded unless explicitly marked live; no real-estate brokerage, lending, insurance, or securities services are being offered.