Privacy policy

1. Overview

FendLand is a service operated by 97Dev LLC, which owns and operates the fendland.com website. This Privacy Policy explains what data we collect, how we use it, and the choices you have. We do not sell your personal information.

2. Information we collect

Information you provide

• Account information: email address and password
• Message text you submit for scanning
• Sender phone numbers you optionally provide with scans
• Personal information for removal requests: full name, phone number, mailing address (street, city, state, ZIP), and email address. You can also add your date of birth. It is optional, and we use it only to file with the few sites that will not remove a listing without one.
• Notes you add to your evidence log
• Property inquiry form responses (if you use an inquiry link)
• If you ask for your removal checklist or re-check alerts on the free exposure check: your email address, the name, city, state and street address you entered, and which sites listed you. We use them to send the checklist and to re-check those sites about every three months for one year, and we email you only when a site newly lists you. We send marketing email only if you tick the separate box for it. Every email has a one-click unsubscribe; unsubscribing stops all email to that address and deletes the name, city and street address we kept for re-checking. If you do not unsubscribe, we delete them when the year ends. We do not keep the phone number you entered.
• If you report a number on its lookup page: the fixed answers you choose (whether it called or texted, and what it was about) and a keyed one-way hash of your IP address, used only to count each visitor once. We never store the IP address itself. Reports are shown only in aggregate, as unverified, and are deleted after one year.
• Phone numbers you enroll in Phone Protection (a Shield Pro feature), so we can watch them for SIM-swap and carrier port-out fraud
• Subscription and billing details, handled by our payment processors (we do not store full payment card numbers)

Information from title and closing partners

• If your real estate closing is protected through a FendLand partner (such as a title or escrow company), that partner gives us your name, email address, phone number, property address, and closing date so we can invite you to activate protection and monitor for wire-fraud and data-broker exposure around your closing.

Information processed by the iOS SMS filter

• The filter reads the text and the sender's number of SMS and MMS messages from senders who are not in your contacts. It does this on your iPhone, to decide whether each one is property spam.
• None of that leaves your phone. The filter makes no network requests, so the message text, the sender's number and the verdict are never sent to FendLand or to anyone else, and we do not store them.
• The app tells us whether the filter has run on your phone and how many senders it flagged in the last 30 days. These are counts only.
• If you choose to report a message to FendLand from the Messages app, iOS sends us a one-way hash of the sender's number and the scores our filter gave that message. The message text is never sent. See Section 9.

Information collected automatically

• IP address (used for rate limiting, and stored with a consent record when you give consent; see Section 3)
• Standard server logs (request paths, timestamps)
• Authentication session tokens (stored in secure cookies)
• On Android with Shield Pro, the phone number of an incoming caller, in one case: when a call arrives from a number that is not already on the block list saved on your phone and that your carrier has not verified, the app sends that caller's number to FendLand while the phone rings, to check it against our spam list. Only the number is sent. The call is never forwarded or recorded, the request does not carry your account, and we do not save the number to a database, though it appears in the standard server logs above as part of the request. On iPhone, call blocking matches numbers on the device and sends nothing per call.
• On our public pages only, a Meta Pixel ad-measurement cookie and page-view signal, in Limited Data Use mode (see Section 5 and our Cookie Policy)

Third-party data

• Phone number carrier and line type data from Twilio Lookup (cached up to 60 days)
• Carrier, line type, and SIM-swap status for numbers you enroll in Phone Protection, retrieved from Twilio Lookup to detect port-out and SIM-swap fraud

3. How we use your information

• To provide the Service: scan messages, save results to your evidence log, and submit removal requests on your behalf.
• To classify messages using AI: when the scanner cannot confidently classify a message you submit, the message content and carrier metadata (not your phone number) are processed by Anthropic's Claude AI API to classify it. See Section 5 for details.
• To improve spam detection: periodically, a redacted sample of messages already classified as spam is processed by Anthropic to identify new scam and wholesaler phrasing, which becomes new detection rules. Email addresses, phone-style numbers and long digit sequences are removed before the sample leaves our systems, and it carries no account identifier. The same sample also informs the examples used in our own marketing about scam tactics. Both uses are controlled by the AI features switch in the app under Settings → Legal; turning it off stops your messages being used for either, from that point on.
• To send transactional emails: account-related emails (password reset, confirmation) and removal request submissions via Resend.
• To enforce rate limits and prevent abuse: IP addresses are used transiently for rate limiting (held in Redis only for the length of the limit window, at most 24 hours) and are not persisted in our database for this purpose.
• To keep evidence of your consent: when you give consent, such as agreeing to receive SMS messages, signing the removal authorization letter, or signing a closing opt-in, we store your IP address with that consent record as evidence that you gave it. The IP address is kept for as long as the consent record is kept. Consent records tied to your account are deleted when you delete your account, with one exception: a closing opt-in signature is part of the closing record your title company holds, so its IP address stays with that record.
• To maintain audit logs: we keep a record of actions taken on your removal requests, which protects both you and us.
• To operate Phone Protection (Shield Pro): we periodically check the carrier, line type, and SIM-swap status of numbers you enroll and alert you when they change, which can signal a port-out or SIM-swap attack.
• To process payments: our payment processors bill Shield Pro and partner plans and manage renewals on our behalf.

