HTTP logs cannot be redacted, suppressed, or selectively deleted before or after storage; there is no self-serve control, API, or operator action that removes or masks a field (source IP, path, etc.) from a log entry, and the fixed 90-day underlying TTL cannot be shortened. Your plan's retention figure (Hobby: 7 days) is a read-time query window over data that persists for the full 90 days. All logs are stored in US West regardless of deploy region. These are the documented constants; there is no separate policy-audit surface beyond them.

Edge rules match source IPs only via the ipv4.src attribute. A native IPv6 caller presents no IPv4 source, so any ipv4.src condition simply does not fire, meaning a rule like "block if ipv4.src not in [allowed CIDRs]" silently passes IPv6 traffic. The supported pattern is explicit allow rules for your permitted CIDRs followed by a terminal catch-all block (with no IP condition) as the last rule, which denies everything not already allowed, IPv4 and IPv6 alike.

For deployment provenance, Railway provides variables like RAILWAY_GIT_COMMIT_SHA and RAILWAY_DEPLOYMENT_ID at runtime, and the Deployment Details pane shows the configuration a deployment went out with, including which values originated from a config-as-code file.