Privacy Policy

Marshall Media, LLC — “Marshall Media”, “we” — operates marshallmedia.io from 825 Parkway St, Suite 12, Jupiter, FL 33477. This policy covers this website, the messages you send us through it, and calls and texts to our number.

Two things it does not cover. Work delivered under a signed client or vendor agreement is governed by that agreement. Our client and vendor portals are ours as well — software we run on our own infrastructure, at portal.marshallmedia.io and agency.marshallmedia.io, behind a login and under the notice you are shown there. What leaves this site for them: the roster application and the project inquiry form. What you enter after that is covered by that notice rather than this one: same company, different document. The newsletter list is the only thing you can hand this website that reaches them.

One thing that happens away from this website is described here in full, because people rightly ask about it before they start: connecting a social account for us to run. See “Connected social accounts” below.

Only what you choose to send, and today that is a short list:

• ·Email and phone. Still the plainest channel, and still open. What you write to us, and what we note from a call, is what we hold — as much or as little as you choose to put in the message.
• ·Calling or texting us. Calls and texts to our number are answered by an automated assistant. On a call it says so, and that the call is recorded, before anything else, and it turns what you say into text so it can answer you. We keep that transcript or your texts, your number, what you contacted us about and any message you leave. The first time you get in touch it may ask for your name, your email and the area you are in; you can decline any of it. If you book a call or ask to be sent something, that is kept too, and it may text you a confirmation. If it asks whether we may keep in touch, we keep your answer.
• ·Project inquiries. The link that starts a project does not submit anything to this website — it opens a form we host on our client portal, portal.marshallmedia.io. It asks who you are, how to reach you, and the shape of the project you have in mind. What you enter goes to us there, under the notice on that form, and none of it reaches this website.
• ·Booking a call. Arranged the same way as anything else, in a message or on the phone — there is no booking page on this site, so nothing asks you to pick a time.
• ·The newsletter box — in the footer, and on the M1 and store pages. It takes an email address, a first and last name if you feel like giving them, and a consent box that is never pre-ticked. Ticking it does not put you on the list: we send one message asking you to confirm, and only a confirmed address is added. Alongside it we keep the record that proves the consent — which page you signed up from, and the time, IP address and browser string of the moment you ticked the box. That record exists so we can show, if anyone ever asks, that you asked for this. The list is held on software we run on our own infrastructure, and confirming also files you there as a contact, in the same records we keep for anyone we do business with.
• ·Roster applications. Handled on our vendor portal, agency.marshallmedia.io, under the notice there — not on this site.

Send the brief, not the secrets. A web form is the wrong place for confidential, regulated, health or payment information; if an engagement needs that, we will agree on a channel for it.

Requests to this site are logged by the providers that serve it: IP address, browser and device string, the page requested, the time, and the referring page. Those logs keep the site up, let us find faults, and let us stop abuse.

We also count page views, using the counter our hosting provider offers. It is served from this domain, it sets no cookie, and it reports aggregates: the page read, the site that sent you, the country and the class of device. Page counts, not people — none of it is joined to anything you send us.

The map at the foot of each page is drawn from files on this website, with one exception: when you use the map (or open the map page), your browser fetches the map tiles for the area on screen from our DNS provider, which, like any server, sees your IP address and the part of the map you are viewing. We do not record which areas anyone views.

When you click a link that leaves this site, the site you land on is told you came from marshallmedia.io and no more than that. The page you were reading is not passed on, because we set the header that withholds it.

Some pages ask your browser about itself before they draw — whether you have asked for reduced motion, roughly how fast your connection is — so that a heavy animation does not run at someone who did not want it or cannot load it. Those answers decide what renders and go no further: they are not sent to us and not recorded.

That is the whole of it. There is no advertising pixel on this site, no cross-site tracker, no session recording, and no embedded player. Nothing this site picks up is joined to you — the one place we measure a person rather than a page is the newsletter, and the mail bullet below says what that records. Cookies are covered separately in the cookies. The short answer is that this site sets none of its own.

• ·To answer you. If you ask about work, we use your details to reply, scope it, and to run the engagement where it goes ahead.
• ·To answer calls and texts to our number, get each one to the right person, and do what you asked — book the call, take the message, send the link.
• ·To send you the newsletter where you have asked for it, on your consent, until you withdraw it — and to keep the proof of that consent for as long as we are acting on it.
• ·To publish and measure posts on the social accounts connected for us to run, and to report how they did.
• ·To keep the site available, fast and free of abuse.
• ·To meet obligations we cannot opt out of: accounting, tax, and lawful requests.

We publish and measure posts on social platforms — for Marshall Media itself, and for clients who ask us to run their accounts. This section covers what happens when an account is connected for that work. Nothing on this website connects one.

