Privacy Policy
Seeking for Pro
This policy explains how this application handles information and how to contact us about privacy.
Information we process
Seeking for Pro stores your finds, selected or captured photographs, signal observations, outing plans and timers, ordered visit plans and recorded route points, text addresses, optional coordinates, equipment profiles, research notes, collections and preferences on your iPhone. You do not create an account or provide a login email. When you enable optional metadata sync, find, outing and signal metadata, including notes, linked context and any recorded coordinates, are transmitted to our backend; photo bytes are excluded. When you choose encrypted cloud backup, the complete diary, including photographs and other sections, is encrypted on your device before upload. A random installation secret authorizes private requests; a separate encryption key stays in Keychain. The server stores a hash of the installation secret, scoped metadata, timestamps, deletion markers and the latest encrypted backup. Requests to the public website or API also reach Railway infrastructure, which can process network addresses, request timing and operational logs.
How we use information
Local information powers your private collection, research notebooks, signal comparisons, outing timing, equipment history, statistics, reminders and exports. Optional server processing provides installation-scoped metadata synchronization and storage of the latest encrypted backup. Operational request information is used to deliver, secure and diagnose the hosted service. We do not use advertising, behavioral analytics, account registration or outbound email delivery services.
Service providers and sharing
The backend and public privacy page are hosted on Railway, which processes service data and infrastructure request information as our hosting provider. Apple system services handle your device permissions, Keychain, photo selection and local notifications. The app contains no third-party analytics, advertising or mapping SDK. Data leaves the diary when you enable synchronization, request a cloud backup, or choose an export destination through the iOS file interface. Anyone you share an exported file with receives its contents under your control. The app does not publish your diary or make it accessible to other installations. No additional recipients are integrated by this application.
Data retention
Local records remain until you delete them, replace the diary through restore, or remove the app; exported files remain wherever you saved them. Keychain installation and encryption keys can survive app removal on the same device according to iOS behavior. Server metadata and the latest encrypted backup remain until replaced or deleted for that installation. Minimal deletion markers are retained during metadata sync to prevent stale records returning. The service has no automatic expiry schedule. We have not configured a separate application backup or log archive schedule. Railway operational logs and any infrastructure backups follow the provider and project configuration; no fixed retention duration or immediate removal from provider backups is promised.
Deleting your information
Delete a find to remove its local photographs, notebook and linked signals. Other records have explicit deletion controls. When sync is enabled, record deletion is sent as a marker without the deleted content. Delete All Local Data clears the on-device diary and turns sync off; it does not delete previously exported files or existing cloud data. Delete Cloud Data removes the current installation’s server records, deletion markers and encrypted backup, turns sync off, and leaves the local diary intact. Re-enabling sync or uploading another backup creates server data again. Cloud deletion requires network access and the installation secret. Remove exported files separately in their destination. Logical deletion does not guarantee forensic erasure of device storage, database journals or infrastructure backups, whose lifecycle is controlled by the storage provider. There is no recovery process after installation keys are lost.
Permissions and your choices
Camera access is requested only to photograph a find or research detail. The system Photos picker shares only images you select and does not require broad photo-library access. Location When In Use is requested when you explicitly record coordinates or an outing route point; the app does not request background location or display geographic maps. Notifications are optional local reminders scheduled from planned outings, with no push messaging service. You can deny or withdraw camera, location and notification access in iPhone Settings, continue entering records manually, and remove scheduled reminders inside the app. Turning off permissions does not erase previously saved information; delete it using the diary controls. Cloud sync is off by default and can be turned off in Settings.
Your privacy rights
You can view and edit your diary, export CSV or PDF reports, make a full local backup, restore a backup and delete local or server data through Settings. Exact coordinate fields are excluded from CSV and PDF by default, but a full backup includes all fields; free-form notes may contain any details you enter. Depending on your location, you may have rights to access, correct, delete or restrict processing of personal information and to contact your data protection authority. Send privacy questions or requests to hi@nezapotoc.boats. No in-app email delivery or support account is required. We cannot identify an installation from an email address alone and do not ask you to send its secret or encryption key.
Security
Private API requests use HTTPS and a random 32-byte secret stored in device-only Keychain storage. Every server query is scoped by the hash of that secret. Cloud backups are encrypted with AES-GCM on the iPhone using a separate device-held key that is not uploaded. Synced metadata is authorized but is not end-to-end encrypted; the backend must process it. Local diary files use iOS file protection and atomic replacement. The application does not log record contents or authorization secrets. Hosting administrators and infrastructure may access unencrypted server metadata and operational information as needed to run the service. No storage or network system can be guaranteed completely secure. Protect your device and any unencrypted local backups or exports you create.
Children’s privacy
Seeking for Pro is intended for hobbyists and experienced detector users rather than children. We do not knowingly solicit information from children or provide child profiles. If you believe a child has provided personal information through the service, contact hi@nezapotoc.boats so we can assess an appropriate deletion request. Field activity must follow applicable safety, access and heritage rules.
Changes to this policy
We may update this policy when application processing or hosting practices change. The current policy is available through the app’s Privacy Policy link and the public /privacy page. The effective date identifies the version currently published. Review the policy before enabling optional cloud features after an update. Privacy questions can be directed to hi@nezapotoc.boats.