Terms of Service

For the wedding planning businesses in early access, the people they invite in, and the clients who open their links.

Effective date: November 8, 2026

These terms are published at https://neatlywed.com/terms. They are linked from the footer of every page of neatlywed.com, from the sign-in page and the menu of app.neatlywed.com, from the page where a person accepts an invitation, and from every page a client opens from a client's link.

1. Who we are, and what these terms cover

1.1. NeatlyWed is software for wedding planning businesses: their weddings, the names of each wedding's guests and the tables they sit at, a seating chart laid out on a mirror, the design of the table cards, printing them and making files for a Cricut machine, and a warehouse of the mirrors a business owns. It is made and run by Built by Bean LLC, a Texas limited liability company ("Built by Bean", "we", "us"), 3244 Spaulding Dr, Paris, Texas 75460.

1.2. These terms cover:

Together, "the Service".

1.3. These terms do not cover a business's own dealings with its clients (its contract, its prices, its wedding day), or the services of the third parties named in section 10, which have their own terms.

1.4. Early access. NeatlyWed is in early access. It is open only to the wedding planning businesses Built by Bean invites, it is free, and nothing in it is for sale. Section 9 says what happens if that ever changes.

2. Who uses the Service

2.1. A Business. A wedding planning business that Built by Bean has given early access, with its own account in NeatlyWed. The Business is "you" in sections 5, 6, 13.1 and 16 and wherever the text says "the Business".

2.2. A Member. A person who belongs to a Business, invited by email, with one of three roles: the Owner, who runs the Business's account; an Admin, who manages its people; or a Planner, who plans its weddings.

2.3. A Client. A person a Business sends a wedding's client's link to, usually the couple, who opens it to fill in the guest names. A Client never has a login.

2.4. A Guest. A person whose name is on a wedding's guest list. Guests never use the Service; their names are put in by the Business or by its Client.

2.5. Everyone in 2.1 to 2.3 is "you" unless the text names one of them.

3. How you accept these terms

3.1. A Member accepts these terms when they accept their invitation: a required, unticked box naming the Terms of Service and the Privacy Policy, with links that open the full text, before the button that makes the login. The Service records which version of each was accepted and when. A Member whose login was made before these terms were published accepts them the same way the first time they sign in after. If you do not agree, do not accept the invitation.

3.2. The Owner accepts these terms for the Business as well as for themselves, and by accepting says they may bind the Business to them.

3.3. A Client accepts these terms by using a page opened from a client's link. Every such page links these terms and the Privacy Policy. If you do not agree, close the page and deal with the Business directly.

3.4. You must be at least 18 years old to accept these terms or to hold a login.

4.1. By invitation only. There is no public sign-up. A Business is set up only when Built by Bean gives it early access and invites its Owner; the Owner or an Admin invites the Business's other Members, each at their own email address.

4.2. One person, one login. A login is for the person it was made for. Do not share a password and do not sign in as another person.

4.3. The client's link is a key. Whoever holds a wedding's client's link can open that wedding's names page and change the names and tables there without signing in. Send it only to the people who should have it. A Member can turn the link off, or make a new one, which stops the old one working at once.

4.4. Keep it safe. You are responsible for what is done with your login until you tell us it has been lost or taken, at hello@neatlywed.com; tell your Business's Owner or an Admin too. We keep your password only as a salted hash, never the password itself, and we never ask for it by phone or email.

4.5. What the Business controls. The Owner and the Admins decide who belongs to the Business and what role each has. A Member's access ends when the Business removes them or when the Business's early access ends (section 13).

5. The Business's data

5.1. Business Data. Everything a Business, its Members and its Clients put into the Service is "Business Data": its weddings (the couple's names, the date, a client's email address and notes), the guest names with their tables and seats, the seating charts, the card designs and the designs and layouts it saves, its mirrors and their photos, and the photos it keeps from the day. As between Built by Bean and the Business, Business Data is the Business's. We claim no ownership of it and no right to it beyond what this section and section 6 give.

