How we handle your data

Aviation Inventory (“we”, “us”) runs the Aviation Inventory web app at zebradev.cloud and its companion phone app (together, the “service”). This policy covers the service and this website.

For your shop's records, your organization decides what goes in and who can see it; we process that data on its behalf.

Account details: your name, email, company name and role. Passwords are stored only in hashed form.

Your shop's records: parts, inventory, serial numbers, locations, work orders, aircraft tail numbers, purchase orders, vendors, certificates and documents you upload, plus your customers and the sales orders, quotations and exchanges you create for them.

Label photos: when you scan or classify a photo, we keep the text read from it (part number, serial, manufacturer) and a fingerprint of the image, so the same photo isn't paid for twice. We don't keep the photo itself. Documents you upload on purpose are stored.

Photos and listings: photos you add to a part are kept as Photo documents attached to that part. If your admin connects eBay, we also keep your eBay sign-in as tokens (cleared when an admin disconnects eBay; never your eBay password), your listing settings, and a record of each listing (title, price, quantity, condition, status and eBay's listing number).

Scrapped parts: scrapping a part is final. We keep a record of how it was disposed of, who checked it, why, who did it and when, as part of your shop's records.

Emails sent to your shop: each shop has a private request address. When a customer emails it, we keep the sender's name and address, the subject, the message text and up to five attachments (PDF, pictures, spreadsheets and documents), so your team can answer. Each order we email to a vendor also has its own reply address; a vendor's reply is kept with that order (sender, subject, text and up to five files) and a copy of the words is emailed to the person who placed it. These emails arrive on our own mail server, not through an outside mail service. The copy of a vendor's reply that we email to the person who placed the order goes out through our email provider.

Vendor records: for each vendor, the contact names, emails, phone numbers and addresses you enter, a second email for orders, the approvals you record for it (certificate type and number, who issued it, its dates and your notes, and a scan if you upload one), whether you have approved the vendor and who decided and when, whether a W-9 is on file and the date it came, and where to send payment if that is a different address. We do not check any of it with the issuer.

Shelf checks: when someone confirms a part on the shelf, we keep who checked it, when, and whether they found it.

Billing: your plan, invoices and a payment processor reference. Card numbers are entered on our payment processor's own checkout page, and we never see them.

Sign-in security: if you turn on two-factor sign-in, an encrypted copy of the secret your authenticator app uses, and your backup codes stored only as one-way hashes, which we can't read back to you.

Activity records (audit log): a record of who did what and when - the person's name, email, IP address and browser, and what a change was before and after, for stock, orders, approvals, vendor approvals, data exports, certificates, suspected unapproved parts, scrapping, eBay connection and listings, and settings. It is kept as part of your shop's compliance record, and users can't edit or delete entries.

Notification settings: which alerts you want and how, your quiet hours and time zone and, if you turn on push notifications on the phone, a push token with your phone's type and name.

People you invite: the names and email addresses of teammates, and of customers and vendors who are given a read-only portal login.

Technical logs: IP address, browser type and request times, kept by our servers for security and troubleshooting.

To run the service: store your records, read the labels you photograph, bill your subscription, sync with your accounting software if you connect it, keep the service secure, and answer your support requests.

We don't sell personal information, share it for advertising, or use it to build profiles. We don't use your shop's records to train AI models.

Shared parts database: when you save a part to your catalog, its part number, description, manufacturer, ATA chapter and unit of measure are added to a parts database every account can search, so other shops can identify the same part without a paid label read. It never includes your stock levels, prices, serial numbers, locations or anything that says which shop saved it. An admin can switch this off in Settings > Organization.

Shared price ranges (off by default): an admin can opt your shop in to price sharing in Settings > Organization. If they do, for each part number you have sold only a price range - lowest, median, highest and how many sales - is shared, never an individual sale, a customer, or your shop's name, and other opted-in shops see it merged with everyone else's. Turning sharing off deletes what you contributed. Prices suggested on your own quotations come from your own sales history and your own price rules, never from other shops.

Reports and suggestions - parts usage, vendor performance, compliance overviews, cost analysis, suggested orders and suggested prices - are worked out from your own records and shown only to the people your organization allows.

We use these companies to provide the service, each only for the job described:

Our AI provider's commercial terms don't allow it to train its models on data sent through its service. We may also disclose information if the law requires it.

Between shops on the service. When a shop chooses to send part details to a linked customer shop, the receiving shop sees a limited copy: part number, serial number, condition, release document type and number, life status of a life-limited part, the price charged, and the order's freight, handling and tax. The sender's own costs, margins and notes are never included. Only the shop it was sent to can see it. If the receiving shop adds the part to its inventory, it keeps that copy as its own record. If a shop reports a difference on arrival (a short quantity or a different serial number), the sending shop is told what was different.

Matching by email. To let a shop send part details to a customer who is not linked, we compare the customer's email address with the addresses of shop administrators. We use the match only to deliver a request; the receiving shop sees the sender's company name and order number until it accepts, and the sender is never told whether an address matched.

Chain of custody. A part sent between shops carries its history of holders (names, dates and release document references, never costs or notes). The receiving shop keeps that history with the part as its own record, and passes it on if it sells the part. The sender can withhold the names of earlier holders.

We set one cookie, which keeps you signed in. It's needed for the service to work and expires after 24 hours. Your browser also stores your sign-in token and any form you haven't saved yet, so a half-finished entry survives a page reload.

There are no analytics, advertising or tracking cookies.

The app asks for camera access to scan barcodes and photograph labels, and, if you want them, for permission to send notifications. It doesn't use your location, contacts or other photos on your device.

We keep your records while your organization has an account. After an account is closed, we delete its records within 90 days, except billing records we must keep for tax and accounting law. Copies in backups are overwritten on their normal cycle. Part numbers already added to the shared parts database stay there, since they don't identify your shop. The activity log stays with your records for as long as your account is open and is deleted with them; if you turn two-factor sign-in off, its stored secret and backup-code hashes are deleted.

You can ask for a copy of your personal information, ask us to correct it, or ask us to delete it. Email support@zebradev.cloud and we'll reply within 30 days. Depending on where you live, you may have further rights under laws such as the GDPR or California's CCPA; the same address handles those requests.

For your shop's records, your organization's admin can edit and delete records in the app, and can email us to delete the whole account.

Getting all your records out. An admin emails support@zebradev.cloud and we switch on a data export for your organization's admins, usually within 5 business days. We tell your admins when it is on, and it stays on for a limited time (7 days unless we agree otherwise). They then download everything as CSV files or an Excel workbook from Admin > Export my data. The export holds your records, including prices and costs; it leaves out passwords, sign-in details and uploaded scans. Only an admin of your organization can ask for it, so we check that the request comes from one. Switching it on, and each download, is written to your activity log.

Connections are encrypted (HTTPS). Each organization's records are kept separate from every other organization's, and access inside an organization follows the roles its admin sets. No system is perfectly secure; if a breach affects your information, we'll tell you as the law requires.

The service is for businesses and isn't meant for anyone under 16.

If we make a significant change, we'll tell account admins by email or in the app before it takes effect, and update the date at the top.

Aviation Inventory, Florida, United States · support@zebradev.cloud

See also our Terms of service.