Legal

Privacy Policy.

Version 1.0 · Effective: November 2026 · Last updated: 19 October 2026

1. Introduction and who we are.

Innspeed AI Limited (“Innspeed”, “we”, “us”, “our”) is a company registered in Malta (C117372), with its registered office at 52 Triq Sant Antnin, Hamrun, HMR 2251, Malta, Europe.

Innspeed operates an artificial intelligence-powered guest communications platform (“the Platform”) provided to hotels, accommodation providers and hospitality businesses (“Hotel Clients”) on a software-as-a-service subscription basis.

This Privacy Policy explains how we collect, process, use, share and protect personal data in connection with: (a) your use of our website at innspeed.com (“Website”); (b) your use of the Platform as a Hotel Client or Hotel Staff member; and (c) the processing we carry out on behalf of Hotel Clients in relation to their hotel guests (“Guests”).

For the purposes of EU Regulation 2016/679 (the General Data Protection Regulation, “GDPR”):

  • Innspeed is the data controller for personal data collected from Website visitors and Hotel Clients in the context of our commercial relationship.
  • Innspeed is the data processor for personal data relating to Guests of Hotel Clients, processed on behalf of, and under the instruction of, the Hotel Client (who is the data controller for that data). This relationship is governed by our Data Processing Agreement (DPA), which forms part of our Terms of Service.

Data protection contact: info@innspeed.com | Innspeed AI Limited, 52 Triq Sant Antnin, Hamrun, HMR 2251, Malta, Europe.

2. Personal data we collect.

2.1 Hotel clients and hotel staff.

When a hotel registers for and uses the Platform, we collect:

  • Account registration data: full name, job title, work email address, telephone number, hotel name, hotel address, and website URL.
  • Billing data: name on payment card, billing address, payment method token (stored by Stripe; we do not store full card numbers).
  • Communications: emails, support tickets, and messages sent to us.
  • Usage and log data: login timestamps, IP addresses, browser type, device identifiers, features accessed, and actions taken within the Platform.
  • Platform configuration data: AI persona name and settings, escalation rules, working hours, custom response templates, connected channel credentials (WhatsApp Business Account ID, Meta page tokens, PMS API keys, OTA credentials, Nylas email account tokens, Twilio phone number configuration).
  • Multi-property data: account structure, per-property permissions, and assigned staff member roles (Collection plan only).

2.2 Hotel guests (processed as data processor).

In delivering the Platform services, we process the following categories of Guest personal data strictly as instructed by Hotel Clients.

2.2.1 Identification and contact data.

  • Guest name (first name and/or full name).
  • Mobile phone number (for WhatsApp and SMS communications).
  • Email address (for email communications via Nylas integration).
  • Booking reference number and reservation identifiers.
  • OTA profile identifiers (Booking.com, Airbnb, Expedia Group — pseudonymised identifiers as provided by those platforms).

2.2.2 Reservation and stay data.

  • Hotel property name and location.
  • Room type and room number.
  • Check-in date and check-out date.
  • Length of stay.
  • Booking monetary value (where synced via PMS integration).
  • Number of guests in reservation.
  • Special requests recorded at time of booking.
  • Arrival time preferences (collected via WhatsApp Flows).

2.2.3 Communication and message content.

  • WhatsApp Business message content and metadata (timestamps, delivery status, read receipts).
  • Web chat widget message content and metadata (session identifier, page URL, timestamps).
  • Email message content and metadata (subject lines, body content, thread identifiers) — processed via Nylas when the Hotel Client has connected an email account.
  • Instagram Direct Message content and metadata — when the Hotel Client has connected an Instagram Business Account.
  • OTA platform message content (Booking.com, Airbnb, Expedia Group) — when OTA messaging integration is connected.
  • WhatsApp Flows submission data: arrival time preferences, dietary requirements, room preferences, specific service requests, and satisfaction ratings submitted through interactive WhatsApp Flow forms.

2.2.4 Voice communication data (Voice AI feature).

Important: Call recording is only activated where the Hotel Client has enabled this feature and has obtained required consents from Guests under applicable law. Innspeed provides the technical capability; the Hotel Client as data controller is responsible for ensuring a lawful basis for recording.

  • Call recordings (audio files) — captured via Twilio infrastructure, where Voice AI is enabled.
  • Call transcripts — generated by Deepgram or AssemblyAI speech-to-text processing.
  • Call metadata: call duration, timestamps, phone numbers, call outcome.
  • Voice AI interaction log: AI responses delivered during call (text-to-speech via ElevenLabs).

2.2.5 Derived and analytical data.

  • Sentiment analysis scores derived by AI from Guest message content (positive/neutral/negative classification per conversation).
  • Guest Intelligence Report data: aggregated patterns, frequently asked questions, topic clustering — compiled per Hotel Client property.
  • AI-generated draft responses for online review platforms (TripAdvisor, Booking.com) — drafts only; the Hotel Client is responsible for review and posting.
  • Conversation labels, tags and categories applied by Hotel Staff.
  • Resolution status and conversation outcomes.

