FreightConnect

Security / Backup Recovery

Backup & Recovery

How FreightConnect ensures your data is safe and recoverable.

Backup Strategy

Frequency: Hourly automated backups

Retention:

  • Last 7 days: hourly backups (can restore to any point)
  • Last 30 days: daily snapshots
  • Last 90 days: weekly snapshots
  • Older: available on request (6+ month recovery is manual, slower)

Storage:

  • Primary: AWS S3 (multi-region)
  • Secondary: AWS Glacier (long-term cold storage)
  • Encryption: AES-256

Recovery Scenarios

Accidental Data Deletion

If you accidentally delete a load:

  1. Contact matt@freightconnect.ai within 7 days
  2. We restore from the nearest backup
  3. Restore takes 1-2 hours
  4. Deleted data is recovered

After 7 days, recovery is harder but still possible (older snapshots).

System Failure

If one server fails:

  1. Automatic failover (< 5 seconds downtime)
  2. Data is replicated across 3 availability zones
  3. Users are redirected to working servers
  4. No data loss

Data Corruption

If we detect corrupted data:

  1. Automated integrity checks detect it immediately
  2. Revert to the last good backup
  3. Minimal data loss (at most 1 hour of recent transactions)

Ransomware / Malicious Deletion

If an attacker deletes your data:

  1. Our monitoring detects unusual delete patterns
  2. We immediately snapshot the system
  3. We revert to a pre-attack backup
  4. Typically recover within 1-2 hours

Ransomware recovery is tested quarterly.

Recovery Time Objectives (RTO)

  • Minor issues (can't login): < 30 minutes
  • Data loss (deleted loads): < 2 hours
  • System failure: < 5 minutes (automatic failover)
  • Ransomware/major outage: < 4 hours (full system restore)

Recovery Point Objective (RPO)

  • Best case: < 1 hour (recent hourly backup)
  • Typical: < 4 hours (restoration process)
  • Worst case: < 1 day (older backups require manual retrieval)

We rarely lose more than 1-2 hours of data.

Disaster Recovery Plan

We maintain a documented DR plan:

  • Tested quarterly
  • Covers: data center failure, power outage, ransomware, natural disaster
  • Alternate data center can be spun up in < 4 hours
  • All team members trained on procedures

Copy of the DR plan is held by a third party (not accessible to attackers).

Backup Verification

We verify backups work:

  • Weekly: automatic test restore (read-only verify)
  • Quarterly: full test restore to a separate environment
  • Annually: third-party audit of backup procedures

If we can't restore from a backup, we immediately fix the issue.

Your Backup Responsibility

Best practice for you:

  1. Export your data monthly (Tools → Download Data)
  2. Store offline or in your own cloud storage
  3. This protects against our failure, hacks, or service discontinuation

We maintain backups, but you should too (defense in depth).

Geographic Redundancy

Data is replicated across:

  • US-East-1 (Virginia) — primary
  • US-West-1 (California) — secondary
  • US-West-2 (Oregon) — tertiary

If an entire AWS region fails (very rare), data is replicated elsewhere.

For EU customers (GDPR), data can be kept in EU regions only.

Backup Encryption

All backups are encrypted:

  • Algorithm: AES-256
  • Key management: AWS Secrets Manager (rotated quarterly)
  • Keys are never stored with backups (separate security domain)

Even if someone steals our backup media, they can't decrypt it without the keys.

Long-Term Archival

For compliance / legal holds:

  1. Go to Settings → Compliance → Create Archive
  2. Select date range (e.g., "all loads from 2024")
  3. We create an encrypted snapshot
  4. Download the archive or we store it for you

Archives are retained indefinitely if stored with us.

Ransomware Protection

Specific measures against ransomware:

  • Immutable backups — once written, can't be deleted or modified
  • Air-gapped storage — offline copies not accessible from the internet
  • Change detection — we monitor for suspicious bulk deletes
  • Snapshot-based — we snapshot before major system changes

We assume "zero trust" — even our admins can't delete old backups.

Failure Scenario Examples

Example 1: Hard drive fails

  • One server's drive dies
  • Automatic failover to replica
  • RTO: 5 seconds
  • RPO: 0 (fully replicated)

Example 2: Shipper email data lost

  • You accidentally delete a shipper record
  • Contact us within 7 days
  • We restore from hourly backup
  • RTO: 1-2 hours
  • RPO: < 1 hour

Example 3: Ransomware attack

  • Attacker encrypts your load data
  • Our integrity checks detect anomalies
  • We isolate affected systems
  • Restore from clean backup pre-attack
  • RTO: 2-4 hours
  • RPO: < 1 hour

Post-Incident Review

After any data loss incident:

  1. We investigate root cause
  2. We implement improvements to prevent recurrence
  3. We publish a post-mortem (if major incident)
  4. We update backup procedures if needed

SLA Guarantees

Enterprise customers have backup/recovery SLAs:

  • RTO ≤ 4 hours for total data loss
  • RPO ≤ 1 hour for non-critical systems
  • 99.99% data durability (4 nines)
  • Backup restoration tested monthly (verified in writing)

Brokerage/Solo use best-effort backups (tested quarterly).

Compliance & Audits

Our backup procedures are audited:

  • SOC 2 — includes backup adequacy review
  • GDPR — backups don't prevent "right to be forgotten" compliance
  • Third-party penetration testing — testers verify restore procedures work

Contact for Restore

To request a data restore:

  1. Email: matt@freightconnect.ai
  2. Subject: "Data Restore Request: [Load IDs or Date Range]"
  3. Include: what you want restored, when it was lost, why
  4. Timeline: 1-4 hours depending on backup age

Next Steps

Last updated: April 2026