Privacy Policy

This Policy applies to information we process for account administration, product use, website visits, billing, connected systems, support, security, and business operations. It does not govern a third party's independent practices, including Jobber, Stripe, Twilio, Anthropic, or a Customer's own business.

RelayHitch primarily provides a business-to-business service. For account, website, billing, security, and direct relationship information, RelayHitch determines why and how the information is processed. For records a business Customer makes available about its own clients, contacts, jobs, quotes, invoices, or communications, RelayHitch generally processes the information to provide the Service on that Customer's instructions. The Customer remains responsible for its relationship, notices, and lawful basis with its end customers. Use of the Service is also governed by our Terms of Service.

Depending on how the Service is used, we collect the following categories:

• Account and business information: name, business email, phone number, authentication identifiers, company name, business profile, role, user permissions, support contact, and account settings.
• Company policy and authority: skill settings, business hours, thresholds, communication preferences, recurring-service rules, allowed actions, owner approvals, suppressions, and authority levels from Off through Operate.
• Connected-system information: authorized provider account identity, provider-native identifiers, clients and contact fields, properties or service locations, requests where available, quotes, jobs, visits, invoices, balances, due dates, payments or deposits where available, statuses, relationships, and relevant timestamps.
• Revenue Manager records: Revenue Threads, Revenue Cases, source references and evidence, economic values, confidence and eligibility, priority components, strategies, proposed and approved actions, Human Attention items, conversations and classified intent, typed memory, events, worker runs, audit history, and outcome attribution.
• Communications information: sender and recipient routing information, consent and suppression evidence, bounded message content or redacted excerpts where needed, classification, delivery status, reply status, provider identifiers, and communication audit records. Messaging is processed only when the applicable feature is used; live Revenue Manager communications can remain disabled even when a subscription exists.
• Billing information: Stripe Customer, Checkout Session, subscription, invoice, payment and dispute status; plan, price, billing period, billing address, and tax identifier where supplied through Stripe. Stripe collects payment-card details in its hosted interface. RelayHitch does not receive or store the complete card number or card security code, though it may receive limited card metadata such as brand, last four digits, and expiration.
• Website, analytics, and attribution information: pages and source paths, referring page, first and latest touch, UTM parameters, event name, anonymous and session identifiers, scan category counts, broad revenue bands or aggregate identified value, browser consent or opt-out state, and conversion events. The funnel event schema rejects customer names, phones, emails, addresses, message bodies, and raw source records.
• Device, log, and security information: IP address and request metadata available to our infrastructure providers, browser and device information, timestamps, authentication and security events, diagnostics, performance traces, and error details. Sentry is configured not to send default personal information; client replay masks text and blocks media.
• Support and feedback: information you include in support requests, chats, emails, interviews, or feedback.

The Service is not designed to collect Social Security numbers, biometric identifiers, health or medical records, complete payment-card numbers, bank-account credentials, or precise device geolocation. Connected records may include customer service addresses and scheduling geography because those facts can be relevant to a job or capacity case; that is different from continuously tracking a person's device. Please do not place unsupported sensitive information in free-text fields or support messages.

When an authorized business user connects Jobber, RelayHitch uses encrypted OAuth access and refresh credentials on its servers to read the authorized account identity and relevant source records. Jobber data may be used for a read-only Revenue Health Scan and source-backed Revenue Manager workload. Connecting Jobber does not itself authorize customer outreach, provider writes, a subscription, or Revenue Manager live effects.

Provider webhooks are treated as signals to reevaluate relevant records, not necessarily as complete source truth. Before a material action, the Service may reread the connected source and compare its current state with the approved proposal. If Customer disconnects Jobber, RelayHitch revokes or removes stored Jobber credentials and stops future reads through that connection. The provider may retain its own records under its policies.

We use information to:

