Equistar AI
Conformation & biomechanics analyst
Welcome!
GDPR privacy notice
Equistar AI is operated by Coralsystem Kft., 2045 Törökbálint, Otelló utca 7, Hungary (tax number: HU14310364). Contact for privacy requests: coral@coralsystem.hu.
Images are processed temporarily, in memory, for the duration of the analysis request. Equistar AI application code does not save uploaded photos to its cloud database or file storage. Photos and scan history are saved only in app storage on your device. A resized JPEG copy is sent securely through Lovable's AI service to OpenAI for analysis; re-encoding removes embedded photo metadata. Photos selected from your library are not removed or changed there. The in-app camera saves a processed scan copy, not a separate full-resolution original in Camera Roll. Clearing app/browser storage can permanently remove local scans. AI service logging and retention are separate from our application's local storage and are described below.
OpenAI states that API inputs and outputs are not used to train its models by default, unless the API customer opts in. No training opt-in is implemented in this app. No-training is not the same as Zero Data Retention (ZDR): OpenAI's standard API abuse-monitoring logs can retain content for up to 30 days, and ZDR requires approval and compatible endpoints. This app currently calls OpenAI through Lovable, not a directly configured OpenAI account. ZDR, gateway request-log retention and the applicable upstream account settings have not been verified for this app; we do not claim that the complete provider chain is retention-free. Avoid including people, documents or other personal information in horse photos. OpenAI's current data-control terms: developers.openai.com/api/docs/guides/your-data.
Lovable Cloud processes your account email, authentication data and information supplied by your chosen sign-in provider. Your password is handled by the authentication service and is not included in exports or AI requests. Protected subscription status and photo-analysis usage timestamps are stored centrally to enforce plan allowances across devices: 2 Free photo attempts per calendar month, 60 per month on Pro Monthly, 600 per year on Pro Yearly and 1500 per year on Premium, resetting on the first day of the period in Central European Time. Usage records contain no photos or horse names. Submitted attempts count, including imperfect photos and attempts whose AI response fails after reservation; there is no separate retry allowance. Only provider-verified subscriptions can grant paid access.
Horse profiles, health journal entries (care notes, professional names and next-care dates), processed photos, scan results, contacts, calendar entries, favourites, rides and Star conversation history are stored in this device's app/browser storage. Health journal entries are not sent to AI or shared reports; next-care dates appear in the local calendar and startup reminder. They are included in Download my data and removed when deleting the horse or local data. They are not synchronized to our account database. A new device will not automatically have these records. Export a backup before clearing storage or uninstalling the app. Shared written reports and messages sent to other users are exceptions described below.
Ride GPS points, speed-estimated gait duration/distance totals and route markers are kept on your device and are not sent to OpenFreeMap. To display the map, your device requests map tiles from OpenFreeMap; those requests reveal the map area and viewport being viewed, but not your exact GPS coordinates or route markers. In the native app, background location permission lets Equistar AI record your ride while the app is in the background; you can manage or revoke this permission in your device settings. In a browser, tracking may stop when the screen is locked.
When mobile purchases are configured, RevenueCat processes your Equistar account ID, purchase receipts, transaction identifiers and subscription status to validate access. Apple App Store or Google Play handles store billing. No horse photos or analyses are sent to RevenueCat. Billing records may have separate legal retention requirements; contact coral@coralsystem.hu for access or deletion requests concerning these records. Deleting your Equistar account or uninstalling the app does not cancel store renewal. We cannot intercept the phone's uninstall action. Before deleting, manage cancellation in the store where you subscribed. Account deletion remains available immediately even with an active subscription; it removes access to that account. Cancellation alone normally preserves access until the paid period ends. Unused prepaid time is not automatically refunded, subject to mandatory consumer rights and applicable store refund decisions.
Community is now private one-to-one messaging, not a public chat. The contact dropdown lists only contacts saved for your signed-in account on this device. Contact names, phone numbers and email addresses remain local. Optional vet and trainer details entered in New scan are also added to your own on-device Contacts. Connecting a contact sends only their entered account email to our authenticated service to find a confirmed Equistar account; no global user directory is provided. The cloud stores the resulting owner/contact account-ID link to enforce contact-only sending. Recipients need to add you to their own contacts before replying. Removing a connected contact removes your sending link but does not erase past messages. Account switching does not reveal another account's contact list. Older unassigned device contacts are not automatically assigned to an account.
Message content, sender display name, sender/recipient account IDs and timestamps are stored centrally and readable only by the conversation participants. Enabling phone notifications is optional and requires device/browser permission. We store a device notification token, platform and registration time for your account; Firebase/Google and Apple notification services process delivery identifiers and a generic new-message notification. Notification previews intentionally omit message text and sender name. Tokens are not displayed to other users. A messaging-only browser worker receives background notifications and does not cache the application for offline use. Disable notifications in Community or revoke permission in device settings. Device registration is not proof of current installation; an unavailable notification does not prove the app is uninstalled. Messages remain available at the next sign-in even if no notification can be sent. Delivery can fail or be delayed; use another channel for urgent matters. Native notification delivery still requires platform setup and real-phone verification.
Star conversation history stays on your device, but each support request sends your message and recent conversation context through Lovable's AI service to OpenAI. Do not put sensitive personal information in chats. The provider-retention caveat above also applies to Star.
Creating a share link stores the horse name, selected recipient label and written results and scores in the cloud, without photos. Anyone possessing the link can view it until it expires or is revoked; it is a link-access report, not recipient-identity verification. Links expire after the selected 1, 7 or 30 days. PDFs are created on-device and may contain photos; sharing or downloading a PDF sends it to the destination you choose, outside the app's control.
Account management, requested AI analysis, messaging, sharing and subscription validation are processed to provide the service you request (Article 6(1)(b)). Necessary security, error handling and enforcement of usage limits rely on legitimate interests in protecting the service (6(1)(f)), subject to your rights. Legal billing and compliance obligations may rely on 6(1)(c). Device camera/location permission allows requested features; permission alone is not a blanket consent to unrelated processing. Account details are required for cloud features; local records can be used without uploading them for analysis. Revoking camera or location permission disables the corresponding feature.
Lovable provides the managed Cloud account/database service and routes AI requests to OpenAI. Other recipients include your selected sign-in provider, RevenueCat and mobile app stores for subscriptions, map infrastructure for displayed maps, and people you choose to message or share with. This project uses Lovable Cloud; importing a database client does not establish a direct customer contract with the underlying database vendor. Coralsystem Kft. must confirm the applicable Lovable Data Processing Agreement, subprocessor list, processing regions and international-transfer safeguards before commercial operation. A separate vendor DPA is needed only where Coralsystem contracts with that vendor directly. A DPA or Standard Contractual Clauses alone do not certify GDPR compliance; applicability and coverage must be verified. Ask coral@coralsystem.hu for confirmed processor and transfer information.
Local records remain until you delete them or clear app storage. Legacy public Community messages are no longer publicly readable, but remain for owner export and account deletion. Direct messages remain until applicable deletion/account removal; account deletion removes messages involving you, your messaging links and notification tokens. Notification tokens are removed when disabled, when the delivery service confirms they are unregistered, or on account deletion; local storage deletion alone does not remove their server registration. Clearing local data does not delete cloud contact links; use account deletion or contact removal for those. Accounts, subscription profiles and usage timestamps remain while the account exists. Report expiry/revocation blocks access but does not automatically erase the stored report; account deletion removes it. Provider logs, backups and statutory billing retention follow separate schedules not yet verified for this deployment. Contact coral@coralsystem.hu for details.
The app uses local storage for its sign-in session and your on-device records; no advertising trackers are intentionally implemented. Runtime error-reporting hooks may send diagnostic messages, stack traces and page paths to Lovable, particularly in the editor preview. Uploaded photo bodies are not intentionally logged by application code. Provider telemetry, cookies and retention must be checked in the published service before making a blanket tracking-free claim. External links and store services apply their own policies.
Where applicable, you may access, rectify, erase, restrict or port your personal data; object to processing based on legitimate interests; and withdraw consent where consent is the legal basis, without affecting earlier lawful processing. Use Download my data, Delete data on this phone or Delete my account below, or write to coral@coralsystem.hu for correction, restriction, objections or provider-held records. Downloads include local records and account-owned application records, but not authentication secrets, provider AI logs or app-store records. Requests are answered without undue delay and normally within one month; a justified extension of up to two further months will be communicated within the initial month. Reasonable identity verification may be required. You may complain to the Hungarian authority NAIH (naih.hu) or your local supervisory authority.
AI scores and recommendations are automated, may be inaccurate and are not veterinary diagnoses. They do not make legal or similarly significant decisions about you. Do not rely on a photo score alone for animal health or safety decisions; seek qualified veterinary advice for concerns.
Updated 25 October 2026. This notice describes the implemented application flows and explicitly identifies unverified provider arrangements. It is not a certification of GDPR compliance; commercial launch requires confirmed processor agreements, retention/transfer settings and legal review.