Privacy policy

Who we are

RouteToHuman (routetohuman.com) is operated by Development Partners Software LLC (“DevPartners”, “we”). This policy covers the public website you are reading and, where noted, the RouteToHuman service. Questions: hello@routetohuman.com.

This website

This site is static. It runs no third-party analytics, no advertising or tracking pixels, and no third-party embeds, and it sets no cookies. Fonts are served from our own domain, so viewing this site sends no request to a font or script CDN.

One thing the pricing page does count. That page offers two tools an AI agent in your browser can call to ask what a plan costs and which one fits. When one is called we record that it was called, and the shape of the question — which tool, roughly how many messages a day (as a band such as 11–100), whether an answer was needed, whether the recipients were you or other people, and which plan we suggested. That is the whole record.

There is no identifier of any kind attached: no cookie, no session, no account, and never the words you or your agent typed. The free-text argument is reduced to “you” or “other people” in your browser before anything is sent, and our edge rebuilds the record from a fixed list of permitted values, so a stray address or a pasted question cannot be stored even by mistake. Two people asking the same thing produce the same row, which is the point: it tells us what people need, and nothing about who needed it.

Edge logs — kept at most 10 days

routetohuman.com is fronted by Cloudflare. Our edge request log may include your raw IP address and user-agent string. We keep that raw data for no more than 10 days, after which it is purged automatically. This retention window follows the EFF Do Not Track policy posture.

Operational telemetry and security logging

Our backend services emit operational telemetry (OpenTelemetry to Azure Application Insights) so we can diagnose failures. For traffic arriving through our Cloudflare edge, the standard client-IP field is masked to 0.0.0.0 and coarse geolocation is retained.

There is a security exception: requests that reach the origin directly, bypassing Cloudflare, are recorded with their raw peer IP address, user-agent, host, and forwarded-address chain. Operational logs can also contain request URLs and error details. These logs are separate from message records and are not a content-free audit trail.

Messages and receipts

We process message content to deliver messages and operate the service. Messages created through /v1/messages are stored with their recipient, full prompt, choices and context, delivery timeline, sender attribution, and any human response. Response evidence can include the responder’s IP address, user-agent, authenticated identity, or Slack identity, depending on how they answer. These are message records, not just hashes.

The separate transactional-email endpoint, /v1/email/sends, stores a different receipt: recipient and request hashes, sender address, provider operation identifier, and status, rather than the email subject and body. API keys are stored as SHA-256 hashes, not as recoverable keys.

Retention and deletion

Message records currently have no automatic expiry and remain stored unless erased. The message history number on a plan describes a list-view window, not a deletion period. Where that window is applied, an older message can still be retrieved by its id. A seven-day history does not mean content is deleted after seven days.

Eligible owner-only accounts can request erasure from the application’s Account page. If an account includes other people’s records or the self-service path refuses the request, contact us to review it. Erasure removes the applicable live account records; backups and operational logs have separate retention, and messages already delivered to an inbox or Slack are not recalled. The erasure receipt explains remaining data and any follow-up steps.

Email sender identities

Free notifications are sent from robot@free.routetohuman.com. Our other platform notification sender is robot@send.routetohuman.com, and operational notices use ops@send.routetohuman.com. Platform email is delivered through Azure Communication Services. Replies addressed to us route through Cloudflare Email Routing to our mailbox. An account configured with its own email provider uses its configured sender instead.

Sign-in

The application at app.routetohuman.com uses Descope for authentication. Sign-in data (such as your email address) is processed by Descope on our behalf; the public site you are reading has no sign-in and no accounts.

Service providers and delivery services

• Microsoft Azure — hosting, telemetry, and Azure Communication Services email
• Cloudflare — edge network, DNS, and inbound email routing
• Descope — authentication for the application (not this site)
• Slack — workspace identity and message delivery when you connect Slack
• Expo and the device’s push service (such as Apple or Google) — notification delivery when you use the mobile preview
• Your browser’s push service — encrypted web notification delivery when you enable browser notifications
• An account’s configured email provider — delivery when that account uses its own sending configuration

Optional delivery services receive the data needed for the channel you choose; not every account uses every provider. Delivered messages also reside with their recipients and are subject to the receiving service’s policies. We do not sell personal data. We may disclose data where the law requires.

Your rights and changes

To ask what we hold about you, or to have it corrected or deleted, email hello@routetohuman.com. When this policy changes we update this page and its effective date; adding any new data collection to this site is treated as a change to this policy.