Security & Compliance

Backup and disaster recovery

FretTrack uses provider recovery points, independently retained database exports, actual Storage object backups, encrypted local and offsite repositories, and isolated restore exercises. No production system is used as a restore-test target.

Layered recovery

Supabase-managed database recovery points are useful, but they do not include the bytes stored through the Storage API. FretTrack's independent recovery design therefore uses separate logical PostgreSQL exports, Storage object inventories and files, and application source archives at known commits.

  • Database exports include application, private-function, Auth metadata, Storage metadata, and migration schemas.
  • Storage objects are downloaded separately and recorded with sizes and SHA-256 hashes.
  • Verified full snapshots are encrypted with Restic locally and again in an offsite OneDrive repository.
  • The Linux schedule is designed to run independently on TrueNAS rather than depending on a development workstation; the existing Windows schedule remains active until cutover evidence is approved.

Fail-closed verification

Each corrected snapshot has an immutable manifest. Verification writes separate evidence so routine checks do not rewrite the manifest. A backup is rejected when required schemas, functions and procedures, cross-schema trigger functions, extension inventories, exact row counts, Storage inventories, or checksums are missing.

Retention deletion is disabled by default and cannot proceed merely because a backup command ran. A recent verified and replicated full snapshot is required before a snapshot can become eligible under an approved retention policy.

Restore testing

Database testing uses an ephemeral, network-isolated Supabase-compatible PostgreSQL target. The test provisions recorded extensions, restores the archive, compares exact table row counts, and verifies cross-schema functions and triggers. Storage testing recreates buckets in a disposable target, restores every object, and downloads and compares every byte by SHA-256 without recording customer filenames or contents in its evidence. Separate isolated checks validate Auth startup, disposable sessions, shop separation, application build/startup, and recovered application-data access.

Detailed evidence remains restricted. Public status notices are reserved for confirmed customer-impacting outages or recovery activity, not routine backup operations.

Current validation status

An October 11, 2026 exercise successfully restored and verified both local and offsite encrypted copies and correctly exposed that the older database archive omitted a custom private schema. On October 13, corrected production snapshot full-20261013T075420Z passed a timed 89.532-second isolated exercise covering Database, Auth, REST, Storage, role and tenant isolation, refresh/revocation, captured recovery email, exact-source application startup, browser navigation/logout, and recovered customer photo rendering. Storage recovery verified 4 private buckets, 347 objects, and 62,552,635 bytes with zero missing files or checksum mismatches. Attachment rendering awaits a snapshot containing attachments, and recovered real-factor plus Edge/scheduled runtime exercises remain open. This is recovery-test evidence, not an RTO guarantee or SOC 2 certification.

FretTrack is building toward SOC 2 readiness. It does not claim SOC 2 certification, completion of an independent audit, or a guaranteed recovery time.