Privacy Policy
Version 2026-09-01 · Effective September 1, 2026
This Privacy Policy explains what Data 486 LLC ("Data 486", "we", "us") collects, why, who else sees it, and how to get it back or get rid of it. It covers data486.com and every product we run: Business Meetings, Beef Squared, CropData, CalculateFoam, and 486 Creations.
One policy, all products. It replaces the separate privacy notices and per-product addenda that used to live on each site.
Two different roles run through this document. For your account and billing, we decide what is collected — we are the controller. For the records you enter into a product — your members, your herd, your customers — you decide, and we only hold and process them for you. Section 8 is the processing agreement that covers that half.
1. What we collect at data486.com
- Account: your name, email address, a hashed password (never the password itself), an internal id, and whether your email is verified.
- Billing: a Stripe customer id, your plan and subscription state, invoices, and the card brand plus last four digits. We never receive or store your full card number — Stripe does.
- Team: the account name, who owns it, who has been invited, and each member's role.
- Contact form: your name, email, organization if you give one, the product you asked about, and your message.
- Agreement records: which version of the Terms and this Policy you accepted, when, and the IP address you accepted from. We keep this because it is the proof of what you agreed to.
- Technical: a session cookie to keep you signed in, and server session records and logs that include IP address and browser user agent. No advertising trackers, no third-party analytics, no pixels.
2. What each product stores
Business Meetings — organization name; member names, family relationships (Head, Spouse, Child), positions, seats and term years; meetings, nominations, vote counts and results; access requests from the home page. If a church shares a pre-meeting nomination link, visitors may enter a first and last name, matched against the roster or queued for the operator — that public page never lists the roster or the other nominees. If a church connects schedule.church, we store the API token they paste (encrypted, never shown again) and import member names, membership status, and household grouping with Head/Spouse/Child roles; we do not import addresses or household names, and disconnecting deletes the token. Sign in with Apple gives us an identifier and, when Apple provides it, an email, used only to match an account that already exists. We also keep a daily count of visits to the public home page — a number only, no IP, device id, or tracking cookie.
Beef Squared — ranch (tenant) name, its members and their roles; the markets you follow; herd lots with class, frame, muscle grade, weights, counts and prices; trades and buy/sell scenarios; saved calculator drafts; and USDA AMS market reports pulled for your markets. If you supply a USDA MARS API key, it is stored encrypted and only the last four characters are ever displayed.
CropData — the agronomy shop's name and its Data 486 account id; the people who use it, with name, email address, a hashed password and their role. Then the working records: growers and field names, report dates, acres and sample depth, the summary text typed for a report, the nutrient baselines, product percentages and prices the shop sets, and the generated report PDFs. When a soil sample export is imported, we store the per-sample laboratory values it contains and, when the file carries them, each sample's latitude and longitude, along with any field-map images pasted into a report. Grower names, field identifiers and sample locations are your customers' information, not ours — you decide what goes in, and section 8 covers how we hold it. CropData does not connect to FieldAlytics or any laboratory; it reads the file you give it.
CalculateFoam — company and user accounts; your customers, jobs, quotes and revisions; expenses, job costs and transactions; internal notes; beta signups; and usage events used to see which features get used. If you connect QuickBooks, we store the connection and exchange invoice and customer data with it at your direction.
486 Creations — a one-time purchase. Stripe takes the payment and the email address the receipt and download go to. There is no account and no stored customer profile.
3. How we use it
To create and run your account, verify your email, take payment and send invoices, provision access to the products you pay for, run the features you ask for (sync a roster, pull a market report, build a quote, generate a results PDF), answer support requests, keep the systems secure and working, and meet legal and tax obligations. We do not use your records to train models, and we do not sell your information.
4. Who can see it
- You and your organization. Members see the account or organization they belong to, according to their role.
- Data 486. Ryan Wiebe operates the Services and can access what is necessary to run and support them. Data 486 is a one-person company; there is no support department behind it.
- Anyone you show it to. A projector screen, a shared projector link, or a results PDF is visible to everyone who can see it or has the link. Quotes and reports you send leave the Services under your control.
- The service providers in section 5, each for the one job it does.
- Legal: if we are legally required to disclose something, or need to protect the Services or someone's safety.
5. Service providers (subprocessors)
| Provider | What it does | What it gets |
|---|---|---|
| Railway | Application hosting, database, backups (United States) | Everything stored in the Services |
| Vercel | Hosting for 486creations.com | Site traffic only |
| Stripe | Payments, subscriptions, invoices | Name, email, payment details, purchase history |
| Resend | Transactional email (verification, invites, notices), when enabled | Name, email, message contents |
| Apple | Sign in with Apple, when you choose it (Business Meetings) | Authentication identifier, and email if Apple provides it |
| schedule.church | Roster import, only if your church connects it (Business Meetings) | Your API token and the roster request |
| USDA AMS (MARS) | Public market reports (Beef Squared) | Your market selection — no personal data |
| Intuit QuickBooks | Accounting sync, only if you connect it (CalculateFoam) | Customer and invoice data you sync |
| Namecheap | Domain registration and DNS | No customer data |
We keep this list current. If we add a provider that handles customer records, we update this page before or when it starts.
6. Cookies
Only what is needed to run the site: a session cookie that keeps you signed in and a CSRF token that stops forged form submissions. No advertising or cross-site tracking cookies, so there is no consent banner to click.
7. Where it is processed
The Services are hosted in the United States. If you are outside the US — including Canada — your information is processed there. Using the Services means you accept that transfer.
8. When we process records for you
For the records you or your organization enter into a product, you are the controller and Data 486 is the processor. In that role we agree to:
- Process only on your instructions — running the Services for you, and what the law requires.
- Keep it confidential and limit access to what operating the Services requires.
- Secure it: encryption in transit, hashed passwords, encrypted third-party tokens, tenant scoping wherever a product holds more than one organization's records, and backups.
- Use only the providers in section 5, each bound to comparable obligations, and tell you before adding a new one that touches your records.
- Help you answer requests from the people in your records — access, correction, deletion — within a reasonable time.
- Tell you without undue delay if we learn your records were exposed by a breach.
- Delete or return your records when your account closes, subject to section 9.
If you need a standalone Data Processing Addendum signed for your file, ask through the contact form and we will sign one.
9. Keeping and deleting
We keep information while your account or organization uses the Services, and for as long after as we need it for backups, security, tax, and legal obligations. Backups roll off on their own schedule, so deleted records can persist in a backup for a period after deletion.
- Delete your own login from your profile. That removes your account and detaches you from the organizations you belonged to; it does not delete the organization's records.
- Delete an organization's records — ask from the product or through the contact form. We review the request and delete when appropriate.
- Agreement records and invoices are kept even after an account closes: we are required to keep proof of what was agreed and what was billed.
10. Your choices
Correct or delete most information yourself inside the product. To ask what we hold, get a copy, correct something we will not let you edit, or have information deleted, use the contact form. We answer within a reasonable time and will not charge you for a reasonable request. Depending on where you live, you may have rights under laws such as PIPEDA, GDPR, or state privacy laws; we apply this policy to everyone regardless.
11. Children
The Services are for adults running an organization or a business. If you enter or import the name of a minor — a youth committee member, a child in a household roster — you are responsible for having the right to do so. We do not knowingly collect information directly from children.
12. Changes
We may update this Policy by posting a new version here with a new effective date. If a change materially affects how we handle your information, we will tell account holders.
13. Contact
Data 486 LLC — use the contact form at data486.com for any privacy question, request, or complaint.