Privacy Policy

Last updated: October 26, 2026

Entity: REMA Tech LLC Address: Texas, United States

This Privacy Policy describes how REMA Tech LLC ("we," "us," or "our") collects, uses, and protects information when you use realestatemaps.app and related services (the "Service"). The Service is a commercial real estate mapping tool offered only to individuals located in the United States and to companies established in the United States (see our Terms of Service, Section 2). We do not verify these statements. We handle information under this policy and U.S. law, and we do not accept obligations under non-U.S. privacy laws because someone used the Service from outside the United States.

This policy covers two kinds of information: information about you, our user (Sections 1 to 3), and public-record property data that the Service displays, which can include the names and mailing addresses of property owners (Section 4).

1. Information We Collect About Our Users

Account Information (Clerk)

When you register or sign in, Clerk processes authentication on our behalf. We receive and store account-related information such as your name, email address, and profile photo (if you provide one through your identity provider or Clerk profile). If you belong to a team, we store your team membership and role.

Billing Information (Stripe)

If you subscribe to a paid plan, payment processing is handled by Stripe. Stripe collects and stores your payment method details (e.g., card information). We receive limited billing metadata such as subscription status, plan type, and transaction identifiers. We do not store full payment card numbers on our servers.

To apply our one-refund-per-customer rule (Terms of Service, Section 5), when a charge is refunded (by us, or by Stripe or Link) we keep a refund record. It stores the card's fingerprint (a stable identifier Stripe assigns to that card; we do not store the card number), a hash of the billing email address (we do not store the address itself, but someone who already knows an address can match it to the hash), the organization on the account, and your user ID, the Stripe customer and charge IDs, and the amount refunded. This record is personal data. We use it only to recognize a later refund request from the same customer.

Usage and Technical Data

We collect information about how you use the Service, including map interactions, features enabled, viewport positions, layer preferences, searches, and saved map configurations. We and our providers also receive technical information such as IP address, browser and device type, and server log and diagnostic data. We use this to deliver the Service, persist your workspace, enforce usage limits, and prevent abuse.

Maps, Annotations, and Files You Create or Upload

Content you create in the Service, such as saved maps, folders, POI callouts, measurements, annotations, and exports, is stored server-side and associated with your account. Files you upload, such as custom logos and images you submit to AI Enhance, are stored in our file storage. You retain ownership of your content; we process it to provide and back up the Service.

Device and Error Information (Sentry)

We use Sentry for error monitoring. Sentry may receive device and browser information, stack traces, and diagnostic context when errors occur.

2. How We Use Information About Our Users

We use collected information to:

• Provide, authenticate, and secure access to the Service
• Process subscriptions and billing through Stripe
• Save your maps, annotations, uploads, and workspace preferences
• Provide AI-assisted features you choose to use (see Section 5)
• Monitor performance, diagnose errors, and prevent abuse
• Communicate with you about your account, security, or material policy changes
• Comply with legal obligations and enforce our Terms of Service

We may also disclose information to courts, government authorities, or others when the law requires it, or when reasonably necessary to investigate abuse, protect safety, or defend legal rights.

3. We Do Not Sell Our Users' Personal Information

We do not sell or share our users' personal information for money or for cross-context behavioral advertising, and we do not use advertising cookies.

4. Public-Record Property Data

The core of the Service is parcel and property data compiled from public sources, mainly county and state government records (such as appraisal district and assessor rolls) and open geographic datasets. This data is about properties, but it can include information about people, such as:

• the names of property owners
• the mailing addresses of property owners
• property values, sale or deed information, legal descriptions, and parcel boundaries

