Support — Marshal

Get in touch

That address reaches the people who build Marshal. Anyone can use it — customer, evaluator, or an end user of a Marshal deployment someone else runs. There is nothing to sign up for.

We respond to every request within two business days, and usually much sooner. If two business days pass without a reply, send it again and say it is a second attempt — something went wrong on our end.

What to include

Send whatever you have; we will ask if we need more. These are the details that usually save a round-trip:

What you were trying to do, and what happened instead.
Where it happened — the URL, the CLI command, or the integration involved.
Roughly when, including your time zone.
Any error message, in full.
The Marshal version, if you know it (marshal version).

Please do not send us credentials, tokens, or private keys. We never need them to help you, and an email inbox is the wrong place for them.

Reporting a security issue

Send security reports to security@marshal.codes, which goes straight to the people who can act on it rather than through the normal queue. Tell us what you found and how to reproduce it. We will confirm receipt, keep you updated while we fix it, and credit you if you would like us to.

Privacy and data requests

To access, export, correct, or delete personal data we hold about you, email privacy@marshal.codes. What we hold, and how long we keep it, is set out in the privacy policy.

If your organization runs its own Marshal deployment, your administrator controls the data inside it. Requests about that data go to them — but write to us anyway if you are not sure who that is, and we will point you in the right direction.

Evaluating Marshal

Questions about pricing, deployment, or a trial are welcome at the same address, or you can request access and we will follow up.