Terms of Use & License Agreement

Matext Hub grants a non-exclusive, worldwide, perpetual right to use downloaded licensed content while your subscription terms remain satisfied.

Licensed content may be used in commercial projects, marketing assets, applications, presentations, film, and packaging, but it may not be resold, sublicensed, or redistributed as a competing asset library.

Users must keep account credentials secure, provide accurate information, and avoid unlawful, abusive, or infringing use of the platform or generated materials.

Matext processes account, billing, usage, and support data to operate the service, secure accounts, and improve platform performance.

Personal data is handled according to the service purpose, retained only as long as operational or legal obligations require, and shared with subprocessors only when needed to deliver the product.

Users can contact Matext for access, correction, deletion, and export requests related to their account data.

Essential cookies and local storage are used for authentication, localization, theme, and product continuity.

Analytics, payment, and support integrations may set additional browser storage when enabled by the product flow.

Disabling required cookies or storage may prevent sign-in, checkout, notifications, or plugin auth from working correctly.

Matext supports lawful processing, purpose limitation, data minimization, and access control for user data handled in the EU context.

Users may request access, portability, rectification, restriction, or erasure of personal data where applicable.

Operational security, audit trails, and role-based access are used to protect account and billing data.

Matext services may not be used to generate or distribute unlawful, deceptive, or harmful material.

Users remain responsible for validating generated outputs before commercial or public use.

Platform access may be restricted or terminated for misuse, fraud, abuse, or attempts to bypass product controls.

Matext may rely on cloud infrastructure, identity, analytics, storage, support, and payment providers to operate the service.

Each subprocessor is limited to the minimum scope necessary for the function it performs, such as authentication, file delivery, billing, or notifications.

Material changes to critical subprocessors should be reflected in platform documentation and privacy materials.

Business customers that need controller-processor terms for enterprise deployments can request a DPA through support.

The DPA covers processing scope, confidentiality, subprocessors, incident response, deletion, and audit cooperation where contractually required.

Operational and regional details may vary depending on the product, hosting region, and enterprise agreement.