Privacy Policy
Effective August 12, 2026 · Octoflow
This policy explains what Octoflow (“Octoflow”, “we”, “us”) collects when you use the Octoflow website and services, why we collect it, who else handles it, and how to have it removed. It forms part of our Terms of Service.
The short version: we collect what is needed to take your order, get it cooked and get it paid for. We do not sell it, we do not use it for advertising, and we will delete it if you ask.
1. Who this applies to
This policy covers everyone who uses the Service: members who order meals, administrators who run a community, and owners and staff of the kitchens that cook. Where it matters, the sections below say which.
The Service is operated from, and its data is stored in, the United States. If you use it from elsewhere, you are sending your information to the United States.
2. What we collect
From signing in. Accounts are created through a third-party identity provider. We receive your name and email address from it, and store those along with a profile photo if you set one. We never receive your password for that provider, and we do not store one of our own.
From using the Service as a member. The community you belong to; the orders you place — which dishes, in what quantities, for which week, from which kitchen; what you were charged and the status of the payment; and the times these happened.
From running a community or a kitchen. Business details you enter: the business name and description, its street address and approximate coordinates, its time zone, a contact phone number for the business, logos and photographs, menu and dish information, and — for kitchens — the identifier and status of the Stripe account payouts are sent to.
From invitations. If you invite someone to a community, we store the email address you sent the invitation to so we can deliver it and match it when they join.
Automatically. Ordinary server and access logs — IP address, browser and device information, pages and API requests, timestamps and errors — kept for security, debugging and abuse prevention.
Some things we deliberately do not collect.
Card numbers. Payment details are entered directly with Stripe and never reach Octoflow’s servers. We store only Stripe’s reference for the payment, the amounts and the status.
Allergies, dietary needs or anything about your health. The Service has no field for them, and you should not put them into one that exists for something else. Allergen information on the Service describes dishes, not people.
A personal phone number. We do not ask members for one. The phone numbers we hold belong to businesses, not to individuals.
3. Why we use it
We use the information above only to:
- create and authenticate your account, and place you in the right community;
- take, price, confirm and record orders, and pass the counts to the kitchen that has to cook them;
- process payments and send payouts, through Stripe;
- send transactional email — order confirmations, receipts, delivery and cancellation notices, invitations, and payout notices to kitchens;
- show communities and kitchens the information they need to run a week;
- operate, secure, debug and improve the Service, and detect fraud and abuse;
- comply with law, tax and accounting obligations, and resolve disputes.
We do not use your information to build advertising profiles, and we do not run third-party advertising or analytics trackers on the Service.
4. Who can see your information inside the Service
Your community administrator can see that you are a member of their community and what you ordered — your name, the dishes and quantities, and the order’s status.
The kitchen cooking your week can see the order it has to prepare and the totals for the delivery.
We can see all of it, and do look at individual orders when something goes wrong or someone asks us to.
Other members of your community cannot see your orders through the Service. What happens to a delivery once it is dropped in a shared space is between you and your community.
5. Service providers who process it for us
We use a small number of providers to run the Service. Each handles only what it needs for its function, processes it on our instructions, and is bound by its own agreement with us. All are based in the United States.
- Stripe — payments, refunds, payouts and kitchen onboarding. Receives your name, email, payment details and order amounts, and for kitchens the identity and bank information Stripe requires by law.
- Supabase — the database and the authentication system. Holds essentially everything in Section 2.
- Google Cloud and Firebase — hosting for our application programming interface and storage for uploaded images.
- Google — sign-in. When you sign in with Google, Google knows you did.
- Vercel — hosting for the website, including access logs.
- Resend — delivery of transactional email. Receives the recipient address and the contents of the message.
- Mapbox and Google Places — maps and address lookup when a business address is entered. Receives what is typed into the address field, not your account details.
- Telegram or Slack — our own internal operations feed. Confirmed orders generate a message to whoever runs Octoflow that includes the member’s name and email, the community, the kitchen and the amount charged. This is us reading our own notifications; it is named here because the message travels through a third party to get to us.
We may also disclose information to professional advisers, or to a successor in a merger, acquisition or sale of assets, in which case this policy continues to apply until it is replaced by one you are told about.
We will disclose information if the law requires it — a subpoena, a court order, a valid legal demand — or where we believe in good faith that it is necessary to protect someone from harm, or to establish or defend a legal claim.
6. We do not sell or share your information
We have never sold personal information, and we do not share it with anyone for their own purposes.
No advertising networks, no data brokers, no list rental, no cross-context behavioural advertising, and no disclosure to another company to market to you. The providers in Section 5 process our data on our behalf and are not permitted to use it for anything else. If this ever changes, we will say so here and tell you before it does.
8. Your choices, and removing your information
You can, at any time, ask us to:
- tell you what we hold about you;
- correct anything that is wrong;
- send you a copy of your account and order data;
- delete your information and close your account.
Email hello@octoflow.club from the address on your account and we will act on it within 30 days. There is no charge and we will not treat you differently for asking. If we cannot verify that the request came from you, we will ask before doing anything.
What deletion cannot reach, and why.
We keep records of completed transactions — what was charged, when, and to which order — for as long as tax, accounting and dispute-resolution obligations require, typically seven years. Those records are retained for that purpose only and are not used to contact you or to rebuild a profile of you.
Payment records also exist inside Stripe under Stripe’s own retention rules, which we do not control. We can delete our copy; we cannot delete Stripe’s.
Where an order is part of a week a kitchen has already been paid for, the record of the order survives; your name is removed from it where we are able to.
You can also unsubscribe from any non-essential email using the link in it. Transactional messages — receipts, order confirmations, delivery and cancellation notices — are part of the Service and continue while you have an account.
Depending on where you live, you may have specific statutory rights, including under California law, to know, delete, correct, and to opt out of sale or sharing. We extend the rights above to everyone, and — as Section 6 says — there is no sale or sharing to opt out of.
9. How long we keep things
Account information is kept while your account is open and deleted on request. Orders and payment records are kept as described in Section 8. Server and access logs are kept for a short period for security and debugging and then discarded. Invitations that are never accepted are deleted when they expire.
10. Security
Data is encrypted in transit, access to production systems is limited to the people who operate the Service, and card data never enters our systems at all. Database access is governed by row-level rules so that an account can only read what its role permits.
No system is perfectly secure, and we do not claim otherwise. If a breach affects your information, we will tell you and any regulator we are required to tell, without undue delay.
11. Children
The Service is for adults. It is not directed at children, and we do not knowingly collect information from anyone under 18. If you believe a child has given us information, email hello@octoflow.club and we will delete it.
12. Changes to this policy
We may update this policy. When we do, we will change the effective date at the top of this page, and for a material change — a new category of information, a new purpose, or a change to Section 6 — we will give notice in the Service or by email before it takes effect.
13. Contact
Questions about this policy, or a request under Section 8, go to hello@octoflow.club.