Black Label Real Estate

Policy

Privacy, in plain language.

This policy maps what stays on your device, what reaches our hosted services, what comes from public records, and how to request access, deletion or record suppression.

Effective and last updated: October 8, 2026

1. Scope

This policy applies to blbestate.com, the Black Label Real Estate desktop software, account and newsletter features, the hosted property-data service at api.blbestate.com, and support interactions. In this policy, “we,” “us” and “Black Label Real Estate” refer to the operator of those services.

County, recorder, assessor, GIS and court websites linked from the product are run by other organizations. Their policies govern their sites. The checkout and fulfillment path may move to Black Label Bots and Stripe; their notices govern the information they collect directly.

2. Data we handle

Account and subscription

Email address, optional name, account creation and last-login timestamps, sign-in method, marketing choice, plan and entitlement identifiers. An optional passcode is stored only as a salted PBKDF2 verifier, not as readable text.

Newsletter

Email address, signup source, consent and confirmation timestamps, suppression status and a shortened hash of the signup IP address. Subscription requires email confirmation.

Site and support

Pages viewed, button interactions, referrer and device/browser context, browser analytics identifiers from PostHog and Cloudflare Web Analytics, support questions, and contact messages you choose to send.

Service requests

IP/network metadata, request time, route, rate-limit counters, authentication tokens, and search parameters such as an owner name, address, parcel, county, state or map bounds that you submit.

Billing

Stripe processes payment details. We may receive customer, subscription, payment-status and receipt identifiers needed to deliver access and open the billing portal. We do not receive a full card number.

Public-record corpus

Source and harvest details plus parcel IDs, owner names, situs and mailing addresses, property coordinates, county/state, assessed values, land and improvement values, sale dates and prices.

3. Local and hosted data

The desktop workspace is local-first, not universally local-only. Leads, notes, buyers, settings and imported material can remain on your device. Parcel searches still contact the hosted public-record API.

If you use authenticated workspace sync, the app sends the named workspace blobs you choose to sync to our hosted Postgres service and associates them with your subscriber token. The current API accepts those blobs as Base64-encoded content. Base64 is an encoding format, not encryption by itself. You can delete a synced blob through the authenticated workspace endpoint, and you can request account deletion.

Features that call a provider using a key you supply may send the selected query or record to that provider. The provider's terms and privacy notice apply. Do not place data in a workspace or support message unless you are authorized to process it.

Private SalesSwipe web workspace

The browser workspace stores imported owner records, recorded contact details, property photos, client profiles, deal terms, and saved analysis in your account on Cloudflare Durable Objects, KV, and R2. Browser session storage also holds a temporary cache. Account authentication controls access to your private workspace and uploaded photos.

Creating Bot access grants the scoped workspace operations shown during setup to whoever holds the token. You can revoke or replace that access. Configuring an external assistant also makes the data it retrieves subject to that provider's handling.

Preparing legal documents sends the selected seller, property, client, and deal terms to the Black Label Sign service. Starting signing sends the reviewed invitations to the selected signers and records signing status and the resulting documents.

Archiving an imported property does not delete its uploaded photos or existing deal records. Those are retained to preserve the saved deal and document history. Contact us through the removal channel below for workspace-data deletion requests; retention for executed agreements, disputes, and backups may still apply.

4. API and public-record data

The hosted corpus is limited to sourced government-record fields; it does not append owner phone numbers, owner email addresses or a stored skip-trace bundle. But public-record status does not make a name, home address or coordinate non-personal. We treat those fields as public-record personal information and operate a removal channel.

The public API can return sourced owner and address fields without field-level masking. The homepage demo uses labeled illustrative images and sample numbers. Its owner and client walkthroughs use fictional examples. Authenticated property cards use your recorded property and owner information. Data may be inaccurate, outdated or incomplete because source records can be inaccurate, outdated or incomplete.

We use source URLs, harvest dates, suppression flags and provenance hashes to maintain and audit the corpus. We do not use this data to make credit, employment, tenant, insurance or government-benefit eligibility decisions, and the service is not a consumer reporting agency.

5. How we use data

  • Provide accounts, sign-in, product access, search, maps, optional sync, support and billing management.
  • Deliver confirmed newsletters and transactional email, honor unsubscribes, and prevent repeat sends to suppressed addresses.
  • Secure the services, rate-limit abuse, diagnose errors, measure page and purchase-intent performance, and maintain audit records.
  • Source, normalize, update, suppress and show county public records with provenance.
  • Comply with valid legal requests, protect users and enforce the Terms.

