How Muvexa handles account data, store credentials and API metadata.
Last updated: August 16, 2026
We collect account information such as name, email address, login provider identifiers and tenant membership data.
When you authorize a store, we store the authorization mapping and encrypted marketplace credentials needed to refresh tokens and sign API requests.
Muvexa request logs store metadata such as method, path, status code, latency, platform, tenant and store identifiers.
We do not retain request bodies or response bodies in API logs by default.
Muvexa is designed not to collect, store or expose buyer personally identifiable information. Buyer-data restricted endpoints are outside the documented public proxy surface.
You are responsible for how your own systems process, store and protect any buyer data received from marketplace APIs.
We use collected information to operate the service, authenticate users, authorize stores, process API requests, diagnose errors, prevent abuse and manage billing.
We may use aggregated, non-identifying operational data to improve reliability and product performance.
Privacy questions can be sent to [email protected].