See also Worldwide Distribution Compliance Notes.
OFeed SI-Droid Connector is a professional tool for orienteering event organisers and competition staff. When configured by the organiser, the app retrieves IOF 3.0 result lists from the app “SI-Droid Event” and uploads them to the OFeed platform. The app is intended for use in event-management workflows and is not designed for children or for general end-user consumption by athletes or spectators.
OFeed SI-Droid Connector does not collect, request, store, transmit, or infer any personal information about the device user. It does not collect age, accounts, contact details, analytics data, advertising identifiers, or location data. The app does not require creating or signing in to any user account.
OFeed SI-Droid Connector processes only event-related data retrieved from the organiser’s SI-Droid Event instance. The retrieved data consists of result lists formatted as IOF 3.0 XML, containing competition-related information such as competitor names, clubs, classes, bib numbers, chip numbers (SPORTident card numbers), split times, and finish results.
All such data is supplied by the organiser’s SI-Droid Event installation and is processed only to perform the organiser-configured upload to OFeed. The app performs only a minimal technical transformation: it ensures that each competitor has a numerical ID required by OFeed, inserting one when necessary. It does not otherwise alter the competitor information and does not store event data beyond what is needed for upload operations.
When enabled by the organiser, OFeed SI-Droid Connector periodically performs local GET requests to http://localhost:port/reports/ResultsIof30Xml (where the port number is defined in SI-Droid Event’s settings). This URL is served by the built-in web server of SI-Droid Event. These requests occur only on the organiser’s device using localhost. No external communication takes place during this retrieval.
When configured by the organiser, OFeed SI-Droid Connector uploads IOF 3.0 XML result lists to the OFeed platform via https://api.orienteerfeed.com. Uploads occur only when the organiser has enabled them. Only the IOF 3.0 XML data retrieved from SI-Droid Event is uploaded. The app never uploads hidden analytics, tracking data, device information, or advertising identifiers. All uploads are performed using secure HTTPS communication.
OFeed SI-Droid Connector contains no advertising, no in-app tracking, no third-party analytics SDKs, no behavioural profiling, and no cookies or similar tracking technologies. The app does not personalise content or features based on behaviour, identity, or demographics.
OFeed SI-Droid Connector does not target children. It does not collect or infer age, does not provide age-dependent features, does not change behaviour based on age, and does not contain child-directed content.
OFeed SI-Droid Connector requests only the permissions required for its core functionality. The app does not request any permissions beyond those listed below.
Used to communicate with OFeed and to retrieve IOF 3.0 XML data from SI-Droid Event’s local web server.
Used to determine whether the device has a usable network connection.
Used to keep the upload service active while performing periodic data retrieval and upload tasks.
Used to display optional system notifications indicating upload status or errors. Notifications occur only if the user has granted permission.
OFeed SI-Droid Connector does not store event data permanently. An IOF 3.0 XML result list is held in memory only long enough to perform the upload to OFeed. No long-term storage, caching, or archiving of event data is performed by the app.
Event data retention on OFeed is governed by OFeed’s own policies and by the organiser’s configuration.
All communication with OFeed uses secure HTTPS. Retrieval from SI-Droid Event occurs only on the same device via localhost. The app does not transmit data to any third-party services other than the organiser-configured OFeed endpoint.
The organiser is responsible for configuring OFeed credentials and safeguarding access to their SI-Droid Event installation.
This privacy policy may be updated as the app evolves or as platform or regulatory requirements change. Any changes will be reflected in this document.