Privacy Policy
Written from what this site actually does, not from a template. Every claim below is checkable against the page source.
The short version: this website runs no analytics, no advertising pixels and no third-party tracking of any kind. If you do not use the contact form, we do not know you were here beyond the ordinary web-server log our host keeps.
Who we are
DIDm is the agentic-systems practice of Dive In Digital Marketing, LLC, a Tennessee limited liability company in Memphis, Tennessee. This policy covers didmscout.com only. Data we handle inside a client engagement is governed by that engagement's agreement, and is described separately below.
What this website collects
Almost nothing, and nothing automatically. Specifically:
- No analytics. There is no Google Analytics, no Google Tag Manager, no Meta pixel, no heatmap or session-recording tool, and no advertising or conversion tag anywhere on this site. If that changes, this line changes in the same release — it is not a setting somebody can flip without editing this page.
- No third-party requests. Fonts, motion libraries and every image and audio file are served from this domain. Your browser is not asked to contact another company in order to render a page, so no other company learns your IP address from visiting us.
- No cookies from us. We set none for reading the site. WordPress sets a cookie only if someone logs in to the administrator area, our host may set a short-lived cookie to decide whether to serve a cached page, and the contact form's spam check may set one for the length of your visit.
The contact form
The form asks for your name, your organization, your work email address and a description of the task you would like handled. You choose what to put in that last field, so please do not paste anything confidential, personally sensitive, or covered by a duty you owe someone else — a matter file, a student record, a patient record or a customer list. You can tell us what the task is without sending us the data it runs on.
Where a submission goes, exactly. The form is handled by WPForms, a plugin running on this site. When you submit it:
- The four answers are emailed to two named people — Sky Romero and Jordan White, at their
@diveindigitalmarketing.comaddresses. Nobody else is on that notification, and the reply-to is set to your address so an answer comes back to you directly. - A copy is kept in this site's own WordPress database so a lead is not lost if an email bounces. It sits on our host (WP Engine) with the rest of the site.
- The plugin records the submitting IP address and the page you submitted from, which is how its spam check works. That is the plugin's standard behaviour, and it is the only automated profiling that happens anywhere on this site.
- You are then sent to a thank-you page. It sets no cookie and loads no tracker.
We use what you send to reply to you and to prepare for a first conversation. We do not sell it, rent it, trade it, or add you to a marketing list, and no third-party advertising or CRM tool receives it. If a conversation does not go anywhere, say the word and we delete both the email thread and the stored entry.
Hosting and server logs
The site is hosted by WP Engine, which keeps ordinary web-server access logs — IP address, timestamp, the page requested, the referring page and the browser's user-agent string — and uses them to serve pages, cache them, and block abusive traffic. Those logs are WP Engine's, kept on their retention schedule, and we do not mine them, join them to anything, or build profiles from them.
Client data, which is a different thing
When we build and run an agent fleet for a client, that work touches that client's own systems. The commitments there are contractual, not merely editorial, and they are the same ones stated across this site: agents read through views the client controls and cannot write to a system of record; the AI account is the client's own, with retention disabled and no training on their inputs; what we store on our side is identifiers, timestamps and counts, never narratives, case facts or student records; and the engagement is work-for-hire, so the code, the configuration and the data belong to the client. None of that is decided by this policy — it is written into the agreement before any credential is issued.
How long we keep things
Form entries and correspondence stay for as long as the conversation is live, and are removed on request — the stored entry as well as the email. Server logs expire on our host's schedule. We do not keep a shadow copy of anything a client has asked us to delete.
Your choices
Write to info@diveindigitalmarketing.com and ask what we hold about you, ask for a copy, ask us to correct it, or ask us to delete it. A person answers, usually within one business day. You do not need to be in a jurisdiction with a data-protection statute for us to do this; we do it because it is the right way to run.
Children
This site is for businesses and institutions and is not directed at children. We do not knowingly collect information from anyone under 13. Where we build a fleet for a school, student records stay inside the school's systems and are read through views the school controls — the design point of that work is that student data does not leave.
Changes
If this policy changes in a way that matters, the date below changes with it and the previous version stays in our repository's history. We will not quietly widen what we collect.
Last updated 2026-09-13 · Questions: info@diveindigitalmarketing.com · (901) 617-4905 · Memphis, Tennessee