Legal
Privacy Policy
What we collect, why we collect it, who we share it with, and the choices you have.
Last updated November 14, 2026
1. Introduction
This Privacy Policy explains how Afterblast LLC (“we,” “us,” or “our”), which operates FloodMaps, collects, uses, shares, and protects information when you use floodmaps.ai, our reports, and related services (the “Service”). It is part of our Terms of Service.
2. Information We Collect
Information you give us
- Addresses you search and the coordinates we look up for them.
- Report details you enter, such as year built, living area, stories, wall type, foundation, first-floor height, elevation certificate values, flood protections, and mortgage dates.
- Account and contact data: name, email, profile details (for example your brokerage, if you’re an agent), and messages you send us.
- Sign-in data: if you sign in with Google, Google shares your name, email address, and profile picture with us; we never receive your Google password. If you sign in with a code we email you, we keep a record that the code was sent and used. To give each person one free allowance, we also store a standardized form of your email address (for example a Gmail address without dots or a “+” tag) and check whether its domain is a temporary-inbox service.
- Questions you ask FloodMaps AI. We keep the question text, the report card it was asked from, and whether you marked the answer helpful, without your name, email, or IP address. When you mark an answer unhelpful, we keep that answer too, so we can fix it.
- FloodMaps Monitor choices: the homes you turn alerts on for, including the free map-change alert we add when you sign in at the free-report limit, the email you confirm, and when you confirm, stop, or turn alerts back on.
- Plan and billing data: your plan, its start, renewal, and end dates, and how much of it you’ve used. Payment details are collected and held by our payment processor, Stripe, under its own privacy policy. From Stripe we receive the purchase or subscription details, payment status, invoices, and the last digits and type of your card, never the full card number.
Information collected automatically
- Usage and device data: IP address, browser and device type, pages viewed, clicks, referring site, and dates and times.
- Homes and addresses you open: each property report you open, when, how you reached it (for example a search, a link, or a search engine), whether it counted toward a limit, and which plan covered it. We record this with your account when you’re signed in, and otherwise with a visitor identifier.
- Visitor identifier: a random ID stored in a first-party cookie for up to 400 days, with a copy in your browser’s local storage, so free limits work without an account. It isn’t used for advertising.
- How you found us: the first FloodMaps page you visited, the site that sent you, any campaign tags in that link, and your approximate city and region from your IP address, kept in a first-party cookie and saved with your account if you sign up.
- Network check: to stop people from resetting their visitor identifier to get more free reports, we keep a one-way, keyed code made from part of your IP address and your browser type for 7 days, then delete it. It can’t be turned back into your IP address.
- Cookies and similar technologies to keep you signed in, remember preferences, and measure use (Section 5).
- Session recordings: Microsoft Clarity records how pages are used (clicks, scrolling, and mouse movement) so we can find and fix problems. Clarity masks text you type into fields.
- Error reports: when something breaks, Sentry records technical details about the error and the page.
- Email delivery: our email provider, Resend, tells us whether each email we send was delivered, bounced, or marked as spam, and we record when you use a link in a FloodMaps Monitor email. We use this to send alerts, honor stop and unsubscribe requests, and stop mailing addresses that don’t work.
3. How We Use Information
- To find the property, gather its data and generate, store, and deliver your reports and PDFs.
- To run your account, process payments, purchases, and subscriptions, and prevent fraud and abuse.
- To apply free-report limits, the home limit on the Home Search Pass (our 90-day pass), and FloodMaps Pro’s monthly allowance, and to stop people from getting around them.
- To answer AI questions about your report, and to learn which questions people ask most so we can improve the answers and the reports.
- To send transactional emails you request or that relate to your account or purchases.
- To send the FloodMaps Monitor alerts you turned on, by checking each monitored home’s location against public warnings, flood maps, and disaster declarations.
- To provide support and respond to data-accuracy reports.
- To measure, secure, debug, and improve the Service and our methods.
- To comply with law and enforce our Terms.
4. How We Share Information
We do not sell personal information. We share information only as follows:
- Service providers that process data for us under contract: Vercel (hosting), Supabase (database and sign-in), Stripe (payments and subscription billing), Mapbox (maps and address search; it receives the addresses you search), Google (Google sign-in, if you use it; Gemini AI, which receives your report data, your AI questions, and, for a work email address, its domain and a summary of your account activity so we can tell whether a Pro offer fits; and Google Analytics and Tag Manager for site measurement), Microsoft Clarity (session recording and heatmaps), Sentry (error monitoring), Resend (email delivery), and Sanity (site content).
- Public data services: to build a report or check a monitored home, we send the property’s coordinates, not your identity, to public sources such as FEMA, USGS, NOAA, the Harris County Flood Control District, the Harris Central Appraisal District, and the City of Houston. See Our Data.
- When you share: if you share a report or link, whoever receives it can see its contents.
- Applications you connect: if you reach FloodMaps through a third-party application, platform, or digital assistant, we exchange what’s needed to fulfill your request with that provider. See Section 12.
- Legal and safety: to comply with law, legal process or government requests, or to protect the rights, property, or safety of Afterblast LLC, our users, or others. See “Requests from authorities” below.
- Business transfers: in a merger, acquisition, financing, or sale of assets, subject to this Policy.
Requests from authorities
We disclose personal information to a government or law-enforcement authority only in response to valid legal process, such as a subpoena, court order, or warrant, or in a genuine emergency involving risk of death or serious injury. We review each request for legal validity, push back on requests that are overbroad or unclear, and disclose only the minimum the request requires. Unless the law or a court order forbids it, we notify the affected user before disclosing so they can object.
5. Cookies, Analytics, and Your Choices
We use necessary cookies to keep you signed in, remember settings, and apply free-report limits (the visitor identifier in Section 2), and analytics cookies from Google Analytics and Microsoft Clarity to understand use. You can block or delete cookies in your browser (some features may stop working), install the Google Analytics opt-out add-on, and read how Microsoft handles Clarity data. We honor Global Privacy Control signals as a request to opt out of any sale or targeted-advertising use of personal data, neither of which we currently do.
6. How Long We Keep Information
- Account data and saved reports: while your account is open, and up to 3 years after it closes.
- Address searches, report data, and AI questions: up to 3 years, to provide the Service, prevent abuse, and improve accuracy.
- Records of homes and addresses opened: up to 3 years. The network check code is deleted after 7 days.
- FloodMaps Monitor records (monitored homes, alerts sent, delivery events, and link use): while the home is monitored, and up to 3 years after its alerts stop.
- Records of requests from connected applications (Section 12): 90 days, then deleted automatically.
- Payment and tax records: as long as tax and accounting law requires, generally 7 years.
- Session recordings and analytics: under the provider’s retention settings (for Clarity, generally about 30 days for recordings).
We may keep information longer when required by law or to resolve disputes.
7. Your Rights, Including in Texas
Depending on where you live, including under the Texas Data Privacy and Security Act, you may have the right to: confirm whether we process your personal data and access it; correct inaccuracies; delete it; get a portable copy; and opt out of the sale of personal data, targeted advertising, and profiling that produces legal or similarly significant effects (we do none of these). To make a request, use our contact form and choose “Legal & privacy request”. We’ll verify your identity and respond within 45 days, which may be extended once by 45 days when reasonably necessary. If we decline your request, you can appeal by replying to our decision; we’ll answer the appeal within 60 days, and if you’re unhappy with the result you may contact the Texas Attorney General. We won’t discriminate against you for exercising these rights.
8. Email
We send transactional emails about your account and purchases. If you turn on FloodMaps Monitor, we also send the alerts you chose. Every alert has one-tap links to stop alerts for that home or unsubscribe from all Monitor email, and mail apps that show an unsubscribe button use the same one-click request. We may send past buyers a one-time email saying Monitor is included with their purchase; it carries an unsubscribe link and our postal address. We also send a few marketing emails: a reminder and, sometimes, a discount when you start checkout or reach a free-report limit and don’t finish, and, if you look like a real estate or insurance professional, an offer to try FloodMaps Pro. Every marketing email includes our postal address and a one-tap unsubscribe link, mail apps that show an unsubscribe button use the same one-click request, and opting out won’t stop transactional emails or Monitor alerts.
9. Security
We use reasonable administrative, technical, and physical safeguards, including encryption in transit and at rest, role-based access controls, and multi-factor authentication for administrative access. No system is completely secure, and we can’t guarantee the security of information you send us.
To report a security vulnerability, email support@floodmaps.ai with “Security” in the subject. Our security.txt has the details. If a breach affects your personal information, we’ll notify you and any authorities as the law requires.
10. Children
The Service is not intended for anyone under 18, and we don’t knowingly collect personal information from children. If you believe a child has given us information, contact us and we’ll delete it.
11. Changes to This Policy
We may update this Policy. We’ll post the new version with a new “Last Updated” date, and for material changes we’ll also notify account holders by email or in the Service.
12. Third-Party Applications, Assistants, and Integrations
FloodMaps can be reached through third-party applications, platforms, digital assistants, and similar integrations that connect to our programmatic interfaces on your behalf. This section applies whenever you use FloodMaps that way.
What’s exchanged
When you make a request through a connected application, it sends us what’s needed to answer it, typically the property address or location you asked about, with an identifier that lets us apply usage limits and link any purchases to you. We return the flood risk information to that application, which presents it to you. We ask connected applications to send identifiers that don’t identify you personally on their own.
The provider’s own practices
What you give a connected application, and what we return to it, is also handled by that provider under its own privacy policy and terms, which we don’t control. Review the provider’s policies before connecting FloodMaps, and disconnect FloodMaps in that application at any time to stop the exchange.
Records we keep
We keep operational records of programmatic requests, including the endpoint called, the identifier supplied, timing, and outcome, to enforce usage limits, prevent abuse, bill correctly, diagnose faults, and meet legal obligations. We delete them after 90 days. We don’t use them for advertising or marketing profiles, and we don’t sell them. Purchases and the reports they unlock are kept as described in Section 6.
Connecting your FloodMaps account
Some applications let you sign in to FloodMaps so reports you’ve bought on floodmaps.ai are available there, and purchases you make there appear in your account. Before connecting, we show you which application is asking and what it will be able to do, and nothing is shared until you approve. The application receives your email address and access to your FloodMaps reports and purchases, not your password or payment details. You can disconnect it at any time in that application, or ask us to revoke its access through our contact form.
Deleting data from connected applications
To delete what we hold about your use of FloodMaps through a connected application, use the contact form and tell us which application you used. We’ll delete the request records and the identifier linked to you, subject to the payment-record retention in Section 6.
Purchases through a connected application
If you buy a report through a connected application, our payment processor collects your payment details and email address directly. We use that email to create or find your FloodMaps account so your purchase stays available to you, and we may send you transactional messages about it.
13. Contact Us
Afterblast LLC, through our contact form.