5.2. What we may do with it. The Business gives Built by Bean the right to host, copy, back up, transmit, display and process Business Data only as needed to run the Service, to keep it safe, to help the Business when it asks, and to comply with law. We do not sell Business Data, use it for advertising, use it to train any machine-learning model, show it to another Business, or share it with anyone except the providers named in the Privacy Policy, section 5, and anyone the Business tells us to share it with.

5.3. Whose names they are. The Business decides what goes into the Service about its clients and their guests, and it holds the relationship with them. For that data the Business is the controller (in California's words, the business) and Built by Bean is its processor (service provider), holding it for the Business on its instructions as section 6 says. The Business is responsible for having the right to put its clients' and guests' names and details into the Service and to send its Clients the client's link, and for any notice the law asks it to give them.

5.4. What not to put in. The Service is built for names, tables and the details of a wedding. Do not put anyone's health information (a guest's medical needs or allergies), government identification number, bank or card number, or password into a note, a name or anywhere else in the Service.

5.5. Between the Business and its Clients. A Client's arrangement is with the Business, not with Built by Bean. We are not a party to any contract, payment or dispute between a Business and its Clients, and we vet neither.

5.6. Our own records. We keep records about how the Service is used (sign-ins, failed sign-ins, request logs, error reports, and each acceptance of these terms) to run it and keep it safe. They are ours, kept as the Privacy Policy says.

5.7. Feedback. If you send us an idea or a suggestion, we may use it without owing you anything.

6. How Built by Bean holds a Business's data

This section is the contract between a Business, as the controller of its Business Data, and Built by Bean, as its processor. It carries what a processor's contract must hold under the Texas Data Privacy and Security Act (Texas Business and Commerce Code 541.104) and the state laws written on the same pattern, so that a Business one of those laws reaches has the contract it needs.

6.1. Instructions. We process Business Data only on the Business's instructions: these terms, what its Members and Clients do in the Service, and what its Owner asks of us in writing at hello@neatlywed.com. If we believe an instruction breaks the law, we say so and do not follow it until that is settled.

6.2. What, whose and why. We hold the Business Data in 5.1: its clients' names, wedding dates, email addresses and the notes the Business writes; its guests' first and last names, with their tables and seats; its card designs; and photos of its mirrors and from the day. We hold it so that the Business can plan each wedding's seating and cards, and for no other purpose.

6.3. How long. For as long as the Business has access to the Service, and then until it is deleted as section 13 says.

6.4. Our people. Every person at Built by Bean, or working for us, who can reach Business Data is bound by a duty of confidentiality, and reaches it only to run the Service, to keep it safe or to help the Business when it asks.

6.5. Our providers. The providers that handle Business Data for us are the ones the Privacy Policy, section 5.2, names (today Railway, Cloudflare, Resend and Anthropic), each under a written contract (its terms of service and its data processing terms) that binds it to protect the data it handles for us as this section binds us. We give every Owner at least 30 days' notice by email before a new provider handles Business Data, and a Business that objects may stop using the Service before then (section 13.1). We remain responsible to the Business for how our providers handle its Business Data.

6.6. Requests from people. If a client or a guest asks the Business to see, correct or delete what it holds about them, the Business can do most of it in the Service itself (a name, a wedding, a photo); for the rest, we help within 10 business days of the Owner's request. A request that reaches us about Business Data is passed to the Business.

6.7. Security and incidents. We protect Business Data with the measures in the Privacy Policy, section 10. We tell the Owner of a breach that reaches Business Data immediately after we discover it, and never later than 72 hours after, as section 11 of that policy says, with what we know and the help the Business needs to tell others.

6.8. Showing that we keep this section. On the Owner's request, we give the Business the information it needs to show that we keep this section, and the information it needs for any data protection assessment the law asks of it. Where a law the Business is subject to requires an assessment of how we process its data, we cooperate with a reasonable one by the Business or an assessor it names, on 30 days' notice, at the Business's cost, under confidentiality and without access to any other Business's data; or, if we choose, we arrange an independent assessment ourselves and give the Business its report.

