Privacy notice
Version 2.0 of this notice, published on 4 September 2026.
Courtesy translation. The Italian version is authoritative.
WildRelay lets you calculate and work on projects without an account. Accounts, synchronisation and sharing are additional services: calculations still run on your device when you use them. Requests for maps and geographic data are separate from project synchronisation.
Controller and contacts
The controller for WildRelay is Tecnica - Formazione - Sicurezza s.r.l. (TFS), Via Chambery 51, 11100 Aosta (AO), Italy, VAT IT00649260072, REA AO-58660.
For personal data requests: [email protected]. The Data Protection Officer (DPO) can be reached at [email protected].
ICE & FIRE S.r.l. co-created the project and appears in its branding and credits; it is neither a controller nor a processor for this service. Notices for other websites operated by these organisations do not replace this notice.
Browsing the website
The information website does not use behavioural analytics, advertising, profiling cookies or third-party embedded content. Fonts, images and scripts are served by the website.
Your Light, Dark or Automatic choice is stored only in the browser’s localStorage, under the key wildrelay-theme. It remembers the appearance of the pages, contains no identifier and is not sent to the server. It remains until you clear the site’s data; selecting Automatic follows your device again. This technical preference does not require profiling consent or introduce a cookie banner.
Cloudflare hosts and distributes the pages. HTTP requests make the IP address, requested URL, date and time, technical browser information and request outcome available to the service. TFS processes logs to deliver the website, diagnose problems and prevent abuse, based on its legitimate interest in service availability and security (GDPR Article 6(1)(f)). The retention period set for web logs is 24 months from recording, unless deleted earlier.
External links open the relevant provider’s service, which applies its own notice. The website does not send a referrer with external links.
Local work and mapping services
Data on your device
The calculation engine processes routes, elevations, equipment, pressures and flows locally. Projects, preferences, caches and geographic packages may be stored on your device or, in the web version, in the storage allocated to the site by your browser. Local work does not require registration.
Clearing browser data may also remove local projects and preferences. Exported copies and device backups remain under your control: deleting a project from the service does not withdraw those files.
Sign-in credentials and map-provider keys, where used, support your session and requests to your chosen provider respectively. Mapping keys are not part of a shared project; the receiving service gets the key required for the request.
Network requests
When you view an online map, sample elevations or search for geographic features, the app may request map tiles, imagery and data for your working area. The recipient receives your IP address and request parameters: geographic area, detail level and any filters. These requests may therefore reveal where you are working even without sending the project file.
The services contacted depend on the selected layer, locally available data and any fallback layers; not every provider is contacted on every use.
| Function | Services and recipients |
|---|---|
| Maps and satellite imagery | OpenStreetMap Foundation (tile.openstreetmap.org), OpenTopoMap (tile.opentopomap.org), EOX IT Services (tiles.maps.eox.at) |
| Italian regional orthophotos | Tuscany (www502.regione.toscana.it), Aosta Valley (servizisct.regione.vda.it), Autonomous Province of Bolzano (geoservices.buergernetz.bz.it), Friuli Venezia Giulia (geoserver.protezionecivile.fvg.it), Veneto (idt2.regione.veneto.it) |
| Other orthophotos | IGN France (data.geopf.fr), basemap.at (mapsneu.wien.gv.at), European Environment Agency/Copernicus (copernicus.discomap.eea.europa.eu) |
| Maps using your own key | Esri (static-map-tiles-api.arcgis.com) |
| Elevation models | Mapterhorn (tiles.mapterhorn.com); Terrarium data distributed through Amazon Web Services (s3.amazonaws.com/elevation-tiles-prod) as a fallback |
| OpenStreetMap features | Overpass (overpass-api.de): geographic queries, for example water sources and road networks |
| TFS geographic services | geoserver.gtsu.org: operational layers and mapping, including Trentino orthophotos made available through TFS |
| Offline packages | packs.wildrelay.app: catalogue and downloads of requested packages |
| Custom services | The WMS address or other service configured by the user, with the parameters and any credentials required by that service |
Geographic functions are provided to perform the service you request (GDPR Article 6(1)(b)). External operators also process connection data under their own notices. TFS services operate within its infrastructure; data originating from a public body does not mean your device contacts that body directly.
Working without a connection avoids these requests, within the limits of data prepared before deployment. Downloading a package requires a connection; opening the catalogue may already trigger a request before any download.
Accounts, synchronisation and sharing
Data and purposes
An account requires an email address and processes user identifiers, authentication data and information needed to maintain the session. Email is used for access codes and service communications, not marketing.
Synchronisation transfers projects associated with your account and their changes to the backend: name, route and coordinates, scenario, notes, equipment, saved results, revisions and technical metadata. Where supported by the project, this includes handling attachments. Offline work is synchronised when connectivity returns and the session permits it. Signing in and using synchronisation does not mean all data stays only on your device.
Sharing makes data available to authorised recipients according to their permissions. Invitations involve processing the recipient’s email, including before they have an account, and the sender’s identity. Shareable links allow access to anyone who holds the link within its permitted scope; treat them as confidential. Revocation and expiry prevent new access, but do not erase copies already downloaded or exported by recipients.
Team use may also involve memberships, roles, locations and inventory records, including deployments and the relevant operators. Visibility depends on organisation and project permissions. Do not include unnecessary personal information in notes or equipment names.
These operations provide functions requested by the user (GDPR Article 6(1)(b)); handling invitations and permissions also relies on legitimate interests in collaboration and service security (Article 6(1)(f)). Without an email address an account cannot be created; without the necessary data synchronisation and sharing cannot be provided. Refusing does not prevent local calculations.
Infrastructure and data access
TFS operates the backend on Scaleway in the Paris region (fr-par), France. Scaleway also provides transactional email.
Data may be accessed by authorised TFS personnel, providers assigned the relevant technical work, collaborators you grant access to and competent authorities where required by law. Providers acting on behalf of TFS are governed by agreements under GDPR Article 28.
Optional diagnostics
Error and crash reports through Sentry (Functional Software, Inc.) are disabled until you consent. You may withdraw consent in the app settings: this stops subsequent submissions without affecting the lawfulness of earlier ones. The legal basis is consent (GDPR Article 6(1)(a)); refusal does not restrict calculation functions.
Reports include technical error details, the execution stack, app version and essential runtime environment information. Before sending, the app removes user fields, requests, tags, additional messages and action history; screenshots, session recordings and performance analytics are not enabled. This reduction does not guarantee that every exception message is free of personal data. The provider also receives the technical data needed for the connection.
The European region has been selected for Sentry. Events are retained for 90 days from the event, unless deleted earlier. The region choice concerns event data and does not guarantee that all provider administration or support activities take place exclusively in the EU.
Retention, deletion and backups
- Accounts and projects: for the duration of the requested service, until account or content deletion, subject to legal obligations and data retained separately for security or legal claims. Removing items from the trash and deleting backup copies are distinct operations.
- Revisions: history pruning deletes a revision only when it is older than 90 days and is not among the latest 50. Pruning runs when projects are saved; 90 days is therefore not an absolute maximum for every revision.
- Sharing: links and invitations expire or can be revoked. Access expiry does not mean that all records of the operation are deleted.
- Security audit: 24 months from recording. Records include the operation, date and time, actor, affected object, outcome and, where available, IP and client information. They are not copies of project content. They support investigation of access, relevant changes and abuse, based on legitimate interests in security and legal protection.
- Web logs: 24 months from recording; Sentry diagnostic events: 90 days from the event, as described above.
- Backups: up to 24 months from creation of the copy, to restore the service after a failure or incident. Content deleted from active systems may remain in copies until they rotate out. Backups are not intended for routine data use.
Any further retention needed for legal obligations or specific disputes is limited to relevant data and the necessary period. You can use the contacts above to request deletion of copies and records that cannot be managed directly through the interface.
Processing outside the European Economic Area
Hosting the backend in Paris does not make every app network request or provider activity European. Cloudflare and Sentry are US providers; their networks and subprocessors may involve processing outside the EEA.
Their agreements provide international transfer mechanisms, including European Commission standard contractual clauses and, where applicable, the Data Privacy Framework. You can consult the Cloudflare DPA and Sentry DPA or ask TFS about applicable safeguards. Directly contacted mapping services, including the public AWS service, may have their own terms and locations: they are not all processors for TFS.
Operational data and precautions
The location of a fire, water source or team may be operationally confidential even when it does not identify a person. Viewed maps, synchronised projects and shared files are separate channels through which this information can leave your device.
Enter only necessary data and check recipients and permissions before sharing. Photographs and documents may contain faces, names, coordinates or EXIF metadata: do not assume importing automatically removes them. Review attachments and exports before sending them.
WildRelay does not require special categories of personal data, such as health information. Its technical calculations do not profile people or make automated decisions with legal effects under GDPR Article 22.
Rights and updates
Where applicable under GDPR Articles 15–22, you may request access, rectification, erasure, restriction, portability and object to processing. In particular, you may object to processing based on legitimate interests for reasons relating to your situation.
You may withdraw diagnostic consent at any time in settings or by contacting us. To exercise your rights, write to [email protected] or the DPO at [email protected]. We respond within GDPR time limits; if necessary, we request only information useful to verify identity and locate the data.
You also have the right to complain to the Italian Data Protection Authority (Garante).
This notice is available on the website and in the app. Changes to processing are accompanied by an updated version and, where necessary, a notification or a new request for consent.