Privacy in the beta
Draft notice · 16 September 2026. This describes the current product and its limits. It has not been legally reviewed; operator identity, contact details and final retention terms still need confirmation before a wider launch.
What Basecamp stores
We store your sign-in identifier and email, household membership, search briefs and answers, proposed and applied search plans, listing reviews, saved or dismissed homes, scan progress and usage. We also store billing references and subscription status, and the help or privacy requests you submit. Don’t include financial account numbers, identity documents, medical information or other sensitive details in a brief or request.
Your brief draft and one-time save intention can be stored in your browser so a sign-in does not lose your work. Signing out does not necessarily remove that local draft; clear the site’s browser storage on a shared device when finished.
Why this data is used
Basecamp uses these records to prepare your search, compare listings, share results with your household, manage subscription allowances, answer requests and investigate errors or abuse. We do not currently sell household records or add advertising trackers. Technical logs and provider systems may still record network and device information needed to operate the service.
Providers and sharing
Clerk handles sign-in and identity records. Stripe handles hosted checkout, payment details and billing; Basecamp does not receive your full payment card number. AWS hosts the application, database and backups. Anthropic’s managed agents receive search briefs and related context for planning; Google’s Gemini service receives listing facts, photos and search criteria for reviews. The listing provider accessed through RapidAPI receives listing or area queries. Routing services can receive the origin/destination coordinates used for travel estimates.
Providers process data under their own terms and account settings. Their training, retention, regional processing and deletion settings are still being verified for this beta; we cannot promise zero provider retention or that every provider excludes model training. If that uncertainty is unacceptable, do not submit personal details. Ask a privacy question before continuing.
Household members can see shared briefs, plans and decisions, and member email addresses. Your help requests and operator responses are visible to you and the operator, not to other household members. The operator may access records to support you and maintain the service.
Export, correction and deletion
In Help and your data, an owner can download a JSON export and request household deletion. Any member can request their own personal records, a correction, or help leaving a household. The immediate export is a defined product-data export, not a copy of every record held by external providers.
Deletion is reviewed manually. Submitting a request does not immediately delete records, stop jobs, cancel billing or delete your Clerk login. We must verify the request, shared-household impact, billing obligations and any records that must be retained before confirming completion. You can withdraw an open request, but that cannot undo steps already completed.
Retention and backups
Active product records are retained to provide the service. There is currently no automatic expiry for household records or closed help requests, and no final retention schedule has been adopted. Operators must review retention and explain any necessary exceptions when handling a deletion request.
Backups and other recovery copies can outlive active records. The cloud-storage lifecycle rule for scheduled database backups keeps each current backup object for 35 days and its noncurrent version for another 35 days. That rule applies only to those scheduled database backups; it is not a limit on every copy. Other copies — including retained database storage volumes, database snapshots taken locally before software updates, and configuration and release recovery artifacts, which currently have no automatic expiry — are outside that rule, and their retention is still under operator review. Provider records have separate retention that also still needs review. A restored backup must have completed deletion decisions reapplied before service resumes.
Questions and updates
Use the privacy request option in Help. It is a manually reviewed in-app queue with no guaranteed response time or automatic email notification. If you cannot sign in, contact the person who invited you to the beta. Material policy changes will be dated on this page; no claim is made that this draft meets every jurisdiction’s requirements.