Skip to main content
Media Alert Press Media Alert Press Check a URL
Friday, October 9, 2026
Live
Philadelphia police say Anthropic AI submitted a “false homicide tip”Vance says he wouldn’t watch livestream of Fort Hood shooter’s executionVance says if live stream of Hasan’s execution happens, he’s not going to watchWATCH: Get ready to go bananas in the 1st-ever Banana BowlTsunami threat after 7.6 magnitude earthquake recorded in PanamaVance on Guilfoyle texts: If ‘something bad’ happened, ‘people have to suffer consequences’
28,089 Ledger Records 112 added in the last hour1,622 in the last 24 hours
What is counted?

Counted at 19:22:28 UTC. These figures count ledger entries that have a record hash, the same entries as the total. The newest of them was added at 19:12:31 UTC on 2026-10-09. Entries are added in batches when MAP checks its feeds, so the figures vary through the day.

LEGAL

Compliance

A plain accounting of the security and privacy practices we actually have in place, and the frameworks we operate under.

Last updated: October 2026

1. Purpose of this page

This page is a factual summary of Media Alert Press LLC’s (“MAP”) compliance posture: what security and privacy measures are actually implemented today, what legal frameworks we align our practices with, and which formal certifications we do and do not hold. We would rather be precise here than impressive.

2. Security measures in place

The following technical measures are live on our systems today: HTTPS/TLS encryption site-wide; security headers including Content-Security-Policy, HTTP Strict-Transport-Security, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy, enforced via server configuration; XML-RPC disabled to reduce attack surface; rate limiting on our API to prevent abuse; a fix applied to close a REST API user-enumeration information leak; weak-TLS legacy endpoints disabled on our cloud API gateway; and a least-privilege IAM policy governing the cloud infrastructure roles used by our verification services; AWS CloudTrail activity logging across our cloud infrastructure, spanning all regions, with log-file integrity validation enabled so that changes to the log files themselves can be detected; encryption at rest on all production databases and storage; and a written incident-response plan and access-review process, adopted September 2026, that we actually follow rather than keep on file unused.

3. Certifications we do not currently hold

We do not currently hold SOC 2 certification. We do not currently hold ISO/IEC 27001 certification. We do not currently hold ISO/IEC 42001 certification. We do not undergo annual third-party security audits at this time. We have begun documenting and logging the underlying access-control, logging, and incident-response practices that a future third-party audit would evaluate. We are not currently engaged with an auditor, and we do not describe ourselves as “SOC 2 in progress” until that engagement actually exists — a real audit requires an independent firm observing these controls operate over a period of months, which cannot be shortened or skipped. If you require evidence of a specific control for your own vendor-compliance review, contact us at legal@mediaalertpress.com and we will tell you plainly what documentation is and is not available.

4. Frameworks we align with

We do not hold formal certification under GDPR or CCPA — these are legal frameworks, not certifications one is “certified” against — but we structure our data handling to honor their core principles in good faith: we collect only the data needed to operate the services, we tell you which third parties process your data (see our Data Processing Agreement), and we respond to access, correction, and deletion requests within a reasonable timeframe.

5. Subprocessors

We rely on a small set of subprocessors to operate the services: Amazon Web Services (cloud infrastructure, API hosting and database backups), Namecheap, Inc. (website hosting and Private Email, which sends follow and newsletter emails), Automattic Inc. / WordPress.com (image CDN and Jetpack), Google LLC (Google Analytics, only if you accept analytics cookies), and Stripe, Inc. (payment processing). Each is bound by its own data protection terms. See Privacy Policy section 4 for the full list of third parties, and our Data Processing Agreement for more detail.

6. AI governance

MAP Verified™ context records are produced by automated, rule-based extraction code that reads a page’s HTML and metadata; no generative AI model writes record text. MAP’s founder uses AI coding and writing assistants to build and maintain the website and its code. We do not claim independent third-party certification of our AI governance program. Our internal operating principles are described in our AI Ethics & Responsible Use Policy.

7. Related legal pages

Terms of Service · Privacy Policy · Cookie Policy · Data Processing Agreement · AI Ethics & Responsible Use Policy · API Terms of Use

8. Reporting a concern

If you believe you’ve found a security issue or a compliance gap not reflected accurately here, email legal@mediaalertpress.com and we will investigate.

9. Contact

Media Alert Press LLC, 15050 Elderberry Lane, Fort Myers, FL 33907. Email: legal@mediaalertpress.com | Phone: (800) 423-9379

FAQ

Compliance — Frequently Asked Questions

Does MAP hold SOC 2 or ISO certification?

No. Media Alert Press LLC does not currently hold SOC 2, ISO/IEC 27001, or ISO/IEC 42001 certification, and does not undergo annual third-party security audits at this time.

What security measures does MAP actually have in place?

Sitewide HTTPS/TLS, standard security headers (CSP, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy), XML-RPC disabled, API rate limiting, and a least-privilege IAM policy for cloud infrastructure roles. Subprocessors used are AWS, Google Analytics, and Stripe.

Powered by