6.9. Return and deletion. At the Owner's written direction we give the Business a copy of its Business Data, or delete it, within 30 days, unless the law requires us to keep it. When the Business's use of the Service ends, section 13 applies.

6.10. Nothing for ourselves. We do not combine Business Data with any other Business's, and we use it for nothing of our own.

7. Rules for using the Service

7.1. You may use the Service only to plan the Business's weddings, lawfully and as the Service is meant to be used.

7.2. Do not:

7.3. If you find a security problem, tell us at hello@neatlywed.com before telling anyone else, and give us a reasonable time to fix it. We will not take action against a person who reports in good faith and does no harm.

7.4. Copyright complaints. If you believe something in the Service infringes your copyright, write to our Copyright Agent: Built by Bean LLC, Attn: Copyright Agent, 3244 Spaulding Dr, Paris, Texas 75460; telephone (903) 491-2095; or hello@neatlywed.com with "Copyright notice" in the subject. Your notice needs what 17 U.S.C. 512(c)(3) asks for: your physical or electronic signature; the work you say is infringed; the material and where it is in the Service, closely enough for us to find it; your address, telephone number and email address; a statement that you believe in good faith that the use is not authorized by the owner, its agent or the law; and a statement that the notice is accurate and, under penalty of perjury, that you are the owner or authorized to act for the owner. We remove or disable the material promptly and tell the Business that put it in. The Business may send us a counter-notice with what 17 U.S.C. 512(g)(3) asks for; we then send you a copy, and put the material back in 10 to 14 business days unless you tell us first that you have gone to court. We end, in appropriate circumstances, the access of anyone who infringes repeatedly.

8. Emails

8.1. The Service sends email from mail.neatlywed.com, through the provider named in the Privacy Policy, for two reasons only: about a login (an invitation to join a Business, a link to set or reset a password), and, when a Member presses Send, a wedding's client's link to the email address the Business gives for its Client. Neither the Service nor the website sends marketing email; an early-access request is answered by a person.

8.2. The Business decides who is sent a client's link, and sends it only to its own Client.

9. No charge during early access

9.1. Early access is free. Built by Bean charges nothing for the Service, takes no payment details, and nothing in these terms makes a Business or anyone else pay.

9.2. If Built by Bean ever offers NeatlyWed for a price, the price and the terms of paying will be shown and agreed separately, and nothing will be charged without that agreement. We will tell every Owner at least 30 days before early access ends for that reason, and a Business that does not want to pay may have a copy of its Business Data and leave (section 13.1).

9.3. The Service takes no payments between a Business and its Clients.

10. Other services

10.1. The Service runs on services that others provide: Railway (hosting and the database), Cloudflare (the network in front of every address, the website and its early-access form, the status page, our email address and our backup copy), Resend (email) and Google Fonts (the typefaces). The Privacy Policy, section 5, says what each receives.

10.2. We are not responsible for how a third party's service performs, its outages or its changes. We remain responsible for how our own providers handle the data we give them.

10.3. Cricut. The Cricut page makes files that open in Cricut Design Space. Cricut is not part of the Service and has no connection with NeatlyWed or Built by Bean; what you do in Design Space is under Cricut's own terms.

10.4. Fonts. The typefaces come from Google Fonts, under the open licenses their authors give them. The Service uses them to draw a card's lettering and to trace it into the outlines a Cricut file holds; it never gives you the font files.

11. Our intellectual property

11.1. The Service, its software, its design, and the name NeatlyWed and its logo belong to Built by Bean LLC or its licensors. You get a limited, non-exclusive, non-transferable right to use the Service as these terms allow, while your Business has access. Nothing here transfers any of our intellectual property to you.

11.2. The cards a Business designs, prints and cuts are its own to use; what it puts on them is Business Data (5.1).

12. Early access, availability, support and change

