Tenant data
Tenant records should remain scoped to the correct workspace, branch, user permissions, and subscription context.
This data processing overview explains how Farexa platform data should be handled across tenant isolation, role-based access, operational records, public forms, booking flows, attachments, notifications, integrations, backups, retention, and support operations.
Tenant records should remain scoped to the correct workspace, branch, user permissions, and subscription context.
ERP data may include sales, inventory, procurement, HR, fleet, financial records, attachments, notifications, and audit history.
Public booking, inquiry forms, tenant websites, guest invitations, and support chat collect customer-facing information for follow-up.
Calendar sync, email, SMS, WhatsApp, analytics, payment, and business integrations should follow approved configuration and access rules.
ERP rollout should define backup planning, file protection, retention, recovery expectations, and deletion review processes.
Role-based access, tenant isolation, logging, HTTPS, validation, and least-privilege operations help protect SaaS and tenant data.
Contact Farexa sales or support to align processing terms, hosting, retention, backups, and integration responsibilities.