Keep personal and marketplace data protected in its local country.
Country-local storage, authenticated workspaces, server-side authorization, auditability, and session controls protect marketplace operations.
Specific controls, not abstract promises.
Availability can depend on country, plan, and deployment configuration.
Least access needed
Workspace scope, roles, groups, permissions, and backend authorization.
Local-country storage
Personal and raw marketplace data remain in the applicable country data plane.
Unified reports without raw-data relocation
Cross-country views use approved aggregates, access, and currency rules.
Secrets stay out of the frontend
Provider credentials and service secrets remain in backend-controlled workflows.
Control who can see and change each workspace.
Permission paths stay server-owned.
Tenant and workspace scope
Users, groups, and roles
Fine-grained permissions
Report and data scopes
Access review
Sessions, devices, and login history
Customer-authorized support access
Separate data operation by design.
Central configuration contains no personal or raw marketplace data.
Central configuration contains no personal or raw marketplace data.
Personal data
Marketplace data
Object storage
Logs and audit
Application services
Approved aggregate for Unified Reporting
Security covers the full data journey.
Specific retention, encryption, backup, recovery, and deletion claims are published only after verification.
Connection and credential handling
Provider data ingestion
Backend processing and calculations
Workspace access and exports
Archive, retention, and deletion policy
Clear answers require current evidence.
Where is customer data processed?
Personal and marketplace data remain in the applicable local-country data plane.
How does Unified Reporting work?
Approved aggregates can support consolidated views without silently moving raw data between countries.
Can staff access my account?
Only through configured, permission-controlled, auditable support-access workflows where enabled.
How are credentials handled?
Credentials belong in authenticated backend-controlled storage and are never collected on public pages.
Report a security concern
Use the configured country security path. Never include passwords, credentials, personal data, or exploit details in a general enquiry.