Guspora
← Back to Legal

Guspora

Security

Last Updated: March 8, 2026

Infrastructure

Guspora is hosted entirely on Amazon Web Services (AWS), leveraging enterprise-grade infrastructure:

  • Compute: AWS ECS Fargate (serverless containers) with auto-scaling and zero-downtime deployments
  • Database: AWS RDS PostgreSQL with automated backups, point-in-time recovery (35-day retention), and Multi-AZ standby
  • Storage: AWS S3 with server-side encryption (AES-256) for all uploaded documents, photos, and reports
  • DNS & CDN: AWS Route 53 with health checks and failover routing
  • Region: US East (N. Virginia) — us-east-1

Encryption

  • In Transit: All connections use TLS 1.2+ (HTTPS enforced via HSTS). API endpoints reject unencrypted connections.
  • At Rest: Database storage encrypted with AWS-managed keys (AES-256). S3 objects encrypted with SSE-S3. Backups inherit encryption from the source.
  • Passwords: Hashed with bcrypt (cost factor 12). We never store plaintext passwords.

Access Control

Guspora implements Role-Based Access Control (RBAC) with six defined roles:

RoleAccess Scope
Platform AdminFull system access, tenant management, billing
Tenant OwnerOwn company data, billing, team management
TechnicianAssigned inspections, field data entry
Building OwnerOwn properties, compliance status (read-only)
AHJ OfficialJurisdiction inspection records (read-only)
Agent / LenderTransaction-linked property records (read-only)

Multi-Tenant Isolation

Every database query is scoped by tenant_id. Tenant isolation is enforced at the API layer — tenant identifiers are extracted from authenticated sessions, never from client input. Cross-tenant data access is architecturally prevented.

Authentication

  • Magic Link Authentication: Passwordless login via time-limited, single-use email codes
  • Biometric Authentication: Device-bound biometric unlock on mobile (Android)
  • CSRF Protection: All mutation endpoints require matching CSRF tokens
  • Session Management: HTTP-only, Secure, SameSite cookies with configurable expiration

Application Security

  • Content Security Policy: Strict CSP headers on all pages prevent XSS attacks
  • Input Validation: All API inputs are validated and parameterized queries prevent SQL injection
  • Rate Limiting: API rate limits prevent abuse (100–200 req/min per authenticated user)
  • Audit Logging: All write operations are logged with user, timestamp, IP, and change diffs
  • Dependency Scanning: Automated vulnerability scanning of npm dependencies

Privacy by Design

  • Face Blurring: On-device ML-powered face detection and blurring (default ON). Unblurred frames are never stored or transmitted.
  • Data Minimization: We collect only the data necessary for inspection management and compliance
  • Right to Deletion: Users can request account and data deletion via the platform or by contacting support

SOC 2 Readiness

Guspora is pursuing SOC 2 Type II certification. Our security controls are designed to meet the Trust Services Criteria for Security, Availability, and Confidentiality. Target completion: Q4 2026.

Responsible Disclosure

If you discover a security vulnerability, please report it responsibly to security@guspora.com. We commit to acknowledging reports within 48 hours and providing updates on remediation progress. We do not pursue legal action against researchers who act in good faith.

Security | Guspora™ | Guspora