2.2.6 PMS integration data.

Where a Hotel Client has connected a Property Management System (Mews, Cloudbeds, Little Hotelier, Apaleo, or Opera Cloud), we process reservation data synchronised from that PMS, including:

  • Active and upcoming reservations: guest name, contact details, check-in/check-out dates, room type, room number, booking value, number of guests.
  • Guest profile data as made available by the PMS: loyalty status, language preference, previous stay count (varies by PMS).
  • Reservation status changes: arrivals, check-outs, modifications, cancellations.

2.3 Website visitors.

  • Technical data: IP address, browser type, operating system, referring URL, pages viewed, session duration, cookie identifiers. See our Cookie Policy for full details.
  • Contact form data: name, hotel name, email address, and message content.
  • Marketing data: email address where you subscribe to a newsletter or request updates.

3. Legal basis for processing.

3.1 Hotel Clients and Hotel Staff — legal bases are summarised below.

3.2 Hotel Guests (as data processor): where we process Guest personal data on behalf of Hotel Clients, we act as data processor under GDPR Article 28. The Hotel Client determines the legal basis for processing Guest data (typically Art. 6(1)(b) performance of accommodation contract; Art. 6(1)(a) consent for marketing; or Art. 6(1)(f) legitimate interests for operational communications).

3.3 Website visitors: Art. 6(1)(f) legitimate interests (analytics and security); Art. 6(1)(a) consent (non-essential cookies and marketing); Art. 6(1)(b) performance of contract (responding to contact form enquiries).

Processing activityLegal basis
Account registration and delivery of Platform servicesArt. 6(1)(b) — Performance of contract
Billing and payment processingArt. 6(1)(b) — Performance of contract
Responding to support enquiriesArt. 6(1)(b) — Performance of contract
Sending product updates and operational noticesArt. 6(1)(b) / Art. 6(1)(f) — Legitimate interests
Sending marketing communicationsArt. 6(1)(a) Consent / Art. 6(1)(f) Legitimate interests (existing customers)
Security monitoring, fraud preventionArt. 6(1)(f) — Legitimate interests
Analytics to improve the PlatformArt. 6(1)(f) — Legitimate interests
Legal compliance, regulatory requestsArt. 6(1)(c) — Legal obligation

4. How we use personal data.

4.1 Delivering and operating the Platform:

  • Provisioning and managing Hotel Client accounts and subscriptions.
  • Processing and routing Guest messages across connected channels (web chat, WhatsApp, email, voice, Instagram DM, OTA messaging).
  • Generating AI responses to Guest enquiries using AWS Bedrock (Claude and Cohere models, eu-west-1 Ireland).
  • Synchronising reservation data from connected Property Management Systems for contextually aware AI responses.
  • Delivering sentiment analysis scores and Guest Intelligence Reports to Hotel Clients.
  • Generating AI-assisted review response drafts for Hotel Client review and posting.
  • Sending WhatsApp marketing messages to Guests on behalf of Hotel Clients (subject to Meta-compliant opt-in consent obtained by the Hotel Client).
  • Operating Voice AI call handling (where enabled) via Twilio infrastructure.

4.2 Communications and support.

  • Sending transactional notifications to Hotel Clients (billing receipts, system status, security notices).
  • Providing customer support.
  • Sending marketing communications to Hotel Clients who have consented or where legitimate interest applies.

4.3 Safety, security and legal compliance.

  • Monitoring for fraudulent, abusive or prohibited Platform use.
  • Maintaining Platform security and data integrity.
  • Complying with applicable laws, court orders and regulatory requests.
  • Enforcing our Terms of Service.
  • Establishing, exercising or defending legal claims.

5. Sub-processors.

5.1 EU data residency: all primary data processing is hosted within the EEA. Primary infrastructure uses AWS eu-west-1 (Ireland) for application servers (ECS), caching (ElastiCache), storage (S3), and AI inference (Bedrock). Database uses Supabase PostgreSQL hosted in the EU.

5.2 An up-to-date sub-processor list is maintained for Hotel Clients. Hotel Clients will receive at least 30 days prior written notice of new sub-processors, in accordance with the DPA. Key sub-processors include:

