Section 1
Who's agreeing
- These terms are an agreement between Crafted for Community, LLC ("Crafted", "I", "me") and the homeowner association that accepts them in the Crafted client portal ("the HOA", "you").
- The HOA accepts these terms when its board contact checks the box to agree in the portal and pays. The person accepting confirms they're authorized by the HOA's board to do so.
- The plan, price, start date and account owner shown in the portal when you accept make up your order. If the order and these terms conflict, the order wins for that item.
Section 2
What I provide
- Build. A website designed for your community, with the features of your plan as listed on the pricing page on the start date.
- Move-over. Copying your existing pages and documents, and on a members site importing and cleaning up your member directory.
- Launch. Connecting your domain, sending launch emails to residents, and one training call for the board of up to an hour.
- Ongoing service. Unlimited requests under Section 3, keeping the site's software up to date, and looking into problems you report.
- Handover guide. A written guide stored with your site's code, explaining how to change it, renew the domain, export your data and hire someone else.
Section 3
Requests and turnaround
- The board names one person to send requests and approve previews, such as the president or the head of the communications committee. I set up a portal account for that person, and requests are sent through it. The board can change that person at any time by telling me.
- Requests form a list that you can reorder at any time. I work on one request at a time, starting with the one at the top.
- While your list has requests waiting, I'll finish at least one request in every 30-day period, and often more. If a request is too big for one go, I'll tell you and split it into smaller pieces for an orderly launch. Each piece counts as a request. You'll get a preview to approve before changes go live, except for small text fixes you ask me to publish directly.
- Rush changes. For a fee of $100, agreed before I start, I'll complete an urgent change within 24 hours. I can decline a rush request if I can't meet that time. If I accept one and miss the deadline, there's no charge.
- If you don't respond to a question or a preview for 30 days, I may move on to the next request and come back when you reply.
- Turnaround times depend on you giving me what a request needs, such as content, decisions and access. Time spent waiting on you doesn't count toward them.
- What a request is. Requests are for building and changing the site and its features. Writing or sending the HOA's content, such as posts, newsletters and emails to residents, and tasks the HOA can do itself with the site's tools, aren't requests.
- I may decline a request that falls outside the service, that I think would make the site harder to keep running, that isn't technically possible or practical with the site's tools and providers (for example, when the data or service it needs isn't available), or that I can't do safely or legally. I'll tell you why. Declining a request isn't a breach of these terms.
Section 4
What isn't included
These are quoted separately, and only done once you approve the quote in writing:
- A feature that doesn't exist yet in any Crafted site.
- Connecting a management company's or accountant's software.
- Writing content, photography or printed materials for the HOA.
- Urgent work outside a paid rush change.
If I think a request falls in this list, I'll tell you before doing any work on it.
Section 5
Fees and payment
| Plan | Yearly fee |
|---|---|
| Public site | $1,000 |
| Members site | $5,000 |
- Plans are paid yearly, in advance, and include setup. Plans renew automatically each year until the HOA cancels (Section 14).
- Hosting. Hosting, database, domain and email-sending costs are billed by those providers directly to the HOA's own accounts. I don't mark them up.
- Invoices are due within 30 days. If a payment is more than 30 days late, I'll remind you in writing. If it's still unpaid 15 days after that, I may pause new requests until it's paid. I'll never take your site down over a late payment.
- I may change prices for your next renewal by giving at least 60 days' written notice. Your price never changes in the middle of a paid term.
- Prices don't include taxes. If any apply, they'll be shown on the invoice.
Section 6
Ownership
- Your content. Everything you or your residents provide (text, photos, documents, member data) stays yours. You give me permission to use it only to provide the service.
- Your site. Once you've paid for the period in which it was made, the code of your site is licensed to the HOA permanently, irrevocably and free of further charge. You may use, change and copy it, and hire anyone to work on it.
- My building blocks. I keep ownership of the general components and tools I use across all Crafted sites. The license in 6.2 includes those components as they appear in your site, so you never need my permission to keep running it.
- I won't use your HOA's name, site or screenshots in my marketing without your written permission.
Section 7
Accounts and access
- The code repository, hosting, database, domain and email-sending accounts are created in the HOA's name, using a board email address you control.
- A board member chosen by the HOA is made owner of each account. I recommend adding a second owner as a backup, so one volunteer leaving can't lock the HOA out. When the owner changes, they hand the accounts to the next owner and tell me.
- I'm invited as a collaborator or team member with only the access I need. You can remove my access at any time, for any reason.
- I never have access to your bank, your payment service or any account that holds the HOA's money. If I need a developer setting or key from one of those accounts, I'll ask, and an HOA account owner will set it up or share only that setting.
- The HOA is responsible for the security of its own accounts, passwords and devices, and for any access it gives to others.
Section 8
Resident data and privacy
- The HOA controls its residents' personal information. I handle it only on your behalf and only to provide the service.
- Resident data stays in the HOA's own database. I won't copy it to my own systems, except briefly and securely when a specific request requires it, and I'll delete any such copy when the request is done.
- I'll never sell resident data, use it for advertising, or share it with anyone except the service providers that run your site.
- Members-only information is protected by sign-in, and each resident can choose what they share in the directory.
- If I become aware of unauthorized access to resident data in systems I work on, I'll notify the board promptly, explain what I know, and help you notify residents if that's required.
- I'll provide a privacy policy for residents based on a template, for your board to review and approve before launch. The HOA is responsible for its privacy policy and for how it collects and uses resident information.
Section 9
How I use AI
- I use AI tools to help design, write code and draft content. Much of the code on your site is written by these tools.
- I review each feature to check that it works as requested before it goes live. I don't review or guarantee every line of code, and AI-written code and content are covered by Sections 12 and 13 like the rest of the service.
- I don't give resident personal data to AI tools, except where a specific request requires it and the tool's terms prohibit using it for training.
- Drafted content is a starting point. The HOA reviews and approves it before it's published (Section 10).
Section 10
Your responsibilities
- Name one main board contact for requests and approvals, and tell me when that changes.
- Only send content the HOA has the right to publish, including photos and documents.
- Review and approve anything published on the site, including drafts I prepare. The HOA is responsible for all content on its site.
- Keep the HOA's hosting and domain accounts paid. If a provider suspends an account for non-payment, I'll help restore it, but I can't prevent it.
- Follow the HOA's own governing documents and applicable law in what you publish and how you contact residents.
- Make sure the site meets the laws that apply to the HOA, such as accessibility, privacy and HOA statutes. I build to common good practice, but I don't give legal advice or guarantee compliance.
- Keep your own copies of important documents and records. Daily database backups are available from your database provider for an extra fee. If the HOA doesn't use them, I'm not responsible for data that can't be recovered.
Section 11
Hosting and availability
- Your site depends on third-party providers chosen with you at setup. Their own terms govern their services, and I'm not responsible for their outages.
- If your site stops working, I'll investigate and work to restore it as a priority, without it counting as a request or a rush change.
- If a provider raises its prices or changes its terms in a way that matters to you, I'll explain the options, including moving to another provider.
- I don't guarantee that the site will be available at all times or free of interruptions.
- If a provider changes or withdraws something a feature depends on, I'll adapt the feature where I reasonably can, as a priority. If I can't, I'll explain the options. Changing or retiring that feature isn't a breach of these terms.
Section 12
Warranty and fixes
- I'll perform the service with reasonable care and skill.
- If something I delivered doesn't work as described in its request, tell me through the portal within 30 days of it going live, and I'll fix it at no charge, ahead of your other requests. This doesn't cover problems caused by changes your HOA makes, by the services your HOA pays for directly, or by browsers and devices that are no longer supported. This is your only remedy for defects.
- Except as stated in this section, the service and the site are provided "as is". I disclaim all other warranties, express or implied, including merchantability, fitness for a particular purpose and non-infringement, and I don't warrant that the site will be uninterrupted, secure or error-free.
Section 13
Limits of liability
- Neither of us is liable to the other for indirect, incidental, special or consequential losses, such as lost profits, lost data, lost opportunities or harm to reputation, even if warned they were possible.
- My total liability under these terms is limited to the fees the HOA paid me in the 12 months before the claim.
- These limits don't apply to fraud, willful misconduct, or anything else the law doesn't allow to be limited.
- I'm not liable for problems caused by third-party providers, by the HOA's or residents' content or actions, or by changes made by anyone other than me.
- The HOA will defend and compensate me for claims by residents or others arising from the HOA's content, its use of the site, its decisions, or its breach of these terms or the law.
- Any claim under these terms must be brought within one year of when it arose.
Section 14
Ending the service
- You can cancel at any time in your portal, or by telling me in writing. Plans renew automatically each year until cancelled. Once you cancel, your plan runs to the end of the paid year and doesn't renew, and I close your portal account at the end of that year.
- Refunds. Fees already paid aren't refunded. If you cancel, service carries on until the end of the paid term and doesn't renew.
- If I end the service, for any reason other than non-payment or a serious breach, I'll give at least 30 days' written notice and refund any prepaid fees for time after the service ends.
- Either of us may end the agreement with 15 days' written notice if the other seriously breaches these terms and doesn't fix it within that time.
- On ending, you keep everything in Section 6. I'll make sure the handover guide is current, and finish or hand back the request in progress. Removing my access to the HOA's domain, hosting and any other accounts is the HOA's responsibility. Nothing is switched off, and there's no exit fee.
- Sections 6, 8, 10, 12, 13, 14, 15 and 16 continue after the agreement ends.
Section 15
Disagreements
- If a dispute comes up, we'll first try to resolve it by talking, within 30 days of one of us raising it in writing.
- If that fails, we'll try mediation with a mediator we both accept, sharing the cost, before starting any court case.
- These terms are governed by the laws of the State of Maryland. Any court case will be brought in the state or federal courts located in Maryland.
Section 16
Everything else
- Changes. I'll give 30 days' notice of any change to these terms. A change that reduces your rights only applies from your next renewal, unless you agree to it sooner.
- Notices. “In writing” and “written notice” in these terms include email and messages sent through the portal. I'll send notices to the board contact's email address in the portal. You can send yours to hello@craftedforcommunity.com or through the portal. A notice counts from the day it's sent.
- Confidentiality. Each of us keeps the other's non-public information private and uses it only for this agreement.
- Independent contractor. I'm an independent business, not an employee or agent of the HOA.
- Subcontractors. I may use a backup developer to cover illness or holidays, under confidentiality terms at least as strict as these. I'll tell you who before they have any access.
- Events outside our control. Neither of us is responsible for delays or failures caused by events beyond reasonable control, such as a major provider outage or a natural disaster.
- Whole agreement. These terms and your order in the portal are the entire agreement. If any part is found unenforceable, the rest still applies.
- No third-party rights. These terms are only between the HOA and me. Residents and anyone else can't enforce them.
- Transfer. I may transfer these terms to a business that takes over Crafted, with notice to you.