EventPlannerNL← Home

Privacy

EventPlanner NL is a Netherlands-first team outing planner. This page describes the pilot defaults for planners and anonymous pulse respondents (AVG-minded).

What we process

  • Planners: work email and password for Sign up / Sign in (Supabase Auth in production; passwords hashed by Supabase), outing briefs, shortlists, generated packs, and QR pulse tokens.
  • Employees (pulse): anonymous preference answers only. No name or email on the form.
  • Optional free-text on the pulse is shown only to the planner in-app and is not written to application logs.
  • Partners (vendors): listing contact details and lead enquiries when a planner requests availability on a connected listing.

Where data lives

  • Preferred database region: Supabase eu-central-1 (Frankfurt).
  • App hosting: Vercel region fra1 when deployed as documented.
  • Optional OpenAI (typically US) for brief extraction — disabled when no API key is configured (form fields only).
  • Optional Google Places (server) to search venues or nearby rent/buy suggestions — not used to invent catalog recommendations.
  • Optional Resend email: when configured, we may email a partner about a new availability lead. Without Resend, leads stay in the vendor dashboard only. We do not process payments in this pilot.

Retention

After you close an outing, pulse responses become eligible for deletion about 30 days later (configurable via PULSE_RETENTION_DAYS). Retention can be run dry-first, then for real, via ops scripts or the secured cron endpoint.

Your choices

  • Close an outing from the event page to stop collection and start the retention clock.
  • We do not run clinical personality or MBTI-style diagnosis.
  • Application logs scrub obvious PII fields.
  • Submit an AVG access or erasure privacy request — ops reviews manually; nothing is auto-wiped on submit.
  • See also our Terms of use, Cookies, and Accessibility.

Pilot notice — refine with counsel before large company rollouts. Last updated 2026-11-03.