PII & Encryption

How BindPilot encrypts personally identifiable information

PII & Encryption

BindPilot encrypts sensitive personal information (PII) to protect against unauthorized access.

What Is PII?

Personally Identifiable Information includes:

  • Social Security Number (SSN)
  • Date of Birth (DOB)
  • Driver License Number
  • Bank Account Numbers
  • Medical Records
  • Immigration Status / Visa Info

Storing PII in insurance systems requires careful handling per state regulations.

Encryption Standards

BindPilot uses AES-256 encryption (Advanced Encryption Standard):

  • Strength: 256-bit key (practically unbreakable)
  • Algorithm: AES (NIST-approved, military-grade)
  • Mode: GCM (provides authentication + confidentiality)
  • Key Rotation: Quarterly

In Transit (TLS 1.3)

All data sent between your browser/app and BindPilot servers:

  • Encrypted: TLS 1.3 (Transport Layer Security)
  • Certificate: Valid SSL/TLS certificate (verified by browser)
  • No Man-in-the-Middle: Eavesdropping impossible

You know it's secure when you see:

  • URL starts with https:// (not http://)
  • Lock icon in browser address bar
  • No browser security warnings

At Rest (Database Encryption)

All data stored in BindPilot's databases:

  • Encrypted: AES-256 at the field level
  • Key Management: Encryption keys stored separately from data
  • Access: Only authorized BindPilot systems can decrypt

Even if a hacker accessed the database directly, data would be gibberish without the encryption key.

Sensitive Field Handling

SSN (Social Security Number)

Storage: Encrypted (stored as ciphertext in database) Display: Masked in UI (shows only last 4 digits: *--1234) Use Cases:

  • FICO/credit check (used for underwriting, not stored)
  • Tax records (kept for 7 years, encrypted)
  • License verification (checked against NIPR, not stored)

State Regulations:

  • Some states prohibit SSN collection (ask first)
  • Vermont, Massachusetts, Nevada have strict SSN rules
  • BindPilot respects state-specific restrictions

DOB (Date of Birth)

Storage: Encrypted Display: Shown in UI (medium sensitivity) Use: Age-based risk assessment, rating

Driver License

Storage: Encrypted Display: Last 4 digits visible (for verification) Use: Auto underwriting, identity verification

Bank Account

Storage: Encrypted OR not stored Best Practice: Ask if really needed (most carriers don't require it) If stored: Encrypted with quarterly key rotation

Medical Records

Storage: Not directly stored; linked via secure upload only Encryption: File encrypted before upload to BindPilot Retention: Deleted after 1 year or per your request

CCPA & State Privacy Laws

BindPilot complies with state-by-state PII rules:

| State | Rule | BindPilot Compliance | |-------|------|----------------------| | California (CCPA) | Can't sell SSN, DOB | We don't sell any data | | Massachusetts 201 CMR 17.00 | SSN special handling | Encrypted, separate from other data | | Vermont | Can't require SSN | We request only if needed | | Nevada | Can't use SSN for ID | We verify via other means | | New York | Notification if breach | 24-hour notification |

Encryption in Backups

BindPilot's automated backups:

  • Encrypted: Backups encrypted with same AES-256 standard
  • Geographic Redundancy: Copies in multiple US regions
  • Access: Only authorized personnel can restore
  • Retention: Kept for 30 days (older backups deleted)

If you request data export:

  • Option 1: Encrypted ZIP file (you receive encryption key separately)
  • Option 2: Plaintext CSV (only over TLS; you download securely)

Key Management

Encryption keys are protected by:

| Protection | Details | |-----------|---------| | Separation | Keys stored separately from encrypted data | | Rotation | Keys rotated quarterly | | Access Log | Every key access logged and audited | | Disaster Recovery | Multiple key copies in secure vault | | HSM | Hardware Security Module (planned for SOC 2) |

What BindPilot Can & Cannot Do

Can Access Your Encrypted Data:

  • BindPilot's system (via server-side decryption)
  • You (as the account owner)
  • Your team members (per their role)

Cannot Access:

  • A person with database access but no encryption key
  • A hacker without the key
  • Government agencies (without legal process)
  • BindPilot staff casually (keys required, access logged)

In Case of Breach:

  • Hacker gets encrypted data (useless without key)
  • We detect access, revoke keys, rotate keys
  • Your encrypted data is now inaccessible even to the hacker

Checking Encryption in Your Browser

See TLS certificate details:

  1. Go to BindPilot in your browser
  2. Click the lock icon in address bar
  3. Click "Certificate" or "Details"
  4. You'll see:
    • Issued to: BindPilot
    • Issued by: Certificate Authority (Cloudflare, DigiCert, etc.)
    • Valid from/to: Expiration date
    • Cipher: TLS_AES_256_GCM_SHA384 (or similar)

This verifies secure encryption is active.

Best Practices When Using BindPilot

  1. Use HTTPS — Always; never use HTTP
  2. Lock your device — Don't leave BindPilot open unattended
  3. Strong password — 12+ chars, unique to BindPilot
  4. Don't screenshot SSN — Avoid storing sensitive data locally
  5. Log out when done — Automatic after 1 hour
  6. Report issues — Email security@bindpilot.ai if something feels off

Next: Backup & Recovery and State Insurance Regulations.

Last updated: Recently