Provider: The Fmly Group, LLC d/b/a Fried
As of: July 29, 2026
Fried uses the third-party sub-processors below to provide its restaurant-intelligence Service. We use them only to deliver and support the Service. We do not sell or share your data. This list is incorporated by reference into our Data Processing Addendum (DPA).
Notice of changes: We will provide notice before adding or replacing a sub-processor that processes Customer Data, so you have an opportunity to review and, if you reasonably object on data-protection grounds, to terminate. Notice will be given by updating this list (with a dated change) and/or by email to your account contact.
| Sub-processor | Purpose | Data categories processed | Location |
|---|---|---|---|
| Supabase | Application database and file storage, including encrypted storage of POS OAuth tokens in an access-controlled secrets store | Operator/account info; POS-derived business data (sales, labor — incl. employee identity and wage data); POS access tokens | US (global infrastructure) |
| Vercel | Application hosting and delivery of the dashboard and web app | Operator/account info; data in transit while rendering the app; minimal request/log metadata | US (global edge network) |
| Anthropic | AI processing to help generate the narrative portions of insights. Under Anthropic’s commercial API terms, it does not train on our inputs/outputs and retains them only briefly for trust and safety | Computed business metrics, summary figures, top-selling menu items, plus the restaurant name for context — no individual customer, employee, or wage records | US |
| Resend | Delivery of the daily insight email | Recipient name and email; the aggregated insight content of the email | US (global delivery) |
| Stripe | Billing and payment processing (used only if/when an account converts to paid). Card data goes only to Stripe and never touches Fried (PCI SAQ-A) | Billing contact info; payment card data (held by Stripe, not Fried) | US (global) |
| Cal.com | Scheduling for demo bookings. If you book a demo through our site, Cal.com hosts the booking form and sends us the resulting booking details | The name, email address, and booking details (meeting title, time, and booking reference) you submit when booking a demo — no POS, sales, or employee data | US |
| Google sign-in (OAuth) for account authentication, internal Google Workspace email used to operate the Service and respond to support requests, and Google Places to look up your restaurant’s name and address during onboarding | Operator/account info; authentication data; the content of any support email you send us; the restaurant name or address text you enter when searching for your location during onboarding | US (global) | |
| Connected POS vendors — Toast, Square | Connected at your direction via a secure connection (OAuth or credential entry, depending on the provider) so Fried can read your sales and labor data. These are your existing POS providers; Fried accesses them on your instruction, not as a sub-processor Fried independently selects to host your data | Sales, transaction, menu, and labor data (incl. employee identity and wage data) that Fried reads from the POS you connect | US (varies by vendor) |
This list reflects our sub-processors as of the date above. The current version of this list always governs. Questions: [email protected].