4. Community Blocklist

When you scan a message classified as WHOLESALER or SCAM with a phone number, FendLand anonymously increments a counter for that number in our Community Blocklist. This contribution:

• Contains no information that identifies you
• Stores only: the phone number (E.164 format), classification type, and count
• Is used to show aggregate reputation data to other users

You can opt out of contributing to the Community Blocklist by not providing a sender phone number when scanning.

5. How we share your information

We do not sell your personal information. We share information only in the limited circumstances below:

When a feature you use needs it

These features share information only when it is needed for the feature to work.

• Data brokers (removal requests): When you start an Assisted or Hybrid removal, we share your name, phone number, mailing address, and email with the broker you are asking to remove you, on your behalf. This is the purpose of the feature. If you added your date of birth, we send it only to the sites that require one to remove a listing, in the opt-out we file on that site's own form for you. It is never included in the emails or the authorization letter we send to brokers.
• Exposure scan (search provider): When you run an exposure scan, our search provider (SerpAPI) processes your name, city, and state to find where your information is published on data-broker and people-search sites. When a search by name does not find a confident match, we may also search by the phone number or street address you entered, because some sites list people by those instead of by name. We never send your email address to the search provider. Results are used solely to show your exposure and offer removal.
• Anthropic (AI classification): When our rule-based scanner cannot confidently classify a message you submit, the message text and sender carrier metadata (carrier name, line type, VoIP flags) are processed by Anthropic's Claude API to classify it. Separately, a redacted sample of messages already classified as spam is processed periodically so we can learn new scam phrasing and turn it into detection rules; that sample has email addresses, phone-style numbers and long digit sequences removed first. Messages handled by the iOS SMS filter are never sent to Anthropic, because they never leave your phone (Section 9). In both cases we do not send your phone number, email, name, or any user identifier to Anthropic, and you can stop both with the AI features switch under Settings → Legal. Under its API terms, Anthropic does not retain the content to train its models. See Anthropic's Privacy Policy.

Companies that run the service

These providers host, store and deliver FendLand, report errors so we can fix them, and process payments.

• Service providers: Supabase (database and auth), Resend (email delivery), Twilio (phone carrier lookup), Vercel (hosting). Each provider follows its own privacy policy.
• Sentry (crash and error reporting): Receives crash reports and handled errors from our apps and servers: the error, a stack trace, your device model and OS version, and a record of the screens and actions leading up to it. We configure Sentry not to collect personally identifying request data, and it receives your account's internal ID so we can tell whether one person hit an error repeatedly. Sentry also records a sample of app sessions as replays (roughly one in ten sessions, and any session where an error occurs). Replays are configured to mask all text and images, so they show how the app was used rather than what it displayed. The contents of your messages are never captured. See Sentry's Privacy Policy.
• Payment processors: Stripe processes subscription payments made on the web and by partners. Subscriptions purchased in our mobile apps are processed by Apple or Google and managed through RevenueCat. We receive your subscription status but do not store full payment card numbers.

Product analytics and ad measurement

These tell us which features are used and whether our ads lead people to FendLand.

