Skip to content

Legal

Privacy Policy

Written for this education site. We collect little on purpose.

What we collect when you type

If you submit the contact form, we receive the name, email, company, inquiry type, and message you entered so the desk can read it and reply. It is delivered to our inbox by email through Resend, our email provider. If you join The Scutum Brief, we send a confirmation email to the address you typed, also through Resend; only after you confirm is the address stored in our Resend contact list. We use it to send the Brief and nothing else.

To limit abuse, the server briefly keeps your IP address in memory to count recent submissions. It is not stored or logged with your message.

What stays on your machine

The trade checklist journal and the editable playbook JSON live in browser localStorage under SCUTA keys. We do not upload that file unless you export it yourself. Clearing site data deletes it.

Analytics

If a Google Tag Manager container ID is set in the environment, the container may load tags the operator configures. Until that ID is a real container, the Site does not inject GTM. We do not sell a profile of your academy reading habits.

Cookies

The Site is static enough that we do not require an advertising cookie wall. A future host may set a cookie for locale or load-balancer reasons. Third-party tags, if enabled, follow those vendors’ policies — read them before you enable GTM.

Children

The Site is not directed at children. If you are not old enough to form a contract where you live, do not send us personal information.

Retention and rights

Contact messages stay in our email inbox for as long as the conversation needs them. Newsletter addresses stay in our Resend contact list until you unsubscribe: every issue carries an unsubscribe link. You can also ask us to delete your address or your messages by writing through the contact form. This page should be updated with the legal entity name and a postal address before SCUTA operates as a business.

Changes

If collection practices change — for example when a CMS or another vendor is wired — this page will be rewritten to name the vendor and the purpose.