Your customer relationships, operational information, documents, and workflow data deserve thoughtful protection. FreshToFr8 pairs layered application controls — tenant isolation, role-based permissions, and audit history — with established cloud infrastructure providers, and describes both plainly.
FreshToFr8's most important security controls are implemented in the application and database layers, where they apply to every request — not just to what the interface shows.
FreshToFr8 is a multi-tenant application. Each company operates in its own workspace, and tenant-level authorization is enforced in the database using Row Level Security — not only in the interface. These controls are designed so authenticated users can access records belonging to the companies and workspaces they are authorized to use.
Access requires an authenticated account — email/password or Google sign-in. Inside a workspace, Admin and Team Member roles govern what each person can do. Records are private to their owner by default and shared deliberately at View, Edit, or Manage levels. Platform administration is separated from customer workspace access through a distinct administrative role.
Ask Your Workspace is designed to operate within the signed-in user's workspace context. It retrieves only the records that user is already authorized to open — never a coworker's private records and never another company's workspace. It summarizes and recommends; it does not act on your accounts.
Customer documents are stored in workspace-scoped storage with access checks applied to every file path. Document access follows the permissions of the customer record it belongs to. Data is encrypted in transit, and encryption at rest is provided by our infrastructure providers; this provider-level encryption is distinct from application-level, end-to-end encryption, which FreshToFr8 does not currently offer.
Significant workspace events — pipeline stage changes, onboarding updates, cargo risk overrides, and document activity — are recorded so companies can review what happened and when.
Company Admins manage their own team's access: inviting members, disabling or re-enabling accounts, and controlling record sharing — so access can be removed promptly when roles change.
FreshToFr8 runs on established cloud and application infrastructure rather than self-managed servers. Our backend platform — providing the database, authentication, and file storage — is Supabase, which operates on major cloud infrastructure.
Our infrastructure provider Supabase maintains SOC 2 Type II and ISO 27001 certifications for its platform. These are the service provider's own audited credentials.
Connections to FreshToFr8 are encrypted in transit with TLS, and data at rest is encrypted by our infrastructure providers. Provider-managed encryption is an infrastructure control, separate from the application-level authorization controls described above.
These certifications apply to the service provider and do not represent an independent SOC 2 or ISO 27001 certification of FreshToFr8. We attribute them to the vendor that earned them.
FreshToFr8's subscription billing architecture is built on Stripe, with payment collection designed to use Stripe-hosted payment components. Under this design, raw payment card numbers are entered into Stripe's hosted interface and are not stored on FreshToFr8 systems. Online checkout is being rolled out; until it is enabled for your company, billing is arranged directly with FreshToFr8 and no card is collected in the app. FreshToFr8 does not claim PCI DSS certification; card data handling is delegated to Stripe by design.
FreshToFr8 offers an optional Microsoft Outlook calendar integration. When enabled, each user authorizes their own Microsoft account through Microsoft's OAuth sign-in, the connection is specific to that user, and it can be disconnected at any time from workspace settings. Connection credentials are stored encrypted on the server. The Outlook integration is separate from signing in to FreshToFr8 itself.
FreshToFr8 collects and uses information to operate the service: running your workspace, supporting your team, and improving the product. Access to workspace data is limited according to application roles and tenant context, as described on this page.
FreshToFr8 is a logistics relationship and workflow platform — not a system of record for highly regulated data. Please do not upload protected health information, payment card numbers, passwords, government classified material, or similarly sensitive data unless FreshToFr8 has expressly agreed in writing to process it under applicable contractual and compliance requirements.
FreshToFr8 protects the application and configures its infrastructure providers responsibly. Your organization owns the rest of the equation: choosing who gets a seat, keeping account credentials hygienic, entering only data appropriate for the platform, and removing access promptly when employees leave or change roles. The strongest tenant isolation in the world can't compensate for a shared password.
We distinguish carefully between three things that are often blurred together:
FreshToFr8 application controls
Infrastructure provider certifications
Independent FreshToFr8 attestations
FreshToFr8 does not currently hold its own SOC 2, ISO 27001, HIPAA, or PCI DSS certification, and we do not claim otherwise. FreshToFr8 is an evolving SaaS platform: we build on established providers with mature security programs while continuing to formalize our own security governance and controls. If your procurement process requires a specific attestation, ask us directly — we would rather answer honestly than imply a certification we have not earned.
Procurement reviews, security questionnaires, and technical questions are welcome. Reach the FreshToFr8 team through our inquiry form and we'll respond directly.