Clear boundaries. Accountable use.

Hosted project processing

RoaDRain sends project inputs selected by the user to Hydroism’s managed processing environment so terrain, GIS, hydrology, reports, and downloadable outputs can be generated. Project files and intermediate outputs may be stored on hosted infrastructure for processing, recovery, and retrieval. Access controls, tenant separation, retention periods, deletion controls, backups, and paid-account policies must be finalised and published before commercial access opens.

Privacy and third-party services

Operational records may include timestamps, app version, browser and network metadata, requested routes, processing status, errors, and service-security events. Uploaded engineering data can contain coordinates, project names, client references, and other user-provided content; users should remove unnecessary personal or confidential information and follow their employer and project data policies.

Public terrain, land-cover, map, rainfall, and similar functions may request data from their identified external providers. If a user deliberately starts AI engineering review, the selected engineering context is sent through Hydroism’s protected server-side integration to the configured AI provider. API keys remain server-side and are not delivered to the browser.

Preliminary engineering disclaimer

RoaDRain is an early-stage road-drainage screening and watershed decision-support tool. Its outputs are not a substitute for verified survey, ground investigation, authoritative rainfall and flow data, detailed hydrologic and hydraulic modelling, structural design, site inspection, statutory review, or approval by a qualified engineer. The responsible engineer must verify all inputs, assumptions, basin boundaries, crossing locations, discharges, dimensions, risks, and final deliverables before professional or construction use.

Availability and acceptable use

Beta availability may be interrupted for deployment, maintenance, data-provider incidents, resource limits, security response, or product changes. Users must not upload unlawful material, attempt unauthorised access, probe private administration, bypass technical limits, interfere with other users, expose the service as a general AI proxy, or use automated traffic that degrades the application.

Future commercial terms

Authentication, subscriptions, usage allowances, billing, taxes, refunds, service levels, and customer-support commitments have not yet been selected for the web-app model. They will be designed and published before paid access is offered.