An account is connected on the platform’s own sign-in page, by someone with the right to it — its owner, or someone the owner has authorized — who approves the access we asked for. We never see or keep the account’s password. What the platform then gives us is what posting and measuring need: the account’s name, identifier and follower count; the posts on it, with their dates and links; and the figures the platform reports for the account and for each post — views, reach, likes, comments, shares, saves and clicks, as counts.

We use it to publish what was approved, when it was scheduled, and to report how each post did — to our own team and, for a client’s account, to that client. It is kept on servers we run ourselves. It is not sold, and not shared with an advertiser.

You can end it at any time, two ways. Revoke our access in the platform’s own settings, which ends it at the source, immediately. Or write to intel@marshallmedia.io and we will disconnect the account and remove the access we hold. Posts already published stay on the platform, where they are yours to keep or delete; the figures we recorded stay with our records of the work unless you ask us to delete them too.

What you share with a platform itself is governed by that platform’s own terms and privacy policy.

The outside companies, and that is the whole list. Each is under contract, and each handles only what its job needs:

• ·Our hosting and analytics provider — it serves this website, keeps the request logs that come with serving it, and runs the cookieless page-view counts described above.
• ·Our email provider — the inbox anything you write to us arrives in. It is stored there, and today that is where the whole of it sits.
• ·Our DNS provider, which also runs the bot check that now sits in front of the newsletter box. That check looks at the request and at signals about the browser making it, answers our server yes or no, and is told nothing about who you are or what you typed. It is there to keep automated signups off the list. What it can leave on your device is described in the cookies page. It also serves the tiles for the map: the map pictures your browser asks for when you use the map, which tell it your IP address and the area on screen.
• ·Our newsletter delivery provider, which is a different company from the one that holds our inbox. It delivers the newsletter and the confirmation message that starts it, so it sees the address it is sending to, and it records what happened to each message, recipient by recipient: whether it arrived or bounced, whether it was opened, and which links in it were clicked. We read that to work out what is worth sending, and it sits on your contact record with the rest of what we hold. It is not sold and not shared with an advertiser. The list itself stays on our own systems — the provider sends from it, it does not hold it.
• ·Our phone and text-message provider — the same company that delivers the newsletter. It carries calls and texts to and from our number.
• ·Our AI provider — it reads the text of a call or a text message so our assistant can understand it and answer. It processes it for us, and does not use it to improve its own products.

We do not sell personal information. We do not rent or trade it, and we do not share it for cross-context behavioral advertising. Nobody on that list is permitted to use your data for their own purposes.

• ·What you email us: kept while there is a reason to follow up, then deleted.
• ·Calls to our number: the transcript and the record of the call for 24 months, then deleted automatically. Texts: kept with the record of the conversation until you ask us to delete them.
• ·Newsletter: for as long as you want it. Every message carries an unsubscribe link that works on the first click — nothing to log into, no reason to give — and the moment you use it you are off. We do not delete the record then, and you should know why: the address stays on a suppression list so we cannot add you back by accident, the consent record stays with it as the proof we were entitled to write to you at all, and the contact record stays because leaving a mailing list is a statement about mail rather than about knowing us. An address that never confirms never joins the list and never gets a second message. Ask us and all of it goes for good.
• ·Client and vendor records: for the life of the relationship, and afterwards for as long as tax and contract law requires.
• ·Connected social accounts: the access you granted works until you revoke it on the platform or ask us to remove it. The posts we published and the figures we recorded stay with our records of the work for as long as we keep them, or until you ask us to delete them.
• ·Server logs: as long as our providers hold them. That window is theirs, not ours.

A copy of what we hold. A correction. Deletion. An end to marketing. A restriction on how we use it. Withdrawal of a consent you gave, with no effect on what was done before you withdrew it.

We apply these to everyone. Not only to the people a particular statute happens to cover, and not only to the jurisdictions that made it a requirement. A right you need the right ZIP code for is not much of a right.

Write to intel@marshallmedia.io. We may need to confirm you are who you say you are before we hand anything over. Expect an answer within 30 days, and expect it from a person.

This site is for people doing business with us. It is not directed at anyone under 16, and we do not knowingly collect their information. If you believe a child has sent us something, write to intel@marshallmedia.io and we will remove it.

Encrypted transport for every page and every submission, and a site permitted to load nothing but itself and the bot check in front of the newsletter box. Access limited to the people whose job needs it. Secrets kept out of the code, and no personal data in anything we publish.

We run a cybersecurity division, so we will not insult you with the word “impenetrable.” No system is. If a breach ever affects your data we will tell you, and we will tell you what we know rather than what sounds best.

This is version 1.4. When it changes, the version number changes and the change is described at the foot of this page. Material changes to how we use what you have already given us are notified to you before they take effect.

The clauses above describe what this site does today, not what it is being built to do. That is not a promise we are asking you to take on trust: the wording for each thing we have not switched on yet is already written and already reviewed, sitting behind a switch in the code beside the feature it describes. Turning the feature on turns the clause on, in the same release. There is no version of this site where something starts collecting and the page catches up later.