Legal

Privacy Policy

Last updated 28 September 2026 · Applies to hearth.symphia.ai, the Hearth web console and the Hearth iOS and Android apps.

Who we are

Hearth is an AI guest-experience platform for hotels, operated by Symphia LLC ("Symphia", "we", "us"). Hotels use Hearth to message their guests across SMS, WhatsApp, email, web chat and voice, to run their guest CRM, and to automate parts of the stay.

This policy covers the Hearth marketing site, the Hearth web console and the Hearth iOS and Android apps. It does not cover a hotel's own website, its property-management system, or any other service the hotel connects to Hearth.

Our two roles

Which rules apply depends on whose information is involved. Hearth handles two very different categories of data, and we treat them differently.

Whose data	Our role	What that means
Hotel staff	Controller	We decide how staff account data is handled, because the account relationship is between the hotel's team and us. This policy governs it.
Hotel guests	Processor	Guest information belongs to the hotel. We process it only on that hotel's instructions, under our agreement with them. The hotel's own privacy notice governs why a guest's data was collected in the first place.

Put plainly: a guest's reservation, phone number and message history are the hotel's records, held by us on the hotel's behalf. We do not use them for our own purposes, we do not sell them, and we do not market to a hotel's guests for anyone else.

What we collect

From hotel staff (our users)

Name, work email address, work phone number, job title and role.
The hotel organisation and properties you have access to.
Sign-in records: one-time email codes, session tokens, sign-in time and IP address.
Device push tokens, so we can notify you about new guest messages and escalations.
Server-side operational logs: request identifiers, timestamps, endpoint, status and IP address, used to keep the service running and to investigate faults.

