Privacy Policy

Revr AI, Inc. ("we," "us," or "our") operates the Revr platform at getrevr.com. This Privacy Policy explains how we collect, use, store, and protect your information when you use our service.

Account Information

When you create an account, we collect your name, email address, and password. If you subscribe to a paid plan, we collect billing information through Stripe (we do not store credit card numbers directly).

Usage Data

We collect information about how you use the Platform, including features accessed, properties viewed, outreach sent, and AI interactions. This data is used to provide the service and improve the user experience.

Property & Contact Data

The Platform processes property information, owner data, and contact details obtained through third-party data providers on your behalf. This data is associated with your account and used to provide deal sourcing, scoring, and outreach services.

Outreach Data

If you use email or SMS outreach features, we process the content of messages sent and received through the Platform, including email addresses, phone numbers, message content, and engagement metrics (opens, clicks, replies).

Mailbox Content (only if you switch it on)

If you turn on mailbox reading for a connected mailbox, we process the messages in that mailbox, including senders and recipients, dates, subject lines and message bodies. It is off by default and it is never implied by connecting an account to send from. It is available today for Microsoft Outlook. For Gmail it is in limited early access: it needs a second Google consent for a restricted scope that is still under Google’s verification review, so while that review runs it is offered only to accounts we have invited. Section 8 sets out exactly what is read, what is stored, for how long, and how to switch it off.

Mobile Number & Text Messaging Consent

If you opt in to receive text messages from us, we collect that mobile number, your opt-in consent and the time it was given, and the content of the messages you exchange with us. No mobile information is sold, rented, or shared with third parties or affiliates for their own marketing or promotional purposes. See our SMS / Text Messaging Program section for the full terms.

Gmail API Usage & Compliance

Revr’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

• Send-only today. The Gmail API is used solely to send emails you personally compose or review and approve.
• Mailbox reading is a separate opt-in. Revr’s product includes an opt-in feature to read a connected mailbox, described fully in Section 8. It is off by default and never implied by connecting Gmail to send. For Gmail, turning it on requires a second, explicit consent to a restricted Google scope whose verification review is still running, so for now it is offered only to accounts we have invited. Either way, reading is switched on only by you, per mailbox.
• You choose who you email. The Gmail API sends only messages you write, or review and approve, to the people you choose, one at a time or by enrolling them in a campaign. That can include clients, contacts you already know, and new prospects. Revr does not choose recipients for you.
• No email warming. Revr does not provide email warming services for Gmail or any Google account. Any per-mailbox daily sending limits exist solely to protect your account’s health and deliverability, and are not a service to circumvent spam filtering or artificially inflate sender reputation.
• Recipient opt-out. Every outreach, campaign and prospecting email sent through the Gmail API includes a working one-click unsubscribe link and a postal address. (A message you send to your own client about their deal or agreement goes as ordinary one-to-one email.) Using the link adds the recipient to a suppression list that is checked before every send, so an address that opts out is permanently blocked from further email through the Platform. Addresses you mark as do not contact are blocked the same way.

AI Conversations

Conversations with Reggie (our AI assistant) are stored to provide context continuity and improve the service. These conversations may include property data, investment criteria, and business preferences you share.

The Revr iOS app is a companion to your Revr account. It signs you in to the same workspace and shows the same records; there is no separate account and nothing is purchased inside the app. This section describes the device permissions the app asks for, what each one is used for, and what leaves your phone.

The app asks for a permission only at the moment the feature needs it, and never collects any of this in the background. Declining a permission disables that one feature and nothing else. You can change any of them later in iOS Settings → Revr.

Camera

Used only when you choose to take a picture: a photo of a building for that building's record, or a flyer, sign or document for Reggie to read. Photos of a building are uploaded to your workspace's private storage and are visible to your team, exactly like a photo uploaded from the web. A picture for Reggie is sent with that message and stored with the conversation. The app does not open the camera at any other time.

Photo Library

Used only when you choose an existing image to attach: a flyer, floor plan or listing sheet for Reggie to read, a photo for a building's record, a picture in an email you are writing, or the logo in your email signature. Only the image you pick leaves your phone, and it is stored where you attached it. The app never browses or indexes your library.

