Privacy Policy
Last updated: 13 June 2026
Who we are
EventOps ("we", "us") provides software that event-planning agencies use to run their events. This policy explains what personal data we process and why. If you have questions, email privacy@eventops.app.
Information we collect
- Account information — your name, email address, and the agency you belong to, plus authentication data needed to sign you in.
- Content you upload — events, tasks, timelines, budgets, files, comments, and the vendor and client details you add to the product.
- Usage analytics — basic, largely aggregated information about how the product is used, to help us improve it and diagnose problems.
How we use your data
We use your data to provide and operate the service, to secure and support your account, to communicate with you about the product, and to bill your subscription. We do not sell your personal data.
Sub-processors
We rely on a small set of vendors to run EventOps. Each processes data only as needed to provide their service. Providers marked active are used in the launch service; providers marked integrated but dormant are present in the codebase but not active until their launch gate is enabled.
- Supabase — active: database, authentication, and file storage
- Vercel — active: application hosting
- Stripe — active: subscription billing and payments
- Resend — integrated but dormant: transactional and notification email
- Sentry — integrated but dormant: error monitoring
- PostHog — integrated but dormant: product analytics
Data retention
We retain your data for as long as your account is active. After you delete your account, we remove your data within 90 days, except where we must retain limited records to meet legal or accounting obligations.
Your rights
You can request access to, an export of, or deletion of your personal data. Email privacy@eventops.app and we will respond within 30 days. See also our help article on data export and deletion.
Changes
We may update this policy as the product evolves. Material changes will be reflected here with a new "last updated" date.