Information Security Addendum
This addendum describes the technical and organizational security measures implemented by GuestPass Plus to protect customer data and maintain the integrity of our services.
Table of Contents
1. Security Overview
GuestPass Plus is committed to maintaining the security, confidentiality, and integrity of all data processed through our platform. This Information Security Addendum describes the security measures we implement to protect your data.
Our security program is designed to:
- Protect the confidentiality, integrity, and availability of customer data
- Prevent unauthorized access to systems and data
- Ensure compliance with applicable laws and regulations
- Maintain customer trust through transparent security practices
- Continuously improve our security posture
This addendum supplements our Data Processing Agreement and provides additional detail on our security controls.
2. Infrastructure Security
2.1 Hosting Environment
Our infrastructure is hosted on enterprise-grade cloud platforms with robust security certifications:
| Component | Provider | Security Features |
|---|---|---|
| Application Hosting | Vercel (AWS) | SOC 2 Type II, ISO 27001, automatic DDoS protection |
| Database & Storage | Supabase (AWS) | SOC 2 Type II, data encryption, automated backups |
| Edge Network | Vercel Edge | Global CDN, automatic SSL, request filtering |
2.2 Physical Security
Our hosting providers maintain physical security controls including:
- 24/7 security personnel and surveillance
- Biometric access controls
- Environmental controls (fire suppression, climate control)
- Redundant power and connectivity
- Regular security audits and assessments
2.3 Geographic Distribution
Production data is stored in data centers located in the United States. Our infrastructure leverages multiple availability zones for redundancy and high availability.
3. Data Security
3.1 Encryption in Transit
- All data transmitted between clients and our servers is encrypted using TLS 1.2 or higher
- We enforce HTTPS for all connections with HSTS headers
- Internal service-to-service communication is encrypted
- API endpoints only accept encrypted connections
3.2 Encryption at Rest
- Database storage uses AES-256 encryption
- File storage (waiver PDFs, logos) uses server-side encryption
- Encryption keys are managed by our infrastructure providers
- Backups are encrypted with the same standards as production data
3.3 Data Isolation
- Multi-tenant architecture with logical data separation
- Each customer's data is isolated using tenant identifiers
- Row-level security policies enforce data isolation at the database level
- Cross-tenant data access is prevented at the application and database layers
3.4 Sensitive Data Handling
| Data Type | Protection Measures |
|---|---|
| Passwords | Hashed using bcrypt with appropriate work factor; never stored in plaintext |
| Member PINs | Hashed using secure algorithms; never stored in plaintext |
| Phone Numbers | Verified via SMS; stored for service functionality |
| Verification Tokens | Cryptographically random; expire after 10 minutes; single use |
| Session Tokens | Secure, HttpOnly cookies; regular rotation |
4. Access Control
4.1 Authentication
- Secure authentication via Supabase Auth
- Password requirements enforce complexity standards
- Session management with secure token handling
- Automatic session expiration for inactive users
- Rate limiting on authentication endpoints
4.2 Authorization
- Role-based access control (RBAC) with defined permission levels
- Principle of least privilege applied to all access grants
- Tenant-scoped access ensuring users can only access their organization's data
- Staff roles: Administrator (full access), Staff (operational access)
- API authorization with validated tokens
4.3 Administrative Access
- Administrative access to production systems is strictly limited
- All administrative actions are logged
- Access reviews conducted regularly
- Privileged access requires additional authentication
5. Application Security
5.1 Secure Development
- Security-focused code review process
- Static code analysis for vulnerability detection
- Dependency scanning for known vulnerabilities
- Regular updates to frameworks and libraries
- TypeScript strict mode for type safety
5.2 Input Validation
- All user input is validated using Zod schemas
- Input sanitization to prevent XSS and injection attacks
- HTML stripping from text inputs
- SQL injection prevention through parameterized queries
- Rate limiting on all public endpoints
5.3 Security Headers
We implement security headers including:
- Content-Security-Policy to prevent XSS attacks
- X-Frame-Options to prevent clickjacking
- X-Content-Type-Options to prevent MIME sniffing
- Strict-Transport-Security to enforce HTTPS
- Referrer-Policy to control referrer information
5.4 CSRF Protection
Cross-Site Request Forgery (CSRF) protection is implemented at the middleware level, validating Origin headers for all state-changing requests (POST, PUT, PATCH, DELETE).
6. Network Security
6.1 Perimeter Security
- Web Application Firewall (WAF) protection
- DDoS mitigation at the edge
- IP reputation filtering
- Automatic bot detection and blocking
6.2 Monitoring
- Real-time monitoring of application performance
- Error tracking and alerting
- Anomaly detection for unusual activity
- Log aggregation and analysis
7. Incident Response
7.1 Incident Classification
| Severity | Description | Response Time |
|---|---|---|
| Critical | Active breach, data exposure, service outage | Immediate (< 1 hour) |
| High | Potential breach, significant vulnerability | < 4 hours |
| Medium | Limited security issue, minor vulnerability | < 24 hours |
| Low | Minor issue, no immediate risk | < 72 hours |
7.2 Response Process
Our incident response process includes:
- Detection and identification of the incident
- Containment to prevent further damage
- Eradication of the threat
- Recovery of affected systems and data
- Post-incident review and lessons learned
- Customer notification as required by law and contract
7.3 Notification
In the event of a security incident affecting customer data, we will notify affected customers in accordance with our Data Processing Agreement (within 72 hours of becoming aware of the incident).
8. Business Continuity
8.1 Backup and Recovery
- Automated database backups (daily with point-in-time recovery)
- Backups stored in geographically separate locations
- Encrypted backup storage
- Regular backup restoration testing
- Recovery Time Objective (RTO): < 4 hours for critical systems
- Recovery Point Objective (RPO): < 1 hour for database
8.2 High Availability
- Multi-region deployment for application hosting
- Database replication across availability zones
- Automatic failover for critical components
- Load balancing across multiple instances
8.3 Service Level
We target 99.9% uptime for our production services. Scheduled maintenance windows are communicated in advance and performed during low-traffic periods when possible.
9. Personnel Security
9.1 Security Training
- Security awareness training for all personnel
- Role-specific security training for developers and administrators
- Regular updates on emerging threats and best practices
- Phishing awareness and testing
9.2 Access Management
- Background checks for personnel with access to customer data
- Confidentiality agreements for all personnel
- Access provisioning based on role requirements
- Prompt access revocation upon termination or role change
9.3 Secure Workstations
- Full-disk encryption required on all devices
- Screen lock requirements
- Automatic security updates
- Secure configuration baselines
10. Vendor Management
10.1 Vendor Selection
We evaluate vendors based on:
- Security certifications and compliance (SOC 2, ISO 27001)
- Data protection practices and policies
- Track record and reputation
- Contractual commitments to security and privacy
10.2 Ongoing Management
- Regular review of vendor security posture
- Monitoring vendor security advisories
- Prompt response to vendor security incidents
- Annual reassessment of critical vendors
10.3 Current Vendors
A current list of our sub-processors and their security certifications is maintained in our Data Processing Agreement.
11. Compliance
11.1 Regulatory Compliance
Our security program is designed to support compliance with:
- California Consumer Privacy Act (CCPA/CPRA)
- General Data Protection Regulation (GDPR) where applicable
- Telephone Consumer Protection Act (TCPA) for SMS communications
- CAN-SPAM Act for email communications
- Payment Card Industry Data Security Standard (PCI DSS) for payment processing
11.2 Security Assessments
- Regular internal security assessments
- Vulnerability scanning of production systems
- Third-party penetration testing (annual)
- Continuous monitoring for new vulnerabilities
11.3 Certifications
Our infrastructure providers maintain SOC 2 Type II and ISO 27001 certifications. We can provide documentation upon request for customers with specific compliance requirements.
12. Security Contact
For security-related inquiries, to report a vulnerability, or to request additional information about our security practices, please contact us:
GuestPass Plus - Security Team
Security Inquiries: security@guestpassplus.com
Vulnerability Reports: security@guestpassplus.com
Privacy: privacy@guestpassplus.com
Responsible Disclosure
We appreciate security researchers who report vulnerabilities responsibly. If you discover a security issue, please report it to us privately before any public disclosure. We commit to acknowledging reports within 24 hours and providing regular updates on our investigation.