12.1. Early access means the Service is still being built. We change it often, sometimes several times a day: a feature may be added, changed or removed, and we try to say so in advance when a change affects how you work. We aim for the Service to be available all the time, but it is not guaranteed to be, and there is no service level.

12.2. Support is by email to hello@neatlywed.com. We never ask for your password.

13. Ending

13.1. A Business may stop at any time. Its Owner writes to hello@neatlywed.com from the Owner's email address. If the Owner asks, we first send the Business a copy of its Business Data in a form it can take elsewhere (the weddings and names as spreadsheets, the photos as image files). We delete the Business's account and its Business Data from our live systems within 30 days of the Owner's instruction. Deleted data lingers in our backups until they age out, within 90 days of the deletion.

13.2. We may end early access for a Business, or for everyone, with at least 30 days' notice by email to every Owner. During that time the Owner may ask for a copy as 13.1 says, and afterwards we delete the Business Data as 13.1 says.

13.3. A Member's access ends when the Business removes them; what they put into the Business stays the Business's. A Member's own login (their name, email address, password hash and favorite fonts) is deleted within 30 days of their asking us at hello@neatlywed.com, or with their Business under 13.1.

13.4. We may suspend or end a login, a client's link or a Business's access, with notice where we reasonably can, when these terms are broken, when the Service or a person is at risk, or when the law requires it. We will say why, and we will restore access when the cause is fixed, unless the breach was serious.

13.5. Sections 5, 6 (for as long as we hold any Business Data), 11, 14, 15, 16, 17 and 19 survive the end of these terms.

14. What we do not promise

14.1. THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE", FREE OF CHARGE. TO THE FULLEST EXTENT THE LAW ALLOWS, AND EXCEPT FOR WHAT THESE TERMS PROMISE IN WORDS, BUILT BY BEAN MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, GOOD AND WORKMANLIKE PERFORMANCE, AND ANY WARRANTY ARISING FROM COURSE OF DEALING OR USAGE OF TRADE.

14.2. We do not promise that the Service will be uninterrupted, error-free or secure, that an email will be delivered, or that a backup will be complete. Check what matters before the day: measure the mirror against the positions the seating chart gives before you hang a card, look over a printed sheet before you cut it, and check a Cricut file in Design Space before you cut cardstock.

14.3. Some laws do not allow the exclusion of some warranties; where that is so, the exclusion is limited to what the law allows.

15. Limitation of liability

15.1. EXCEPT AS SECTION 15.3 SAYS, BUILT BY BEAN AND ITS OWNERS, MANAGERS, EMPLOYEES AND SUPPLIERS ARE NOT LIABLE TO YOU FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, LOST REVENUE, LOST DATA, LOST BUSINESS, OR THE COST OF REPRINTING OR REPLACING CARDS OR CARDSTOCK, HOWEVER CAUSED AND UNDER ANY THEORY, INCLUDING BUILT BY BEAN'S OWN NEGLIGENCE, EVEN IF WE WERE TOLD THEY WERE POSSIBLE.

15.2. EXCEPT AS SECTION 15.3 SAYS, BUILT BY BEAN'S TOTAL LIABILITY TO ANY PERSON UNDER OR IN CONNECTION WITH THESE TERMS AND THE SERVICE, IN CONTRACT, IN TORT (INCLUDING BUILT BY BEAN'S OWN NEGLIGENCE) OR OTHERWISE, IS LIMITED TO US$100, BECAUSE THE SERVICE IS FREE.

15.3. Nothing in these terms excludes or limits liability that cannot be excluded or limited under Texas law, including liability for fraud, for gross negligence or willful misconduct, for death or personal injury caused by negligence, and for a claim under the Texas Deceptive Trade Practices-Consumer Protection Act that a consumer may bring and that these terms cannot waive.

15.4. The limits in this section apply together, so that sections 15.1 and 15.2 are read as one limit, and they are a basis of the bargain between you and Built by Bean.

16. The Business's promise to us

