Skip to content

Data and security

Handle necessary information by property boundary

Acori handles information needed for lodging operations. It does not replace the operator's legal responsibilities or use connection credentials for advertising or sale.

Organization and property separation

Admin surfaces, Beds24 connections, property settings, bookings, guest registration, billing, and activity records are handled within the organization boundary. Acori checks membership and property access before processing.

Beds24 credentials

Credentials created by the operator are encrypted at rest and are not returned to the screen, analytics, or logs. Acori checks the connected properties and permissions, stops PMS operations when credentials expire or are revoked, and lets operators revoke them in Beds24.

Guest information

Acori handles information needed for guest registers, identity checks, property operations, guidance, and incident or misuse investigation. Operators set the purpose, required fields, and a three- or five-year retention period for personal information; it is anonymized after the period ends.

Connected services

Acori uses Cloudflare for hosting and data processing, Google for authentication, Beds24 for PMS connections, Stripe for payments, Resend for email, and Anthropic or DeepL for configured writing or translation assistance, only as needed for the stated purpose.

The boundary at service end

After the recovery period following paid-service termination, Acori revokes Beds24 credentials and removes reusable invitation or login tokens and the paid-property membership. Billing, consent, security, audit, and legally required records follow their respective retention policies.

Need a safe next step?

Do not send credentials or personal information. Start with the current support path and setup guide.

Support