This Privacy Policy explains how REAP Technologies LLC ("REAP," "we," "us," or "our") collects, uses, shares, and protects information when you visit getreap.ai, use the REAP application at app.getreap.ai, or otherwise interact with our services (collectively, the "Services").
1. Information We Collect
Information you provide directly
- Account information — name, email address, password, and company or organization name when you create an account.
- Billing information — when you subscribe to a paid plan, payment details are collected and processed by our payment processor (see Section 4). REAP does not store full payment card numbers.
- Property and deal data — addresses, financial figures, notes, and other information you enter into the REAP platform to analyze real estate opportunities.
- Communications — information you provide when you email us, request support, or respond to surveys.
Free deal score requests (getreap.ai/start)
If you use the "Paste an address, get a free deal score" form on getreap.ai/start, we collect:
- What you enter — your email address and the property address you want scored. We do not ask for your name or phone number, and we do not call or text you.
- Campaign parameters — the utm_source, utm_medium, utm_campaign, utm_term, utm_content and utm_id values from the link that brought you to the page, if any.
- Referral and ad-click details — the referral code from a REAP partner link (if you arrived through one), the Facebook click ID (fbclid) that Facebook or Instagram adds to links from our ads, and a fixed lead-source label that identifies the form (for example "getreap_start"). Like the rest of your request, we keep these for 12 months from submission.
- A salted hash of your IP address — we do not store your IP address. We combine it with a secret value (a "salt") and store only the resulting one-way hash, which we use to limit repeat and automated submissions. The form also uses a Cloudflare Turnstile bot check (see Section 3).
- Timing and status — when you submitted the request and whether it has been scored and emailed.
Purpose: we use this information to score the property, email you the result, measure our marketing, and prevent abuse. Retention: we keep these requests for 12 months from submission and then delete them, unless you create a REAP account, in which case your account information is handled as described in this policy. You can ask us to delete your request sooner by emailing hello@getreap.ai.
Information collected automatically
- Usage data — pages viewed, features used, actions taken, and timestamps.
- Device and connection data — IP address, browser type, operating system, and referring URLs.
- Cookies and similar technologies — used to keep you signed in, remember preferences, and understand how the Services are used.
- Advertising data — on our ad landing page we use the Meta Pixel, which runs in your browser and sends information about your visit to Meta for advertising, and when you create an account in the REAP application our own code sends two requests about the sign-up to Meta. Our servers also send Meta events through Meta's Conversions API: a Lead event when you send the free deal score form or the free report form (with a SHA-256 hash of your email address, plus a SHA-256 hash of your phone number if you give one on the free report form), a CompleteRegistration event when you create an account, and Subscribe or Purchase events when you pay for a REAP plan (each with a SHA-256 hash of your email address and of your REAP account ID). See Section 3 and Do Not Sell or Share My Personal Information.
2. How We Use Your Information
We use the information we collect to:
- Provide, operate, maintain, and improve the Services;
- Create and manage your account and authenticate logins;
- Process subscriptions, billing, and transactions;
- Send transactional messages — confirmations, password resets, security alerts, and service notices;
- Send product updates, onboarding guidance, and marketing communications (you can opt out — see Section 6);
- Advertise on Meta platforms (Facebook and Instagram): measure which ads lead people to visit and sign up, and help Meta show our ads to people who are more likely to be interested (see Section 3);
- Respond to your questions and provide customer support;
- Monitor usage, detect and prevent fraud or abuse, and maintain the security of the Services;
- Comply with legal obligations and enforce our agreements.
3. Cookies and Tracking
We use cookies and similar technologies to operate and improve the Services. Essential cookies are required for sign-in and core functionality. Analytics cookies help us understand aggregate usage patterns. Advertising cookies are used for advertising on Meta, as described below. You can control cookies through your browser settings; disabling certain cookies may affect how the Services function.
Meta Pixel (advertising)
We advertise on Facebook and Instagram, which are operated by Meta Platforms, Inc. ("Meta"). For that advertising we use the Meta Pixel. On our ad landing page (getreap.ai/start), the Pixel is a small piece of code from Meta that runs in your browser and sends information about your visit to Meta. In the REAP application, no Meta code is loaded: only at the moment you create an account, REAP's own code sends two direct requests to Meta's Pixel service (one page view and one account-creation event). The REAP application does not use the Pixel after that. Besides these browser requests, our servers send Meta a Lead event when you send the free deal score form on getreap.ai/start or the free report form, a CompleteRegistration event when you create an account, and Subscribe or Purchase events when you pay for a REAP plan. These server events are covered below. Under California privacy law this is "sharing" of personal information for cross-context behavioral advertising, and you can opt out (see Do Not Sell or Share My Personal Information).
What is collected.
- Page views on the pages listed above, including the page address, the referring page, and the ad campaign parameters in the link you clicked (for example utm_source or utm_campaign).
- Interaction and sign-up events — these are the only events we send: PageView (a visit to getreap.ai/start, or the moment you create an account in the REAP application), ViewContent (playing the demo video on getreap.ai/start), StartCTAClick (clicking a "Try REAP free" button on getreap.ai/start), Lead (successfully sending the free deal score form on getreap.ai/start; the browser event carries only the event name and a fixed label, and the property address is never sent) and CompleteRegistration (creating an account in the REAP application). With each we send the event name, a short fixed label (for example which button was clicked), and, for account creation, a random event ID that is not linked to your account details.
- Browser and device information that Meta receives with these requests from your browser, such as your IP address and browser type, and, on getreap.ai/start, information that Meta's code collects automatically, including the Meta cookies described below.
- Server events with a hashed email — for ad measurement, our servers also send Meta a copy of some of these events through Meta's Conversions API: Lead when you send the free deal score form or the free report form, CompleteRegistration when you create an account, and Subscribe or Purchase when you pay for a REAP plan. Each server event includes a SHA-256 hash of your email address (lowercased and trimmed before hashing; your email itself is not sent). If you give a phone number on the free report form, its Lead event also includes a SHA-256 hash of your phone number (digits only, with the country code, before hashing; the number itself is not sent). Account and payment events also include a SHA-256 hash of your REAP account ID, and payment events include the plan, amount and currency. When available, we also include Meta's own browser identifiers (the _fbp and _fbc cookie values), your browser's user agent, and the page address without its query string. The server event uses the same event ID as the browser event, so Meta counts it once. Our servers do not send your IP address to Meta.
- Your opt-out applies to server events too — if you used the opt-out link, or your browser sends Global Privacy Control (GPC) or Do Not Track (DNT), we send no server events from that browser. If anything about your opt-out status is unclear, we send nothing. Payment events are sent only if your account was created without an opt-out, and they stop as soon as you opt out in the REAP application.
- What we do not send — we do not send your name, and we do not send your email address, phone number or REAP account ID in plain (unhashed) form. We do not send the contents of any form beyond the hashed email and phone number described above, and the Pixel's automatic collection of button and form details is turned off. We also do not send your property address, property or deal data, or card or bank details.
Why. We use this information for advertising: to count how many people who saw or clicked our ads visited our site or signed up, and to help Meta show our ads to people more likely to find REAP useful. Meta processes this information under its own Privacy Policy and may combine it with information it already has, for example if you are logged in to Facebook or Instagram.
Cookies used by the Meta Pixel. When the Pixel loads on getreap.ai/start, Meta's code sets a first-party cookie named _fbp on getreap.ai (which app.getreap.ai can also read) so Meta can measure our ads, and an _fbc cookie when you arrive from one of our ads. If you opt out (see Do Not Sell or Share My Personal Information, or turn on Global Privacy Control or Do Not Track), the Pixel is not loaded, no _fbp or _fbc cookie is set, and we delete any _fbp or _fbc cookie already set on getreap.ai in that browser.
| Cookie | Set by / domain | Purpose | Duration |
|---|---|---|---|
| _fbp | Meta Pixel, first-party cookie on getreap.ai / app.getreap.ai | Assigns your browser a random identifier so Meta can recognize visits and events from the same browser and measure ad results. | 90 days |
| _fbc | Meta Pixel, first-party cookie on getreap.ai / app.getreap.ai | Stores the click ID (fbclid) added to the link when you click one of our ads on Facebook or Instagram, so a later sign-up can be attributed to that ad click. | 90 days |
| Meta's own cookies (for example fr) | Meta, third-party cookies on facebook.com | Set and read by Meta under its own policies, for example to connect activity to a logged-in Facebook or Instagram account. | Set by Meta |
How to opt out.
- Do Not Sell or Share — use the button in Do Not Sell or Share My Personal Information, or turn on Global Privacy Control (GPC) or Do Not Track (DNT) in your browser (see Do Not Track and Global Privacy Control). In each case, we do not load the Meta Pixel in that browser, no _fbp cookie is set, and any existing _fbp/_fbc cookie is deleted.
- Meta ad settings — control how Meta uses activity from other websites and apps to show you ads in your Meta ad preferences, and review or disconnect it under Your activity off Meta technologies.
- Browser settings — you can block or delete cookies (including _fbp and _fbc) and block third-party cookies in your browser's privacy settings, or use a content or tracker blocker. Doing so stops the Pixel from recognizing your browser but does not affect your ability to use REAP.
- Industry opt-out tools — you can also use the Digital Advertising Alliance (US) or Your Online Choices (EU) opt-out pages.
- Ask us — to ask us not to share your information with Meta, email hello@getreap.ai.
Bot check on sign-up, sign-in and getreap.ai/start (Cloudflare Turnstile)
To keep automated bots out, the sign-up, sign-in and password-reset screens of the REAP application (app.getreap.ai), and the free deal score form on getreap.ai/start, use Cloudflare Turnstile, a bot check provided by Cloudflare, Inc. When one of these pages loads, your browser loads a script from challenges.cloudflare.com. Cloudflare may process technical data such as your IP address and browser and device signals to tell people from automated traffic, under its own privacy policy. We use the result only to protect sign-up, sign-in and the deal score form. On getreap.ai/start the script loads when the page opens, and our server checks the result with Cloudflare before your request is accepted. Turnstile is not used for advertising, is separate from the Meta Pixel described above, and we do not send any Turnstile data to Meta. Content or tracker blockers may block the script; if that happens the check may not appear or may fail, and you can turn the blocker off for this site and try again.
Microsoft Clarity (site analytics)
Offer timer on getreap.ai/start. When the page shows a time-limited offer, it needs to know when you first opened it so the timer is fair and does not restart. Your browser stores that time and a random offer session ID in local storage under the key reap_start_offer on getreap.ai. Our server keeps the same random session ID with its start time and a salted, one-way hash of your IP address (never the IP address itself); if you then submit the form, we add a one-way hash of your email address so the offer can be applied to your new account. This is used only to apply the offer, not for advertising, and is not shared with Meta, Microsoft or anyone else. You can delete the reap_start_offer entry by clearing this site's data in your browser; that does not restart an offer timer that has already started.
On our ad landing page (getreap.ai/start) we may use Microsoft Clarity, an analytics service from Microsoft Corporation, to see how visitors use the page (for example clicks, scrolling and where people leave) through heatmaps and session replays, so we can improve it. Clarity runs in your browser, sets first-party cookies (such as _clck and _clsk) and sends usage and device data to Microsoft, which processes it under the Microsoft Privacy Statement. Everything you type into a form is masked and never sent to Clarity. We do not load Clarity if you have opted out with the button in Do Not Sell or Share My Personal Information, or with Global Privacy Control or Do Not Track.
4. Third Parties We Share Information With
We share information with service providers who help us operate the Services, only to the extent necessary for them to perform their functions. We also share information with Meta for advertising when the Meta Pixel is active and when our servers send Meta Lead, CompleteRegistration, Subscribe or Purchase events through Meta's Conversions API (see Section 3). Under the California Consumer Privacy Act, as amended by the California Privacy Rights Act (CCPA/CPRA), that is "sharing" personal information for cross-context behavioral advertising, and it may be treated as a "sale" under California and other state privacy laws. You can opt out at any time; see Do Not Sell or Share My Personal Information.
| Provider | Purpose | Information shared |
|---|---|---|
| SendGrid (Twilio Inc.) | Sending transactional and marketing email | Email address, name, message content |
| Stripe | Payment processing and subscription billing | Name, email, billing details, payment information |
| Supabase | Application database and authentication hosting | Account data, property/deal data, usage records |
| Meta Platforms, Inc. (Meta Pixel) | Advertising on Facebook and Instagram, including measuring our ads (see Section 3). This is "sharing" under the CCPA/CPRA; you can opt out. | Page views and sign-up events, campaign parameters, IP address, browser information, Meta cookie IDs (_fbp, _fbc). No name, email address, phone number or account ID. |
| Cloudflare, Inc. (Turnstile) | Bot check on sign-up, sign-in and password-reset pages, and the free deal score form on getreap.ai/start (see Section 3) | IP address, browser and device signals, and the check result |
| Microsoft Corporation (Clarity) | Site analytics on getreap.ai/start: heatmaps and session replays to improve the page (see Section 3). Not loaded if you opt out, or with Global Privacy Control or Do Not Track. | Clicks, scrolling and page interactions (everything typed into forms is masked), IP address, browser and device information, Clarity cookie IDs (_clck, _clsk) |
| Analytics provider | Understanding aggregate site and product usage | Usage data, device data, IP address |
Each of these providers maintains its own privacy and security practices. We may also disclose information if required by law, to protect our rights or the safety of others, or in connection with a merger, acquisition, or sale of assets.
5. Data Retention
We retain your information for as long as your account is active or as needed to provide the Services. After account closure, we retain certain information as required to comply with legal obligations, resolve disputes, and enforce our agreements. You may request deletion of your data as described below.
Free deal score requests from getreap.ai/start (email address, property address, campaign parameters including utm_id, referral code, Facebook click ID (fbclid), lead-source label and salted IP hash) are kept for 12 months from submission and then deleted (see Section 1).
6. Your Choices and Opt-Out Rights
- Marketing email — every marketing email from REAP includes an unsubscribe link. You can opt out at any time. You will still receive essential transactional messages related to your account.
- Access, correction, and deletion — you may request a copy of your personal information, ask us to correct it, or request deletion by emailing hello@getreap.ai.
- Cookies — you can manage cookies through your browser settings.
- Do Not Sell or Share — you can opt out of the sharing of your personal information with Meta for advertising, and we honor Global Privacy Control and Do Not Track. See Section 7.
- Meta advertising — you can also limit how Meta uses our Pixel data through your Meta ad preferences and your browser settings, as described in Section 3.
- Account data — you can edit most account information directly within the REAP application.
Advertising and Meta (Facebook and Instagram)
We use Meta's advertising tools to measure our ads and show REAP ads to people who may be interested.
What we use. The Meta Pixel runs on our public web pages, but not on our investor pages or our email consent pages. We also send certain events to Meta from our servers using the Meta Conversions API: when you request a deal score or free report (Lead), create a REAP account (CompleteRegistration), and pay for or subscribe to a plan (Purchase or Subscribe).
What Meta receives. Your email address, phone number and REAP user ID in hashed (scrambled) form, Meta browser identifiers stored in cookies (fbp and fbc), your browser's user agent, and the page or event involved. We never send your street address, payment card details, or deal and property information you enter. Hashed data can still be matched by Meta to an account it already has, so we treat it as personal information. Meta uses this data under its own policies, including the Meta Privacy Policy at facebook.com/privacy/policy.
Your choices. You can turn off Meta advertising tracking at any time with the "Do Not Sell or Share My Personal Information" link at the bottom of every page. We also treat a Global Privacy Control (GPC) or Do Not Track signal from your browser as an opt-out. When you opt out, we stop the pixel in your browser and stop sending your events from our servers. You can opt back in from the same link unless your browser is sending GPC, in which case we keep you opted out. Depending on where you live, this use of your data may count as "sharing" for cross-context behavioral advertising or targeted advertising, and opting out is how you exercise that right. You can also manage ad settings in your Meta account.
Questions. Email support@getreap.ai.
7. Do Not Sell or Share My Personal Information
When the Meta Pixel is active on our ad landing page (getreap.ai/start), when you create an account in the REAP application, and when our servers send Meta Lead, CompleteRegistration, Subscribe or Purchase events, information about you is sent to Meta for advertising, as described in Section 3. Under the CCPA/CPRA this is "sharing" of personal information, and it may be treated as a "sale" under some state laws. You have the right to opt out, and you do not need an account to do so. We will not treat you differently for opting out.
Global Privacy Control (GPC)
We honor the Global Privacy Control signal as a valid request to opt out of the sale or sharing of your personal information. If your browser or extension sends GPC, we do not load the Meta Pixel on getreap.ai, the REAP application does not send its account-creation events to Meta, and we send nothing to Meta from that browser.
Do Not Track and Global Privacy Control
Some browsers can send a Do Not Track (DNT) or Global Privacy Control (GPC) signal. When our website or app detects either signal, we treat it as your request to opt out of advertising measurement. We will not load Meta's pixel or send Meta pixel events from that browser, and we will delete the Meta cookies (_fbp and _fbc) that may have been set. You can also opt out at any time with the button on this page. These choices apply to the browser and device where you make them. If you clear your cookies or switch browsers, you may need to opt out again.
Opt out in this browser
Click the button below to opt out on getreap.ai. We will not load the Meta Pixel on getreap.ai in this browser from now on.
Your choice applies per website and per browser. It is saved in this browser's storage for getreap.ai only. The REAP application at app.getreap.ai is a separate website with its own storage. If you have opted out on getreap.ai, its sign-up buttons pass your choice on to the REAP application automatically. You can also turn on GPC or DNT, which both sites honor. In the REAP application, you can also use the ‘Do Not Sell or Share My Personal Information’ link at the bottom of the sign-up and sign-in screens before you create your account. If you clear your browser data, or use a different browser or device, you will need to opt out again there.
You can also opt out by emailing hello@getreap.ai.
8. Data Security
We use industry-standard technical and organizational measures to protect your information, including encryption in transit, access controls, and row-level security on our database. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
9. Children's Privacy
The Services are not directed to individuals under 18, and we do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us so we can delete it.
10. Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date above. Material changes will be communicated through the Services or by email.
11. Contact Us
If you have questions about this Privacy Policy or how we handle your information, contact us at:
REAP Technologies LLC
3422 W Idlewild Ave
Tampa, FL 33614
Email: hello@getreap.ai