1. Product and account scope
Guester is a browser-based service offered under The Artifics brand that helps hotel operators assess reviews, market indicators, hotel records and selected workflows in one panel. Contractual service scope is determined by the accepted account/order summary and module-enablement records. Listing a module here does not mean it is enabled for every Customer.
This document applies with the Terms of Service. Available properties, roles, connections, usage limits and pilot commencement are determined from account records. Guester is not an independent hotel operator; the seller of accommodation and guest-facing additional services is the hotel or the provider identified on the relevant screen.
Guester runs on private-cloud and cluster infrastructure. Infrastructure service providers are Sunucun and Netlen; the physical facilities identified in the inventory are Mars Datacenter Istanbul-1 and DATACASA Istanbul-1. Primary Hotel databases and PMS reports are stored on infrastructure supplied through Sunucun. The panel frontend displays API data and does not operate an independent persistent Hotel/PMS database. Browser display, sessions and transmission, and website application records, are assessed separately. Actual data routes and provider roles are described in Subprocessors and Data Flows; a physical facility location does not establish that external services also process in Türkiye or that Guester holds a particular Tier/ISO certification.
2. Reviews, reputation and guest experience
Review functions may include retrieval from supported sources, classification, theme and sentiment analysis, translation, response drafting and reporting by date/source. Connections to your own property accounts and collection from public sources are distinct processes. Survey creation and sending are available only within the relevant account scope, communications authority and sending settings.
Review collection options are not configured to restrict access to public review opportunities based on whether a guest's evaluation is positive or negative. An AI association between a review and a staff member or department is not an established incident record. Incorrect matches and drafts must be corrected; an automated score alone is not grounds for adverse employee decisions.
3. Competitor and market analysis
Market tools may compare supported-source room offers, historical observations, review indicators, events and weather information. Sources may include Booking.com, Agoda, Google and other supported OTAs and review services; collection may use browser-based retrieval, an API or Apify actors. Current sources and recipients are described in Subprocessors and Data Flows.
The observation time, room type, occupancy, stay dates, taxes, currency and cancellation conditions form part of the comparison. An OTA offer is not presented as realised ADR or collected revenue. Records may be missing, delayed or blocked by the source. The Provider assesses its own collection methods; Customer connection authority is not a general licence for platform or competitor content.
4. PMS and hotel records
PMS connections may retrieve or analyse reservation, room, stay, pricing and related operational reports in supported accounts. The source may be the hotel's own OPERA/SFTP report transfer or a separately authorised API. A connection working for one hotel does not guarantee the same fields or actions for another PMS version.
Personal data is limited to fields genuinely necessary for the selected processing. There is no blanket authority to use guest names, contacts, country or nationality, dates of birth and free text in every module. Country information is not automatically treated as nationality. Health information, identity documents and full card data are excluded unless a separately assessed purpose is expressly supported; the DPA applies.
5. Channex and communications connections
Channex may support property, room-type and rate-plan mapping, distribution of rates/availability/restrictions and retrieval of reservation flows for supported, hotel-authorised channels. Live use of Channex does not mean that all channels and write functions are enabled for every Customer. Channel acceptance, identity mapping and third-party results must be monitored.
Email, Google Business Profile, survey and external AI/MCP connections are in scope only where the relevant connection and function are enabled. The Customer's choice of email provider affects the recipient and flow. Chat drafts or local reports and sending messages or updates externally are separate permissions; AI and Automation Authority governs that distinction.
6. AI and team functions
AI may support review analysis, translation, response drafting and panel chat. Current routes include Cloudflare Workers AI, Gemini chat services and multi-model routing through OpenRouter, including Google/Gemini and Anthropic/Claude. Modules, data fields and actual serving providers depend on enabled configuration; the model developer and actual serving endpoint may be different parties. New providers such as OpenAI may be added after the required notices and processing/transfer conditions are completed; this document does not identify OpenAI as currently active. Actual recipients, model endpoints and transfers are limited to the data-flow scope; a model brand alone does not guarantee retention, location or training arrangements.
Team functions may display authorised personnel, department, shift and task records or review associations. Employer notices, role restrictions and human review are preserved. Undisclosed chat context, conclusive automated employee performance judgments or outputs containing another hotel's information are not assumed to be part of the accepted service. External actions are kept disabled by default.
7. Portal, implementation and support
An enabled guest portal may provide access to hotel content, contacts, surveys or information about offered services. The hotel keeps sales, cancellation and guest notices aligned with its operations. Maps, images and external links may cause browser requests to separate providers; local databases alone do not establish that all flows remain in Türkiye.
Implementation may include property/user settings, configuration of supported connections and standard remote guidance within the accepted scope. Migration, custom development, on-site training or other system installation are excluded unless separately accepted. Support and maintenance are governed by the Support and Service Level Agreement (SLA); personal data and security are governed by the DPA.
8. Limits and document date
The service does not guarantee that the hotel can discontinue its own PMS and continuity arrangements without assessment. Legal, tax, payroll, consumer-compliance and guaranteed revenue advice are excluded. Unsupported payment/POS, fiscal-document creation, sustainability and out-of-scope modules are not promised. This document creates no guarantee of revenue increases, absolute security, a specific uptime percentage or completeness across every source.
Version: 3.3. Updated: 13 October 2026. Any ambiguity between module descriptions and account scope is clarified before activation. Material scope changes follow the express-acceptance and notice process in the Terms of Service; updating this page alone does not automatically change an earlier agreement.