DuckeryOS

Privacy Policy

Last updated: August 26, 2026

This Privacy Policy explains what information The Dank Duckery LLC ("we," "us," "our") collects through DuckeryOS (the "Service"), how we use it, and the choices you have. It's meant to describe what actually happens when you use DuckeryOS, not a generic template.

1. Information we collect

Account information. When you register, we collect your email address and a password (which we never store in plain text — it's hashed using industry-standard bcrypt hashing) and the name you give your farm.

Farm Data. Anything you enter into the Service — flock and breeding records, egg and health logs, financial ledger entries, asset records, certification records, and information about your own customers and visitors — is stored in a database isolated to your account. We don't access, read, or analyze this data except as needed to operate and support the Service, troubleshoot a problem you report, or comply with a legal obligation.

Usage and security information. We log IP addresses in connection with login attempts, account registration, and password reset requests, for a limited time, solely to detect and prevent abuse (for example, automated account creation or password-guessing attempts). We don't use this information for advertising or tracking, and we don't share it with advertisers.

Cookies. DuckeryOS uses a single session cookie required to keep you logged in. We don't use advertising cookies, third-party tracking cookies, or analytics cookies that follow you across other websites.

2. What we don't do

3. How we use information

4. Who we share information with

We don't sell or rent your information. We share it only with:

5. Data retention

We keep your account information and Farm Data for as long as your account is active. If you cancel your account, we retain your Farm Data for a limited period afterward in case you want to export it or reactivate, after which it's deleted from our active systems. Backups containing your data may persist for a short additional period before being rotated out, consistent with our normal backup retention schedule.

You can export your own Farm Data at any time using the Service's built-in backup feature, independent of anything on our end.

6. Your choices and rights

If you're located somewhere with specific statutory privacy rights (for example, certain U.S. states or other jurisdictions), you may have additional rights under local law. Contact us and we'll do our best to accommodate your request.

7. Security

We take reasonable technical measures to protect your information, including password hashing, per-farm database isolation, encrypted connections, and rate limiting on sensitive actions like login and password reset. No system is perfectly secure, and we can't guarantee absolute security — but we take it seriously and will notify affected account holders if we become aware of a breach affecting their data, as required by applicable law.

8. Children's privacy

DuckeryOS is not directed at children, and we don't knowingly collect information from anyone under 13 (or the relevant minimum age in your jurisdiction). If you believe a child has provided us with personal information, contact us and we'll delete it.

9. Where your data is processed

DuckeryOS is operated from the United States, and your information is stored and processed there. If you access the Service from outside the United States, you understand that your information will be transferred to and processed in the United States.

10. Changes to this Policy

We may update this Privacy Policy from time to time. If we make material changes, we'll make reasonable efforts to notify account holders (such as by email or a notice within the Service) before the changes take effect.

11. Contact

Questions about this Policy, or requests regarding your data, can be sent to info@thedankduckery.com.

This is a general-purpose template reflecting how DuckeryOS currently works. It hasn't been reviewed by an attorney and shouldn't be treated as a finished legal instrument — have it reviewed before relying on it commercially, particularly if you expect customers in jurisdictions with specific privacy statutes (e.g. GDPR in the EU/UK, or state-specific laws like the CCPA in California).