Privacy policy

Information we collect

Capacity requests collect your name, company, email, phone number, pickup location, city and state, optional ZIP code, approximate pounds per day, linen type, completion deadline, and optional notes.

When you contact us about supplying capacity, we receive the information you send by email, which may include plant/company name, contact name, email, phone number, city/state, hospitality processing capabilities, and notes. Opening an email draft does not submit this information to Flatwork.

We also maintain supplier business and contact details, location and processing information, outreach history, replies, and operational records used to handle requests. Supplier information may be imported into our internal records or updated from communications.

How we use information

We use information to handle capacity requests, identify relevant plants, send request receipts and updates, ask plants whether they may be able to help, make introductions, and maintain service records. We use supplier information and replies to assess relevant opportunities and manage future outreach.

Request records include status, outreach and introduction activity, email delivery records, and supplier replies. Operational messages help us track a request and communicate with the parties involved.

Request sharing and introductions

Requests are not posted publicly, and suppliers are not publicly listed as available capacity. Relevant plants are contacted selectively. Initial outreach describes the city, approximate volume, linen type, and deadline without naming the buyer or giving the buyer’s contact details or exact pickup address.

When a plant is interested, an introduction email connects the buyer and supplier, sharing names, company context, and email addresses so they can discuss the load and agree on terms directly. Information you subsequently share with another plant is handled by that plant.

Keep request notes focused on the processing need and avoid including unnecessary personal or sensitive information.

Website analytics and browser storage

When configured, Flatwork uses PostHog for website page views, departures, and capacity-request interactions such as starting or submitting a request. It also measures supplier-interest email clicks, calculator use, and resource print/copy clicks without collecting entered values or copied text. Analytics can include anonymous browser, device, screen, and session identifiers, public page paths, referring domains, and campaign parameters.

The analytics implementation filters out form values, request identifiers, private request links, and arbitrary event properties. Analytics events from private request, internal, and API paths are excluded. Session recording, automatic interaction capture, and person profiles are disabled.

PostHog may use browser storage to maintain anonymous identifiers. You can manage browser storage through your browser settings.

Service providers

Flatwork uses third-party infrastructure to operate the service: Vercel for application hosting, Supabase/PostgreSQL for operational records, Google Gmail for sending and receiving operational emails, and PostHog for analytics when configured.

The U.S. Census Bureau geocoding service receives pickup street address, city, state, and ZIP code when available to help determine a location for matching nearby plants. These providers receive information needed for their role in the service.

Retention and access

We retain information as needed to operate the service and maintain business records. No fixed automatic deletion period is specified for request, supplier, or communication records.

Private request pages use a dedicated access link. Treat that link as private: anyone with it may be able to view and manage the request. Internal operational pages require operator authentication.

Questions and updates

For privacy questions, corrections to your contact or plant information, or requests concerning your information or supplier outreach, email jamie@flatwork.net. We will review your request in the context of the service and applicable requirements.

We may update this policy as the service changes. The last updated date above identifies the current version.