16.1. The Business will defend Built by Bean and its owners, managers, employees and contractors against a claim by a third party arising from Business Data the Business had no right to put into the Service, from a client's link the Business sent, or from its or its Members' use of the Service in breach of these terms or the law, and will pay the damages, costs and reasonable attorneys' fees finally awarded or agreed in settlement. This does not cover a claim to the extent it arises from Built by Bean's own negligence or breach. We will tell the Business of the claim promptly, let it run the defense with our reasonable help, and settle it only with its agreement. This section is for the Business only; Members and Clients give no such promise.

17. Disputes, governing law and where

17.1. Talk first. If you have a problem with us, write to hello@neatlywed.com with what happened and what you want. We will answer within 15 business days and try to resolve it within 30 days. Neither side starts a court case before that period has run, except to seek an injunction to stop a breach of section 7 or 11 or to protect data.

17.2. Texas law. These terms, and any dispute about them or the Service, are governed by the laws of the State of Texas, without regard to its conflict-of-laws rules. The United Nations Convention on Contracts for the International Sale of Goods does not apply.

17.3. Texas courts. A case about these terms or the Service may be brought in the state courts sitting in Lamar County, Texas, where Built by Bean is, or in the United States District Court for the Eastern District of Texas, Sherman Division, and each of us consents to their jurisdiction. This takes away no venue Texas law gives you, including the venue the Texas Deceptive Trade Practices Act gives a consumer. If you are outside Texas, those courts are the only place such a case may be brought, to the extent the law where you live allows. Either side may use a small-claims court that has jurisdiction.

17.4. Time limit. To the extent the law allows, a claim must be brought within two years after the day you knew or should have known of it, or within any longer time the law gives. (Texas Civil Practice and Remedies Code 16.070 voids a contractual limit shorter than two years.)

18. Changes to these terms

18.1. We may change these terms. For a change that matters (a new limit, a new rule for Members, an end to free early access), we give at least 30 days' notice by email to every Member, saying what changes, and we update the date at the top. A change needed for the law or for safety may take effect sooner, and we say so. A change applies only from the day it takes effect, and never to a dispute that arose before then.

18.2. The current terms are always at https://neatlywed.com/terms. Earlier versions are available on request.

18.3. Signing in or using the Service after a change takes effect means you accept the changed terms. A Business that does not accept a change may stop using the Service before it takes effect (section 13.1); a Member who does not accept it should stop signing in and ask the Business to remove them.

19. General

19.1. Entire agreement. These terms and the Privacy Policy are the whole agreement about the Service and replace any earlier terms.

19.2. Assignment. You may not assign these terms without our written consent, except that a Business may assign them to a successor to all or substantially all of its business, on notice to us. We may assign them to a successor to all or substantially all of our business, or of the part of it that runs NeatlyWed, on notice to every Owner. Nothing here limits a right the law gives to assign a right to payment.

19.3. No waiver, severability. Our not enforcing a term is not a waiver. If a court finds a term unenforceable, the rest stands and the term is read as narrowly as needed.

19.4. Force majeure. Neither side is liable for a delay or failure caused by something outside its reasonable control (a hosting provider's failure, an internet failure, a natural disaster, a law).

19.5. Notices. Notices to us go to the address in section 20. Notices to a Business go to its Owner's email address; to a Member, to the email address on their login; to a Client, to the email address the Business holds for them. A notice by email is given when sent, unless it bounces.

19.6. Independent parties. Nothing here makes us partners, joint venturers, employer and employee, or agent and principal with any of you.

19.7. No third-party beneficiaries. These terms are between you and Built by Bean. Nobody else, a Guest included, may enforce them, except that Built by Bean's owners, managers, employees and suppliers may rely on section 15.

19.8. Export and sanctions. You will not use the Service where US law forbids it, and you confirm you are not on a US sanctions list.

19.9. Language. These terms are written in English. A translation is a convenience; the English text governs.

20. Contact

Built by Bean LLC

3244 Spaulding Dr, Paris, Texas 75460

hello@neatlywed.com

https://neatlywed.com

Copyright notices go to our Copyright Agent at this address (section 7.4).