Privacy Policy
Feet Fighter Club
This policy explains how this application handles information and how to contact us about privacy.
Information we process
Feet Fighter Club uses no user accounts. When the app connects, the server creates a random installation identifier and secret. The secret is stored in this device’s Keychain; the server stores a hash. Your chosen name, city and biography, saved walk identifiers, surface, time, duration, step count, distance, club memberships and meeting participation are stored on the server and cached locally. Route bookmarks, blocked-person identifiers, unsent chat messages, a paused walk draft and your chosen avatar remain on this device. Location coordinates are used temporarily on this device to calculate distance and are not uploaded or retained as a route trace. Community warnings, reviews, chat messages, reports and photos you choose to share are sent to the server. Photo uploads are re-encoded to remove metadata. Requests to our website and API also expose network information such as IP address, request path, timing and response status to the hosting infrastructure and server logs.
How we use information
We process installation credentials to authorize access to private data; profile details and membership to operate walking clubs and meetings; walk totals to maintain your history and calculate achievements; messages and shared photos to support meeting conversations and club photo reports; and reports to let administrators moderate content. Location and motion are used only for walks you explicitly start. Local notifications provide reminders you request. Network and server information supports delivery, rate limiting, security and troubleshooting. We do not include advertising, analytics or outbound email delivery services.
Service providers and sharing
The backend and persistent database are hosted on Railway, which processes requests and infrastructure information as our hosting provider. Public city, route, club and meeting descriptions and aggregate membership counts are available without a secret. Profile names and installation identifiers are visible with club membership and authored contributions. Route warnings and reviews are readable by connected installations; chat messages and meeting participant details are restricted to meeting participants who belong to the club; shared photos are restricted to club members. Administrators can review reports and moderate content using a server-side administrative token. Your personal walk history and full profile are restricted to your installation. Apple’s system photo picker, Calendar editor and local notification system handle the device features you invoke. If an organizer provides an external HTTPS route photograph, loading that photograph contacts its host. We do not sell personal information or add unrelated third-party SDKs.
Data retention
Profile, walk, membership and authored community data remain in the active database until you delete your installation data or an administrator removes applicable content. Local history, settings and pending records remain until cleared through the app or removed with device data. Rate-limit counters are kept in process memory and expire according to their request windows or server restart. Hosting and operational logs may be retained under Railway’s applicable practices; we do not assert a fixed retention period for those logs. No application-managed backup or fixed backup expiration schedule is configured. Infrastructure snapshots, existing device backups and database journal remnants may have separate lifecycles and are not guaranteed to disappear immediately after active-record deletion.
Deleting your information
Use Profile, Settings & Privacy, Delete My Data while connected to delete the server profile, walks, memberships, meeting participation, messages, warnings, reviews, reports and uploaded photos belonging to this installation. The server revokes its secret and the app clears local records and avatar and cancels pending app reminders. Calendar events you saved are controlled separately in Calendar. Revocation prevents the old secret from accessing the service. Active database deletion does not promise immediate physical erasure of infrastructure logs, journals or any existing backups. If you uninstall the app or lose the secret before deleting, we cannot offer login recovery or guarantee that we can identify your installation from a name alone. Contact corinkershaw@icloud.com with privacy questions; do not send your installation secret.
Permissions and your choices
Motion & Fitness permission enables step counting and location while using the app enables distance calculation during an active walk. If either is unavailable, the timer still works and unavailable measurements are explained. Backgrounding pauses tracking. The system Photos picker grants access only to the images you select for a local avatar or club photo upload; the app does not request full photo-library access. Add to Calendar opens Apple’s event editor, where you choose whether to save an event; the app does not read your calendar. Notifications are requested only when you choose a meeting reminder. You can withdraw location, motion or notification permissions in iOS Settings, stop selecting photos, and manage saved events in Calendar. Withdrawal does not delete previously saved records or previously shared photos; use Delete My Data for those records.
Your privacy rights
Depending on where you live, you may have rights to access, correct, delete or restrict processing of your personal information and to raise concerns with a relevant authority. The app lets you edit your profile, review your walk history, block people and delete your installation data. For privacy requests or questions contact corinkershaw@icloud.com. We may need information sufficient to identify the relevant data and verify authority without requesting your secret. There is no account-based data transfer or recovery on another device.
Security
The deployed service uses HTTPS. Private endpoints verify a unique random installation secret, stored in Keychain on the device and as a hash on the server. Chat authentication is sent in the first encrypted WebSocket message rather than in a URL. Server-side membership checks protect chat and photos; payload limits, image validation and database transactions protect service operation. Administrative access uses a separate server token that is not embedded in the app. Local record files use iOS file protection. No system is perfectly secure; protect access to your device and avoid sharing private information in community posts.
Children’s privacy
Feet Fighter Club is intended for adults interested in outdoor walking, not for children. We do not knowingly seek children’s personal information. If you believe a child has provided personal information, contact corinkershaw@icloud.com so the concern can be investigated. Community descriptions and warnings do not replace personal supervision or assessment of outdoor conditions.
Changes to this policy
We may update this policy when the app’s processing or service operation changes. The current policy is available at this public privacy page and from the app’s Settings & Privacy screen. Its effective date identifies the current version. Material changes will be described in the updated policy and, where required, communicated through an appropriate app notice.