Estate MVPThis is a pre-launch privacy draft for attorney review. It describes the current system from its database schema and provider boundaries; it is not yet the final privacy notice. Counsel must add the exact LLC identity and address, determine which state and international privacy regimes apply, and approve the rights and notice language.
Scope and responsible company
The final notice will identify the Estate MVP legal entity responsible for the website and application, its mailing address, and an effective date. It will cover visitors, account holders, workspace members, buyers recorded by customers, sellers who submit information, and recipients of authorized communications. Privacy requests currently route to legal@estatemvp.com.
What is collected, why, and how long it is kept
| Category | Purpose and source | Retention | Deletion treatment |
|---|---|---|---|
| Account and workspace | Provided by users to authenticate them and enforce workspace access | Until workspace deletion is completed | Erased through workspace deletion, subject to required records |
| Buyer records and buy-box criteria | Entered by customers to organize demand and perform matching | Until the customer deletes them | Erased on customer deletion |
| Property and market data | Customer entries, licensed providers, and public records used for underwriting | According to the source contract and operational need | Customer entries can be removed; provider records follow source obligations |
| Investor seller submissions and consent | Provided by a seller who asks to be contacted about a property | Identity erasable on request; consent evidence retained for 3 years | Identity erased while minimum consent evidence is retained |
| Agent representation inquiries | Homeowner contact and property details, optional planning answers submitted with the inquiry, the campaign link used, the named team’s consultation disclosure, follow-up notes, appointments and agent-prepared comparable sales. Unsubmitted planning answers stay in the page and are not saved. | Until the workspace is deleted; contact details and drafts can be erased earlier by its administrator | Kept separate from investor purchase inquiries; withdrawal stops follow-up on the inquiry |
| Optional passwords | A salted password hash and change timestamp authenticate password sign-in; plaintext passwords are not stored | Until changed, removed from Your account, or the account is erased | Account-owned passwords remain when one workspace is deleted; remove the password in Your account |
| Connected accounts and passkeys | Provider issuer and subject identifiers, passkey public keys, device labels and security events; provider tokens and biometric data are not stored | Until removed from Your account; sign-in challenges expire after ten minutes and security events after two years | Account-owned methods remain when one workspace is deleted; remove them in Your account |
| Captured text and source URLs | Content a customer deliberately saves from a source they were viewing | Until the customer deletes it or a source contract requires earlier removal | Erased rather than republished |
| Proposals, messages, and delivery events | To record what was sent, its terms, authorization, delivery, and opt-out status | Recipient redacted on deletion; minimum record retained for 3 years | Identity redacted while delivery and compliance evidence remains |
| Billing records | Created through billing activity to explain invoices and disputes | 7 years | Retained for financial and dispute records |
| Security, rate-limit, and audit events | Generated to prevent abuse, investigate incidents, and prove material actions | 2 years; free-form details redacted during deletion | Identity minimized or redacted while necessary evidence remains |
How information is used
- Provide authentication, workspace access, matching, underwriting, exports, and support.
- Deliver authorized service and transactional emails and record delivery outcomes.
- Process subscriptions, meter only confirmed billable events, and resolve disputes.
- Prevent fraud and abuse, enforce security controls, and investigate incidents.
- Maintain source provenance, quality, confidence, and licensing restrictions.
- Meet legal obligations and honor deletion, withdrawal, and opt-out requests.
Service providers and data disclosures
Estate MVP does not sell or rent personal information. Providing the service nevertheless requires processors: hosting and database requests go to Cloudflare; card and subscription details go to Stripe; outgoing email goes to Resend; and requested property lookups go to enabled property or public-record providers such as RentCast, HUD, Census, or FEMA. The contracted provider list, locations, and transfer terms must be verified before launch. Card data entered on Stripe does not pass through Estate MVP servers.
When you set or change a password, the Pwned Passwords service receives only the first five characters of its SHA-1 hash so Estate MVP can compare the returned breach candidates locally. Your password, full hash and account email are not sent to that service. This check is required for a new password; email sign-in remains available if the service cannot be reached.
Data licensing and customer content
Provider data remains subject to the provider's license, permitted-purpose, attribution, derivative-use, and retention limits. Demonstration fixtures remain labeled as demonstration data. Customer uploads remain private to the authorized workspace and are not republished publicly. Customers must have rights to the content and contact information they provide.
Email consent, delivery, and suppression
Estate MVP records the source of communication authority where available. It processes delivery, hard-bounce, complaint, and opt-out events to protect recipients and sending reputation. Suppression records may remain after other workspace data is deleted because deleting a request not to be contacted would enable the very contact the person stopped. A suppressed address is checked again immediately before sending.
Deletion and retention process
A workspace owner can schedule workspace deletion. Access ends immediately and destructive deletion follows a 30-day recovery period. Some financial, consent, suppression, delivery, and security evidence is retained for the periods above with identity redacted where practicable. A seller can withdraw using the link in the message received without creating an account. The final policy must specify identity verification, response deadlines, exceptions, appeals, and any state-specific rights.
Security and incident notices
Estate MVP uses server-side sessions, organization-scoped access checks, limited API projections, rate limits, hashed tokens, provider-secret isolation, signed webhooks, and audit records. No system can promise absolute security. If an incident affects personal information, the company will investigate, contain, document, and provide notices required by applicable law. Counsel must approve the incident-notification procedure, recipients, timing, regulator contacts, and state-specific language before launch. See the security page for current technical controls and limitations.
Cookies and automated tools
Essential cookies support sign-in and session security. Turnstile helps detect automated abuse. The current product does not use advertising pixels. First-party screen views and product milestones are already recorded for product and cost analysis. Optional onboarding answers, saved research, notes and walkthrough progress are stored for workspace use; optional answers never affect matching or pricing. Minimal trial sponsorship and billing records support cost reconciliation and prevent repeat grants. If new analytics providers, cookies, or AI-assisted features are enabled later, this notice and any required consent controls must be updated first. See AI transparency.
Children and sensitive uses
The service is intended for business users, not children. The service may not be used to create housing criteria based on protected characteristics or demographic proxies. Counsel must determine whether any collected information is sensitive under the laws of the states where the product is offered.
Rights and requests
Depending on location, a person may have rights to access, correct, delete, restrict, or obtain a copy of personal information, or to appeal a decision. The final policy must list the rights that actually apply and a verified request process. Requests may be sent to legal@estatemvp.com. Estate MVP will not require a seller to create a paid account merely to submit a privacy or opt-out request.
Changes
The final notice must explain how material changes will be announced and how the effective date and prior versions are retained. Product or provider changes that alter collection, purpose, disclosure, or retention require this page to be reviewed before deployment.