About hotel guests (on the hotel's behalf)

Identity and contact details: name, email address, phone number, and channel handles.
Reservation and stay data synced from the hotel's property-management system: confirmation number, arrival and departure dates, room, rate, and stay notes.
Message content and metadata across every connected channel.
Voice call metadata and, where the hotel has enabled it, call recordings and transcripts.
Anything a guest submits through a hotel's digital check-in or mini app — which may include identity-document fields the hotel is legally required to collect.
Staff notes, tags and task records attached to the guest.

What we do not collect

No advertising or tracking. Hearth contains no advertising SDK, no cross-app tracking, and no data broker integrations. We do not track you or a hotel's guests across other companies' apps or websites.
No card numbers. Payment capture is tokenized; card numbers do not touch Hearth's servers.
No location tracking. The Hearth app does not request or collect device location.
No access to your device contacts, photo library or health data. Guest messages, attachments and registration records supplied by a hotel may contain images or documents; authorized staff can view these records in Hearth.

The Hearth mobile apps

The iOS and Android apps are staff tools. They provide the console in a native form: you sign in with your work email, and you see the guest conversations, reservations and tasks for the properties your hotel has given you access to.

The apps use the staff account data listed above. Signing in and authorized updates to messages, guest profiles, notes and operational records are transmitted to Hearth over encrypted connections.
When push notifications are available and enabled, a device push token is used to deliver work notifications. Android notification delivery uses Google Firebase Cloud Messaging when configured; builds without this configuration do not register a push token.
Guest information shown in the app is the hotel's data, fetched over an encrypted connection each time; it is displayed to you, not resold or repurposed.
The app contains no third-party analytics or advertising SDKs.
You can manage app notification and microphone permissions in your device settings. Messaging by typing remains available without dictation.
Android session credentials and pending message retries are encrypted using the device Keystore. Downloaded attachments are kept in temporary app-private storage and cleared on logout or the next cold launch.

Microphone & dictation

Dictation is optional. Tap the microphone button in the message composer to convert your speech to text, review the result, and choose whether to send it as a reply.

On iOS, the microphone is active while you are dictating and stops when you stop dictation or send the message.
On iOS, speech-to-text is performed by Apple's speech recognition. Depending on your device and language, audio may be processed on-device or sent to Apple for transcription under Apple's privacy policy.
On Android, dictation opens the speech-recognition app installed on your device. That provider controls microphone capture and may process audio on-device or on its servers under its own privacy policy. You can cancel that activity without sending a message. Hearth receives the recognized text, not the raw dictation recording.
Hearth does not store your dictation audio. Only the resulting text reaches our servers, and only if you choose to send the message.
We do not use dictation audio to train any model.

Calls & recordings

Hotels can run an AI voice concierge on a phone line, and can review the resulting calls in Hearth. Where a hotel has enabled recording, the recording and its transcript are stored against that hotel's account and are visible to that hotel's staff only.

Recording is the hotel's decision and the hotel's legal responsibility. Consent and notice requirements for recording calls vary by jurisdiction. Hotels using Hearth are responsible for providing the disclosures their local law requires.

AI processing

Hearth uses AI to draft replies, classify what a guest is asking about, route urgent issues to a human, and power the voice concierge. To do that, message content and relevant reservation context are sent to our AI providers.

Providers process this content to return a response to us. Under our agreements, they do not use it to train their models.
Complaints, billing disputes and safety issues are always routed to a human rather than answered autonomously, and the AI's confidence gates what it may send on its own.
A hotel can turn AI replies off per conversation or per property at any time.

How we use information

To provide the service: deliver messages, sync reservations, run journeys, raise tasks and escalations, and show analytics to the hotel.
To authenticate you and keep accounts secure.
To send you operational notifications about your own work — new guest messages, escalations, assigned tasks.
To keep the platform reliable: monitoring, debugging, capacity and abuse prevention.
To meet legal obligations and enforce our terms.

We do not sell personal information, and we do not share it for cross-context behavioural advertising.

We share data only with service providers who help us run Hearth, each under contract and only for that purpose:

Provider	Purpose
Amazon Web Services	Hosting, storage and database infrastructure (United States).
Symphia	Our own AI, messaging and voice engine.
Twilio	SMS, WhatsApp and voice delivery.
Anthropic, OpenAI	Language models used for drafting, classification and voice.
Apple	iOS push notification delivery and speech recognition for dictation.
Google Firebase	Android push notification delivery when configured and enabled.
Your Android speech-recognition provider	Optional dictation, under the provider's privacy policy.
Email delivery providers	Transactional email — sign-in codes and notifications.
The hotel's own systems	Property-management systems (such as Mews) and booking channels the hotel connects.

We may also disclose information where legally required, or in connection with a merger or acquisition — in which case this policy continues to apply to the transferred data.

Retention

Guest data is retained for as long as the hotel's account is active, or until the hotel deletes it. Hotels control retention for their own records.
Staff accounts are retained while the account is active. Deactivating a staff member revokes access immediately.
Sign-in codes expire in ten minutes and are purged.
Operational logs are retained on a rolling short-term basis for troubleshooting.
On termination, a hotel may export its data; we then delete or anonymise it within a reasonable period, except where law requires us to keep it.

Security

TLS in transit and encryption at rest.
Passwordless sign-in with hashed, expiring, single-use, attempt-capped codes.
Strict tenant isolation — a hotel's data is scoped to its own organisation and properties on every request.
Role-based access (owner, manager, agent) plus per-property access, with an audit trail of who changed what, across staff and AI alike.
Tokenized payment capture, so card numbers never reach our servers.

No system is perfectly secure. If we become aware of a breach affecting personal data we will notify affected hotels without undue delay, as our agreements and applicable law require.

Your rights

Depending on where you live, you may have the right to access, correct, delete, port or restrict the use of your personal information, to object to certain processing, and to withdraw consent. You also have the right not to be discriminated against for exercising these rights.

If you are a member of hotel staff, contact us using the details below and we will respond within the time your law allows.

Deleting your staff account

To request deletion of your staff account and its personal data, use the Request account deletion link in the Android app menu or Settings, or visit Support: Delete your account. You can also email support@symphia.ai from your work address with the subject Delete my account. We verify your identity and handle the request. Deactivation by a hotel manager revokes access immediately but is not full deletion. Hotel-owned guest records and records retained for legal or security obligations are handled separately as described above.

If you are a hotel guest

The hotel you stayed with — not Symphia — decides what guest information is collected and why. Please contact the hotel first: they can amend or delete your record directly in Hearth, and they are the party whose privacy notice governs it. If you contact us instead, we will pass the request to the relevant hotel and support them in fulfilling it, but we cannot act on their records on our own initiative.

To stop receiving messages, reply STOP to any SMS or WhatsApp message. Opt-outs are recorded per channel and enforced immediately across automated journeys, campaigns and AI replies.

Children

Hearth is a business tool for hotel staff and is not directed to children. We do not knowingly collect personal information from children under 16. If you believe a child's information has reached us, contact us and we will delete it.

International transfers

Hearth is operated from the United States and our infrastructure is hosted there. If you or a hotel's guests are located elsewhere, information will be transferred to and processed in the United States. Where required, we rely on appropriate safeguards such as the European Commission's standard contractual clauses.

Changes to this policy

We will update this page when our practices change and revise the date at the top. If a change is material we will also notify hotel account owners by email. Continued use of Hearth after an update means you accept the revised policy.

Contact us

Symphia LLC, operator of Hearth.

Privacy questions, data requests and account deletion: support@symphia.ai

General enquiries: hello@hearth.hotel