Santara AI

What we do with your data, in plain terms

Running Santara AI means handing us reservations, guest contact details, calendars and revenue for every property you manage. This page says what happens to that data. It describes what the product does today, not what we intend to build.

Security at a glance

Santara applies layered controls to accounts, workspace access, connections and operational data. This page explains the purpose of those controls, each party's responsibilities and the limits customers should understand.

Data transfer
Protected while exchanged with the service
Accounts and sessions
Access is limited and can be revoked
Authorisation
Based on role and work scope
Connection information
Protected and used only for selected integrations
Operational data
Separated by workspace
Service commitments
Defined by the applicable plan and agreement

Services that may process data

ProviderPurposeWhen data is sent
Amazon Web ServicesApplication infrastructure, database and storageWhile the service operates
StripeSubscription and direct-booking paymentsWhen billing or payments are used
ResendTransactional emailWhen the service sends email
ChannexSales-channel connections and synchronisationWhen a channel is connected
Google AnalyticsOptional public-website analyticsOnly after a website visitor gives consent
PriceLabsExternal pricingOnly when the account is connected
AnthropicAI-assisted drafts, summaries and recommendationsOnly when the relevant AI feature runs

01Security scope

Santara security covers accounts, operational data, third-party connections and the systems used to provide the service.

Individual measures can evolve with the product. Santara maintains the corresponding protection objective and updates this page when data handling changes materially.

02Shared responsibility

Santara protects the platform and enforces configured access; customers decide who joins a workspace and which data sources are connected.

Use individual accounts, grant only necessary access, remove former team members and report suspected unauthorised access promptly.

03Infrastructure and region

Data is operated on cloud infrastructure and supporting services needed to provide Santara.

Some providers can process data where they operate. Where a transfer safeguard is required, Santara uses the European Commission's Standard Contractual Clauses together with appropriate organisational and technical measures, as described in the Privacy Policy.

04Encryption

Santara protects data in transit and applies appropriate safeguards to sensitive information at rest.

Encryption is one layer only; access controls, scoped permissions and operational procedures work alongside it.

05Authentication and sessions

Santara uses authentication and session management to restrict account access to authorised users.

Sessions can expire, refresh or be revoked. Sign-out and account changes are enforced by the service rather than only hiding the interface on a device.

06Workspace access

Permissions are determined by role, workspace and the scope of properties or work assigned to a member.

The interface can hide unnecessary information, while important permission checks occur on the server before data is read or changed.

07Integration credentials

Information used to connect external channels and services is used only to operate the integration selected by the customer.

Disconnecting stops future activity but does not necessarily erase records already synchronised. Historical data follows workspace retention rules.

08AI data handling

When an AI feature is used, Santara sends only the input and context needed to produce the requested result.

Santara does not sell customer data and does not use it to train AI models.

AI output can be incomplete or wrong. Guest communications, pricing changes and operational decisions require review by an authorised person according to the product workflow.

09Logging and monitoring

Santara records operational and security information needed to detect faults, investigate unusual activity and support customers.

Coverage depends on the workflow. Operational logs are not automatically a customer-facing immutable audit ledger unless a feature expressly says so.

10Incident handling

When unauthorised access or data exposure is suspected, Santara validates the event, limits impact, restores service and gives notices required by applicable obligations.

Customers should report concerns early, preserve relevant information and change credentials under their control when exposure is possible.

11Backups and continuity

Santara uses appropriate backup and recovery capabilities to support restoration after an incident.

Recovery also depends on infrastructure providers. Customers should retain independent copies of records required for legal, accounting or business-continuity purposes.

12Retention, export and deletion

Data is kept as needed to provide the service, protect the platform and meet legal obligations.

Removing access, disconnecting a service and deleting a workspace are different actions. Export and deletion requests are verified for scope and authority before processing.

13Vulnerability disclosure

Report a suspected security issue through the contact form or email hello@santara.ai with the subject ‘Security report’. Do not send passwords, login details, full payment-card information or unnecessary guest data in the first message.

We aim to acknowledge a security report within five business days. Santara will not pursue good-faith research that avoids privacy violations, data destruction, service disruption and public disclosure before we have had a reasonable opportunity to investigate.

Include reproduction steps, the affected area, expected impact, discovery time and a safe contact method. Do not access other users’ data, perform destructive testing or social engineering, or disclose publicly before Santara has had a reasonable opportunity to investigate.

FAQ

Common questions

Who else can see my data?

Only the subprocessors the product actually runs on: Amazon Web Services (hosting and storage, ap-southeast-1), Stripe (billing), Resend (transactional email), our channel connectivity provider (connections to your sales channels), PriceLabs (only if you connect your PriceLabs account), and our AI provider (only for features you invoke that draft text). No advertising or analytics vendor receives guest or reservation data.

Where is the data stored?

In AWS ap-southeast-1 (Singapore), which is also where the application runs. Backups stay in the same region.

Do your staff read guest messages?

Only when you ask us to look at something and only for as long as it takes. Access is logged. During white-glove migration we work inside your workspace with your knowledge, which is the one routine case.

What happens to my data if I leave?

You export it and we delete the workspace. There is no annual contract and no exit fee, and the export is not withheld pending anything.

Is there a DPA?

Yes — ask us and we will send the current version. If your own owners or a management contract require specific terms, tell us before you sign rather than after.

Get your next morning back.

0% commission on channel bookings and upsells. No annual contract — leave any month.