Privacy Policy

We may collect and process account registration data and sign-in information, including email address, name when supplied, authentication codes or password credentials, session data, and the identity details returned when you choose Google sign-in. The sign-in system also records legal-acceptance time and policy version; the pending acceptance record includes the request IP address.

The current waitlist form collects only an email address. Its server handler also records request IP address and user-agent and uses the IP address for rate limiting. The public API still accepts optional name and rental-unit count from direct callers; those values are stored if sent. The waitlist entry is stored in the application database and a confirmation email may be sent.

The testimonial form collects a quote, display name, and optional role/context. Its handler stores the request IP address for abuse prevention. The public API still accepts an optional submitter email from direct callers, but the current form does not send one.

Property workflows can store property and unit details, tenant and vendor information, lease details, documents and extracted fields, ledgers, messages, maintenance requests and photos, and other records you enter or upload. Account profile data can include timezone, phone number, and notification preferences.

For tenant rent payments, payment-method details are entered through Stripe Elements and sent to Stripe. RentMochi receives and stores application payment records and provider identifiers/status needed to display and reconcile a payment; Stripe processes the payment method.

The application uses submitted information to authenticate accounts, save and retrieve property records, process documents, provide chat and AI-assisted features, create reports, send requested emails or enabled SMS notifications, support user-selected integrations, record legal acceptance, prevent abuse, and diagnose errors.

The application source contains no analytics tag, advertising pixel, Session Replay integration, or marketing-email opt-in. Browser error reporting is optional and is loaded only after analytics consent; its configuration disables default PII and removes email/IP values from event text and breadcrumbs.

Application records are stored in PostgreSQL through Prisma using the deployment's DATABASE_URL. The code does not identify the database host. Documents may be uploaded to Google Drive when a user connects Drive and uses a workflow that saves or retrieves them.

The repository includes a GCP Cloud Run service manifest, but application source does not establish which hosting environment currently serves users. The deployment host should be confirmed before launch.

Owner-chat prompts and relevant property context go to Google Gemini by default, or to DeepSeek when selected in our deployment configuration. Resident-chat prompts and relevant tenant and property context go to OpenAI by default, or to Google Gemini or DeepSeek when selected. Utility text tasks, including memory compaction, listing drafts, negotiation assistance, natural-language query planning, and property summaries, go to OpenAI by default, or to Google Gemini or DeepSeek when selected. Google Gemini also processes onboarding chat, public demo chat, OCR, document extraction, and grounded vendor and price lookups. OpenAI may receive bounded document text for fallback metadata extraction. When configured, an automated second-opinion check sends an uploaded lease's extracted fields and OCR excerpt to DeepSeek. Content sent to DeepSeek is processed and stored on servers in the People's Republic of China, and DeepSeek's terms permit it to use submitted content to improve its models, including tenant content when tenant-facing features use DeepSeek. The waitlist and account email workflows use Resend; enabled SMS workflows use Twilio; subscription and tenant payment workflows use Stripe.

Property geocoding sends the address to OpenStreetMap Nominatim. Vendor lookup can send trade and city/state to Google Places or Gemini search. Rent estimates send city, state, and bedroom count to RentCast. Appliance recall lookup sends a manufacturer/brand term to the U.S. CPSC public recall API. Server diagnostics may be sent to the configured Sentry project.

Google sign-in and Google Drive OAuth send authentication requests to Google. The code includes a QuickBooks authorization redirect, but its token exchange/sync functions are stubs; Plaid token/sync functions, Gmail sync, and DocuSign signing functions also do not make provider API calls in the current code. A Cloud Run manifest is present, but the source does not confirm it is the current host; the PostgreSQL host is not identified.

If you configure a developer webhook, selected application events may be sent to the destination URL you provide. That destination is controlled by you or your organization.

Authentication cookies and application records support sign-in and product workflows. Optional browser storage and the consent choices are described in the Cookies Policy. Documents stored in Google Drive remain subject to the connected Google account's settings.

The product includes account export and account deletion/closure actions in Settings. The code does not set a single retention period for every record or provider, so this notice does not promise a universal deletion deadline. Use the available product controls for account data and contact the privacy email in Operator details below for privacy requests.

For privacy questions or requests, use the privacy email shown in the Operator details section above.