1. Data handling principles
- Collect only what is reasonably needed for check-in, hospitality operations, security, support, billing, and compliance.
- Limit access to data according to role, property scope, and operational need.
- Separate environments and workflows for development, staging, and production where practical.
- Keep auditability in mind for guest actions, document access, subscription usage, and administrative changes.
2. Categories of data processed
- Guest check-in records and stay metadata.
- Uploaded identity documents and OCR or MRZ extraction results.
- Property profile, room configuration, compliance settings, and staff account data.
- Payment, invoicing, and subscription usage data.
- Operational logs, security events, diagnostics, backups, and support traces.
3. Storage and access controls
Personal data may be stored in application databases, encrypted object storage, secured backups, and operational logging systems. Access is intended to be limited through authentication, property scoping, least-privilege permissions, and document protection checks.
Documents or extracted identity data should not be made publicly accessible, indexed, or reused outside the stated purpose of check-in, support, compliance, or customer-authorized operations.
4. Retention expectations
Retention depends on the type of data, the property workflow, and applicable law. As a general rule, CheckInd aims to retain data only as long as it is needed for the service, legal compliance, security, support, billing, or dispute resolution.
- Guest check-in records may be retained as required by the property and by applicable guest registration or compliance obligations.
- Billing, invoice, and tax-related records may be retained for accounting, reconciliation, and audit needs.
- Security and audit logs may be retained to investigate incidents, abuse, fraud, and unauthorized access.
- Backups may temporarily hold deleted data until backup rotation or secure destruction is completed.
5. Correction, export, and deletion
Where allowed by applicable law and product design, customers or authorized users may ask for guest or account records to be corrected, completed, updated, or erased. Requests that conflict with mandatory legal retention duties may be delayed or declined until the retention obligation ends.
To request correction or deletion, contact info@checkind.in.
6. Backup, restore, and incident response
CheckInd may use backups and recovery workflows to preserve service continuity and reduce the risk of data loss. Backup access should be tightly limited and used only for recovery, migration, or controlled support activities.
If a confirmed data security incident affects personal data, CheckInd will investigate, contain, and respond in line with applicable law, contractual commitments, and incident handling procedures.
7. Data transfers and subprocessors
Depending on deployment architecture, some data may be processed by carefully selected service providers or subprocessors for hosting, storage, email, billing, logging, or OCR support. Cross-border processing, if any, should remain subject to applicable law, contractual protections, and product security controls.
8. Operational security logs
CheckInd may maintain logs for authentication, access attempts, uploads, administrative changes, suspicious activity, and other operational events. These records help detect abuse, investigate incidents, and support secure operation of the service.