Trust center

One link to send to procurement.

Security, data handling, install and offboarding, support commitments and legal terms, all maintained by Genetrix and kept current.

Documents

Everything, in one place.

Security

Authentication model, data flow boundaries, hosting and tenancy, vulnerability reporting.

Data handling

Full data inventory, sub-processors, residency, retention, export and deletion, DPA.

Install & uninstall

Prerequisites, five-step install, configuration reference, smoke test, clean offboarding.

Support & SLA

Channels by edition, P1 to P4 severity definitions, response targets, escalation path.

Availability & incidents

Availability target, maintenance windows, incident communication timelines and continuity.

Documentation

Admin and end user documentation: install, daily use, reference, governance.

Release notes

Versioning, upgrade and deprecation policy, plus the running change log.

Accessibility

WCAG 2.1 AA working target, supported behaviours, known gaps and how to report a barrier.

Pricing & procurement

Editions, what a unique translation means, billing cycle, invoicing and renewal terms.

Privacy policy

The legal privacy statement covering Genetrix as a company.

Terms of service

License grant, fees, acceptable use, warranty and liability, governing law.

FAQ

The shorter answers, grouped by install, technical, security, hosting, quality and pricing.

Buyer's checklist

The nine questions we get asked every time.

Short answers here, full detail behind each document above.

Does the vendor store our subscriber data?

No. MCT only receives the marketing copy in the block.

How does it authenticate?

OAuth 2.0 client-credentials with Saved Content read and write scopes only.

Where does it run?

On infrastructure you own: Azure App Service, MC CloudPages, or a PHP host.

Who are the sub-processors?

Google Cloud Translation v2, your hosting provider, and your own Marketing Cloud org.

What happens at send time?

Nothing. Marketing Cloud renders the compiled content itself, MCT is not in the send path.

How long is install?

Under 24 hours in most orgs, with no custom code inside Marketing Cloud.

How do we remove it?

Revoke the API integration, uninstall the package, decommission the backend. Output stays yours.

What is the support commitment?

Target first response from 2 hours (Enterprise P1) to 3 business days (Starter P3).

Are you SOC 2 or ISO certified?

Not today, and we say so plainly. We complete customer questionnaires instead.

Posture

What ships with every deployment.

OAuth 2.0 client-credentialsLeast-privilege scopesSecrets in managed vaultNo subscriber dataTLS 1.2+ in transitNo send-time dependencyDocumented uninstall

This page is maintained by Genetrix to answer common security and privacy questions about MCT. It is app-owner content, not an independent audit or certification. Because MCT runs on infrastructure you control, your own hosting, network and access controls form part of the overall posture. Send your questionnaire to security@genetrix.tech and we will complete it against these facts.

Review it, then let's talk.

We will join a call with your security or procurement team and answer anything this page does not.

Book a demo