• Mixpanel (product analytics): Helps us understand how features are used. It receives which features you use and when, for example that a scan was run or a number was blocked, along with your account's internal ID and the answers you gave during onboarding or in the short quiz on /quiz, such as whether you own property and what type. For the iOS SMS filter it receives whether the filter has run on your phone, how many senders it flagged in the last 30 days and how long ago the last one was. On our website's public pages it receives that a phone number lookup page was viewed (with the area code, not the number) and that an app store button or Copy number was tapped, under a random ID that lasts only while the tab is open; tapping through to install passes that ID to the app, so we can tell which pages lead to installs. These website events follow the same opt-outs as our ad measurement (Global Privacy Control, or the switch on our Cookie Policy). It does not receive the contents of your messages, the phone numbers you scan, or your name, email or address. See Mixpanel's Privacy Policy.
• Meta (ad measurement): When we advertise on Facebook and Instagram, we share with Meta which ads led to activity, so we can measure how they perform.

  In plain terms

  • We measure whether an ad led someone to visit our site, run a free scan, finish our quiz, tap through to the app store, create an account, install the app, or start a trial or subscription.
  • This is ad measurement. It is not a sale of your personal information.
  • If you are signed in on the website, your account email and an internal account ID are hashed in your browser first, meaning turned into a one-way code. Meta can still use that code to match the activity to a Meta account, so it is not anonymous.
  • You can turn web ad measurement off on our Cookie Policy page, a browser that sends Global Privacy Control is opted out automatically, and our apps do not ask for the iOS tracking permission.

  The details

  On the website

  On the website, the Meta Pixel runs only on public pages, the two free scanners, the phone number lookup pages and the email-confirmation page (never on sign-in, your account, support, or private links) and sends that a page was viewed, that a free scan ran, that you reached each screen of our short quiz on /quiz (with the options you had tapped so far: how often you get these texts, how long it has been going on, whether you get other spam, what kind of property you own, whether you live there, what you have tried and what bothers you most about it) and the result it showed you, that an app store button was tapped, or that an account was created, with the page address and standard browser details. On a phone number lookup page, that address includes the number being looked up, which is a publicly reported caller, not you. If you are signed in on the website, it also sends your account email and an internal account ID, each hashed (SHA-256) in your browser before it leaves, so Meta can match the activity to a Meta account; this is called advanced matching.

  The quiz link copied on iPhone

  When you tap to install the app from the quiz on an iPhone, we copy a FendLand link to your clipboard. It holds your quiz path (owner, not the owner, or calls), your property type and the result type you were shown, plus your random visitor ID if you allow analytics, so the app can skip the questions you already answered. It stays on your phone. The app only asks iOS whether there is a link on your clipboard, and reads it only if you tap “Skip the questions you answered” and allow the paste.

  Quiz leads sent from our server

  When a quiz result counts as a lead, our server also sends that same event to Meta directly (Meta's Conversions API) with your IP address, your browser's details, and the Meta cookie and ad click ID already on your browser, so Meta can match it to the ad you came from even when the pixel is blocked; it follows the same opt-outs and Limited Data Use, and Meta counts the two copies once.

  App store links

  A "get the app" link on the website tells the FendLand app which page you came from and, where you already told us, whether you own property and what kind, or that you came to stop spam calls, so the app does not ask again. On Android that travels through Google Play, so Google receives it too; Apple receives only the name of the page. None of it includes your name, phone number or address. On /quiz, the app store button also passes a short code of those quiz answers and the result to Apple or Google, so we can count installs by result.

  In our apps

  In our apps, Meta's SDK receives that the app was installed and opened, that an account was created, and that a free exposure scan ran, with an anonymous app identifier; RevenueCat tells Meta when a trial starts or a subscription is purchased, with that same identifier and standard device details.

  What Meta never receives

  Apart from that hashed account email and ID, Meta never receives your name, email, phone number, address, anything you type into our forms, the messages or numbers you scan, or your exposure results. We do not request the iOS tracking permission, and on the web we use Meta's Limited Data Use mode, under which Meta processes this data as our service provider in US states with privacy laws.

  Campaign cookie

  If you reach our website from one of our ads or another tagged link, a first-party cookie (fl_attr, 30 days) records the campaign names in that link, Meta's click ID, the page you landed on and when; if you create an account we keep that record with your account, and it is deleted with it. We use it only to tell which campaigns lead to scans, sign-ups and subscriptions, and it follows the same opt-outs.

  Your choices

  This is not a sale of your personal information. You can turn web ad measurement off on our Cookie Policy page, and a browser sending Global Privacy Control is opted out automatically. See Meta's Privacy Policy.

Legal requirements

We may disclose information if required by law or to protect the rights and safety of FendLand or others.

SMS and text messaging

If you opt in on our SMS preferences page at fendland.com/sms-opt-in, FendLand may send you text messages such as one-time verification codes, account-activation confirmations, security alerts (e.g., password-reset requests), and service updates about your own account (for example, a summary of suspicious property texts we flagged, or the status of a data-removal request). Opting in to SMS is voluntary and is never required to create or use a FendLand account.

We do not sell, rent, or share your mobile information, including your phone number and your SMS/text-messaging opt-in and consent, with any third parties or affiliates for marketing or promotional purposes. Text-messaging opt-in data and consent will not be shared with any third parties, except with the service provider that operates our messaging program (Twilio) solely to deliver the messages you requested.

Message frequency varies. Message and data rates may apply. Reply STOP to any message to unsubscribe at any time, or HELP for help. You can also reach us at fendland.com/support.

6. Data retention

• Scan records and evidence notes: retained while your account is active
• Removal request records and audit logs: retained while your account is active
• Your removal profile (name, address, phone, email and, if you added it, date of birth): retained while your account is active. You can clear your date of birth from the profile in the app at any time, and it is deleted with your account. A site we filed with keeps what it received under its own policy.
• Phone number carrier cache: 60 days
• Message reports sent from the Messages app (Section 9): 90 days
• Authentication sessions: managed by Supabase per their retention policy

When you delete your account, your personal data is deleted within 30 days, except where retention is required by law.

7. Security

We use industry-standard security practices including encrypted connections (HTTPS), secure session management, and role-based database access controls. Sensitive operations run on our servers with keys that are never exposed to your browser. No system can be completely secure, so we also recommend a strong password and two-factor authentication.

8. Your rights

You may:

• Access and export your scan history as a CSV file
• Delete your account and associated data by contacting support@fendland.com
• Request a copy of your data
• Revoke the removal authorization letter at any time in the app's Settings. FendLand will stop filing, following up and re-checking for you. Requests already sent stay with those sites, under their own policies. You can sign again in the Removal Center to resume.
• Opt out of Community Blocklist contributions by omitting sender phone numbers
• Turn off ad measurement on the website (do not sell or share); we also honor Global Privacy Control signals automatically

9. iOS SMS filter

FendLand's iOS app includes an SMS filter that moves property spam from unknown senders into your Spam folder. It runs entirely on your iPhone. This section explains how it works and what data is involved.

How the filter works

When you enable FendLand in Settings > Apps > Messages > Unknown & Spam, iOS hands FendLand each SMS or MMS message from a number that is not in your contacts. FendLand decides whether the message is unsolicited real estate solicitation (from wholesalers, investors, or scammers targeting property owners) or other spam, and if so iOS moves it to your Spam folder. Filtering is a Shield Pro feature. Without Shield Pro the filter allows every message through.

Everything happens on your phone

The filter reads and scores each message on your iPhone. It makes no network requests. The message text, the sender's phone number and the verdict are never sent to FendLand's servers or to any third party. We do not receive, see or store the messages the filter handles, and we do not know which messages it moved to Spam.

What the filter keeps on your phone

• Keywords you add for the filter to block.
• A list of senders whose messages looked suspicious, so a repeat sender is scored more strictly. Each sender is stored as a salted one-way hash, never as a phone number, for at most 30 days and at most 500 senders. The FendLand app can count the entries but cannot read the numbers behind them.
• Whether you have Shield Pro, and whether you have told the app you are selling a property and want offers let through.

What the app tells us about the filter

iOS gives apps no way to see whether a message filter is switched on, so the app reports three numbers: whether the filter has run on your phone at all, how many senders it flagged in the last 30 days, and how long ago the last one was. If you send yourself a test text and confirm it went to Spam, we also note on your account that your filter is on. None of this includes a message, a sender's number or an individual verdict.

Reporting a message (optional)

If you report a message from an unknown sender in the Messages app and choose FendLand, iOS sends us:

• The sender's phone number in hashed form. Because phone numbers are short, FendLand could recover the number from the hash, so we treat it as the number itself
• When the message arrived, and whether you marked it as junk or not junk
• The scores and verdict our filter gave that message

The report never contains the message text or anything that identifies you or your account. We use reports to find messages the filter got wrong, and we delete them after 90 days.

What the filter never touches

• Messages from numbers in your contacts (iOS does not pass these to the filter)
• iMessages (the filter only applies to SMS and MMS from unknown senders)

The message scanner is separate

The scanner in the app and on the website is a different feature. When you paste or type a message into it, that text is sent to our servers to be classified, as described in Sections 2 to 5. The scanner only ever sees a message you choose to give it.

Third parties

No third party receives the messages the filter handles, the senders' numbers or its verdicts. Mixpanel receives the three numbers described above. Sentry receives crash and error reports from the app. Neither receives message contents or sender numbers.

Your control

You can disable the SMS filter at any time in iOS Settings > Apps > Messages > Unknown & Spam. Once it is off, iOS stops passing messages to FendLand.

10. Children

FendLand is not directed at children under 18. We do not knowingly collect personal information from anyone under 18. If you believe we have collected such information by mistake, please contact us right away.

11. Changes to this policy

We may update this Privacy Policy from time to time. We will notify you of material changes by email or by posting a notice in the Service. The effective date at the top of this page reflects the most recent update.

12. Contact

FendLand and fendland.com are operated by 97Dev LLC.

Privacy questions or data requests: privacy@fendland.com

General support: support@fendland.com