Help and policyLoading public guidance
Preparing quick answers, policy topics, public data links, and contact paths.
Preparing quick answers, policy topics, public data links, and contact paths.
How USBorderWait.com handles traveler alerts, forms, advertising, wait cards, analytics, payments, push notices, and account data.
Choose the topic that matches your question. Each topic explains scope and shows the next action when one is available.
This policy covers USBorderWait.com, TiemposDeGarita.com, Border Times wait cards, data pages, alerts, newsletters, advertiser forms, private business areas, and support contacts.
We collect information you choose to submit, such as email address, phone number, alert threshold, newsletter signup, contact message, business profile, advertiser copy, billing selection, and support details.
Waits, lanes, weather, traffic, history, maps, and local guidance are public traveler information. They are not private user records and may appear in search, be summarized, shown elsewhere, or shared with attribution.
Latest waits, history, nearby crossings, wait cards, daily reports, and public page lists are public traveler data. Reuse should preserve provider credit, update time, delay notes, license, and original page attribution.
Use the data guide or contact us for reuse questions. Dunvale handles wait data and licensing. Private pages, dashboards, accounts, billing records, and support records are not public data pages.
We may process IP address, browser, device, page URL, referrer, timestamps, cookie or session values, public session identifiers, event type, and rough location signals needed for region selection, security, analytics, and abuse prevention.
When enabled, we sample Web Vitals and measure a short search-to-crossing-to-alert or app-install funnel. This separate lane uses a random tab-only session value that is hashed on the server. It stores public page paths without queries, coarse device and connection classes, and bounded event context; it does not store raw IP, user agent, referrer, search text, alert recipient, cookie identifier, or a persistent browser ID. Global Privacy Control and Do Not Track disable this collection, and raw events expire after 35 days by default.
Alert recipients and push subscription keys are used for requested notices, verification, delivery, frequency limits, unsubscribe, STOP handling, troubleshooting, and abuse prevention. Web push requires browser permission and can be disabled in the browser.
Sponsored placements may record impressions, clicks, calls, WhatsApp clicks, coupon views, page context, package selection, and aggregated performance reports. Sponsor reporting should use aggregate or business-relevant metrics, not raw personal contact lists.
Payments and subscriptions are handled by payment providers such as Stripe. We store business, package, subscription, invoice, customer, and billing event identifiers needed to operate billing, but we do not store full card numbers.
We use cookies or similar storage for sessions, language, preferences, analytics, forms, rate limits, security, push notification state, and private account access.
Cookie policyWe may share data with vendors that help run hosting, tunnels, databases, email, SMS, WhatsApp, push notifications, payment processing, fraud prevention, analytics, logging, support, and security. They should use data only for assigned service work.
We do not sell alert recipient lists. If future advertising or analytics activity counts as a sale or sharing under a privacy law, we will provide required opt-out controls before using it that way.
Records are kept as long as needed for service delivery, legal compliance, security, audits, billing, disputes, tax records, product improvement, and abuse prevention. First-party field-measurement events expire after 35 days by default. We may aggregate, de-identify, or delete older records when they are no longer needed.
You can stop alerts, unsubscribe from email, deny browser push permission, clear cookies, avoid optional forms, and request access, correction, deletion, portability, restriction, or objection when law grants those rights.
Privacy rightsThe service is intended for general travelers and local businesses, not for children under 13. We do not knowingly collect personal information from children under 13.
We use separate public and private areas, protected sign-in, rate limits, provider notices, audit logs, and limited data collection where practical. No internet service can guarantee perfect security.
Security policyWe may update this policy as features, providers, legal requirements, or business operations change. Continued use after an update means the updated policy applies.
Send privacy, correction, deletion, security, or advertising questions through contact. We may need to verify requests before disclosing or changing account data.
Contact