Microphone

Used only while you are talking to the app: a live conversation with Reggie that you start and end, dictating a message to him, or taking your side of a practice call in Coach Reggie. The microphone opens when you press to talk or start a conversation, and closes when you let go or end it. The audio is sent to our AI and speech-to-text providers to be understood and transcribed, and it is the transcript, not the audio, that is saved to your workspace. The recording itself is written to the app's temporary cache on your phone, which iOS clears automatically, and Coach empties that cache when a practice session ends. The microphone is never opened without a press.

Location

Used only to centre the prospecting map on where you are standing, so you can scan the block in front of you. Your own position is used on the device to move the map; we do not store it, attach it to any record, or track your location in the background, and the app never reads it unless the map is open and you ask it to.

Separately, when you deliberately draw a search area or tap a specific parcel, the coordinates of that area or point are sent to our servers to run the search or look up the public record, because that is the request. Those are coordinates you chose on a map, not a reading of where your phone is.

Face ID

Optionally used to unlock the app instead of typing your password. Face ID is handled entirely by iOS: the app receives only a yes-or-no answer, and no biometric data of any kind is transmitted to us or stored by us.

Notifications

If you allow them, we send notifications about your own work, such as a reply arriving or a draft waiting for your approval. We do not send marketing notifications. You can turn them off in iOS Settings or in the app's own notification settings.

Data stored on the device

The app stores your sign-in token in the iOS Keychain, which is hardware-encrypted and erased when the app is deleted. It also keeps a small cache of records you have recently viewed so they remain readable without a connection. That cache is cleared when you sign out. Conversations, drafts and inbound messages are deliberately never cached.

Deleting your account from the app

You can delete your Revr account from within the app, under Settings → Sign in and security. Deleting removes your access and disconnects every connected mailbox and calendar immediately, and permanently erases your workspace data and stored files 30 days later, the same as deleting from the web.

This section describes how Revr AI, Inc. handles mobile numbers and text messaging consent. It applies to every text message program we operate.

No mobile information is sold, rented, or shared with third parties or affiliates for their own marketing or promotional purposes. Text messaging originator opt-in data and consent are never shared with any third party or affiliate for marketing or promotional purposes. Mobile numbers are disclosed only to our messaging provider (Twilio) for the sole purpose of delivering the messages you asked for, and only under a contract that forbids any other use.

How we obtain your consent

You give consent directly to Revr, never through a partner, a lead vendor, or a purchased list. Consent is collected in one of two places:

• Demo requests. On our booking form at getrevr.com/book-demo you may tick an optional checkbox, unchecked by default, to receive text messages about scheduling and following up on your demo request. Submitting the form without ticking it means you will not be texted.
• Text Reggie. Inside your account you may verify your own mobile number to exchange messages with Reggie, our AI assistant, which then sends you replies to your questions, approval requests, and reminders.

Consent to receive text messages is never a condition of any purchase, and never a condition of booking a demo. We record the wording you agreed to and the time you agreed to it so we can evidence your consent on request.

What we collect and why

For these programs we collect your mobile number, your opt-in consent and its timestamp, and the content of the messages you exchange with us. We use this only to operate the messaging program you opted into.

Frequency, rates, and how to stop

Message frequency varies. Message and data rates may apply. Reply STOP to any message to unsubscribe, or HELP for help. You can also email privacy@getrevr.com. Opting out is honored immediately and permanently for that number, and it does not affect your account or your demo.

Messages our customers send

Separately from the programs above, Revr customers use the Platform to message their own contacts from their own connected accounts. In that case the customer is the sender and is responsible for obtaining consent from their recipients, and Revr acts only as the technology provider that transmits the message at their direction. See our Terms of Service for the obligations that apply to them.

