Who is responsible
Hoskary is operated by Aboubacar Bah. For account, subscription and service-administration data, the operator determines how that information is used. For guest information supplied by a hotel, the hotel determines its purposes and is responsible for authorising the processing; Hoskary processes that information to provide the hotel’s requested service. Contact the operator using the email below. Guests can also contact their hotel about reservation data.
Google sign-in and your account
Google sign-in provides basic identity information such as your name, email address, profile image and Google account identifier. Supabase handles authentication and stores your account and session information; Hoskary uses the verified identity to protect your workspace, manage access and associate your subscription. Your account email may also be used for billing through Stripe. Google profile data is not included in the hotel summaries sent for AI analysis. Hoskary does not request Gmail inbox, Drive, Calendar or contacts access. We do not sell Google user data or use it for advertising or model training.
Hotel files, connections and AI
Imported property files and calculated dashboard data are processed and stored in your browser. When you authorise a supported property-system connection, the server requests relevant reservation information from that provider for your review. AI analysis is optional: after you confirm a request, the calculated hotel summary and selected question are sent through our server to the AI service. Voice evaluation sends microphone audio and the hotel guide to the voice service after consent. Avoid uploading unnecessary identifiers, payment-card details, identity documents, medical information or door-access codes.
Telephone calls and enquiries
When a hotel enables telephone reception, its telephone provider handles the call, caller number and speech transcription. Caller statements and the approved hotel guide may be processed by the AI service to produce an answer. Guest-enquiry capture is separate: after the caller consents, Hoskary can save the caller number, spoken name, stay request, language, summary, relevant statements and consent time for authorised hotel staff. A staff transfer shares call-routing information with the telephone provider and receiving staff. Provider-held call logs or recordings follow that provider’s settings and policies.
Providers, payments and international processing
Cloudflare hosts the website and server-side records. Supabase provides account authentication. Stripe processes payments, invoices and payment-method changes; Hoskary stores subscription identifiers, plan, payment status and access dates, not full card details. Google, property-system providers and optional AI, voice and telephone providers process the information needed for their functions. Hosting and authentication providers may process technical request data for operation and security. Providers may process data outside your country, including the United States; their applicable terms describe locations and transfer safeguards. Contact us for information about transfers relevant to your account.
Why information is used
Account and subscription information is needed to provide and administer the requested service. Security and abuse-prevention processing supports our legitimate interest in keeping accounts and systems safe. Financial records may be needed to meet legal obligations. Optional microphone processing and saved guest enquiries use the consent requested in the relevant flow. Hotel-supplied guest data is processed for the authorised hotel’s service purposes. Account identity is required for a protected workspace; optional AI and voice evaluation can be declined. Pricing and marketing suggestions remain subject to human review.
Storage and retention
Browser files remain on the device until you remove them or clear browser storage; keep your own backup. Signing out does not erase these files. Account and subscription records are retained while needed to operate the service, handle account requests and satisfy financial or legal obligations. Saved guest enquiries are scheduled for removal 90 days after creation; authorised staff can remove their personal content sooner. Transfer-attempt records are scheduled for removal after one day and processed billing-webhook records after 30 days. Separate provider records and backups follow their retention settings; deleting a Hoskary record does not automatically delete a provider’s records.
Your choices and rights
You can stop optional AI or voice requests, remove imported files and revoke Google access through your Google account’s connected-app settings. To request account deletion, access, correction, a copy of your data, restriction or objection where applicable, email the operator. We may need to verify your identity and retain records required by law. Withdrawing consent does not undo processing that was lawful before withdrawal. Where GDPR applies, you may complain to your data-protection authority; rights requests are normally answered within one month, with any permitted extension explained. For hotel-controlled guest data, contact the hotel first.
Browser storage, security and updates
Hoskary uses browser storage for sign-in sessions, language choice and account-scoped property data. No advertising tracker is added by the app; third-party hosted pages have their own storage practices. HTTPS, verified authentication and account-scoped access protect service requests, but no service can guarantee absolute security. Use a trusted device and avoid sharing an active account. This service is intended for professional hospitality users. Material changes to this policy will be communicated through the service or account contact channels; new data uses requiring consent will request it before processing.