Privacy Policy

1. Information We Collect

BinFlow collects information needed to create farm accounts, authenticate users, process grain ticket photos, and maintain farm operating records.

• Account and membership information: farm name, user name or display name, email address, password authentication data handled by Supabase Auth, farm membership, role, and user ID.
• Contact information: information users provide when contacting BinFlow, including name, email address, phone number, and message content.
• Farm records: tickets, bins, inventory transactions, contracts, payment statuses, payment notes, delivery locations, driver names, weekly summary data, and related operational records entered by users.
• Ticket images and extracted data: grain ticket photos selected or captured by users, plus OCR results and reviewed ticket details.
• Technical information: authentication tokens, request metadata, server logs, device/browser information, and error information used to operate and troubleshoot the service.

BinFlow does not currently collect device location data through geolocation APIs. The current application code does not include advertising SDKs, third-party analytics SDKs, or crash analytics SDKs.

2. How We Use Information

BinFlow uses information to provide and support the product, including to:

• create accounts and authenticate users;
• connect users to the correct farm and enforce farm-level access;
• process grain ticket photos and extract ticket fields for user review;
• store and display ticket, bin, inventory, contract, payment, driver, and delivery-location records;
• generate dashboards, summaries, and operational views;
• send or prepare farm summaries and service communications where configured;
• secure, maintain, debug, and improve the service.

3. Ticket Image Processing And Service Providers

When a user uploads or captures a grain ticket photo, BinFlow sends the image to BinFlow's backend API for processing. The backend may send the image content to OpenAI to extract structured ticket information. The extracted information is returned to the user for review before it is saved as a farm record.

BinFlow uses Supabase for authentication and database services, Render for backend API hosting, GitHub Pages for the public website and frontend hosting, OpenAI for ticket-image extraction, and Resend for configured email delivery such as weekly farm summaries. These providers process information only as needed to operate BinFlow.

4. Billing And Financial Information

The current production application does not activate paid subscriptions or in-app billing. BinFlow does store farm-entered financial and operational records such as contract prices, ticket revenue calculations, payment status, payment date, amount received, payment references, and payment notes.

If subscriptions are activated in the future, payment processing will be handled by payment providers such as Stripe for web billing or Apple for iOS subscriptions where required. BinFlow does not intend to store raw credit card numbers.

5. Sharing And Disclosures

BinFlow does not sell personal information and does not use personal information for third-party advertising or cross-app tracking. BinFlow may share information with service providers that help operate the product, comply with law, protect rights and safety, or complete a business transfer such as a merger or acquisition.

6. Data Storage, Security, And Retention

BinFlow stores account and farm records using Supabase and operates its backend through Render. BinFlow uses authenticated requests, farm membership checks, and farm-scoped data access to help protect farm records. No internet service can guarantee absolute security.

Farm records are retained while an account is active and as needed for operational history, accounting, legal, support, security, and dispute-resolution purposes. Because grain tickets, inventory, contracts, and payment records may be part of a farm's operating history, deletion requests may result in account removal or anonymization while certain farm records are retained where legitimately necessary.

7. Account Deletion And Privacy Requests

Users may request access, correction, deletion, or other help with their information by contacting BinFlow using the contact information below. BinFlow will review the request and may need to verify the requester's identity and farm authority before changing or deleting information.

You can permanently delete your personal account from Settings > My Account > Delete account in BinFlow. You must confirm your email address, enter your current password, and acknowledge the consequences before deletion. Deletion removes your login, personal account profile, and farm membership, and removes your account reference and scanning name from retained ticket records.

Deleting your personal account does not delete other farm members or shared tickets, bins, balances, contracts, payments, and other farm business history. If you are the only Administrator and other members remain, an eligible member must become Administrator. If you are the farm's only member, farm access is archived while its business history is preserved. Closing a farm and requesting deletion of retained farm records are separate from deleting your personal login.

If stored files or another safety check prevent automatic completion, contact BinFlow for help completing your request. Retained farm records, service-provider records, security logs, and recovery backups may remain where legitimately necessary as described above; deleting an account does not promise immediate erasure from every provider or backup. Contact BinFlow to request a review of retained information or exercise other privacy rights.

8. Children's Privacy

BinFlow is intended for farm business and operational use. It is not directed to children under 13, and BinFlow does not knowingly collect personal information from children under 13.

9. Policy Updates

BinFlow may update this policy as the product, providers, laws, or business practices change. The effective date above will be updated when the policy changes materially.