Privacy policy

1. What we hold

• Account information: your name, email address, and your role in an organization. Passwords are handled by our authentication provider and are never visible to us.
• Farm records you enter or import: entities, farms, fields and their boundaries, crops, operations, products, purchases, machinery, leases and landowners, budgets, documents you upload, and notes.
• Records read from services you connect (section 2).
• Operational logs: which integration calls were made and when, sync results, error messages, and counts of AI-assisted actions per user. These hold no passwords or tokens.

2. Services you connect

Each connection is made by an administrator of your organization, through the other service's own sign-in and consent screen. We never see your password for those services.

• QuickBooks Online (Intuit). With the Accounting permission, the product reads each connected company file's company information, chart of accounts, and general ledger transactions (date, account, amount, document number, vendor or customer name, class, and memo). It uses them to map accounts to cost categories, allocate overhead to field crops, and compare the books with the costs recorded here. Writing to QuickBooks (vendor bills, rent bills) is off unless an administrator switches a specific push on, and every write is previewed first. The product does not read payroll details, bank credentials, or payment card data.
• John Deere Operations Center. Organizations, fields and boundaries, field operations, products, machines, engine hours, and fuel, for the organizations your Deere administrator grants.
• Turnrow Grain. Production, marketing prices, income, and bin stocks flow in; land records and cost assumptions flow out, under the pairing an administrator sets up.

Nothing read from a connected service changes your fields, boundaries, operations, or products until a person in your organization accepts it on a review page.

3. How connection credentials are protected

• Access and refresh tokens are encrypted at rest (AES-256-GCM) under a key held only in the server environment. They are opened in server memory at the moment of a call and are never sent to a browser, written to logs, or included in exports.
• All traffic is encrypted in transit (TLS).
• A QuickBooks company file can be attached to only one entity, and a file already attached elsewhere is refused before any token is stored.

4. How your organization's data is kept apart

Every record carries its organization, and the database enforces row-level isolation on every table, so a signed-in user can read and write only the organizations they belong to. Cost and financial figures are further limited to the roles your administrator allows to see them.

5. Who processes data for us

We use a small number of service providers to run the product. Each receives only what its job needs.

• Supabase: the database, file storage, and sign-in.
• Vercel: hosting for the web application and its scheduled jobs.
• Mapbox: satellite imagery and map rendering. Field locations are sent as map requests so the imagery can be drawn.
• Anthropic: the AI-assisted features, when a user chooses to use one. Reading an uploaded sheet, photo, or note sends that content; proposing a chart-of-accounts mapping sends account numbers, names, and types (never transaction lines or amounts); explaining a lease settlement sends that settlement's rows. Content sent through the API is not used to train Anthropic's models.

We do not sell personal information or share it with advertisers or data brokers.

6. Disconnecting and deleting

• An administrator can disconnect any service at any time from Settings, Integrations. For QuickBooks, disconnecting revokes the token at Intuit, deletes the stored tokens and the company identifier, and stops all reads at once. You can also disconnect from inside QuickBooks (Apps, then Disconnect); the product notices on its next refresh and stops.
• Records already pulled stay in your organization so your history and reports remain whole. To have pulled QuickBooks data, any other data, or your whole organization deleted, write to stuart@turnrow.farm from an administrator's address. We delete it within 30 days and confirm when it is done. Encrypted backups age out within a further 30 days.
• You can ask us for a copy of your organization's data, or to correct account information, at the same address.

7. Retention

We keep your organization's records for as long as the organization has an account, because farm and lease records are useful across years. Integration call logs are removed after about two months. After an account is closed we delete its data within 60 days unless the law requires us to keep something longer.

8. Security incidents

If we learn of unauthorized access to your organization's data, we will tell the organization's administrators without undue delay, say what was affected, and say what we have done about it. Where the incident involves data from a connected service, we also notify that service as its terms require.

9. Cookies

The product uses the cookies needed to keep you signed in, and stores display preferences (such as map layers) in your browser. It uses no advertising or cross-site tracking cookies.

10. Children

The product is for farm businesses and is not directed to children under 13.

11. Changes and contact

If this policy changes in a way that matters, we will tell organization administrators by email or in the product before the change takes effect. Questions and requests: stuart@turnrow.farm. See also the terms of use.