Privacy policy

Who we are and how to contact us

Meaty Foods provides meat preparation and distribution services for business customers and operates MeatyOps to support that work. For privacy questions, access requests, corrections or deletion requests, email info.meaty@gmail.com. Identify the account or business concerned; do not send passwords, Google tokens or other credentials.

Information we process

• Business and account information: names, business details, contact information, addresses, account identifiers, roles, password hashes and account recovery information.
• Operational records: prospects and proposed rates, orders, product and cut requirements, quantities, processing assignments, notes, messages, invoices, payments, adjustments and audit history.
• Delivery information, when those features are used: assigned locations and routes, device identifiers, location updates supplied by a delivery device, package scans, receiver names and delivery signatures.
• Website and service requests: hosting and service providers may process IP addresses, browser information, timestamps and diagnostic or security logs to deliver and protect the service.

The website’s inquiry tool prepares an email draft in your email application. It does not send the inquiry automatically. When you send an inquiry, we receive the information included in your email.

Google information and permissions

When an authorized owner connects Google, MeatyOps requests Drive access to support its workbook integration. The Google consent permission can allow viewing, creating, editing and deleting Drive files. The application uses that permission to identify the connected Google account, check the selected folder and its permissions, locate MeatyOps workbooks, create workbooks, and update their managed spreadsheet tabs.

We receive the connected account’s email address and Google account identifier, authorization tokens, and relevant folder, file and spreadsheet identifiers and metadata. MeatyOps writes order information to configured workbooks, including order numbers, products, cuts, requested and dispatched quantities, statuses and notes. The master can include customer names; processor workbooks contain assigned items and the fields selected by management.

The integration operates on the configured folder and managed or explicitly mapped workbooks. It does not use the permission to browse unrelated document contents. It can replace managed tab contents and remove the default Sheet1 tab while preparing a workbook. Google access does not give us your Google password.

How information is used

We use information to manage business relationships and accounts, fulfill and document orders, coordinate processing and delivery, maintain billing and payment records, provide requested communications and support, synchronize configured workbooks, and protect the service against misuse.

Google API information is used for the connected account and workbook features described here. We do not sell Google user data, use it for advertising, or use it to train generalized artificial intelligence or machine learning models. MeatyOps follows the Google API Services User Data Policy, including its Limited Use requirements.

Who can receive information

Operational information is available to authorized staff and assigned partners according to application permissions. Google workbook access also depends on the workbook owner’s Google sharing settings. Application field settings do not replace Google Drive sharing controls, and changing settings cannot withdraw copies already downloaded by another person.

Service providers process information needed to operate the relevant features. These include Cloudflare for hosting and application storage, Google for connected Drive and Sheets workbooks and for address or route lookups when those features are used, and email or messaging providers when recovery or business messaging features are used. We may disclose information when required by applicable law, to respond to lawful requests, or to protect accounts, people and the service. Google API information is shared only as permitted by the Google policy linked above.

Storage, security and retention

We use HTTPS, account authentication, role and assignment checks, password hashing, and encryption of stored Google refresh tokens. The application retains connection metadata and operational records needed to provide its features and maintain business and audit history.

Retention depends on the record’s purpose, account needs and applicable recordkeeping obligations. Disconnecting an integration or deleting an unused prospect does not automatically erase invoices, payments, delivery evidence or audit history. Copies in Google Drive remain subject to the connected account owner’s controls and Google’s own service policies.

Disconnecting Google and requesting deletion

The connected owner can use Disconnect Google in MeatyOps to stop synchronization and remove the stored Google refresh token and connected account identity. Access can also be revoked in Google Account connections. Existing workbooks and previously exported information are not automatically deleted when access is disconnected or revoked.

To request deletion of account information, Google connection metadata or other personal information, contact info.meaty@gmail.com. We may need to verify that you are authorized to make the request. We will assess the request and explain any records that must be retained for financial, operational, legal or audit purposes. To remove an existing workbook or restrict its sharing, the Google account owner should also use Google Drive controls.

Cookies and local storage

MeatyOps uses essential cookies for authentication and Google connection verification. Application and mobile features may use device storage for preferences or offline work. These public information pages do not use advertising or analytics cookies.

Audience and policy updates

The website and MeatyOps are intended for business users and authorized working teams, not for children. We may update this policy as the service changes and will display an updated effective date. If Google data will be used for a new purpose requiring consent, we will disclose that use and request the required consent before beginning it.