ColeWorld Reroute™ Privacy Notice

ColeWorld Reroute™ Privacy Notice
Last updated: October 18, 2026
Publisher: ColeWorld
Contact: fi@dredgeoriongateway.com

What you should submit
Reroute compares only metadata you explicitly provide. Send only independently sanitized, public, safe-to-share endpoint origins and paths, resource identifiers, scope names, and client-registration modes. Never submit credentials, tokens, authorization codes, state, PKCE values, private or personal identifiers, raw sign-in URLs, or logs. The service is not intended to receive personal information about children. Validation is not automatic redaction: a rejected request has already reached the service and its host.

Application processing
The application receives your submitted metadata and computes a comparison in memory. It makes no outbound requests to the supplied endpoints, does not access accounts, and has no diagnostic database, saved reports, user accounts, advertising, or application analytics. Application request, request-body, and access logging are disabled. In-memory processing is not secure zeroization. The report does not repeat submitted endpoint or scope values. MCP request identifiers are echoed for protocol correlation; use ordinary non-sensitive identifiers.

Abuse prevention
The application keeps bounded source-IP or IPv6-prefix counters, timestamps and in-flight counts in memory to enforce request limits. Idle entries become eligible for removal after five minutes and are removed on a later limiter request; without another request, they can remain until the process exits. These counters are not saved diagnostic reports. Shared network addresses or prefixes can share limits.

Hosting provider
Railway hosts this service and separately records HTTP metadata, including source IP, user agent, request identifiers and timestamps. Railway states this metadata is retained for 90 days and cannot be disabled, redacted per service, or deleted early. A plan's shorter viewing window is not a shorter storage period. Do not put sensitive data in request paths, headers or identifiers.

Railway's customer-visible HTTP log format has no request-body field. This is not a guarantee about body handling in Railway's internal operational systems or by subprocessors; those practices have not been independently verified here. Your client, such as ChatGPT, may also retain requests and responses under its own policies. No anonymous-use or zero-retention guarantee is made. See Railway's privacy and legal information at https://railway.com/legal and your client's applicable policies.

Support email
If you email support, the support mailbox and email providers process the address, message and any attachments you send. The publisher uses this correspondence to respond to your request. Support correspondence is retained until the publisher deletes it; no fixed deletion schedule is currently offered. Do not email sensitive diagnostics. Contact the address above about support-email deletion; deletion from the publisher's mailbox does not guarantee deletion from provider backups or records retained under their policies.

Questions and deletion requests
Reroute has no saved diagnostic reports or user accounts to retrieve or delete. The publisher cannot promise immediate erasure of transient memory or early deletion of Railway's HTTP metadata. Contact the address above with questions. Do not include the sensitive material you want removed in the request.