Last updated: August 13, 2026

Privacy Policy

This policy explains how voicerow handles information for Realtors who use open house sign-in, voice recap, and Google Sheets workflows.

Voicerow is designed for your own recap after a showing, call, open house, or pop-by.

The first workflow prepares reviewed fields for the sheet or lightweight tracker you already use.

We only request access to the Google Sheet you connect.

1. Information we collect

Account information such as your Firebase user id, email address, display name, profile photo, authentication provider, and sign-in timestamps.
Anonymous session identifiers created after cookie consent so the app can preserve state before you sign in with Google.
Agent recap content and structured fields you choose to enter, record, review, or send to connected tools such as Google Sheets.
Open house event details and visitor information such as name, phone, email, real estate interest, representation status, and contact-consent time.
Founding Member applications, including work email, brokerage, market, showing volume, and the workflow answers you choose to submit.
Technical data such as browser, device, app route, security verification results, consent state, and error information needed to operate and protect the service.

To provide the voice-to-spreadsheet workflow, authenticate users, preserve session continuity, and secure sign-in with Cloudflare Turnstile.
To turn your reviewed agent recaps into structured rows, next actions, and follow-up details for your existing workflow.
To create open house previews, publish shareable event details after Google sign-in, collect visitor sign-ins for the hosting Realtor, show aggregate attendance, and provide private exports or optional Google Sheets sync.
To improve product reliability, troubleshoot errors, understand feature usage, and prevent abuse or automated activity.
To communicate with you about support, product updates, billing, or legally required notices when those features are enabled.

Firebase and Google Cloud host the application, authenticate users, store Firestore documents, and provide analytics when enabled.
Cloudflare Turnstile helps verify that sign-in attempts are made by real users.
Stripe may process billing information if paid plans are enabled. Voicerow does not store full card numbers.
Google Sheets or other integrations are used only when you choose to connect or export to them.

Account records are retained while your account is active or as needed for security, support, tax, or legal obligations.
Open house visitor details are available only to the event owner through authenticated tools; public event pages expose event details and aggregate counts, not visitor identities.
Unclaimed open house previews may be stored temporarily until you sign in with Google to save them, or until they expire. Anonymous records may be linked to the same Firebase uid if you later sign in with Google.
You can request access, correction, export, restriction, or deletion of personal data by emailing us from Privacy Settings or by contacting us directly.

You can sign out at any time and may choose whether to continue using the capture workflow.
Privacy Settings provides email request links for access, correction, export, deletion, restriction, and consent-related requests. It does not use in-app switches.
Where required by law, you may object to certain processing or withdraw consent for consent-based processing.

We use transport encryption, Firebase security controls, service-account-based server writes, Turnstile verification, and data minimization practices.
No internet service is perfectly secure, but we design Voicerow to keep field-capture data limited to the narrow capture workflow.