Privacy Policy

Effective date: 3 August 2026

Last updated: 11 September 2026

EggWire is operated by EggWire LLC, a Michigan limited liability company, 443 Western Ave #1138, South Portland, ME 04106. Contact: [email protected].

Scope and international users

EggWire is operated from the United States and is intended for U.S. commercial users in the egg and poultry industry. We do not target the United Kingdom, European Union, European Economic Area, or Switzerland. If you access the service from one of those places, your information will be processed in the United States, where privacy laws may differ from those where you live.

The short version

We collect what an account needs to work and nothing else. We do not sell or rent your personal information, and we do not share it for cross-context behavioral advertising. We disclose personal information only as described in this policy, including to service providers that help operate EggWire, and we never disclose what you read to another subscriber, to a company we cover, or to advertisers or data brokers. There are no advertising trackers on this site.

What we collect

When you create an account

Your email address
A cryptographic hash of your password — we never store the password itself
Your alert preferences: minimum severity, categories, the states and companies you follow, delivery channels, and quiet hours

When you request a Team invoice

We store your name, email, organisation, seats and optional note to create or link your account, review your request and prepare your invoice. We send these details to [email protected]. We also keep the linked user id, request source, creation and approval times, approval status, notification status and whether introductory Pro access was granted, to avoid duplicate emails and repeat grants. Team provisioning follows separately after payment.

When you subscribe

A Stripe customer identifier and subscription identifier
Your subscription status and renewal date

Your card details are handled entirely by Stripe and never reach our servers. We cannot see your full card number.

As you use the service

Which stories you have opened, and when. This enforces free-tier limits and tells us whether alerts are being received.
Which stories you have saved
Whether an alert we sent was delivered and whether it was opened
If you enable push notifications: the push endpoint your browser provides and the associated cryptographic keys

In your browser

We store an authentication token in localStorage so you stay signed in, and temporarily store an invite or trial code if you arrived by such a link. We do not use cookies for tracking, and there are no advertising pixels or third-party trackers on this site. We do not use Google Analytics or any other outside analytics service, and no third party receives a record of your visit.

Our own traffic measurement

We do count visits, using our own server rather than anyone else's. When a page is served we record one row containing: which page it was, from a short fixed list; for a story permalink specifically, also the id of the story the visit landed on, so we can tell what content brought a reader in; the bare domain of the site that referred you, if any, never the full link; the utm_source tag if the link you followed carried one, which is how we tell whether a campaign worked; a coarse browser family — chrome, safari, firefox, edge, or “other browser” — read off the technical User‑Agent header, never the raw header itself; whether the request looked like a bot; and a one‑way fingerprint used only to tell repeat visits apart from new ones within a single day.

That fingerprint is a salted hash of your IP address and browser user‑agent. We do not store either value — only the hash. The salt changes every day, so the hash cannot be reversed, and today's cannot be matched against tomorrow's. We delete these rows after 90 days.

Team plan page visits are counted in the same way, under the Team page bucket (team_page_view). Starting checkout is recorded with the selected plan.

After the app first renders, it also sends one small first-party beacon. Its row contains: which page it was; the utm_source tag for that page load, if any; the same daily one-way fingerprint; whether the request looked like a bot; and when the beacon was received. Beacon rows are deleted on the same schedule. It sets no cookie. We do not store your IP address or browser user-agent, and share nothing with anyone else. For signed-in readers this traffic measurement is kept entirely separate from the record of which stories you opened — the promise below that we never disclose who reads what is unaffected by it.

What we do NOT do

We do not sell, rent, or trade your personal information.
We do not share your information with advertisers or data brokers, or for cross-context behavioral advertising.
We never disclose who reads what. In an industry this small, which producer is reading about which outbreak is nobody else's business.
We do not track you across other websites.
We do not use your data to train AI models. Our summarization processes published news articles; it never receives subscriber information.

Who we disclose data to, and why

We use a small number of service providers to run the product. Each receives only what it needs to provide services to EggWire:

Service provider or category	What it receives	Why
Stripe	Your email and payment details you enter with them	Payment processing
Email provider	Your email address and message content	Sending the daily brief, alerts, and account mail
Railway	Hosting; data at rest	Running the application
Cloudflare	Standard request data (IP address, user agent)	DNS and protection
Browser push service	The push endpoint your browser issued	Delivering push alerts, only if you enable them

We may also disclose information if legally required to do so, or to protect our rights or someone's safety. If that ever happens we will tell you unless we are legally prohibited from doing so.

How long we keep it

Account information is kept while your account exists. Delete your account and your personal information goes with it, including your preferences, reading history, saved stories, and push subscriptions, except that copies may remain for a limited period in backups, logs, and similar records before routine deletion. Records we are legally required to keep, such as billing records for tax purposes, are retained as required by law.

Your choices

Change your preferences at any time in your account.
Unsubscribe from marketing email using the link in the footer of any marketing email. Daily briefs, alerts you request, account messages, security notices, and essential billing notices are service or transactional communications and may continue unless you change your alert preferences, cancel the related feature, or close your account.
Turn off push notifications in your account or your browser settings.
Delete your account, which deletes your data as described above. See how to request account deletion.
Ask us what we hold about you or request deletion. Email [email protected] and a person will answer. We may need to verify your identity before disclosing, correcting, or deleting account data.

Depending on where you live, you may have legal rights to know, access, correct, or delete personal information, to receive a copy of personal information, and not to be discriminated against for exercising privacy rights. Even where those rights are not legally required, you may email [email protected] to request access to or deletion of your account data, and we will make reasonable efforts to honor verified requests, subject to applicable exceptions and records we are required to keep. We do not sell personal information or share it for cross-context behavioral advertising, so there is no sale or advertising-share opt out to offer.

Do Not Track

Some browsers send a "Do Not Track" signal. There is no industry-standard response to it. We do not track users across other sites in the first place, so our behavior is the same either way.

Security

Passwords are stored as cryptographic hashes. Traffic is encrypted in transit. Card details never touch our servers. No system is perfectly secure, and we will notify you of a breach affecting your information as required by applicable law.

Children

EggWire is a commercial trade service intended for adults in the egg and poultry industry. It is not directed to children under 13, and children under 13 may not create an account or use the service. We do not knowingly collect personal information from children under 13. If we learn that we have collected personal information from a child under 13, we will delete it.

Changes

If we change this policy we will update the date at the top and, for any change that materially affects your rights, tell you by email before it takes effect.

Contact

EggWire LLC, 443 Western Ave #1138, South Portland, ME 04106

[email protected] — a person reads it.