Data collection
We may collect contact details, demo requests, support messages, chat inquiries, tenant registration details, workspace settings, technical metadata, uploaded files, and information submitted through public forms or ERP workflows.
FAREXA ERP is designed to keep tenant business records scoped, controlled, and auditable while supporting sales, inventory, CRM, support, reporting, and SaaS workspace operations.
Tenant data should be used only to operate, secure, support, and improve the platform, with access controlled by role, tenant scope, and legitimate support needs.
We may collect contact details, demo requests, support messages, chat inquiries, tenant registration details, workspace settings, technical metadata, uploaded files, and information submitted through public forms or ERP workflows.
Data may be used to respond to inquiries, provide demos, onboard tenants, operate ERP modules, send service notifications, improve product quality, secure the service, and communicate important platform updates.
Tenant workspace data should remain scoped to authorized tenant users, platform support users, and services required to operate or support the ERP. Role-based permissions and tenant-aware architecture help separate workspace records.
FAREXA ERP references security patterns such as tenant isolation, role-based access, permission-aware navigation, audit visibility, controlled administrative access, KYC workflows, and structured operational logs.
ERP records may include invoices, receipts, orders, customers, products, stock movements, expenses, staff data, fleet records, reports, website inquiries, subscription details, and support conversations.
Business, support, billing, audit, and operational records may be retained for legitimate platform, compliance, troubleshooting, reporting, and service continuity purposes unless deletion is required and technically feasible.
Future integrations such as email, WhatsApp, payments, analytics, hosting, or storage may process limited data needed for the relevant feature. Integration scope should remain tied to the tenant’s configured workflows.
Users and tenant owners may request correction, access, export, or deletion review where applicable. Some records may need to remain for audit, legal, security, tax, or transaction integrity reasons.