Astrava Hospitality Intelligence is designed to support hospitality operations while maintaining responsible handling of guest information, operational records, and restaurant reporting data.
This Privacy Policy explains how guest, restaurant, operational, and reporting information may be collected, processed, stored, and managed within the Astrava platform environment.
Astrava Execution Focus
This platform is built to help hospitality teams:
- Capture guest activity responsibly
- Improve retention workflows
- Recover unhappy visits faster
- Measure campaign performance
- Improve operational visibility
- Maintain structured reporting environments
Every public page maps to a practical operating function: QR registration, offer delivery, redemption control, feedback recovery, reservations, referrals, campaign monitoring, and owner reporting for measurable growth.
Information That May Be Collected
Astrava may support the collection of:
- Guest names
- WhatsApp numbers
- Email addresses
- Reservation requests
- Referral participation
- Feedback responses
- Campaign interaction history
- Redemption activity
- Restaurant operational records
- Branch reporting information
- Staff activity logs
- Consent timestamps
Collection methods may include:
- QR registration
- Reservation forms
- Campaign workflows
- Feedback tools
- Referral systems
- Operational reporting
Consent and Communication Tracking
Astrava records:
- Consent timestamps
- Source of registration
- Communication preferences
- Campaign participation
- Offer acceptance history
This helps restaurants maintain operational accountability for guest communication workflows.
Restaurants are responsible for ensuring that outreach activities comply with applicable local laws and regulations.
Operational Data Usage
Operational information may be used to:
- Monitor campaign performance
- Improve guest retention workflows
- Track redemption quality
- Support reservation follow-up
- Improve complaint recovery
- Generate operational reports
- Measure branch performance
- Improve hospitality execution
The platform focuses on operational intelligence and hospitality workflow management.
Role-Based Access and Tenant Isolation
Astrava uses structured permission controls including:
- Role-based access
- Tenant-level separation
- Branch-level permissions
- Operational activity logging
- Authentication controls
- PIN-secured access systems
Restaurant data is designed to remain logically separated between tenants and organizations.
Reporting and Operational Visibility
Authorized users may access operational reporting including:
- Guest registrations
- Campaign performance
- Redemption activity
- Reservation reporting
- Complaint recovery metrics
- Branch comparison data
- Operational health indicators
Access visibility depends on assigned user role and operational permissions.
Data Retention Controls
Astrava may support:
- Guest data export
- Guest data anonymization
- Historical record deletion
- Operational retention management
- Audit logging for sensitive actions
Restaurants remain responsible for managing retention obligations according to applicable regulations.
Security and Operational Protection
Astrava may include:
- Secure login systems
- PIN-based authentication
- Audit logs
- Activity monitoring
- Backup systems
- Operational access controls
- Failed login monitoring
- Data export logging
No platform can guarantee absolute security. Operational users are responsible for maintaining secure credentials and authorized access practices.
Third-Party Operational Services
Restaurants may optionally use third-party services alongside Astrava, including:
- Email systems
- WhatsApp workflows
- Hosting infrastructure
- Reservation systems
- Operational integrations
Astrava is not responsible for third-party operational environments outside the platform scope.
Guest Rights and Operational Requests
Restaurants may choose to support operational requests including:
- Access requests
- Correction requests
- Data deletion requests
- Communication opt-out requests
- Guest record anonymization
Operational handling procedures may vary depending on restaurant policies and local legal obligations.
Operational Changes and Updates
Astrava may update operational workflows, platform structure, security controls, or reporting functionality over time.
Updated operational policies may be published through the platform environment where applicable.
Continued use of Astrava may indicate acceptance of updated operational practices and platform workflows.
Contact
Operational privacy inquiries may be directed through the Astrava contact environment.
Email: hello@astrava.asia