EggBasket Privacy Policy

Effective date: September 4, 2026 Last updated: September 28, 2026

1. Who we are

EggBasket LLC is a Wyoming limited liability company. We operate the EggBasket commerce platform and the website at eggbasket.io.

• Mailing address: 30 N Gould St #53505, Sheridan, WY 82801, United States
• Privacy contact: privacy@eggbasket.io
• Privacy Officer: the position at EggBasket LLC responsible for privacy questions, reachable at privacy@eggbasket.io

This policy is written in plain language on purpose. If anything in it is unclear, write to us and we will explain it.

2. What this policy covers, and who it covers

This policy covers personal information we handle through:

• the EggBasket website at eggbasket.io, including its waitlist;
• the EggBasket application, where vendors run their storefronts and buyers pay them;
• the emails we send in connection with either.

Four groups of people have personal information in our systems, and we treat them separately throughout this policy.

Vendors. Businesses and individual sellers who create an EggBasket account and use our software to sell things.

Buyers. People who buy from a vendor's storefront. There are two situations: a buyer who follows a vendor's storefront link (or scans a vendor's code) and pays, who does not create an account with us unless they later sign in to view their own purchases; and a buyer whose purchase the vendor records by hand, from a sale made outside our software, who may never have used EggBasket at all.

People invited to view an account. A vendor can invite someone to view their account read only. We hold the email address the vendor typed in, and the person's sign-in identifier once they claim the seat. They see totals and sale counts, not buyers' details.

Waitlist subscribers. People who give us an email address on eggbasket.io to hear about EggBasket before and at launch.

If you are a buyer, you are dealing with the vendor you bought from. They chose to use our software, they decide what to ask you, and they receive what you tell them. We hold the record on their behalf and operate the software that shows it to them. For questions about a purchase, start with the vendor; for questions about how our software handles your information, contact us.

3. Where we operate

EggBasket is offered to vendors in Canada and the United States. Wherever you are, we handle your information as this policy describes. Where the law where you live gives you rights this policy does not mention, you still have them, and we will honour them.

Quebec. We do not onboard vendors located in Quebec. A person in Quebec may still buy from a vendor located elsewhere, and if they do, their information is handled as described here.

4. What we collect

4.1 From vendors

• Your email address, verified, from our sign-in provider. Sign-in is by an emailed code; there is no password. Our software reads only your verified primary email address from that provider, not your name, image, or phone number.
• Your storefront profile: the storefront name, the business name shown on receipts, the purpose and about text, your price list and products, and your thank-you message template.
• Your business location as you select it at sign-up, so we know whether we serve where you are.
• Your payment connection details. Where you connect a payment account through our payment processor's onboarding, we hold the connection reference, its status, and a label. Where a connection instead relies on a credential you supply to us, we store that credential encrypted and never display it back to you in full. Your identity and business details for payment onboarding go to the payment processor directly, on its own pages, not through us.
• From your Stripe account, once you connect it. We read your account's balance, its balance transactions and its payouts. For each sale made through EggBasket we keep what Stripe recorded about it: the amount, the fee Stripe charged you, what you received, the currency, Stripe's exchange rate where it converted the payment, and when the money became available to you. For each payout we keep its amount, currency, status, arrival date, and, where Stripe itemizes the payout, which sales Stripe placed in it. We do not keep Stripe's free-text description of a transaction, because it can contain a buyer's name. We do not keep a line-by-line record of activity on your Stripe account that did not come through EggBasket.
• Diagnostic messages about your payment connection, kept so that a failure can be investigated and fixed. That text is written by the payment processor rather than by us, and it can contain personal information such as an email address or a name.
• Your subscription and plan records: your account identifier, payment identifiers from our own payment processor, tier, and amounts. These hold no card details: your card is entered on the payment processor's hosted page, never on ours.
• A record of corrections you make to sale records you entered by hand, keeping the value before and after the change.
• Email addresses you type in to invite someone to view your account read only, and their sign-in identifier once they claim the seat. A removed seat keeps the address on your viewer list.
• Information tax law requires us to collect about sellers, where it applies to you (see section 8), which we tell you about when we ask for it.
• Your messages to us, when you contact support or write to any of our addresses.

4.2 From buyers, at a vendor's storefront or counter

• The name you give for the purchase and an optional note. At an in-person counter code there is no name field; your name reaches us from the payment page instead.
• The amount and the items you selected.
• Your answers to questions the vendor wrote themselves. The vendor chooses these questions; common examples are a delivery address, a pickup time, or an allergy note. Our software is built to keep sensitive categories out of these questions: it refuses to let a vendor ask for payment card or bank details, a government identification number, a date of birth, or a password. It also checks the answer itself for two things, and refuses one that looks like a card number or like a Social Security or national identification number. These guards are a safeguard, not a guarantee; do not type sensitive information into an answer.
• Your email address and the cardholder name, which reach us from the payment page after you pay. Your card details are entered on the payment processor's page and never reach our software (section 4.6).
• Which storefront link or code you arrived through, recorded on your purchase so the vendor can see which link worked. It is recorded per purchase, not as a browsing history.

4.3 From buyers, when a vendor records a sale by hand

The vendor types in your name (required), your email address (optional), the amount, how you paid, the date, and a message. We hold that record for the vendor. You may never have interacted with us; if you have questions about it, the vendor is the first place to ask, and we will help.

4.4 When a buyer signs in to see their own purchases

If you sign in, we use your verified email address to locate the purchases recorded against that address, across every vendor you bought from, so that you can see your own purchase history in one place. We store your sign-in identifier on those purchase records. For this purpose your verified email address is treated as a credential, not as a contact field.

4.5 Your receipt link

Where your receipt email carries a link to your purchase, opening it shows that one purchase and nothing more. The link works without signing in. Anyone who has the link can open it and see that purchase. Treat it the way you would treat the receipt email it came in.

4.6 What we do not collect: payment card details and money

EggBasket is not a payment processor. We do not hold, route, forward, or transmit anyone's money, and we never receive buyer funds. Card details are typed on our payment processor's hosted page, never on ours, and card numbers never reach our software. Charges for a vendor's sales are created on the vendor's own payment account and settle into the vendor's own balance and bank account. Refunds and disputes are between the buyer and the vendor.

4.7 From waitlist subscribers, on eggbasket.io

• Your email address.
• An optional tag for which part of the page you signed up from.
• The two-letter country code our hosting provider reports for your connection at signup.
• A record of the consent text you agreed to and when, and whether you later unsubscribed or rejoined, so we can prove consent and so we do not email you again after you opt out.
• Delivery information from our email provider, such as a bounce or a spam complaint, so we stop sending to an address that does not want or cannot receive our email.
• The signup form is protected by a bot check operated by our hosting provider, which receives your connection's IP address to perform it.

4.8 What we collect passively

• Website traffic and performance measurements supplied by our website hosting provider, so we can understand visits and improve how the website loads.
• Aggregate page counts for a vendor's storefront: daily totals only. No cookie, no IP address, no browser details, no per-visitor record.
• Your IP address is used briefly to limit request rates and to protect forms from abuse. We do not build a profile from it and we do not keep it as part of your record.
• Server logs at our hosting providers, which carry account and transaction identifiers and technical request data rather than names or email addresses. A diagnostic entry about a failed email can contain the recipient's address.

4.9 If you are an alpha tester: how you use the console

This section applies only to vendors who accept the tracking disclosure on an alpha invitation. It does not apply to your buyers or to vendors who have not accepted that disclosure.

When you accept an alpha invitation, we tell you on that page what we will record, and accepting is your consent. We watch how the alpha gets used so we can fix what does not work. We record:

• Which pages of your console you open, and when. We store the shape of the address and never the address itself, so a basket link or a till code is never recorded.
• A short list of named actions: creating a basket, recording a sale, adding a price, creating a share link, and creating a counter code.
• Your acceptance and withdrawal of tracking consent. Activity is linked to your account, so our operators can review how individual testers use the alpha.

This activity record does not contain buyer information, anything you type, or what anything costs. It uses no cookie and no third-party analytics.

This tracking is part of taking part in the alpha. You can leave the alpha at any time from your console settings. Leaving stops the tracking and ends your place in the alpha. Your account stays open and becomes read only: everything in it stays for you to read and export. An operator can invite you back. What we recorded before you left is kept as section 8 describes, and you can also ask us to delete what we already have (see section 9).

5. Cookies, storage on your device, and analytics

We do not use advertising trackers, and we do not track you across other websites. Our website hosting provider supplies website traffic and performance measurements. We use them to understand visits and improve page performance, not to identify you or advertise to you. The separate alpha console tracking in section 4.9 is linked to consenting testers' accounts.

We set no cookies of our own beyond what signing in requires: our sign-in provider sets a session cookie so that a signed-in vendor or buyer stays signed in. Your browser also stores your display preferences (such as theme) on your own device; those never identify you and are never sent to us.

Because we do not track you across sites and do not sell or share personal information for advertising, a browser "Do Not Track" or opt-out preference signal does not change how we handle your information. We do not respond to those signals. Alpha testers stop the console tracking described in section 4.9 by leaving the alpha from their console settings.

Pages may load fonts, a bot check, or similar files from a third-party provider, and that provider receives your device's IP address to deliver them.

6. How we use information, and why we are allowed to

Vendor information is used to create and operate your account, run your storefront, connect to your own payment account, read that account's balance and payout records (to reconcile your sales against what Stripe recorded, confirm when a sale has settled and which payout it was paid out in, show you your fees and what you received in the currency you received it, and help you when something does not match), send you transactional email about your account and your sales, bill you for your subscription, keep the records our software exists to keep, meet tax and information-reporting obligations, provide support, and keep the service secure.

Buyer information is used to complete the purchase you asked for, send you a receipt and let you view that purchase again, send you the vendor's thank-you message, let you see your own purchase history if you sign in, give the vendor the record of their own sale, and meet tax and information-reporting obligations.

Viewer invitee information is used to grant and check the read-only access the vendor asked us to grant.

Waitlist information is used to send you progress notes before launch and the launch announcement, and to honour your unsubscribe.

Our legal bases. Vendors consent when they create an account and agree to our Terms, and processing is necessary to provide the service they asked for. Buyers consent when they complete a purchase and provide the information the vendor asks for, and processing is necessary to deliver the receipt and record the sale. Waitlist subscribers give express consent when they join, and can withdraw it at any time. Some processing is necessary to comply with law, in particular the retention in section 8. Where a vendor records a sale by hand, the vendor is responsible for having the buyer's consent or another lawful basis to give us that information.

What we do not do. We do not sell personal information. We do not share it for advertising or cross-context behavioural advertising. We do not use it for targeted advertising or profiling. We do not make automated decisions about you that have legal or similarly significant effects. We do not use your information to train artificial-intelligence models.

7. Who we share information with

We share personal information only with the service providers below, described by the function they perform for us. They process it on our instructions to run the service, and otherwise we share it only as this section describes.

Where this processing happens, and what these providers are engaged to do. Our service providers operate in the United States, and may also operate in other countries in which they run their infrastructure. Personal information is therefore collected, used, disclosed and stored in the United States, and may also be processed or stored in other countries where those providers operate. Each provider is engaged to process personal information on our instructions, for the purpose set out beside it in the table above and for the purposes of keeping its own service secure, available and supported, and each is bound by contract to protect it. Section 10 explains what storage outside your own country means.

You can ask us about this. To obtain written information about our practices and policies for service providers outside Canada, or to ask any question about that processing, write to the Privacy Officer at privacy@eggbasket.io. The Privacy Officer is the person able to answer questions of that kind.

If we add a provider that receives personal information, or change what a category above covers, we will update this section before or when the change takes effect, and where the law requires it we will tell you in advance (section 14). Adding a provider does not change what we collect.

The vendor you bought from. A vendor receives the information you gave them at their storefront: your name, your note, your answers, your email address, and your purchase details. They receive it in our software, by email, in their exports, and in their own payment account. They are an independent recipient of that information, not our service provider: what they do with it afterwards is governed by their own practices and by the law that applies to them, not by this policy.

Someone a vendor invites to view their account sees the vendor's totals and sale counts and redacted documents. They do not see buyer names, email addresses, or answers.

Legal and safety. We may disclose personal information where the law requires it, to respond to a lawful request from a public authority, to establish or defend a legal claim, or to protect the rights, property or safety of EggBasket, our vendors, buyers, or others.

Business transfers. If EggBasket LLC is acquired, merges, or transfers the service to a successor, personal information may be transferred with it. We will tell you before that happens where the law requires, and the successor will be bound by this policy until it is changed under section 14.

7.1 Stripe

We work with Stripe to process payments. Stripe processes personal data relating to connected accounts and their transactions as explained in Stripe's Privacy Policy, which you can read at https://stripe.com/privacy.

When you provide personal data in connection with EggBasket, Stripe receives that personal data and processes it in accordance with Stripe's Privacy Policy.

8. How long we keep information

• Alpha console tracking (section 4.9): we keep this information for as long as we need it to understand use of the alpha, investigate issues and improve the service.
• Answers to vendors' questions are erased on a schedule after the purchase. We do not keep them longer than we need them for the purpose they were given for. We set the period by how long a vendor may reasonably need an answer in order to fulfil, correct or support the purchase, how long a buyer may reasonably need to see what they submitted, and any period the law or our own business records require. Every copy we hold of an answer is erased on that same schedule. You can ask us what the current period is.
• Purchase records are kept. A buyer's name, email address, the amount, and the items purchased are not erased on that clock, because a receipt is made of that information and because a buyer who signs in finds their purchases by their verified email address.
• Your payment account's money records (section 4.1) are kept for as long as we need them for the purposes described in this policy, including our legal, tax and accounting obligations.
• Correction records are kept. Our audit record is append only. A mistake is voided rather than deleted, and the record of the correction remains.
• Aggregate page counts are kept indefinitely. They contain nothing that identifies anyone.
• Vendor account information is kept for as long as we need it for the purposes described in this policy. Section 9.2 describes what closing your account removes.
• Waitlist records are kept while you are subscribed. When you unsubscribe we keep your address on our suppression record so that we do not email you again. You can ask us to delete it entirely (section 9).
• Tax and information-reporting retention. Where a tax or information-reporting law requires us to keep records, we keep them for as long as it requires, even after an account is closed. A closure or a deletion request does not override that.
• Legal holds. We may keep information longer where the law requires it or where it is needed to resolve a dispute or enforce our agreements.

9. Your choices and your rights

Wherever you live, you can ask us to tell you what personal information we hold about you, to correct it, to delete it (within the limits in section 8), to give you a copy of it in a usable format, and to stop using it for a purpose you consented to. You will not be treated differently for exercising these rights. If we decline a request, we will tell you why, and you may ask us to reconsider. Some laws give you additional rights, including the right to complain to a regulator (section 15). We honour the rights the law where you live gives you, whether or not this policy names them.

To make a request, email privacy@eggbasket.io from the address connected to your account or purchase, or write to the postal address in section 1. We may need to verify that you are the person the information is about. We will respond within the time the law where you live requires. Requests are free unless they are repetitive or manifestly unfounded, in which case we will tell you before charging anything.

9.1 Access and correction

• Vendors can see and edit their storefront profile and their sale records in their account, and can export their records (section 9.4).
• Buyers who sign in with the email address used for a purchase can see their own purchase history, and can open a single purchase from the link in their receipt.
• Anyone can ask us for access or correction by email.

Two limits are stated plainly. Our correction record is append only, so a correction adds a new entry rather than editing the old one. When a vendor removes a viewer seat, the invited person's email address stays on the vendor's viewer list; if you were invited and want it removed, ask us.

9.2 Deleting your information

Vendors. When you close your account, we remove your display name, your storefront description and about text, your message templates, the labels on your payment connections, and any payment credential you supplied to us, and we archive your storefronts. Other information, including your sales records and the buyer information in them, buyers' receipts, billing records, correction history and your payment account's money records, is kept as section 8 describes. Closure is available regardless of subscription state and is free.

Erasing a payment credential from our systems does not revoke it with your payment processor; you can revoke it yourself in that processor's dashboard, and we recommend that you do.

Buyers. Your answers to the vendor's questions expire on the schedule in section 8, separately from anything else. You can ask us to remove your information; what we can remove is bounded by the retention in section 8, because your name, email address, amount and items are the receipt itself and the vendor's record of a sale that happened. Where the law where you live gives you a deletion right that goes further, we will honour it to the extent the law requires.

Waitlist subscribers. Every email from this list has a one-click unsubscribe. To have your record deleted entirely rather than kept on our suppression list, email us.

9.3 Withdrawing consent

You may withdraw your consent to our use of your personal information at any time, subject to legal and contractual limits and reasonable notice. For a vendor, withdrawing consent to the processing the service needs means closing your account (section 9.2). For a waitlist subscriber, it means unsubscribing. Section 8 describes information we must keep regardless.

If you are an alpha tester, console tracking is part of taking part in the alpha, so withdrawing your consent to it means leaving the alpha, which you can do at any time from your console settings. Leaving stops new recording. Your account stays open and read only, with everything in it there to read and export, and an operator can invite you back. What was recorded before you left is kept as section 8 describes.

9.4 Taking your information with you

Vendors can generate PDF close-out reports and statements, and CSV exports of their sales ledger and bookkeeping records, from inside the product. Anyone can ask us for a copy of the personal information we hold about them by email.

10. Where your information is stored, and international transfers

EggBasket LLC is a United States company, and personal information collected through the service is stored and processed in the United States by our hosting and service providers. This includes the personal information of Canadian vendors and Canadian buyers.

Information stored in the United States is subject to United States law, including lawful access by United States authorities. We remain responsible for personal information we transfer to a service provider for processing, and we use contractual and technical means to require a comparable level of protection from each provider.

11. How we protect information

• Access to personal information in our systems is controlled, and is granted only where it is needed to operate the service.
• A payment credential you supply is encrypted before it is stored, and is never displayed back to you in full. A vendor who connects a payment account through the processor's own onboarding gives us no secret at all.
• A viewer seat is scoped. Someone a vendor invites to view their account read only sees totals, sale counts and redacted documents, never buyer names, email addresses, or answers.
• Our software screens for sensitive values in a vendor's questions and a buyer's answers (section 4.2).
• Access to production systems is limited to the people who operate the service.
• We describe our safeguards in general terms rather than in detail, because publishing the detail would help someone work around them.

No method of storage or transmission is completely secure, and we cannot guarantee absolute security. If a security incident affects your personal information in a way that creates a real risk of harm to you, we will notify you, and the authorities the law requires us to notify, without unreasonable delay and within the time the law where you live requires. We keep records of security incidents as the law requires.

12. Vendors and buyers in the United States

Some United States states give their residents rights to access, correct, delete, and obtain a copy of their personal information, to opt out of the sale or sharing of it and of targeted advertising and profiling, and to appeal a refused request. Section 9 gives everyone those rights whether or not a state law requires it. We do not sell personal information, we do not share it for cross-context behavioural advertising, we do not use it for targeted advertising, and we do not profile you, so there is nothing to opt out of on those points. We do not collect sensitive personal information as those laws define it in the ordinary course of the service, and our software refuses several categories of it (section 4.2).

13. Children

EggBasket is a business tool. An account may be opened only by someone who is at least the age of majority where they live. The website and the service are not directed to children, and we do not knowingly collect personal information from anyone under 13. If you believe a child has provided us with personal information, contact us at privacy@eggbasket.io and we will delete it.

14. Changes to this policy

We may update this policy. When we do, we will change the "last updated" date above. We keep earlier versions and will provide one on request. If a change materially affects how we handle your personal information, we will give notice by email to account holders and by a notice on the site before it takes effect, and where the law requires your fresh consent we will ask for it.

15. Contact us, and how to complain

Questions, access requests, correction requests, deletion requests and complaints:

EggBasket LLC 30 N Gould St #53505, Sheridan, WY 82801, United States privacy@eggbasket.io

Privacy Officer: the position at EggBasket LLC responsible for privacy questions, reachable at privacy@eggbasket.io

We will respond within the time the law requires.

If you are in Canada and are not satisfied with our response, you may complain to the Office of the Privacy Commissioner of Canada at www.priv.gc.ca, or to the privacy regulator of your province where one has jurisdiction.

If you are in the United States and are not satisfied with our response, you may contact the attorney general or consumer protection office of your state.