Event Registration Hub securely manages event registrations, participant data, hotel bookings, payments, emails, and manager access. This page summarizes the security and privacy controls that protect that information.
Event Registration Hub is independently designed, developed, maintained and operated in-house by Rami Madgar Laor.
Customers such as Eshet Incoming, JDC and other organizations use the platform for event registration, hotel bookings, payments and participant communication.
| Feature | Status |
|---|---|
| HTTPS / TLS | Available |
| Role-Based Access Control | Available |
| Row Level Security | Available |
| Two-Factor Authentication | Available |
| Login History | Available |
| Active Sessions | Available |
| Account Lockout | Available |
| Hosted Payments | Available |
| Payment Logging | Available |
| Email Logging | Available |
- HTTPS/TLS encryption for all data in transit
- Supabase-managed PostgreSQL database
- Row Level Security (RLS) enforced on application tables
- Role-based access control (admin / manager / user)
- Managers can only access forms explicitly assigned to them
- Service role keys are used only server-side and never shipped to the browser
- Authentication powered by Supabase Auth
- JWT-based sessions
- Optional two-factor authentication, with required 2FA for admin/manager roles when enabled
- TOTP authenticator app support (Google Authenticator, Microsoft Authenticator, etc.)
- TOTP secrets encrypted at rest using AES-256-GCM
- Account lockout after configurable failed login attempts
- Dynamic inactivity logout based on configured session timeout
- Active session tracking with the ability to revoke individual sessions
- Login history recorded for admin review
- Credit card data is never stored by Event Registration Hub
- All card entry happens through Pelecard hosted checkout
- Payment results are verified server-side before a registration is marked paid
- Payment transactions, receipts, and sync logs are stored securely
- Payment API credentials are never exposed to managers or public users
- Transactional emails are sent through Resend
- Verified sending domain
- SPF, DKIM, and DMARC support for domain authentication
- Confirmation and payment email delivery is logged
- Sensitive fields are not included in emails unless explicitly selected by the form owner
- Managers only see the forms assigned to them
- Receipt, debug, and payment gateway logs are restricted to admins
- Cancellation policy and privacy policy acceptance can be tracked per registration
- Login history
- Active sessions
- Failed login tracking
- Account lockout
- Payment logs
- Email logs
- Receipt sync logs
Up to 12 months after the event, unless otherwise requested by the organizer.
Retained in accordance with applicable accounting and legal obligations.
- Managed cloud infrastructure
- Automatic Supabase backups
- Vercel hosting
- Continuous monitoring
Customer data is stored within the configured Supabase project region. Application traffic is encrypted using HTTPS/TLS. Managed infrastructure provides encryption at rest for stored data.
Event Registration Hub is not currently ISO 27001, SOC 2, HIPAA, or PCI-DSS certified as a platform. Payment card processing is handled by Pelecard hosted checkout, and Event Registration Hub does not store card data.
To report a security concern or ask a question about our security practices, contact us at info@eventreghub.com.
