Cookie Policy
Effective date: 4 September 2026
This policy explains how Diplomatic Protocol Event Management (“DPEM”) uses cookies and similar technologies on our platform at dpem.org.
1. What Are Cookies
Cookies are small text files stored by your browser when you visit a website. They allow websites to recognise your device on subsequent visits and maintain state across pages. Similar technologies include local storage and session tokens transmitted via HTTP headers.
2. Cookies We Use
2.1 Strictly Necessary Cookies
These cookies are essential for the platform to function and cannot be disabled. They do not identify you personally or track your activity for marketing purposes.
| Name | Purpose | Duration |
|---|---|---|
| portal_access_token | Attendee portal session (HttpOnly, Secure) | 15 minutes |
| portal_refresh_token | Keeps you signed in without re-entering your password (HttpOnly, Secure) | 7 days |
| __stripe_mid | Stripe fraud prevention (set by stripe.com) | 1 year |
| __stripe_sid | Stripe session identifier (set by stripe.com) | 30 minutes |
2.2 Analytics (No Cookies)
We use Plausible Analytics, a privacy-first analytics service that does not use cookies, does not collect personal data, and does not build cross-site profiles. Plausible aggregates anonymous statistics about page views and referrers only. No consent is required for this service under GDPR.
2.3 Advertising & Conversion Measurement (Meta Pixel)
DPEM uses the Meta Pixel, provided by Meta Platforms, Inc. (“Meta”), to measure the effectiveness of our advertising on Meta’s platforms (including Facebook and Instagram). When the Meta Pixel loads in your browser, it sets:
| Name | Purpose | Set by |
|---|---|---|
| _fbp | Identifies your browser to Meta for advertising measurement | dpem.org (first-party) |
| _fbc | Records that you arrived via a Meta ad click, where applicable | dpem.org (first-party) |
The Meta Pixel reports page views and specific actions (such as viewing an event, starting checkout, completing a ticket purchase, or submitting an application) to Meta. Separately, DPEM’s servers also send Meta a limited set of confirmed transaction events directly (Meta’s Conversions API) — for example, when a ticket order or application fee payment is confirmed. This server-side transmission includes your email address and, where collected, your name and phone number, each converted to a one-way SHA-256 hash before being sent, so that Meta can match it to the same advertising conversion the browser Pixel measures. See our Privacy Policy for more detail on this data sharing.
3. Your Controls
Strictly necessary cookies and cookieless analytics (Plausible) load unconditionally, as described above. The Meta Pixel described in section 2.3 also currently loads unconditionally on every page. You can control cookies at the browser level:
- Chrome: Settings → Privacy and Security → Cookies and other site data
- Firefox: Settings → Privacy & Security → Cookies and Site Data
- Safari: Preferences → Privacy → Manage Website Data
- Edge: Settings → Cookies and site permissions
Disabling the session cookie will prevent you from logging into the attendee portal. Disabling Stripe cookies may affect payment processing. Blocking the Meta Pixel’s cookies does not affect DPEM’s core functionality. You can also manage how Meta uses information about you for advertising directly at facebook.com/adpreferences.
4. Third-Party Services
Where DPEM embeds third-party content (such as payment forms hosted by Stripe), those third parties may set their own cookies subject to their own privacy policies. DPEM does not control these cookies.
5. Changes to This Policy
We may update this Cookie Policy to reflect changes in our technology or applicable law. Changes will be published on this page with a revised effective date.
6. Contact
For questions about our use of cookies: privacy@dpem.app