How the Service uses it: we provide paid access to these records on maps and parcel detail panels, and the Service groups parcels that share an owner name or an owner mailing address (for example, an owner's portfolio of properties). These matches are made automatically and can be wrong; they do not establish that parcels have the same owner. This data comes from government and public sources; we did not collect it from the property owners directly.

Accuracy: public records can be incomplete, outdated, or wrong. We show them largely as published and do not guarantee them. We do not control the government record.

Questions, corrections, and suppression requests: email support@realestatemaps.app with the property's address or parcel number. We will correct an error we introduced. We will suppress or limit a record in the Service when we decide to, or when a law that applies to us requires it after a proper notice (for example, a state address-confidentiality law such as New Jersey's Daniel's Law). Corrections to the underlying government record must be requested from the agency that publishes it.

5. AI Features

AI Enhance: images you submit for enhancement are processed on servers we operate and stored with your uploads. They are not sent to an outside AI provider.

AI output can be wrong or incomplete; review it before relying on it.

6. Service Providers

We use the providers below to operate the Service:

• Clerk: authentication and user accounts (clerk.com/privacy)
• Stripe: subscription billing and payments (stripe.com/privacy)
• Google Maps Platform: maps, geocoding, and place search (policies.google.com/privacy)
• Mapbox: map rendering in the map designer and exhibit tools, and drive-time areas (mapbox.com/legal/privacy)
• Vercel: application hosting (vercel.com/legal/privacy-policy)
• Neon: database hosting (neon.tech/privacy-policy)
• Cloudflare: file and map-tile storage (cloudflare.com/privacypolicy)
• Sentry: error tracking and diagnostics (sentry.io/privacy)
• Upstash: rate limiting
• Resend: transactional email, such as team invitations, when we send it (resend.com/legal/privacy-policy)

Some of these providers also process information for their own purposes under their own privacy policies. We store your information primarily in the United States; some providers may process it in other countries where they operate.

7. Data Retention

We keep account information, saved maps, annotations, and uploads while your account is open. After your account is closed, or after we verify a deletion request, we delete or anonymize that personal information within a reasonable time, and by any deadline a U.S. law that applies to us sets. We may keep records we need for taxes, billing, fraud prevention, security, or legal claims, and copies can remain in backups until they expire in the normal cycle. Refund records (Section 1) have no fixed end date: we keep them after an account is closed and after a deletion request, for as long as we apply the one-refund rule, so the same card, billing email, or organization cannot receive a second refund. If a U.S. law that applies to us requires deleting part of a refund record, that law controls. If you are on a team, content the team owns stays with the team.

8. Your Rights

You may ask us to access, correct, delete, or give you a copy of your account information by emailing support@realestatemaps.app. Refund records are kept as described in Section 7. We will verify the request and respond within the time required by any U.S. law that applies to us. Residents of states whose privacy laws apply to us have the additional rights those laws give (California residents: see Section 15). Questions about public-record property data are handled under Section 4.

9. Cookies and Local Storage

• Session cookies: Clerk and our authentication flow use session cookies to keep you signed in securely.
• Local storage: the Service may store map state, UI preferences, and viewport settings in your browser's local storage for persistence across sessions on your device.
• No tracking: we do not track you across other websites, and we do not use advertising or profiling cookies. Because there is no cross-site tracking to switch off, a browser "Do Not Track" signal does not change anything in the Service.

We use only essential cookies (to keep you signed in) and, if we add them, performance cookies that measure how the Service itself works. You can control cookies through your browser settings; disabling cookies may limit sign-in and certain features.

10. Security

We implement administrative, technical, and organizational measures appropriate to the nature of the data we process, including encryption in transit and access controls. No method of transmission or storage is completely secure; we cannot guarantee absolute security.

11. Data Breach Notification

If a security incident involves personal information we hold about you, we will notify you and any authorities as required by applicable U.S. law, within the time that law requires.

12. Children

The Service is not directed to individuals under 18. We do not knowingly collect personal information from children. Contact support@realestatemaps.app if you believe we have collected such information.

13. Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we will notify you (for example, by email or an in-product notice) before they take effect, and we will update the "Last updated" date above.

14. Contact

Privacy questions or requests:

support@realestatemaps.app REMA Tech LLC Texas, United States

California residents: see Section 15 for your privacy rights.

15. California Residents

We do not sell the personal information we collect from our users, and we do not share it for cross-context behavioral advertising. California residents who use the Service may make the requests described in Section 8, which are answered on the schedule Section 8 states. Information lawfully made available from federal, state, or local government records is not "personal information" under the CCPA, but that exclusion may not cover information we derive from those records (such as owner portfolios); questions and requests about property data are handled under Section 4.