# GreetScribe Provider Integration Terms **Version:** 2.0\ **Updated:** 2026-09-20\ **Operator:** Qevinto Oy These Provider Integration Terms explain how third-party provider systems and customer-controlled integrations may be used with GreetScribe. These Terms are intended for GreetScribe business customers. --- ## 1. Operator GreetScribe is operated by: **Qevinto Oy** Business ID: 3583823-3 Sarkakatu 3 F23 96460 Rovaniemi Finland Contact: contact@qevinto.com --- ## 2. Scope These Terms apply to provider integrations used with GreetScribe. Provider integrations may include: - Bokun; - Hostaway; - Hospitable; - booking engines; - payment providers; - property-management systems; - channel managers; - CRM systems; - customer-owned booking platforms; - customer websites; - other external APIs selected or used by the Customer. These Terms supplement the GreetScribe SaaS Customer Terms, Data Protection Addendum, Subprocessor List, Security Statement, Support Policy, and Billing, Cancellation and Refund Policy. If a signed customer agreement, written quote, or integration-specific agreement contains different terms, that document controls for that customer. --- ## 3. Integration model GreetScribe may connect with third-party systems to support guest-assistance, availability lookup, booking guidance, activity discovery, stay discovery, recommendations, deep links, and customer-managed booking or payment flows. Integrations may be: - configured by Qevinto Oy; - configured by the Customer; - controlled by the Customer; - controlled by a third-party provider; - manually configured; - API-based; - deep-link based; - enabled only for selected customers or plans. The exact integration behavior may depend on the Customer’s setup, provider account, provider API, provider terms, and written configuration. --- ## 4. Customer-controlled integrations Many provider integrations are customer-controlled. This means the Customer or provider may control: - the provider account; - provider credentials; - API access; - booking rules; - availability data; - pricing data; - cancellation terms; - payment terms; - guest communications; - provider-side support; - provider-side data handling; - provider-side errors or downtime. Customer-controlled integrations may not be Qevinto-controlled subprocessors in every setup. The Customer is responsible for understanding and managing its own provider relationships. --- ## 5. Integration availability GreetScribe contains adapters for customer-controlled availability/booking services including Bókun, Hostaway, Hospitable and Mews. Actual availability and permitted operations depend on the configured adapter, provider account, permissions and agreed setup. A code adapter is not a promise of a working production connection. Guest checkout occurs on the customer's or provider's external booking/payment service. Those providers are separate from Qevinto's own invoice billing. The [Subprocessor List](/subprocessors) describes Qevinto-appointed processors separately. --- ## 6. No guarantee of provider availability Qevinto Oy is not responsible for downtime, errors, pricing, availability, or changes in third-party provider systems. Provider systems may change or become unavailable. Provider systems may impose: - API limits; - authentication changes; - pricing changes; - product changes; - data format changes; - regional restrictions; - account restrictions; - rate limits; - outages; - maintenance windows; - support limitations. Qevinto Oy may need to modify, suspend, replace, or remove an integration if a provider changes its service or if the integration creates security, legal, operational, billing, or reliability risk. --- ## 7. Provider accounts and permissions The Customer is responsible for provider accounts used with GreetScribe. The Customer must ensure that it has: - the right provider account; - valid provider permissions; - valid provider credentials; - authority to connect the provider account to GreetScribe; - authority to process provider data through GreetScribe; - authority to show provider information to Guests; - authority to use booking links, availability data, prices, descriptions, and images. The Customer must not connect an account that it does not own, control, or have authority to use. --- ## 8. Credentials and secrets Provider/API credentials must be supplied through the agreed secure administration process, never through guest chat, public forms, screenshots or unsecured support messages. GreetScribe uses server-side secret references and Scaleway Secret Manager/Key Manager for the relevant credential paths. The Customer must limit provider permissions to the required operations and revoke/rotate compromised credentials promptly. When an integration ends or a credential is no longer needed, Qevinto and the Customer must coordinate revocation and deletion. There is no general right to retain inactive credentials for 24 months. Qevinto remains responsible for its agreed security obligations; the Customer remains responsible for its own provider accounts and permissions. --- ## 9. Provider data Provider data may include: - accommodation availability; - activity availability; - prices; - booking links; - descriptions; - images; - amenities; - restrictions; - cancellation terms; - booking terms; - location information; - provider policies; - guest-facing instructions. Provider data may be incomplete, delayed, inaccurate, unavailable, or changed by the provider. The Customer is responsible for checking that provider data shown through GreetScribe is suitable for Guest-facing use. Qevinto Oy does not guarantee that provider data is accurate, complete, current, or always available. --- ## 10. Customer content and provider content The Customer remains responsible for Customer Content. The relevant provider or Customer remains responsible for provider content. Qevinto Oy may display, transmit, transform, summarize, or route Customer Content and provider content as needed to provide GreetScribe. Qevinto Oy does not assume responsibility for the accuracy of Customer Content or provider content. If Customer Content or provider content is incorrect, AI-assisted or chatbot outputs may also be incorrect. --- ## 11. Booking flow boundary GreetScribe may help Guests move toward a booking flow. GreetScribe may show: - accommodation options; - activity options; - summaries; - recommendations; - booking links; - provider links; - deep links; - call-to-action buttons; - guest-selected details. Final booking completion happens through the Customer’s or provider’s booking system unless separately agreed in writing. GreetScribe does not guarantee that a booking will be accepted, available, priced as previously shown, or completed. Availability and pricing may change before booking completion. --- ## 12. Payment flow boundary Guest booking payments are handled by the Customer, booking provider, payment provider, or third-party booking system. Qevinto Oy does not receive hotel Guest booking payments unless separately agreed in writing. Guest booking payments are separate from GreetScribe SaaS subscription billing. Standard GreetScribe SaaS subscription billing is by invoice under the signed Order. A Customer's external payment provider is a separate service and does not thereby become Qevinto's subscription-billing processor. Customer or provider payment systems may be used separately for Guest booking payments. Qevinto Oy is not responsible for Guest payment disputes, chargebacks, refunds, cancellations, payment-provider decisions, or provider fees unless separately agreed in writing. --- ## 13. Deep links and external booking pages GreetScribe may use deep links or external links to send Guests to a Customer or provider booking page. Deep links may include booking-related parameters, such as selected dates, guest counts, selected property, selected activity, or other context. External booking pages are controlled by the Customer or provider. Qevinto Oy is not responsible for external booking page content, payment processing, availability, pricing, checkout errors, refund handling, or Guest communications unless separately agreed in writing. Guests should review the Customer’s or provider’s booking and payment terms before completing a booking. --- ## 14. Provider API limitations Provider APIs may have limitations. These limitations may include: - missing fields; - delayed updates; - partial availability data; - pricing mismatch; - rate limits; - account-specific restrictions; - endpoint outages; - authentication expiry; - provider-side validation rules; - provider-side errors; - unsupported regions or products. Qevinto Oy may not be able to fix issues caused by provider-side limitations. Where possible, Qevinto Oy may help identify whether an issue appears to be caused by GreetScribe, the Customer setup, or the provider system. --- ## 15. Integration setup and testing Integration setup may require cooperation from the Customer. The Customer may need to provide: - provider account access; - API credentials; - booking URL templates; - property IDs; - activity IDs; - channel IDs; - test data; - allowed domains; - booking terms; - cancellation terms; - payment instructions; - customer content; - support contacts. The Customer must review and test integration behavior before relying on it for live Guest-facing use. The Customer must promptly report errors, incorrect data, broken links, or unexpected booking behavior. --- ## 16. Manual and custom integrations Some integrations may be manual or custom. Manual or custom integrations may use: - manually configured booking links; - booking URL templates; - static provider information; - customer-provided data; - CSV or manual data entry; - custom API mapping; - custom provider routing; - customer-owned booking pages. Manual or custom integrations may have more limited automation than full API integrations. The Customer is responsible for keeping manually configured data accurate and current. --- ## 17. Changes to provider integrations Provider integrations may change over time. Qevinto Oy may update, modify, restrict, replace, or remove integrations. Reasons may include: - provider API changes; - provider terms changes; - provider downtime; - security risk; - data protection risk; - billing risk; - technical incompatibility; - low reliability; - customer plan changes; - provider account problems; - legal or operational requirements. Qevinto Oy may provide notice where practical. Urgent changes may be made without advance notice where needed for security, legal, provider, or operational reasons. --- ## 18. Integration availability by plan Not all integrations are available on all plans. Integration availability may depend on: - plan level; - setup fee; - customer configuration; - provider account type; - provider API access; - geographic region; - technical feasibility; - written agreement; - onboarding scope; - support scope. Qevinto Oy may charge additional fees for custom or advanced integrations. --- ## 19. Customer obligations The Customer must: - provide accurate provider information; - maintain valid provider accounts; - maintain provider permissions; - comply with provider terms; - keep provider credentials secure; - ensure provider data may be processed through GreetScribe; - test integrations before live use; - monitor Guest-facing booking information; - update incorrect Customer Content or provider data; - handle Guest communications, booking disputes, refunds, and cancellations; - maintain its own legal, privacy, booking, and payment terms. The Customer must not use provider integrations in a way that violates law, provider terms, or third-party rights. --- ## 20. Data protection and privacy Customer-directed guest/integration processing follows the [Data Protection Addendum](/data-protection-addendum). The Customer is controller and Qevinto is processor for that service. External providers process information under the Customer's provider relationship and the provider's own applicable terms. Qevinto's own administration and independent GreetScribe-development activities are described separately in the [Privacy Policy](/privacy-policy). Connecting an integration is not permission to use its guest data for unrelated purposes or to send it to undisclosed development tools. --- ## 21. Security Provider integrations must be configured securely. The Customer must protect provider credentials and account access. The Customer must promptly remove or rotate credentials when staff leave, access changes, or compromise is suspected. Qevinto Oy may disable an integration if it reasonably believes the integration creates security, legal, provider, operational, or data protection risk. Security concerns may be reported to: contact@qevinto.com --- ## 22. Support Qevinto Oy may provide reasonable support for GreetScribe-side integration issues. Qevinto Oy does not provide third-party provider support unless separately agreed. The Customer may need to contact the relevant provider for provider-side issues. Provider-side issues may include: - account suspension; - API access denial; - provider outages; - provider pricing errors; - provider booking errors; - payment-provider declines; - provider support delays; - provider authentication issues. Support is provided according to the GreetScribe Support Policy unless otherwise agreed. --- ## 23. Suspension or removal Qevinto Oy may suspend or remove an integration where: - the Customer breaches these Terms; - provider credentials are invalid; - provider access is unauthorized; - provider terms are breached; - the integration creates security risk; - the integration creates legal or data protection risk; - the integration creates excessive load; - the provider system is unavailable or unstable; - fees are unpaid; - continued operation may harm Qevinto Oy, the Customer, Guests, providers, or third parties. Qevinto Oy may act immediately if urgent action is needed. --- ## 24. Liability boundary Qevinto Oy is not responsible for third-party provider downtime, provider errors, provider data accuracy, provider pricing, provider availability, provider API changes, provider payment decisions, or provider support outcomes. Qevinto Oy is not responsible for Customer-side configuration errors, Customer Content errors, Customer provider-account issues, or Customer booking/payment terms. Liability is governed by the GreetScribe SaaS Customer Terms or the applicable signed customer agreement. --- ## 25. Changes to these Terms Qevinto Oy may update these Provider Integration Terms when providers, integrations, technical architecture, security practices, or the Service change. Updated versions may be published on the GreetScribe website. If a signed customer agreement gives different update rights, that agreement controls. --- ## 26. Contact Questions about these Provider Integration Terms may be sent to: **Qevinto Oy** Sarkakatu 3 F23 96460 Rovaniemi Finland contact@qevinto.com [Previous published version](/legal/versions/2026-05-17/provider-integration-terms.md).