1. Scope and who we are
Foreclosure Auction Data is a private Florida foreclosure and tax deed auction research platform. It organizes and analyzes auction records, parcel and property information, sales history, geographic information system data, valuation inputs, and related public-record or lawfully accessible information for research and due diligence. FAD is not a court, clerk of court, tax collector, property appraiser, county government, auctioneer, title company, law firm, lender, real estate brokerage, consumer reporting agency, Google, YouTube, Meta, or another government agency or platform operator.
2. Public-record information is different from user information
A property, owner, party, bidder, purchaser, case, judgment, auction, or sale may appear in FAD because the information was present in a public record, government system, auction system, property-appraiser dataset, tax record, GIS dataset, sales-history dataset, court-related source, licensed source, or another lawfully accessible source. Appearance in FAD does not mean the person created a FAD account, supplied information to FAD, or has a customer relationship with FAD.
Public-record research information is maintained separately from FAD customer-account information. A public property page is a research record about the parcel and associated auction history, not a personal account belonging to the property owner.
3. Information we collect
Information voluntarily provided to FAD may include a user's name, email address, account credentials, profile settings, support messages, saved-property preferences, simulated bids, mailing-template inputs, billing selections, privacy choices, and other information entered into requested features. Service records may include authentication and security events, account status, subscription and billing records, credit balances, research unlocks, export history, followed properties, feature usage, IP address, browser or device characteristics, timestamps, requested pages, response status, and security or performance information.
Payment-card details are generally processed by our payment processor rather than stored directly by FAD. We may retain payment-related identifiers, transaction status, amount, plan, invoice, refund, chargeback, and related records required for account service, accounting, fraud prevention, and disputes.
Depending on source availability, the property research database may include parcel identifiers, addresses, owner or party names, case identifiers, auction dates and statuses, judgments, plaintiff maximum bids where available, tax-deed opening bids, sale results, property characteristics, values, sales transactions, parcel geometry, comparable-sale inputs, estimated market values, estimated equity, and references to source systems.
4. How we use information
We use information to provide, operate, maintain, and secure FAD; authenticate users; process subscriptions and credits; deliver research and exports; power maps, calendars, property pages, search, saved properties and other requested features; provide support; send transactional communications; prevent fraud and abuse; diagnose technical problems; maintain data quality; measure product performance; generate aggregate statistics; administer authorized social publishing; enforce agreements; and comply with applicable legal obligations.
5. Cookies, browser storage, analytics, and advertising measurement
FAD uses essential cookies or browser storage for authentication, security, preferences, privacy choices, and application state. Optional analytics or marketing technologies are subject to the site's privacy choices where applicable. FAD's implementation is designed not to send account email addresses, owner names, property street addresses, raw property-search text, case numbers, parcel identifiers, or state parcel identifiers as third-party advertising or analytics event parameters.
6. Service providers and disclosures
We may disclose information to vendors and service providers that perform hosting, infrastructure, database, payment processing, email delivery, mapping, analytics, advertising measurement, security, customer support, or professional services on our behalf. We may also disclose information when required by law or legal process; to investigate fraud, abuse, or security threats; to protect rights, property, or safety; or in connection with a corporate transaction.
7. Sale, sharing, and targeted advertising
FAD does not sell personal information for money. Depending on applicable law, some optional advertising or measurement technology may constitute "sharing" or targeted advertising. Where those technologies are enabled, applicable privacy controls are provided. Public-record owner information from the property research database is not used to automatically create advertising profiles about the named property owner.
8. Meta and social integrations
When an authorized FAD administrator connects supported Meta business assets, FAD may securely store the resulting business-asset credential and use it to publish authorized content and process configured Instagram or Facebook interactions. Connected-platform information is used for the authorized integration and remains subject to the applicable platform's own terms and privacy practices. FAD provides connected-platform deletion information at /data-deletion.
9. Google and YouTube API data
FAD may use Google APIs, including the YouTube Data API, when an authorized FAD administrator explicitly connects a Google account or YouTube channel for automated publishing. The current YouTube integration requests the youtube.upload OAuth scope so FAD can upload FAD-generated videos to the YouTube channel authorized by that administrator. FAD does not use this integration to access Gmail, Google Drive, Google Photos, contacts, or unrelated Google account content.
Google data we may receive. The integration may receive OAuth authorization credentials, short-lived access tokens, a refresh token used to obtain replacement access tokens, and API responses necessary to perform or confirm the authorized upload, such as uploaded video identifiers, processing status, or error information. FAD does not request the user's Google password.
How Google data is used. Google authorization data is used only to authenticate the authorized integration and carry out the administrator's requested YouTube publishing functions, including uploading FAD-generated Shorts and longer FAD videos, setting upload metadata, and checking the result of those uploads. Google user data is not used for unrelated advertising, behavioral profiling, credit decisions, or sale to third parties.
Storage and protection. OAuth credentials used for unattended publishing are stored server-side in restricted application configuration or an equivalently protected credential store and are not intentionally exposed to ordinary site visitors or placed in public page source. Access tokens are short-lived. A refresh token may be retained while the integration remains authorized so FAD can continue the requested automated publishing without repeated sign-in.
Sharing. FAD does not sell Google user data. Google authorization data is shared only with Google APIs as required to perform the authorized function, with infrastructure or service providers to the limited extent necessary to operate and secure FAD, or when disclosure is legally required. We do not permit service providers to use Google user data for their own independent advertising or profiling.
Retention, deletion, and revocation. OAuth credentials are retained only while reasonably necessary to operate the authorized integration, maintain security and auditability, or comply with law. An administrator can disable the FAD integration and can revoke Google's authorization at any time through Google Account third-party access settings. After revocation or disconnection, FAD will cease using the revoked credential. Non-secret operational records, such as a YouTube video ID, upload timestamp, status, or error log, may be retained for audit, troubleshooting, and publishing-history purposes.
Google API Limited Use. FAD's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
10. Data retention
We retain information for periods reasonably necessary for account operation, purchased research and export history, accounting, tax and billing records, fraud prevention, chargeback handling, security, dispute resolution, legal compliance, auditability, and maintenance of historical research. Different categories may have different retention periods. Historical public-record and auction information may be retained as part of the research database even after an auction changes because historical outcomes and observations are part of the service.
11. Security
We use administrative, technical, and organizational safeguards appropriate to the information we process, including access controls, authentication protections, restricted administrative access, logging, monitoring, and protected credentials for supported integrations. No website, transmission method, database, or storage system can be guaranteed completely secure.
12. Privacy rights and requests
Depending on applicable law, users may have rights to request access to, correction of, deletion of, or portability of certain personal information associated with their FAD account, or to opt out of certain processing. Requests may be sent to [email protected]. We may need to verify a request and may retain information where permitted or required for accounting, legal, security, fraud-prevention, public-record integrity, or dispute-resolution purposes.
13. Public-record corrections and disputes
If you believe a FAD property or auction page contains a factual error, contact [email protected] and identify the FAD URL, the field believed to be incorrect, the reason for the correction, and, when available, an authoritative source. Some inaccuracies must first be corrected by the originating court, clerk, tax collector, property appraiser, county, or other source. FAD cannot alter the official record maintained by another agency.
14. Account and connected-platform deletion
Instructions for closing a FAD account and requesting deletion of supported connected-platform data are provided on our Data Deletion page. Account deletion does not delete records maintained by independent public agencies and does not automatically remove historical public-record research where FAD has a lawful basis to retain it.
15. Children
The service is not directed to children under 13. FAD's paid real-estate research and business features are intended for users capable of entering into the applicable service relationship. We do not knowingly create accounts for children under 13.
16. Changes to this Privacy Policy
We may update this policy as the service, vendors, integrations, laws, or data practices change. The current version and effective date will be posted on this page. Material changes may also be communicated through the service or another appropriate method when required.
17. Contact
Privacy questions, Google or YouTube integration questions, account-data requests, and public-record correction requests may be sent to [email protected]. Please include enough information to identify the relevant account, integration, property page, or issue without sending unnecessary sensitive information.