Privacy policy

[Company name] (“we”) runs this website and the Marshal customer portal and is the controller of the personal data described here. Questions or requests: [email protected].

The short version

• This website uses no analytics, no advertising and no tracking cookies, and loads nothing from other sites.
• Marshal is self-hosted. What it knows about your servers stays on your console; we never receive it.
• A console you bind to the portal sends us numbers once a day (how many customers, machines and users it manages), never names.
• We do not sell personal data or use it for advertising.

Visiting the website

Our web server logs each request: the IP address, the page, the time and the browser’s user agent. We use the logs to keep the site running and to stop abuse, and keep them for [30 days]. Fonts and scripts are served from this site itself, so no third party sees your visit.

Your portal account

When you make an account we keep:

• your email address, your name if you give it, and your password as an Argon2 hash (never the password itself),
• your authenticator secret, encrypted, once you set up two-factor sign-in,
• when you last signed in, failed sign-in attempts, and for each session its IP address and browser,
• the organisations you belong to and your role in them,
• an audit log of changes made in the portal (who, what, when, from which IP address) and of downloads.

We send you email only about your account: confirming your address, resetting your password, and notices about your consoles and licenses.

Organisations, licenses and payments

• For an organisation we keep its name, billing email, country and VAT ID, its licenses and its orders (what was bought, the amount and the status).
• Payments are made through Stripe, which processes your card and billing details under its own privacy policy. We receive and keep only references to the payment, never the card number.

Licensed consoles

When you bind a console to your organisation, it checks in with us once a day. We keep the console’s installation ID and public key, the name you gave it, its version, whether it runs in Marshal Cloud, and for each check-in the time, its IP address and the number of customers, machines and users it manages. Consoles that are not bound never contact us.

Why we use it

• To provide what you asked for (your account, licenses, downloads, payments): necessary for our contract with you.
• Security, abuse prevention and audit logs: our legitimate interest in keeping the portal and licensing safe.
• Invoices and payment records: we keep them as long as tax and accounting law requires.

How long we keep it

• Account and organisation data: as long as the account exists, and up to [90 days] after it is closed.
• Sessions: until they expire, at most 12 hours. Unused binding requests: 7 days. Console check-ins: 180 days.
• Web server logs: [30 days].
• Orders and invoices: as long as the law requires, usually [10] years.

Cookies

The marketing pages set no cookies. The portal sets one cookie, __Host-site_session, when you sign in. It keeps you signed in, is needed for the portal to work, and is deleted when you sign out or it expires. No consent is needed for it, so we don’t ask.

Who else processes it

• Our hosting provider, [provider, country], which runs the servers this site is on.
• Our email provider, [provider], which delivers the emails we send you.
• Stripe, for payments. Stripe may process data outside the EU, under the EU’s Standard Contractual Clauses.

We share personal data with anyone else only when the law requires it.

Your rights

You may ask for a copy of your personal data, have it corrected or deleted, restrict or object to how we use it, and receive it in a portable format. Write to [email protected]; we answer within a month. You may also complain to your data protection authority.

Security

The portal requires two-factor sign-in for staff, stores only hashes of passwords and session tokens, and signs licenses with a key kept apart from the rest of the system. Report a security problem to [email protected].

Changes

We update this policy when what we collect changes, and show the date at the top. For significant changes we email account owners first.