Privacy policy.

Dealer24 is a subscription product that provides anonymized wholesale watch market intelligence — median, min, and max asking prices, price history, and watchlist alerts — sourced from a network of professional wholesale dealers who've granted us approval to ingest and structure their listings into market data.

Subscribers don't see individual dealer identities or source community names. On eligible listings, members buy directly from Dealer24; Dealer24 separately procures from the source dealer.

From subscribers (people who sign up for an account):

• Account identity — email address and password hash (managed via Better Auth).
• Billing information — handled by Stripe; we receive a customer ID and subscription status, not card numbers.
• Usage analytics — for the public signup funnel, an anonymous browser-session ID, fixed event name, page path, referrer hostname, and optional UTM source, medium, and campaign. We do not store an IP address, email, name, phone number, full referrer URL, or device fingerprint in this event stream. Raw funnel events are retained for 90 days. Authenticated product activity such as references searched and watchlists created may also be used to improve the product and detect abuse. We do not sell this data.
• Server-side logs — IP address, user agent, request path. Retained 30 days for security and abuse prevention.
• Order and fulfillment information — order status, amount, payment-provider identifiers, encrypted shipping name and address, tracking, authentication and return records, and an append-only operational event history. Card numbers remain with Stripe.

From the underlying source data (which subscribers never see in unanonymized form):

• Listing content (text + images) from a network of professional dealers who've granted ingestion approval through their group admins.
• One manually reviewed, anonymized dealer offer may be displayed on the public landing page as a product sample. The sample omits seller and source-community identity, uses the same PII redaction as subscriber responses, and is removed automatically if the underlying dealer opts out.
• Sender phone numbers, immediately hashed with SHA-256 (E.164 form) for cross-source deduplication and stored separately as AES-256-GCM ciphertext, accessible only to operators for compliance and opt-out lookups.
• Sender display names, retained internally for operator review and opt-out matching but never exposed to subscribers.

Subscribers see anonymized market data and their own account activity:

• Aggregated statistics — median, min, max, percentile, supply count — across active asking prices.
• Price history and individual observations shown as Dealer24 retail prices. Source dealer and community identities are not included in subscriber-visible surfaces.
• Their own account: email, billing status, watchlists, alert history, purchases, shipment status, and eligible returns.

Dealer24 does not return source phone numbers, real names, source community names, or dealer asking prices in the product or API. Buyers and source dealers do not exchange contact information.

Listing content is routed and parsed through OpenAI's API to extract structured Rolex data (model, reference number, price, condition, and related attributes). Selected images are analyzed only when they can resolve missing or conflicting details. The resulting records are deduplicated, indexed, and made searchable.

Phone hashes are used to identify when the same dealer posts the same watch across multiple source channels (so cross-posts collapse into a single listing) and to honor opt-out requests by mapping a submitted number back to its dealer record.

Encrypted plaintext phone numbers are never displayed in the product UI or returned by the API. Source dealer numbers support opt-out and compliance requests and, where enabled, delivery of Dealer24 procurement requests. Buyer fulfillment information is used only for payment, tax, fraud review, delivery, authentication, support, returns, and legal recordkeeping.

We do not sell your data. We do not share content, phone numbers, or hashes with third parties except as required for operating the product:

• OpenAI — listing text and, when needed, selected images are sent to the Responses API for routing and structured extraction under OpenAI's business data controls.
• Cloudflare R2 — listing image attachments, encrypted at rest.
• Neon — managed Postgres for structured data.
• Resend — outbound transactional and alert emails.
• WhatsApp delivery provider — private Dealer24 procurement requests to source dealers.
• Stripe — subscription billing, watch-payment authorization and capture, tax calculation, refunds, and fraud controls.
• Sentry — error reports, scrubbed of message content.

We will share information with law enforcement only in response to a valid legal order, and we will notify the affected party if legally permitted to do so.

• Source listings, parsed data, and aggregated price observations are retained indefinitely as long as we operate the product — historical price data is the core utility of the service.
• Encrypted phone numbers are retained until the dealer opts out.
• Subscriber account data, WhatsApp verification state, and contact request history are retained until account deletion. On cancellation, account data is retained 60 days for billing reconciliation, then purged.
• Server logs are retained 30 days.
• If we shut the product down, all individually-attributable data is deleted within 30 days of the shutdown notice.

As a subscriber: You can export your account data (watchlists, alert history, settings) by emailing support@dealer24.ai. You can request account deletion at any time by emailing support@dealer24.ai.

As a dealer in the source data: Submit your phone number via the opt-out form. We anonymize the dealer record within 48 hours, stop ingesting future messages from that number, and retain aggregated price history without any attribution to you. For full deletion of aggregated rows, email support@dealer24.ai with proof of phone number control and we'll evaluate the request individually.

We ingest only from source communities whose admin(s) have granted us written approval. Approval records are retained internally for compliance review. We do not scrape consumer marketplaces, public forums, or any source we don't have explicit permission to access.

Plaintext phone numbers are encrypted at rest with AES-256-GCM using a key held only on production servers. Hashes use SHA-256 with no salt (consistent hash for the same phone, required for deduplication). All traffic over HTTPS with HSTS. Database connections over TLS. No credentials in source repositories.

Public API responses are passed through a response-scrubbing middleware that fails closed if any denylisted identity field (phone, hash, real name, source channel ID, etc.) appears in the response payload. This is a structural defense against accidental leakage as the codebase evolves.

We may update this policy from time to time. Material changes are communicated to all subscribers via email at least 14 days before they take effect. The “Last updated” date at the top reflects the most recent revision.

Questions or requests: support@dealer24.ai.