• authenticate users, administer accounts, and provide support;
• connect and reconcile source systems;
• run Revenue Health Scans and identify potential Receivables, Opportunity, Sold-Work, Capacity, and policy-backed Reactivation cases;
• create and maintain economic lineage, cases, queues, source evidence, priorities, next actions, Human Attention, and outcome records;
• apply company policy, authority, consent, suppression, provider-readiness, source-freshness, business-hours, cooldown, risk, and duplicate-action controls;
• prepare or execute an approved action only when all separate product and legal gates are satisfied;
• process customer replies, promises, future dates, disputes, opt-outs, help requests, and requests for a human;
• bill for the Service, administer cancellation, respond to failed payments, prevent fraud, and keep financial records;
• measure safe product and acquisition events, diagnose reliability, secure the Service, enforce terms, and comply with law; and
• improve the Service using feedback, aggregate trends, test fixtures, and product performance, subject to our contractual and legal obligations.

Revenue Manager uses model providers, currently Anthropic, for bounded semantic tasks such as classifying a reply, extracting a date, proposing a strategy, explaining a case, or drafting a message. Depending on the task, RelayHitch may send the model a structured envelope containing selected source facts, relevant company policy, allowed action types, and customer text. Customer and provider content is marked and treated as untrusted data, not as system instructions.

The model has no RelayHitch tool credentials and cannot directly perform an action. Output must match a defined schema and cite available source-fact keys. Low-confidence, malformed, timed-out, or unauthorized output fails closed or goes to Human Attention. Deterministic systems, not the model, decide money, authority, consent, suppression, provider state, source freshness, idempotency, and whether an action is permitted. Model providers process submitted data under their applicable service terms and data-protection commitments; do not assume that source data remains solely within RelayHitch infrastructure.

When messaging is separately enabled, RelayHitch may process contact information, sender configuration, use-case-specific consent evidence, suppressions, approved content, delivery status, and replies to send or reconcile communications on a Customer's behalf. Payment for Revenue Manager does not establish recipient consent or activate messaging. Different skills may require different consent, provider registration, and communication authority.

A STOP response suppresses further applicable messaging and revokes the relevant consent state. A generic START response may remove a sender-level block but does not by itself grant invoice, opportunity, scheduling, or marketing consent. RelayHitch does not sell end-customer mobile numbers or disclose them to third parties or affiliates for those parties' own marketing or promotional purposes. See the SMS Terms for enabled SMS programs.

Stripe hosts checkout and payment-method collection and processes charges, subscriptions, invoices, refunds, disputes, billing addresses, and tax identifiers. RelayHitch receives identifiers and status needed to provision and administer a subscription, reconcile signed webhook events, show billing state, support cancellation, prevent duplicate fulfillment, and maintain accounting and legal records. Stripe's processing is governed by its own privacy notice and, where applicable, its role as our payment processor.

We use necessary cookies and browser storage for authentication, security, consent state, referral attribution, first/latest-touch attribution, and session continuity. We use Vercel Analytics, Plausible, a first-party funnel-event ledger, and Sentry diagnostics as configured. Termly manages cookie consent and preferences. Attribution storage may contain an anonymous identifier, session identifier, landing page, referrer category, and UTM values; it is not intended to contain source-system customer records.

You can use our Consent Preferences control and browser settings to manage optional technologies. We recognize an enabled Global Privacy Control signal to suppress configured advertising and retargeting scripts and also provide an account privacy setting. If the consent manager fails to initialize, the separately consent-gated Plausible and future advertising scripts are not rendered by that loader; essential security telemetry and Vercel Analytics may operate according to their configuration. Details are available in the Cookie Policy.

We may disclose information in these circumstances:

• Service providers: to providers that host, secure, monitor, analyze, support, communicate, process payments, or provide model inference for the Service, subject to appropriate contractual limits.
• Customer direction: to connected systems, recipients, users, or other parties when Customer directs or authorizes the interaction.
• Legal and safety: when reasonably necessary to comply with law or legal process, protect rights or safety, investigate fraud or abuse, or enforce agreements.
• Business transaction: in connection with a financing, merger, acquisition, reorganization, bankruptcy, or sale of assets, subject to confidentiality and applicable law.
• Professional advisers: to lawyers, accountants, insurers, auditors, and advisers under duties of confidentiality.
• Aggregate information: information that does not reasonably identify a person or Customer.

