Trust & Security
Security at Attendir
Your event data deserves enterprise-grade protection. Here is how we keep it safe.
Encryption Everywhere
AES-256-CBC encryption for sensitive data at rest. TLS 1.2+ for all data in transit. Bcrypt-12 password hashing. No plaintext secrets.
Secure Authentication
Rate-limited login (5 attempts/min). Session regeneration on auth. Secure, HTTP-only, SameSite cookies. Google OAuth support.
Webhook Verification
HMAC-SHA256 signature verification on inbound webhooks from Eventbrite, Luma, Bizzabo, Cvent, and Stripe once a signing secret is configured for that integration.
GDPR Compliance
Data export, account deletion, privacy policy, cookie notice. Personal data collected when attendees choose to share, or when the organizer supplies it.
Audit Logging
All authentication events and data changes are logged with timestamps, IP addresses, and user agents. Full audit trail for compliance.
Security Headers
HSTS, Content Security Policy, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy headers on every response.
Data Encryption
Every connection to Attendir is encrypted with TLS 1.2 or higher. We enforce HTTPS across the entire platform — there is no way to access Attendir over an unencrypted connection.
Sensitive data at rest — including OAuth integration tokens and encrypted sessions — is protected with AES-256-CBC, the same encryption standard used by financial institutions. Passwords are hashed with bcrypt at cost factor 12, a one-way algorithm that cannot be reversed even if the database is compromised.
Access Controls
Attendir implements strict access controls at every layer:
- Authentication: Rate-limited login with a maximum of 5 attempts per minute. Session tokens are regenerated on every login to prevent session fixation.
- Authorization: Every resource (events, campaigns, billing) is protected by policy-based authorization. Users can only access their own data.
- CSRF Protection: All state-changing requests require valid CSRF tokens.
- Rate Limiting: All public endpoints are rate-limited to prevent abuse.
Integration Security
When you connect Attendir to event platforms like Eventbrite, Luma, Cvent, or Bizzabo, your integration credentials are encrypted with AES-256 before being stored. We never store credentials in plaintext.
Inbound webhooks are verified using HMAC-SHA256 signatures once a signing secret is configured for that integration; missing or incorrectly signed payloads are then rejected with a 403 error. Webhook replay protection deduplicates identical payloads within a 24-hour window, preventing attackers from re-triggering events.
OAuth flows use HMAC-signed state parameters to prevent cross-site request forgery during third-party authorization.
GDPR & Privacy
Attendir is designed for GDPR compliance from the ground up:
- Data minimization: We collect only the data necessary to power your event sharing campaigns.
- Consent-based collection: Event attendee data is collected when they actively choose to share an event via LinkedIn, or when the event organizer supplies it (for example, via a connected ticketing platform).
- Data export: Account holders can request a full export of their personal data in JSON format. Export files are automatically deleted after 7 days to minimize data retention.
- Account deletion: Users can delete their account at any time, which removes all associated personal data.
- Cookie notice: We display a cookie notice on first visit explaining that we use cookies for site analytics, with a link to our Privacy Policy.
For full details, see our Privacy Policy.
Monitoring & Incident Response
We maintain continuous monitoring through:
- Audit logging: All authentication events (login, logout, failed attempts), data changes (create, update, delete), password changes, and data exports are logged with timestamps, IP addresses, and user agents.
- Dependency scanning: We run vulnerability audits (composer audit, npm audit) on PHP and JavaScript dependencies.
We maintain a documented incident response plan with defined severity levels, response procedures, and communication protocols.
Infrastructure
Attendir runs on DigitalOcean managed infrastructure in Frankfurt, Germany (EU). The platform is protected by firewall rules and managed SSL certificates. Payment processing is handled by Stripe (PCI DSS Level 1 certified) — we never store credit card numbers or payment details on our servers.
Deployments are automated from our GitHub repository to production via a deploy pipeline that installs dependencies, runs database migrations, and builds frontend assets.
Data Residency & Sub-Processors
Attendir is hosted in DigitalOcean's Frankfurt, Germany (FRA1) data centre. Both the application and its database run in the EU, so core customer and attendee data — account details, imported attendee records, campaign configuration, and share analytics — is stored and processed within the European Union.
These are the key sub-processors that deliver specific platform functions:
- DigitalOcean — hosting & database — EU (Frankfurt, Germany)
- Stripe — payment processing (PCI DSS Level 1) — EU/US
- Resend — transactional email delivery — US
- Google — OAuth sign-in & analytics — US
Each sub-processor operates under a GDPR-compliant Data Processing Agreement relying on Standard Contractual Clauses and, where the provider is certified, the EU–US Data Privacy Framework. Event-platform integrations (Eventbrite, Luma, Cvent, Bizzabo) exchange data only when you explicitly connect them, and LinkedIn receives data only when an attendee actively chooses to share an event.
SOC 2 Readiness
Attendir has implemented controls aligned with the SOC 2 Trust Services Criteria and ISO 27001 standards, including:
- Information security policies and access control matrix
- Change management and deployment procedures
- Incident response plan with severity classification
- Risk assessment register with quarterly reviews
- Third-party vendor assessment process
- Disaster recovery plan with defined RTO and RPO
- Data classification and cryptographic controls policies
Frequently Asked Questions
Is Attendir GDPR compliant?
Yes. Attendir is fully GDPR compliant. We process personal data lawfully (consent or legitimate interest), support data subject rights including access, export, and deletion, and our data processing is documented in our Privacy Policy. Event attendee data is collected when they actively choose to share an event via LinkedIn, or when the event organizer supplies it (for example, via a connected ticketing platform).
How does Attendir encrypt data?
All data in transit is encrypted with TLS 1.2+. Sensitive data at rest, including OAuth integration tokens and sessions, is encrypted with AES-256-CBC. Passwords are hashed with bcrypt at cost factor 12, a one-way algorithm that cannot be reversed. OAuth flows use HMAC-signed state parameters to prevent CSRF.
Is Attendir SOC 2 certified?
No — Attendir is not SOC 2 certified and is not currently pursuing certification. We have, however, implemented internal controls aligned with the SOC 2 Trust Services Criteria, including access control policies, change management procedures, incident response plans, risk assessments, and audit logging.
Where is Attendir data hosted?
Attendir is hosted in DigitalOcean's Frankfurt, Germany (FRA1) data centre — both the application and its database run in the EU. Payment processing is handled by Stripe (PCI DSS Level 1 certified). We do not store credit card numbers or payment details on our servers.
Does Attendir transfer data outside the EU/EEA?
Core customer and attendee data is stored and processed in the EU (Frankfurt, Germany). A limited set of sub-processors handle specific functions and may process certain data in the US — Stripe (payments), Resend (transactional email), and Google (sign-in and analytics) — each under a GDPR Data Processing Agreement with Standard Contractual Clauses and, where the provider is certified, the EU–US Data Privacy Framework.
How do I report a security vulnerability?
Please email security concerns to info@attendir.com. We acknowledge reports within 48 hours and work to resolve confirmed vulnerabilities promptly. We appreciate responsible disclosure.