English · العربية
Privacy policy
Khaili is an offline-first horse and stable management application operated by Zayed Albloushi. This policy applies to the complimentary TestFlight beta for an unspecified number of stables, their authorized users, and private horse owners selected and invited by Zayed Albloushi.
Data we handle
Khaili handles email address, account profile, workspace membership and permissions; horse identity and ownership data such as name, optional private profile photo, breed, sex, birth date, stable location, microchip, passport and registry details; privately stored documents; health and care records including checks, measurements, medications, vaccinations, veterinary visits and readiness evidence; tasks, programs, workouts, rides and reminders; internal Stable Notes and optional Inventory records; support, exports and deletion requests; device and synchronization security records; and minimal operational audit and diagnostic events. A user-started ride may include precise or approximate GPS route, timestamps, distance, speed and device-motion measurements.
Disabled features
Paid AI Advisor generation, consumable credit purchases and the new case workflow are production-disabled until provider evaluation, Apple and Google store testing, disclosure publication and explicit release approval are complete. SMS signup, Apple subscriptions and Stripe billing are also disabled. Do not submit payment credentials. Clinical and identity information may be entered only by users authorized by the horse owner or stable and must not be treated as a substitute for official source records or professional care.
Paid Advisor processing if later activated
After the workspace accepts the current disclosure, a connected request may send bounded recent messages and authorized minimized records to the single active evaluated OpenAI or Anthropic model. Khaili excludes identity, workspace name, contacts, raw documents, unrelated records, raw ride routes and raw motion. Emergency checks run before billing and are free. Sensitive horse decisions go to assigned professionals, and private drafts are not shown as owner advice before approval. Apple or Google handles consumer payment; Khaili verifies store proof server-side and does not retain raw receipts, purchase tokens or card details.
Why we use data
We use permitted data to authenticate users by email, provide authorized stable operations, support offline work, record a ride when requested, synchronize approved devices, enforce access and the 40-active-horse limit, deliver reminders, create exports, process deletion requests, respond to support and investigate reliability or security incidents.
Sharing, hosting and processors
Records are available only to people authorized for the relevant stable workspace or horse. Supabase provides authentication, PostgreSQL, private storage and required server functions, with the pilot project hosted in Mumbai, India. Resend delivers email sign-in codes and privacy-safe service alerts. Cloudflare hosts the public policies, support pages, admin web application and five-minute scheduler. Apple provides TestFlight distribution and device services. Nothing is translated automatically. If translation is enabled, you must choose a specific language and explicitly request translation before the selected observation or report text is sent through a protected Supabase function to Microsoft Azure AI Translator. Khaili stores only content-free usage metadata for rate and free-tier controls; machine translation must be checked against the original. For beta reliability, signed-in builds may send error class, build/platform, phase, timing, network state and a pseudonymous account fingerprint to the same Supabase project. The collector rejects horse, clinical, note, email, token, URL and ride-route content and retains accepted events up to 30 days. Khaili uses no third-party telemetry SDK. Calendar sync starts only after you select Add to Calendar and grant access. Khaili creates a dedicated calendar and writes only category, horse name and time for authorized entries during the next 90 days. It reads calendar-account metadata and its own mapped events only, and never imports, stores or transmits unrelated calendar events. These processors may handle network and service metadata under their own terms. Khaili does not sell data, use advertising or perform cross-app tracking.
Ride location, motion and optional research
Ride recording starts only after an explicit user action. Location may continue while that active ride is in the background and the operating system displays its location indicator. A user may deny permission and manually log a ride. An eligible user may separately opt in to ride research. With explicit, revocable consent, pseudonymized ride context and raw motion samples may be uploaded for gait and ride-quality research. Withdrawing consent stops future research collection and starts the applicable deletion or de-identification process; the normal ride record remains controlled separately.
Offline storage
Authorized records may be cached on your device so core work can continue offline. Credentials use platform-protected storage. Encrypted ride batches are processed on the device; the operational route and summary can synchronize to the authorized workspace. The app revalidates access, applies an offline authorization time limit, locks expired caches, and purges data after logout, account switching, deletion, or detected access revocation. Offline devices cannot learn about revocation until they reconnect or the authorization lease expires.
Backups, retention and deletion
The hosted pilot uses daily backups with a seven-day provider retention window. The operational backup objective is no more than 24 hours of data loss and the recovery target is four hours after the operator confirms a recoverable incident; these are targets, not guarantees. A deleted ride is recoverable for 30 days before route data is purged. Account holders can initiate deletion inside Khaili under More → Privacy and account. Direct identifiers, credentials, device registrations, memberships and private exports are removed when deletion completes. Deletions may remain in encrypted backups until those backups rotate out. Shared operational records may require transfer, workspace deletion review or pseudonymized retention for other authorized users and security audit.
Your controls
The app provides account-data export, account-deletion initiation, research-consent withdrawal, language, notification and calendar-sync controls, and support access. Calendar sync can be disabled while keeping existing events or by removing the managed calendar. Export links are private and short-lived. Contact info@khaili.ae for privacy or support.
Security and limits
Khaili uses row-level authorization, protected server functions, private storage, short-lived links, local purge controls, and encrypted platform credential storage. No system is risk-free. Horse-care information is an operational aid and does not replace a veterinarian or emergency service.
Children and changes
Khaili is intended for authorized stable professionals and adult account holders, not children. Material changes will be dated and published at https://khaili.ae/privacy.
Khaili