Changelog

Hotfix cherry-picked directly onto main, deliberately excluding the rest of staging (unverified at time of release). Fixed - The wrong direct phone was published for the named customer-facing contact on /team and /about. Both the visible pill and the tel: href carried +45 65 45 54 51 instead of +45 60 53 24 40, so anyone tapping it dialled a number that is not ours. Corrected at its single source, CUSTOMER_CONTACT.phone, and in the quoted example on the 2026-08-06 row of the regulatory-decisions log. Also carried by this tag (already merged to main under their own PRs since v1.1.0, infrastructure only, no user-facing change): Neon preview-branch reaper on main, pipeline metrics read-out, translation-meta test performance, and the PostHog lazy-module localStorage fix.

Delivery fixes for the data processing agreement emails sent to publishers, so large re-consent and reminder batches arrive reliably.

Correction to the privacy policy so the data controller is named accurately.

A contact-detail correction on the pricing page, plus security updates to third-party components.

Continued maintenance of third-party components, now with automated weekly checks so security updates are picked up promptly.

Beta Push focused on the EU election catalog and compliance hardening: automatic compliance certificates after registration, a streamlined per-ad registration flow, smarter one-line address entry, entity-aware sponsor identifiers (EU Reg 2025/1410), and clearer publisher + complaint tooling.

Public-site copy corrections following the beta launch: the "test version" banner has been removed, and the roadmap notice now states the platform's EU compliance position clearly.

End-to-end Data Processing Agreement (DPA) workflow plus a publisher sign-off step before transparency notices go public. Sponsors now declare EU-eligibility (Art. 5(2) + 12(1)(e)), publishers can register from any EU country, and VAT + currency fields are part of registration. The transparency label is redesigned and now ships in confirmation + partner notification emails. EU data residency is delivered: storage moved to Frankfurt. Plus the public changelog + roadmap with epic-sprint-task hierarchy.

Transparency notices and registration forms restructured to the EU Regulation 2025/1410 Annex II template (Points 1-16). Platform-wide terminology shifts to EU Article 11 'Sponsor', and registration distinguishes payer from sponsor with explicit in-kind contribution handling per Article 12(1)(e). Country-driven validation kicks in for phone, postal code, and address fields; GDPR consent is acknowledged on every personal-data form.

AI-assisted registration arrives with conversational mode and live preview, plus the supporting infrastructure (sessions, Assistant API). Homepage gets three role-specific entry points and live platform statistics. Agencies can register on behalf of advertisers, advertisers can edit drafts before submission, and PDFs of transparency notices are downloadable. EU label content finalized to Regulation 2025/1410 standards. DPA gate now blocks publisher dashboard until consent is signed.

English Translation & Security Hardening

Auth, Chatbot & API

Partner Selection & Compliance

Partner Dashboard & Onboarding

Submission confirmation flow + key bug fixes: one email per advertisement (not per campaign), sponsor creation reliability, registrations now visible on My Page, advertisement creation/update errors resolved, and old Typeform URLs redirect to the new form.

ID system + sponsor data model improvements: short randomized form IDs replace sequential PAID, public/private funding source distinction per sponsor, controller-entity field for sponsors managed by another entity, free-text search disabled for non-audio ad types, and reCAPTCHA removed because it was blocking legitimate submissions.

Initial public launch of polads.eu — political advertisement transparency portal for Denmark (Danish only). Foundational features: multiple sponsors per advertisement, campaign periods, search by PAID identifier, and EU-establishment compliance fields in registration emails.