Privacy Policy
FairWind: Master Regatta
This policy explains how this application handles information and how to contact us about privacy.
Information we process
FairWind: Master Regatta does not require an account. The app stores the name and default boat class you enter, regatta names, dates, text places, boat classes, race status and finishing position, tactical mark sequences, wind and starting notes, maneuver favorites, notes and consultation counts/times, and sailing journal dates, places, boats, wind conditions, hours, results and notes in a local JSON file on your iPhone. If you select a photo, the app creates a resized JPEG copy. These records, including the local profile and selected photo copies, synchronize to the application server when connectivity is available. The interface language is stored locally in preferences. A random installation secret is stored in the iOS Keychain and sent as an authorization bearer over HTTPS; the server stores its SHA-256 namespace, not the raw secret. Requests to the API, home page or privacy page also expose network information such as your IP address, request time and path to the hosting infrastructure. The app does not request device location, contacts, microphone or camera access.
How we use information
Local storage makes planning, the maneuver reference and journal available offline. Server processing persists and synchronizes your installation-scoped records, resolves record changes by modification timestamp, and processes deletion requests. Photos are attached to the journal entries you choose. Progress statistics are calculated on the device from your records. Language preferences control the interface. Installation authorization separates your data from other installations. Hosting request processing and limited error diagnostics support operation and security of the service. There is no advertising, analytics SDK, newsletter or outbound email system.
Service providers and sharing
The backend runs on Railway and stores application data in a SQLite database on its attached Railway persistent volume. Railway and its infrastructure providers process the service requests and stored data as hosting recipients, including network and operational logs. The application has no third-party analytics, advertising, mapping, social sign-in or messaging SDKs. The server does not intentionally log your record contents, photos or bearer secret; application error logs contain a request identifier and error code. Infrastructure may retain request metadata under its own operational practices. A JSON export is created only when you choose it; if you then share that file using the system share sheet, the recipients and applications you select receive its contents, including attached photo data.
Data retention
Local records remain until you delete them or remove the app data. The installation secret may persist in the Keychain independently of app removal; reinstalling is not a guaranteed erasure method. Server records remain until an authorized deletion or record tombstone replaces them. Deleted individual records retain only an identifier, kind, deletion flag and modification timestamp to prevent stale synchronization from restoring their content. Deleting all data removes the installation records and retains only a hashed revocation marker to reject reuse of the old secret. No automatic expiration duration is configured. Railway infrastructure log and backup retention is not controlled by an app-level timer, and no fixed duration is promised. No application backup service or scheduled database backup job is configured by this product. Copies in device or infrastructure backups, if present under platform or hosting settings, may remain until those backups expire under the applicable provider settings.
Deleting your information
In Profile & Settings choose Delete all my data and confirm. The app erases its local record file contents and queues authenticated server erasure. If offline, server deletion remains pending and new entries are blocked until a connection permits the request to finish. Once the server confirms removal, the app rotates the installation secret. The server securely deletes live record content and truncates its live SQLite write-ahead log; it retains a hashed revocation marker so an old client cannot repopulate that namespace. Individual records can also be deleted in their details; deletion synchronizes as an empty tombstone. Remove exported files and copies you shared separately, as the app cannot revoke recipients’ copies. Removing the app alone does not send a server erasure request. Without the installation secret, server records cannot be recovered or reliably linked to a deletion request solely from a name or email address.
Permissions and your choices
The system Photos picker lets you select specific images without granting broad photo-library access. Only the image you select is imported and resized; the app does not scan your library. You can cancel selection, remove an attachment, or delete the associated entry. Removing the source image from Photos does not remove an imported copy; delete that copy in FairWind as well. Any system permission can be managed in iOS Settings, where available. The app does not request location, camera, microphone, contacts or notification permission. Network synchronization uses normal internet access and can be unavailable while offline.
Your privacy rights
You can view, edit, export and delete your records in the app. Depending on your location, you may have rights to access, correct, erase, restrict or object to processing, request portability, or complain to your local data protection authority. For privacy questions or rights requests contact aubrey5.fleetwood@icloud.com. This address is a public privacy contact only and is not an app login or delivery feature. Provide only information needed for your request and never email the installation secret. Because the service has no accounts or email directory, the installation-authorized app controls are the reliable way to access or delete the correct records.
Security
The deployed app communicates over HTTPS. An automatically generated, installation-specific random secret is stored in the device Keychain and authorizes the server namespace. The secret is not shared between installations and is not embedded as a common credential in the app. The server hashes the bearer value for storage separation and rejects requests without valid authorization. SQLite transactions, request size limits, per-namespace rate limits and local atomic file writes protect normal data handling. The local file uses iOS data protection until first unlock after restart. This is not end-to-end encryption: the service processes record contents to store and synchronize them. No system can guarantee absolute security, and loss of the installation secret prevents recovery through a login.
Children’s privacy
FairWind is intended for sailing enthusiasts and athletes and is not designed as a service directed at young children. It does not ask for birth dates or create child accounts. A parent or guardian supervising a young sailor should avoid entering unnecessary personal details or photos. If you believe a child’s information was submitted improperly, contact aubrey5.fleetwood@icloud.com; use the installation’s in-app deletion control where available.
Changes to this policy
This policy reflects the application and service practices as of its effective date. Changes to processing will be reflected in an updated policy at this same public privacy path, with a revised effective date. Review it when updating the app or before entering new types of information. Material changes will be described through the updated app or policy as appropriate.