Skip to content
Hypamoon

For teams that run on Mailchimp

Mailchimp GDPR consent proof per contact

Mailchimp keeps the moment and the internet address of each sign-up and of the confirmation, plus the marketing permissions. They sit in different columns of an export, and a pop-up can add a subscriber without ticking the permission, so a profile can look as if consent was not given.

How it goes today

  1. Export the audience and find the contact in the file.
  2. Read the sign-up time, the opt-in time and the confirm time side by side.
  3. Look up which form or source added the contact.
  4. Check the marketing permissions on the profile by hand.

How it can go

Show when and how each contact agreed to hear from you.

For any contact you name, you get one page: when they signed up, from which internet address and source, when they confirmed, and which permissions are ticked. Once a month you get the subscribed contacts without a ticked permission. Where you hold the proof, you say yes and the permission is set on their profile.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. You paste your Mailchimp key in the portal, never in the chat.

Your request

With Hypamoon, when I name a Mailchimp contact, give me one page with when they signed up, from which IP address and source, when they confirmed, and which marketing permissions they have. Each month, send me the subscribed contacts without a ticked marketing permission. Where I reply yes because we hold the proof, set the permission on their profile.

You create the Mailchimp API key yourself under your profile, Extras, API keys. A key made since June 2026 works for a year, after which you create a new one. It stays yours.

More for teams on Mailchimp