SELENSITY
Privacy policy / SELENSITY
Last updated: 18 November 2026
SELENSITY is published by HALBCO LLC, 30 N Gould St Ste 52443, Sheridan, WY 82801, USA. For privacy questions or data requests, email support@halbco.com or visit SELENSITY support.
Account and device information
The current app requires an email address and password to sign in, including to access the exercise catalog. The server stores your email and a password hash, account identifier, language, time zone, unit preference and account timestamps. It also stores device sessions, including a randomly generated device identifier, a generic device/platform name and session activity and revocation times. The app stores session credentials and its device identifier in secure local storage.
Training records and synchronization
SELENSITY stores and processes the information you enter: custom exercises and favorites, programs, routines and schedules, workouts and exercise sets, loads, repetitions, duration or distance where relevant, notes and optional body mass. Workout history, corrections and statistics are derived from these records. Body mass is not required.
The app keeps records in a local database and sends account-linked changes to the server for synchronization across devices. Synchronization includes device and record identifiers, versions, pending operations, conflict information and deletion markers. Offline changes remain on your device until they can synchronize. Removing the app before synchronization can lose those changes.
Imports, exports and notifications
You can select a training-plan file to import and export plans as JSON or PDF through the device share sheet. The selected receiving app or recipient handles what you share. A plan export is not a complete export of all account or workout data.
Local notifications can provide workout reminders and timer alerts when you grant the required permission. You can manage reminders and workout preferences in Settings. These local notification features do not require an advertising identifier.
Services, analytics and technical records
The current app has no advertisements, in-app purchases, subscriptions, advertising trackers or third-party product-analytics or crash-reporting SDKs. Its training statistics summarize your own workout records rather than sending product-analytics events to a separate analytics provider.
HALBCO's API and its hosting and database infrastructure process account and synchronization requests. The API uses the incoming IP address for authentication request limits and keeps operational error records for reliability and investigation. Exact retention periods for technical logs, synchronization history and backups are not specified here; contact us about a particular record or request.
Support correspondence
When you email support, we receive your email address, message and any files or diagnostic information you choose to include. We use them to investigate and respond. Email services process the correspondence for delivery and storage. Do not send passwords, session tokens or information you do not want to share.
Managing and deleting data
You can edit your preferences and manage device sessions in Settings. Signing out or revoking a session ends that access; it does not delete your account. Deleting individual workouts sends deletion markers through synchronization. Removing a custom exercise or routine does not necessarily remove its name or snapshots from workout history and correction records.
The current app has no account-deletion control or automatic account-deletion schedule. To request deletion of your account, stored training data or support correspondence, email support@halbco.com from your registered address with SELENSITY data deletion in the subject. Specify what you want deleted. We may need information to verify the request, but never ask you to send your password or session tokens.
Removing the app and its data removes local records but does not remove server records. Any device backups or exported copies must be managed separately. Contact us for questions about access, correction or records retained in synchronization history, technical logs or backups; this policy does not promise immediate erasure of every copy.