Your data

Your organization's data stays yours. An admin can download all of it at any time, and can ask DeepLeaf to delete the organization.

Download all your data

1. Sign in to the app with an admin key and open Access keys from the account menu.
2. Under Your data, choose Download all our data. The browser saves one zip file.
3. To include the walk videos, photos, and frames, choose With walk videos and frames. That file can be large. If it is over the size allowed for one download, the app says so; download the data without media and write to us for the media.

Member keys don't see the button, and a member key that asks for the file gets 403. A script can fetch the same file with an admin key: GET /api/organizations/{org}/export.zip, adding ?media=1 for media.

What is in the file

• One JSON file per kind of record, each a list of rows: your organization, access keys (name, role, dates), farms, greenhouses, rows, crop cycles, saved walks, walk corrections, harvests, irrigation, climate readings, weekly summaries, stored forecasts, fruit weight settings, your billing account, monthly walk counts, invoices, payments recorded on them, and the bank payments applied to your invoices.
• Walk corrections are in walk_corrections.json: each ripeness change, removed or added fruit, and typed count, with the walk and the key that made it.
• A README.txt that describes each file and its units.
• With media, a media/ folder with one folder per walk.

Only your organization's rows are in it. It never contains key values (DeepLeaf Yield keeps only a one-way hash), sign-in sessions, payment provider references, DeepLeaf's internal notes, or DeepLeaf's own bank account details.

Deleting your organization

Deleting an organization removes everything listed above, walk corrections included, revokes and removes every key, and removes the walk media. It can't be done from the app. An admin of the organization writes to hello@deepleaf.io from a known address, with the organization id.

• Download your data first if you might need it. DeepLeaf can't send it after the delete.
• A card plan must be canceled, and open invoices paid or canceled, before the delete. DeepLeaf tells you if anything is still open.
• DeepLeaf takes a backup just before the delete, as a safeguard against a mistake. Ask in the same message if you want to know when that backup is removed.
• DeepLeaf keeps a short record that the organization was deleted: its id, how many records were removed, and when. Nothing else about you.

Access request details

When you request access, DeepLeaf keeps what you typed in the form to review the request: the organization name, your name and email, the country, the area, the tomato type, and your note. Only a hash of the claim code is kept.

• Those details are cleared 90 days after DeepLeaf approves or declines the request. What remains is only that a request was made, when, and how it was decided.
• They are not part of the organization download. Deleting the organization also removes its request.