Privacy policy

Two kinds of information

Organizer accounts: when you sign up to run events, we decide how your account information is used, as described here.

Attendee information: when an organization collects information about its guests and attendees through EventForge, that organization decides how it is used, and we handle it on its behalf. If you registered for an event, the organizer is the first place to ask about your information; we will help them answer.

What we collect

Depending on how you use EventForge:

• Account details: name, email address, organization name and team role. Passwords are stored only as a secure hash.
• Event content that organizers add: names, dates, venues, agendas, speakers, sponsors, images and files.
• Guest and attendee details that organizers add or that people give when they register: name, email address, answers to the organizer's questions, ticket, waitlist and check-in status, and an optional profile in the attendee app.
• Payment records: Stripe handles card details. We receive the order, its status and amount, and the buyer's name and email.
• Technical and security records: a sign-in cookie, records used to limit repeated attempts, and a log of actions taken in each organization, including actions taken by the assistant and connected AI apps.

How we use it

To run EventForge: show event pages, handle registration and tickets, send the emails organizers ask for (invitations, announcements, reminders, receipts) and account emails (such as sign-up confirmation and password reset), keep accounts secure, and answer support requests.

We do not sell personal information.

Who helps us run EventForge

These service providers handle information for us, only to run EventForge:

• Railway hosts the application and its database.
• Cloudflare R2 stores uploaded files, such as images and documents.
• Resend delivers email.
• Stripe processes payments.
• Anthropic provides the AI models behind the EventForge assistant. When someone uses the assistant, their request and the event information it needs are sent to Anthropic to produce an answer. Speaker research also searches public web sources.

Cookies and browser storage

EventForge sets a cookie to keep you signed in and stores display preferences, such as language, in your browser. It does not use advertising cookies.

How long we keep it

Account and event information is kept while the account is in use. Some records are removed or reduced automatically today:

• Checkouts that were never finished drop the buyer's name, email and answers after 14 days.
• Waitlist entries that are no longer waiting drop the person's details 30 days after the event ends.
• Proposed changes that nobody applied are deleted after 30 days. The record of applied changes is kept for one year.
• Notifications are deleted 90 days after they are read, and after 180 days in any case.
• Uploaded files that were never used are deleted after a day; replaced files after 7 days.

Your choices

Reminder emails about an unfinished registration include a link to stop them. To see, correct or delete your information, contact the event's organizer, or write to us at the address below.

Security

Connections to EventForge are encrypted. Each organization's data is separated from every other organization's at the database level. Passwords are stored as hashes, never as text.

Changes

We may update this policy. The current version is always on this page.

Contact

Questions about this page go to rashmi@myassistant365.ai.