We do not sell account, billing, contact, workspace or support data, and we do not share those categories for cross-context behavioral advertising. The product does provide access to a sourced public-record corpus; that fact is distinct from selling a buyer's account or private contact information.

6. Providers and disclosures

Provider or recipientWhat it doesData involved
CloudflareDNS, CDN, security, Web Analytics, Workers, Durable Objects, KV, R2, email delivery, hosted AI and database connectivity.Network/request and page-performance data, account and subscriber records, private property records and photos, client and deal records, email routing, support questions and service configuration.
Black Label Sign and selected signersClient-specific legal packets and ordered signing.Seller and buyer details, property and agreement terms, invitations, status, and signed documents.
Managed Postgres / HyperdriveProperty corpus, subscriber entitlements, suppression and removal intake, and optional workspace sync.Public-record data, tokens, request records and synced workspace blobs.
PostHogFirst-party-routed product analytics with autocapture and session recording disabled.Page views, selected button events, browser/session identifier, referrer/device and network metadata.
Stripe and Black Label BotsCheckout, recurring billing, receipts, fulfillment and customer portal.Purchase and subscription information; Stripe receives payment details directly.
Government sourcesSource records and provenance.Parcel, ownership, address, value, sale, court/probate and geographic fields those sources publish.

We may also disclose information when reasonably necessary to comply with law, respond to valid process, protect people or the service, investigate misuse, or complete a business reorganization subject to appropriate protections.

7. Retention

We keep account and entitlement records while an account or subscription is active and for a reasonable period afterward for security, tax, dispute and fulfillment needs. One-time sign-in codes and rate-limit counters expire automatically. The session cookie expires after 30 days unless cleared earlier.

Confirmed newsletter records remain until unsubscribe; suppression records remain so we can honor the opt-out. Public-record rows remain until refreshed, archived, removed at the source, or suppressed through our process. Synced workspace blobs remain until deleted by the authenticated user or removed with the associated service account, subject to backup and integrity cycles. Provider logs follow the provider's operational schedule.

8. Your choices, rights and public-record removal

  • Account: sign in to update or delete the account record. Delete the Stripe subscription from Billing before deleting the account if you want future charges to stop.
  • Email: every Estate Brief has a signed one-click unsubscribe link. An unsubscribe does not cancel a paid product subscription.
  • Analytics: browser storage controls can clear the analytics identifier. Browser privacy tools may block analytics requests.
  • Privacy request: request access, correction or deletion of account-related information by using the privacy contact.
  • Public-record suppression: any person may use the non-login-gated record-removal channel. Subscribers do not receive special priority.

A removal request should identify the record precisely enough to find it: name or parcel/address, county and state, and the relevant source or result URL if available. We may ask for proportionate verification to prevent a request from removing someone else's record. Honored suppression affects future delivery from our service; it cannot recall copies already obtained by others or change the government source.

9. Security, sensitive data and children

We use HTTPS, HSTS, restrictive browser security headers, signed HttpOnly session cookies, salted passcode verifiers, access controls, rate limits and suppression filters. No system is risk-free, so use a strong unique passcode and protect subscriber and provider keys.

The service is business software for adults. It is not directed to children under 13. It is not a healthcare service, is not designed to receive protected health information, and is not offered as a HIPAA business-associate service. Do not upload medical records, Social Security numbers, financial-account credentials, authentication secrets or other unnecessary sensitive data to support or workspace sync.

10. Contact and changes

Privacy questions and requests: michael@blbestate.com or the instructions on our contact page.

Postal address: Black Label Real Estate, 20050 Oak Tree Road E, Apt 8004, Gulf Shores, AL 36542, United States.

We may update this policy as the service or law changes. Material changes will be identified by a revised date and, when appropriate, an account or email notice.

Public-page analytics

We use PostHog to measure visits to public marketing pages. A random identifier is stored in this browser (local storage and a first-party cookie) so repeat visits link to one anonymous PostHog visitor profile. On public pages PostHog records page views, clicks and other page interactions, session replays of page layout, scrolling and clicks with every form field masked, heatmaps, clicks that had no effect, browser errors and console messages, and page-load timing. Page addresses are sent without query strings. Envelopes, signing pages, documents, studios, account, sign-in and checkout pages load none of this. PostHog receives the network request and keeps an anonymous visitor profile for that identifier; IP-based geolocation is disabled; PostHog shows no surveys here. Global Privacy Control, Do Not Track, and the browser opt-out disable public-page measurement.