Privacy

Who Gets the Call? is a public marketplace. Public pages do not use an account cookie. This page describes the analytics and first-party records the product can create. It is not a legal-compliance certification.

Analytics

When production tracking is explicitly enabled, the site loads DataFast’s cookieless script. It records public page views and a small set of sanitized click goals. It does not receive emails, names, payment data, or customer identifiers. The product does not call DataFast identify.

The site is hosted on Vercel. Vercel’s own hosting and web-analytics signals may apply to production traffic.

Outbound visits

A first-party outbound visit is recorded only when a visitor follows an approved sponsor or provider website redirect. The product counts at most one qualified visit per visitor, destination, and UTC hour. The stored event keeps a deterministic identifier, the public target id, a kind, and a timestamp. Daily totals are aggregated from newly inserted events.

Raw IP addresses and user-agent strings are not stored in outbound activity rows. Event rows older than seven days are deleted by an operator cleanup job.

Directory applications

The public “List your company” form collects a company name, HTTPS website, a private contact name and work email, the lanes and countries or cities you say you serve, and a short capability description. We review the company website and may contact you if anything is unclear. That information is used only to review whether the company should appear in the public provider directory. Submissions stay pending until a private administrator on the operator allowlist approves or rejects them. Approval creates public provider and coverage records. Rejection creates no public records.

Access is limited to the operator’s private admin tools. Application rows are retained while they are needed for review, audit, or to prevent duplicate pending submissions, then can be removed by the operator. Raw IP addresses and user-agent strings are not stored with the application. Analytics events for this form, when enabled, send only a lane, country, and surface — never a company name, website, contact name, or email.

Guest territory checkout

When checkout is enabled, the public claim form collects a website, bid amount, and required acceptance of the exact sponsorship terms and advertising disclosure published at /sponsorship-terms. Email and billing details are collected by Stripe Checkout. After payment is verified, the server may fetch a logo from that HTTPS site and store it as a same-origin image. Initials are the public fallback if no logo is found. The form does not accept file uploads. That information is used to create the paid claim. After payment is verified, the sponsored placement can appear on the map. No public account is created.

Access is limited to private administrators on the operator allowlist. After payment is verified, the sponsored placement can appear on the public map. Customers do not get a self-serve refund option. Administrators may refund a payment manually in individual cases. Contact email is passed to Stripe Checkout as the customer email and stored for confirmation and support, not for public display, and is not written into payment event payloads. Acceptance versions and the acceptance timestamp are stored with the purchase together with a digest of the accepted text. Raw IP addresses and user-agent strings are not stored with the purchase. Rate-limit buckets use a keyed hash. Stripe identifiers are not shown in the browser. Production checkout stays closed while legal versions are unapproved, tax mode is unset, or live payment gates are incomplete. Transactional email is sent only when production email delivery is explicitly configured.

Contact

Questions: hello@solvoops.com.