• To provide, maintain, and improve the Platform and its features.
• To process transactions and manage your subscription.
• To send emails and SMS messages on your behalf through your verified domain and provisioned phone number.
• To generate AI-powered property analyses, outreach copy, and recommendations.
• To track usage against your plan limits (monthly usage, daily pulls, skip traces).
• To send you service-related communications (billing confirmations, security alerts, feature updates).
• To detect and prevent fraud, abuse, or violations of our Terms of Service.

We use the following third-party services to operate the Platform. Each processes data according to their own privacy policies:

Revr uses Google APIs to (a) send emails you author or approve from your own Gmail account to the people you choose, and (b) display and manage events on your own Google Calendar. Every outreach email among them carries a working unsubscribe link, and an address that opts out is permanently blocked from further sends. Connecting Gmail and Google Calendar is optional and entirely controlled by you, and by itself grants only send and calendar access, never mailbox reading. (Mailbox reading, described in section 8, is a further, separate opt-in. It is available today for Microsoft Outlook; for Gmail it is in limited early access to invited accounts, because it needs a second Google consent that is still pending Google’s verification review.)

What we access, Gmail

When you click "Connect Gmail", we request the following OAuth scopes from Google:

• gmail.send , to send email from your account on your behalf, only for messages you compose or approve in Revr, to recipients you choose, with a working unsubscribe link on every outreach email.
• userinfo.email , to identify which Gmail account is connected and display it in Settings.
• gmail.readonly , requested only if you separately turn on mailbox reading in Section 8. This is a second, explicit consent screen, never bundled with the connection above.

Connecting Gmail through the button above requests only gmail.send and userinfo.email; it does not request gmail.readonly, gmail.modify, or any other inbox-read scope, and grants no access to read your mail. Replies to your outreach go directly to your own inbox, and unless you separately turn on mailbox reading, Revr never receives or reads them. If you want Reggie to help with a specific reply without turning that feature on, you forward that one message to Reggie's inbound address, and only the message you choose to forward is processed. Turning on mailbox reading is described in Section 8; because gmail.readonly is a restricted Google scope still pending Google’s verification review, that second consent is currently offered only to accounts we have invited.

What we access, Google Calendar

If you click "Connect Google Calendar", we additionally request:

• calendar.events , to display your schedule inside Revr's Tasks calendar and to create or update events you choose to add. Sync is two-way and limited to your own calendar. We do not request the broader calendar scope, which would also cover calendar settings and sharing.

We use your calendar data only to show your schedule and manage events inside Revr. We do not share it or use it for any other purpose, and the Limited Use commitments below apply equally to calendar data.

How we use this data

• Send messages you author or approve within Revr to the recipients you choose.
• Display the Google account you connected so you know which one is active.
• Show send status (sent / bounced) from delivery webhooks, not by reading your inbox. Replies stay in your own inbox unless you choose to forward one to Reggie.
• Show and manage your calendar events inside the Tasks calendar.

Limited Use disclosure

Revr's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

• We do not sell, transfer, or share Google user data (Gmail or Calendar) with third parties for advertising, marketing, or any unrelated purpose.
• We do not use Google user data to train or fine-tune any AI/ML model, including Reggie. AI processing of email content is limited to providing the Revr features you use, such as drafting a message, sorting a reply into interested, not now or opt-out, or recognizing a space inquiry, and is never used for any generalized model training.
• We do not allow humans to read Google user data, except: (a) with your explicit consent, (b) for security purposes such as investigating abuse, (c) to comply with applicable law, or (d) for internal operations where the data has been aggregated and anonymized.
• We only access the Google user data necessary to deliver and improve the features you actively use.

Storage & encryption

OAuth access and refresh tokens are stored encrypted at rest in our database (Supabase) and transmitted over TLS. Through this send-and-calendar connection, we retain only the minimum data needed to power your views: sent-message timestamps, the original outbound body you authored, the details of calendar events synced from your connected calendar, and the contents of any reply you explicitly forward to Reggie. The rest of your Gmail inbox is not transmitted to or stored by Revr through this connection. If you separately turn on mailbox reading (Section 8), a further, explicit consent applies and Section 8 describes exactly what is then transmitted and stored; for Gmail that second consent is in limited early access while Google’s review runs.

Revoking access

