Effective October 4, 2026
Everglades OS is an internal operations application operated by Everglades Oysters LLC for authorized company personnel.
Information Used
The application processes company work records, farm and warehouse inventory, compliance records and attachments, customer and supplier business contacts, orders, delivery activity, assigned work, and connected calendar events. Authorized financial views may use QuickBooks company information, accounting balances, receivables, payables, and sales reports. The application also records the identity of the person making a change and associated audit information.
When enabled and permitted by the user, dictation supplies audio for transcription, and location features supply device coordinates for farm records or delivery tracking. Connecting an external account uses that provider’s authorization process. Connection tokens are stored encrypted on the application server and are not displayed to employees.
Purpose and Access
Information is used to plan and record company work, maintain traceability and compliance evidence, support customers, and display operational and financial analysis. Access depends on the employee’s authorized role. QuickBooks financial access in this pilot is restricted to the approved executive accounts. The current QuickBooks integration reads accounting data; it does not create payments or accounting transactions.
Service Providers
Everglades OS uses Google services for company identity, infrastructure, mapping, and authorized calendar connections. OpenAI processes relevant conversation context and audio when AI assistance or transcription is used. Enabled integrations may exchange information with HubSpot, Intuit QuickBooks, or the company’s delivery messaging provider for the requested workflow. Data sent to a provider is subject to the company’s agreement with that provider. This application does not sell employee or customer information.
Records and Retention
Company operational records and audit evidence are retained under the company’s recordkeeping requirements. Disconnecting an integration prevents future use of that connection; it does not automatically erase previously imported company records. Retention periods, correction requests, and any deletion of records must be managed by an authorized company administrator. Historical compliance evidence is corrected through traceable records rather than silently overwritten.
Security and Choices
The local pilot is for development testing. Team access to a hosted deployment requires company authentication and role controls. Connection secrets are kept on the server; hosted transmission must use HTTPS. Employees should use approved company accounts and report incorrect access or data promptly. Calendar and other provider authorizations can also be revoked through the provider’s account settings.
Contact and Changes
For access, corrections, privacy questions, or concerns, contact fabio@evergladesoysters.com. The company may update this policy as the application and integrations change. Material changes should be communicated to authorized users.