Sub-processorPurposeLocationData types
Amazon Web Services (AWS)Cloud infrastructure, AI inference (Bedrock), storage, caching, monitoringEU — eu-west-1, IrelandPlatform data including application logs which may contain identifiers
SupabaseManaged PostgreSQL databaseEUAll stored Platform data
Stripe Payments Europe, LimitedSubscription billing and payment processingIreland, EUHotel Client name, billing address, payment method token
Meta (WhatsApp Business Platform)WhatsApp messaging and WhatsApp FlowsMeta infra (EU SCCs apply)Guest phone numbers, message content, Flows submissions
NylasEmail integration for guest communicationsEU data residencyEmail content, metadata, account tokens
TwilioVoice AI telephony, call routing, call recordingEU regional endpointsCall audio, phone numbers, call metadata
Deepgram / AssemblyAISpeech-to-text for Voice AI callsEU regionCall audio streamed for transcription; transcripts
ElevenLabsText-to-speech for Voice AI responsesEU regionAI response text converted to speech
ResendTransactional email deliveryEU SCCsHotel Client email addresses, email content
PostHogProduct analytics, usage telemetryEU-hostedAnonymised usage data
Google Ireland LimitedGoogle Analytics 4 (Website; consent-gated)Ireland, EU (SCCs may apply)Anonymised website visitor / session data
Meta Platforms Ireland LimitedFacebook Pixel (Website; consent-gated)Ireland, EU (SCCs may apply)Website visitor identifiers, page views, conversion events
LinkedIn Ireland Unlimited CompanyLinkedIn Insight Tag (Website; consent-gated)Ireland, EU (SCCs may apply)Website visitor identifiers, page views, demographic aggregates

6. Data retention.

We retain personal data only for as long as needed for the purposes described in this Policy, subject to the periods below (or as otherwise instructed by Hotel Clients for Guest data).

Data categoryRetention period
Hotel Client account data (active accounts)Duration of account plus 7 years (Malta legal requirements)
Hotel Client account data (post-deletion)30 days in backup systems, then permanent deletion
Guest conversation data (messages, call transcripts)Default 12 months from last activity; configurable by Hotel Client
Guest call recordingsDefault 90 days; configurable by Hotel Client
Derived analytical data (sentiment scores, intelligence reports)12 months, then anonymised for aggregate benchmarking
PMS-synced reservation dataDuration of stay plus 12 months; or as instructed by Hotel Client
Website visitor dataSee Cookie Policy; server log data 90 days
Contact form and enquiry data24 months from last contact
Billing and financial records7 years (Malta legal requirement)
Security and access logs12 months

7. Your rights under the GDPR.

If you are a data subject whose data we control (Hotel Clients, Hotel Staff, Website visitors), you have the GDPR rights summarised below. To exercise these rights: info@innspeed.com. We respond within 30 days. We may verify your identity before processing.

For Hotel Guests: the Hotel Client is your data controller and first point of contact. Innspeed will assist Hotel Clients in responding to Guest data subject requests under our DPA.

RightDescription
Access (Art. 15)Request a copy of personal data we hold about you.
Rectification (Art. 16)Request correction of inaccurate or incomplete data.
Erasure (Art. 17)Request deletion where data is no longer necessary, subject to legal retention obligations.
Restrict processing (Art. 18)Request restriction of processing in certain circumstances.
Data portability (Art. 20)Request your data in a structured, machine-readable format.
Object (Art. 21)Object to processing based on legitimate interests or to direct marketing.
Withdraw consent (Art. 7(3))Withdraw consent at any time where processing is consent-based.
Lodge a complaintContact the IDPC Malta (idpc.org.mt) or your local EU supervisory authority.

8. Children.

The Platform is for hotel businesses and their adult guests. It is not directed at children under 16. We do not knowingly collect data from children under 16.

9. Security.

Innspeed implements appropriate technical and organisational security measures including:

  • End-to-end encryption for data in transit (TLS 1.2+).
  • Encryption at rest for all stored data (AES-256).
  • Role-based access controls (RBAC) and Row-Level Security (RLS) in the database layer.
  • Multi-factor authentication (MFA) for Platform administrative access.
  • Audit logging of access to personal data by Innspeed staff.
  • Regular security testing and vulnerability assessments.
  • Incident response procedures and breach notification protocols.

9.1 Personal data breaches.

In the event of a personal data breach likely to result in risk to individuals, we will notify the relevant supervisory authority within 72 hours and affected data subjects without undue delay, as required by GDPR Articles 33–34.

10. EU AI Act compliance.

In accordance with EU Regulation 2024/1689 (EU AI Act), Article 50, Innspeed ensures Hotel Guests are informed whenever they are interacting with an AI system. Hotel Clients cannot suppress or remove AI disclosure requirements. Custom AI persona names are permitted; suppression of the fundamental AI disclosure is not. See our AI Transparency Notice at /legal/ai-transparency for full channel-by-channel disclosure details.

11. Cookies.

Our cookie use on the Website is governed by our Cookie Policy at /legal/cookies. The Platform application uses only technically necessary cookies for session management and security.

12. Changes to this policy.

We may update this Policy from time to time. Hotel Clients will be notified of material changes by email with at least 14 days advance notice. The Effective date and Last updated line at the top of this page indicate when the current version came into force.

13. Contact.

Email: info@innspeed.com

Post: Innspeed AI Limited, 52 Triq Sant Antnin, Hamrun, HMR 2251, Malta, Europe

IDPC Malta (supervisory authority): www.idpc.org.mt

Questions about this page?

We are happy to clarify anything. Reach out and we will reply personally.

Contact us