Evidence before access.
This policy explains how MetaBantrix handles information when you use its mobile applications, gateway, member surfaces, library, Forge tools, and related services. A feature that is not enabled or not evidenced as active does not silently gain access to your data.
Information we may process
- Account identifiers and profile information you provide or authorize through sign-in.
- App activity, diagnostics, device and session information needed to operate, secure, and improve the service.
- Content you intentionally submit, upload, record, photograph, import, or create with MetaBantrix.
- Device permissions such as camera, microphone, photos, files, notifications, or biometrics only when a feature requests them and your device grants them.
- Transaction and entitlement metadata such as subscription status, purchase identifiers, tier, access state, and verification timestamps when needed to determine access.
Payments
Payment providers process payment credentials on their own secured surfaces. MetaBantrix may receive transaction, subscription, entitlement, and fulfillment information needed to provide or verify access. MetaBantrix mobile clients should not collect or display raw card numbers, bank passwords, private keys, seed phrases, or provider secrets.
AI and external providers
When you intentionally use an AI-powered feature, the mission and content needed for that request may be transmitted to the selected provider. Provider identity and capability state should remain visible where practical. MetaBantrix does not treat provider configuration, connection, authentication, execution, and result as the same state.
How information is used
- Authenticate users and protect accounts.
- Run requested features and return results.
- Maintain libraries, saved work, entitlements, receipts, and user-selected settings.
- Prevent abuse, troubleshoot failures, and maintain security.
- Meet legal, accounting, tax, fraud-prevention, and compliance obligations when applicable.
Sharing
Information may be shared with service providers only as needed to operate requested features, process payments, host data, deliver authentication, run AI services, provide customer support, or comply with law. Each provider may have its own privacy practices.
Retention and deletion
MetaBantrix retains app-owned information only as long as reasonably needed for the purposes above, legitimate operational needs, and legal obligations. You can initiate account deletion from the mobile app when that control is available. See the Account Deletion page for the current process and boundaries.
Your choices
You can deny optional device permissions, sign out, manage provider permissions on provider surfaces, request access or correction, export available app-owned data, and request deletion. Some features will not function without the permissions or data they require.
Security
MetaBantrix uses access controls and evidence-bounded architecture intended to reduce unnecessary exposure. No system can guarantee absolute security, so raw credentials and highly sensitive secrets should never be placed in normal chat, upload, or support fields.
Children
MetaBantrix is not designed to knowingly collect personal information from children in violation of applicable law. A parent or guardian who believes a child has provided personal information can contact support for review and deletion.
Contact and updates
Questions or privacy requests can be submitted through the public MetaBantrix Contact page. This policy may change as the mobile and provider fabric evolves; the date above identifies the current version.
← RETURN TO METABANTRIX