RelayHitch does not sell personal information for money. We do not currently disclose personal information for cross-context behavioral advertising as that term is commonly used, and configured advertising or retargeting technologies are suppressed when a supported opt-out signal applies. State-law definitions of “sale” and “sharing” vary; the rights section below explains how to contact us about a particular practice.

Current categories and principal providers include:

• Hosting and delivery: Vercel;
• Database and authentication: Supabase;
• Payment and tax-related checkout data: Stripe;
• Connected business records: Jobber when Customer authorizes the connection;
• AI model processing: Anthropic for bounded Revenue Manager reasoning and certain support features;
• Messaging: Twilio when a separately enabled communication path uses it;
• Diagnostics and analytics: Sentry, Vercel Analytics, and Plausible; and
• Consent management: Termly.

Providers and their locations may change as the Service evolves. A provider may act as our processor, as an independent controller for its own account or compliance information, or in both roles depending on the activity.

We retain information for as long as reasonably necessary to provide the Service, maintain source-backed and auditable case history, administer the business relationship, enforce suppression and consent, secure the Service, prevent fraud, resolve disputes, and meet tax, accounting, contractual, and legal obligations. Retention varies by record and context. We do not promise a universal automatic deletion period that the product does not implement.

Disconnecting Jobber removes or revokes stored connection credentials and stops future reads. It does not automatically delete previously derived scan results, Revenue Threads, Revenue Cases, source references, action and decision history, legal acceptance, billing records, suppression evidence, backups, or security logs. When information is no longer required, we may delete or de-identify it. Deletion from active systems may not immediately remove limited copies in backups, provider systems, legal holds, or immutable audit records.

An authorized Customer account contact may request access, correction, export, or deletion at privacy@relayhitch.com. We will verify the request and apply contractual, security, and legal exceptions. An end customer whose data was supplied by a RelayHitch Customer should normally contact that business first; we will assist the business with a valid request as required by our obligations.

Depending on where you live and applicable thresholds, you may have rights to know or access personal information, correct it, delete it, receive a portable copy, opt out of certain sale, sharing, targeted advertising, or profiling, limit certain sensitive-data uses, and appeal a denied request. These rights are subject to definitions, exemptions, and verification requirements in applicable law. We will not unlawfully discriminate against you for exercising a right.

Submit a request or appeal to privacy@relayhitch.com and describe the account or relationship involved. We may request information reasonably necessary to verify identity, authority, and scope. Authorized agents must provide proof of authority. For information processed on behalf of a business Customer, we may direct the request to that Customer.

We use safeguards designed for the nature of the Service, including authenticated access, tenant isolation, role and row-level controls, encrypted transport, encrypted connected- system credentials, least-privilege service paths, signed provider callbacks, audit and idempotency records, source-freshness checks, redaction-oriented logging, and incident monitoring. No safeguard eliminates all risk. You are responsible for securing your own account, users, devices, and connected systems.

RelayHitch is based in the United States. We and our providers may process information in the United States and other countries where privacy laws differ from those where you live. The Service is presently directed to U.S. business customers. Contact us before using it where additional localization or transfer requirements apply so an applicable transfer mechanism and provider posture can be evaluated rather than assumed.

The Service is for businesses and is not directed to children under 18. We do not knowingly solicit personal information directly from children. If you believe a child submitted personal information directly to RelayHitch, contact privacy@relayhitch.com. Customer is responsible for ensuring that records it connects or submits are lawful for the business purpose involved.

We may update this Policy as the Service or law changes. We will publish the effective date and a new immutable version identifier and provide additional notice when appropriate. A historical acceptance record remains associated with the exact version presented at the time; it is not changed to identify a future policy.

Privacy questions and requests:
RelayHitch LLC
Email: privacy@relayhitch.com
Website: https://relayhitch.com

General support: support@relayhitch.com