See also Worldwide Distribution Compliance Notes.
O Checklist is a professional tool for orienteering event organisers and is used on-site by competition staff. Its purpose is to assist in managing event data such as start lists and start-status information. The app is not intended for children or for general end-user consumption by athletes or spectators.
O Checklist 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.
O Checklist processes only the event data that the organiser provides, such as competitor names, clubs, classes, courses, bib numbers, chip numbers (SPORTident card numbers), and start times. In addition, the app processes start-status information generated on-site by competition staff, such as “started OK” and “did not start” (DNS).
All such data is provided, generated, or recorded by the organiser and is processed locally on the device.
O Checklist can upload start-status data either manually (when competition staff chooses to upload) or automatically (if the organiser enables periodic uploads).
Uploads can be sent to the OFeed API, to an organiser-defined server URL (for example, to POST a YAML start-status report), or via the device’s email client. The organiser fully controls whether uploads occur, how often they are made, the method used, and where data is sent.
Uploads include only the event data and the start-status information recorded on-site by competition staff. The app never includes hidden analytics, tracking data, or advertising identifiers.
O Checklist 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.
Depending on the organiser’s configuration:
In all cases:
O Checklist 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.
O Checklist does not request any sensitive permissions. It requests only the permissions needed for network communication.
File imports use the system file picker, so the app never accesses external storage directly. Uploads use only the event data and the start-status data stored in the app’s internal storage, which requires no permissions.
Event data and start-status information are stored locally on the device, and on a server only if the organiser uploads it. The app does not store data in the cloud on its own.
Data retention on remote servers (such as OFeed or an organiser’s custom endpoint) is governed by those services’ policies and by the organiser’s settings.
Organisers are responsible for deleting or anonymising event data when appropriate and for managing data retention on any server they control or use.
O Checklist uses secure communication when interacting with remote services such as OFeed or organiser-defined endpoints. Supported secure protocols include HTTPS, FTPS, and SFTP. If the organiser chooses to use FTP, the transmission will not be encrypted.
When sending reports via email, the app hands the report to the device’s email client. Transmission security then depends on the user’s email provider and account configuration (for example, whether the email service uses TLS). The app itself does not manage or guarantee the security of email transmission.
The security of organiser-defined upload destinations, email recipients, server configurations, and credentials is the responsibility of the organiser.
This privacy policy may be updated as the app evolves. Any changes will be reflected in this document.