You can disconnect Gmail at any time from two places:

• Inside Revr: Settings → Integrations → Gmail → Remove. This deletes your stored OAuth tokens immediately.
• From your Google Account: myaccount.google.com/connections → select Revr → Remove access.

Once revoked, Revr can no longer send email or access your calendar on your behalf. Existing outreach history saved in Revr remains visible until you delete your account or request data removal at privacy@getrevr.com.

Revr can optionally read the mailbox you connect, so that Reggie has the context of your real correspondence rather than only the messages Revr itself sent. This section describes exactly what that means. It is off unless you switch it on.

The feature described in this section, which copies your mailbox into Revr so you can read and search it here, is a separate choice and it starts switched off. Turning it off again deletes the mail Revr stored. It is never implied by connecting an account to send from.

One other thing reads your inbox, and only if you allow it. When you connect Outlook, Revr asks whether it may read your inbox to catch replies. You can untick that before the Microsoft consent screen appears. If you leave it ticked, a scheduled job checks that mailbox every five minutes for messages received in the previous ninety minutes, and keeps a message only when it is a reply to an email you sent from Revr. Anything else is discarded and never stored. That is what lets Revr pause a sequence when somebody replies, and stop emailing somebody who asks you to. For Gmail nothing reads your inbox unless you have turned on the feature below: replies land in your own mailbox and stay there. The same box lets you archive, delete, move or mark mail read from Revr’s Inbox and have it apply in Outlook. Revr changes your mailbox only when you press one of those controls or ask Reggie to, and deleted mail goes to your Deleted Items, where Outlook keeps it.

Which accounts this applies to

This feature is available for Microsoft Outlook accounts where you allowed Mail.Read when you connected. It is not switched on by default, and there is no self-serve control for it today; ask us and we will switch it on for your account.

For Gmail, this feature is in limited early access. Turning it on requests the restricted gmail.readonly scope through its own consent screen, described in Section 7, separate from the send-only connection you get today. Google is still completing its verification review of that scope, so while that review runs Revr offers the switch only to accounts we have invited, and Google asks those accounts to re-approve it every seven days. We will update this policy when the review finishes, and Google’s own consent screen will still ask you separately before anything is read.

What is read

When you switch it on, Revr reads the whole connected mailbox, not only messages that relate to something Revr itself sent, including your Sent Items and any folders you have filed mail into, going back up to twelve months on the first sync and every new message after that. For Outlook, Revr does not read your Drafts, Junk Email, or Deleted Items.

What is stored, and for how long

• Reach: the first sync goes back up to twelve months. The sender, the recipients, the date, whether the message was sent or received, the subject line, and the first line or two of the message are kept for as long as reading stays on, they do not expire on their own; turning reading off deletes them (see “Turning it off” below).
• For ninety days: the full text of the message body, counted from when the message was received. After ninety days the body is deleted automatically and only the details above remain. A message that was already older than ninety days the first time Revr read it never has a body stored at all; opening it in Revr fetches the text live from your provider instead, and that live copy is never written back to storage.
• Attachments: Revr records each attachment’s filename, type and size. Opening one in Revr fetches it live from your provider; that copy is not stored. The one exception: an attachment that looks like deal paperwork, such as an offer, an agreement, an offering memorandum or a floor plan, from someone you work with, is saved to your own private storage and filed on the matching deal or building, or held for you to file. Invoices, receipts, logos and automated mail are skipped.

What it is used for

One purpose: giving Reggie the context of your own correspondence inside your own workspace, so he can answer questions about a thread, tell you who is waiting on a reply, and write a follow-up that reflects what was actually said.

• We do not use your mailbox content to train or fine-tune any AI model, including Reggie.
• We do not sell, rent, transfer, or share it with third parties for advertising, marketing, or any unrelated purpose.
• We do not make it visible to your teammates. Mailbox content is private to your own account, even inside a shared workspace.
• We do not use it to build or enrich any dataset that spans customers.
• We do not allow our staff to read it, except (a) with your explicit consent, (b) to investigate abuse or a security incident, or (c) where the law requires it.

