Security Overview

How we protect your production data

Document Version 1.6 | March 2026

Security Posture

Security Score: 7.7/10 Weekly review cycle Defense-in-depth architecture SOC 2 compliant infrastructure Multi-layer permission checks

Save this document for your records

Our Security Philosophy: Defense in Depth

We assume any single security control can fail. That's why Piper implements multiple overlapping security layers, ensuring that a breach of one layer does not compromise your data.

Layer 1: Network Security

HTTPS everywhere, security headers, WAF protection

Layer 2: Authentication

Passwordless login, encrypted sessions, secure tokens

Layer 3: Authorization

Role-based access, project permissions, API validation

Layer 4: Database Security

Row-level security, encrypted at rest, parameterized queries

Layer 5: Monitoring & Response

Audit logging, anomaly detection, incident response

Never Trust the Client

All permissions validated server-side

Least Privilege

Users only access what they need

Fail Closed

When in doubt, deny access

Encrypt Everything

Data protected in transit and at rest

Authentication

  • Passwordless Login

    No passwords to steal, guess, or forget. Sign in via secure email link or one-time code.

  • Secure Session Management

    Short-lived access tokens with automatic refresh. Sessions validated on every request.

  • OAuth 2.0 / OpenID Connect

    Sign in with Google using industry-standard protocols for secure third-party authentication.

  • Protected Routes

    Unauthenticated users automatically redirected. Direct URL access blocked without valid session.

Authorization & Access Control

Piper uses role-based access control (RBAC) to ensure users only see and modify what they're permitted to.

Role View Edit Admin
Client Assigned Projects Read Only -
Producer Assigned Projects Full Edit -
Company Admin All Company Projects Full Edit Company Users
  • Project-Level Permissions

    Users explicitly assigned to projects. No accidental data exposure across accounts.

  • Row-Level Security (RLS)

    Database enforces permissions at the row level. Even if application logic fails, data stays protected.

  • Client-Side Permission Checks

    All write operations validate permissions before execution. Defense-in-depth ensures multiple layers catch unauthorized access.

  • Entity-Level Isolation

    Legal entity data (companies owning projects) protected with dedicated RLS policies. Users only see entities linked to their accessible projects.

Data Security

  • Encryption in Transit

    All data transmitted over TLS 1.2+ (HTTPS). No unencrypted connections accepted.

  • Encryption at Rest

    Database encrypted with AES-256. Backups encrypted. Managed by SOC 2 compliant infrastructure.

  • Secure File Storage

    Documents and signed NDAs stored in isolated, access-controlled cloud storage buckets.

  • Database Backups

    Managed by SOC 2 compliant infrastructure. Daily automated backups on roadmap for Q1 2026.

API & Application Security

  • CORS Protection

    APIs only accept requests from whitelisted origins. No wildcard (*) access in production.

  • CSRF Prevention

    Token-based authentication plus X-Requested-With header validation blocks cross-site request forgery.

  • Rate Limiting

    API endpoints protected against abuse with automatic throttling. Prevents brute force attacks and controls costs.

  • SQL Injection Prevention

    All database queries use parameterized statements. No raw SQL concatenation.

  • XSS Protection

    Content Security Policy headers, input sanitization, and output encoding prevent script injection.

  • Security Headers

    HSTS, X-Content-Type-Options, X-Frame-Options, and CSP headers enabled on all responses.

Infrastructure & Compliance

Component Provider Compliance
Database & Auth Supabase SOC 2 Type II
Web Hosting SiteGround ISO 27001
CDN & DDoS Cloudflare SOC 2 Type II
Error Monitoring Sentry SOC 2 Type II
  • GDPR Considerations

    Data processing agreements requested with Supabase and Sentry (in progress). Error monitoring receives pseudonymized operational metadata (user IDs and roles) but no personal data such as names or email addresses. Data export and deletion requests handled manually - contact security@siteline.pro.

  • No Payment Card Storage

    PCI DSS not applicable - we do not store credit card or payment information.

Continuous Security Reviews

7d

Security Review Cycle

Our security architecture, protocols, and this document are reviewed and updated weekly to ensure we stay ahead of emerging threats.

  • Vulnerability Assessment

    Regular review of dependencies, configurations, and access patterns for potential vulnerabilities.

  • Protocol Updates

    Security measures updated based on latest best practices and threat intelligence.

  • Documentation Maintenance

    This security overview kept current with all implemented protections and roadmap items.

  • Security Event Logging

    Comprehensive audit trail capturing authentication events, permission changes, data access, and admin actions for investigation and compliance.

Incident Response

We have a defined incident response process to handle security events:

  • 1

    Identify & Contain

    Confirm the incident and isolate affected systems to prevent further impact.

  • 2

    Eradicate & Recover

    Remove the threat, restore systems from clean backups, and verify integrity.

  • 3

    Notify & Document

    Affected users notified within 72 hours. Full post-incident report and remediation.

Report security concerns: security@siteline.pro