If you switch on Leads from your inbox, Revr also reads emails from real estate portals (such as Zillow, Homes.com, Realtor.com and Redfin) in that mailbox to create leads for you. To tell a real lead from an ad, Revr may send such an email to our AI provider. The lead details Revr copies into your pipeline (the person's name, their contact details, the home and what they asked) then follow your pipeline's sharing, like any other lead.

The other people in your mailbox

Reading a mailbox necessarily involves messages written by other people. Revr processes that content solely to provide this feature to you, the account holder, on the same terms set out above. It is stored under your account, deleted on the schedule above, and removed entirely when you switch the feature off.

Turning it off

You can switch mailbox reading off at any time in Settings → Integrations. Doing so stops all further reading and, by default, deletes every message Revr has stored from your mailbox. Disconnecting the Outlook account entirely, or revoking Revr’s access from your Microsoft account, has the same effect on future reading and cuts off access immediately.

Your data is stored in Supabase (cloud-hosted PostgreSQL in the United States). Every request is limited to your own account and workspace by the application, and row-level security is enabled on every table as a second lock. We use encryption in transit (TLS) and at rest, and the credentials for your connected accounts are additionally encrypted with AES-256-GCM under a key held outside the database. Authentication tokens are managed securely and never exposed to client-side code.

Payment information is processed and stored by Stripe. We do not have access to your full credit card number.

While we implement industry-standard security measures, no system is completely secure. We cannot guarantee absolute security of your data.

We retain your account data and associated property/contact data for as long as your account is active. Cancelling your subscription does not delete your data. Deleting your account does: your access and every connected mailbox and calendar end immediately, and 30 days later your workspace data, including stored files, is permanently erased. If you share a workspace with teammates, the workspace and its records stay with your team, and we erase your own account data by hand within the same 30 days.

Conversations with Reggie are kept for 12 months and then automatically deleted.

Call recordings and transcripts are kept with your account data: for as long as your account is active, and erased with it after you delete your account. Revr uses call audio and transcripts only to provide the service to you, and does not use them to train AI models.

You may request data export or deletion at any time by contacting support@getrevr.com.

Depending on your jurisdiction, you may have the right to:

• Access , request a copy of the personal data we hold about you.
• Correction , request correction of inaccurate personal data.
• Deletion , request deletion of your personal data (subject to legal retention requirements).
• Portability , request your data in a machine-readable format.
• Opt-out , opt out of non-essential communications at any time.

To exercise any of these rights, contact us at privacy@getrevr.com.

Revr uses essential cookies for authentication and session management. We do not use third-party advertising cookies or advertising pixels. On our public website only (the homepage, pricing and signup pages, not the app), we count visits with a random ID kept in your browser, and Microsoft Clarity records how pages are used (clicks and scrolling, with anything you type hidden) so we can fix pages that confuse people. Neither runs inside the app. Emails you send through Revr may carry Revr's own open and click tracking, described in section 13. We do not sell your data to advertisers or data brokers.

When you use Revr to send outreach, the recipients of those messages are not our users, they are your contacts. We process their contact information (email, phone, name, address) solely to facilitate outreach on your behalf. We do not use recipient data for our own marketing purposes.

Emails you send from Revr may contain open and click tracking: a small image and links that pass through revrlink.com, Revr's tracking address, so you can see when an email was probably opened and which links were clicked. We record the time, the kind of mail app, and a one-way hash of the network address, never the address itself. These records belong to your account and are never used for advertising. You can turn tracking off in Settings, Outreach.

Recipients who unsubscribe from your emails or reply STOP to your SMS messages are added to a suppression list specific to your account. We honor all opt-out requests promptly.

Revr is not intended for use by anyone under the age of 18. We do not knowingly collect personal information from children.

We may update this Privacy Policy from time to time. Material changes will be communicated via email or in-app notification at least 14 days before taking effect. The "Last updated" date at the top reflects the most recent revision.

For questions or concerns about this Privacy Policy or our data practices, contact us at:

Revr AI, Inc.
Email: privacy@getrevr.com
Web: getrevr.com