Use Policy
The house rules for our design tools. Most of this is what you would guess: use them for real design work, do not attack them, do not copy them, and do not take what belongs to somebody else. This page spells the rest out so nobody has to guess.
The short version
A plain-words summary for orientation. The full text below is the policy.
- Use the tools for lawful design and shop work, including the commercial work you do for your own clients.
- One account per person. Do not hand your sign-in to people outside your workspace, and do not resell access.
- Both products are free during the open beta, and the bug reward is real. Do not farm it with duplicate reports or extra accounts.
- Do not scrape the catalogues, do not reverse engineer the tools, and do not use the output to train a competing model.
- Do not enter other people's personal information that you have no right to enter.
- If something goes wrong we start with a message, not a ban. Serious or repeated abuse ends in suspension.
1. Who this applies to
Everyone who uses either of our design tools, signed in or not.
Bespoke Woodcraft Studio LLC, a California limited liability company, operates two design services: CabDesign at cabdesign.app and StackDesign at stackdesign.app. This Use Policy applies to both, to everyone who uses them, and to anything you do with them, whether or not you have an account.
It sits alongside the Terms of Service, which is the actual agreement between you and us. Where this policy adds detail, the detail applies. Where the two could be read differently, the Terms govern. Words defined in the Terms carry the same meaning here.
If you are using our tools on behalf of a business, this policy binds the business as well as you, and you are responsible for the people you invite into your workspace.
2. Use it lawfully
Do not use a cabinet design tool to break the law. It should not need saying, and it is here so it has been said.
You may not use our services to do anything unlawful, or to help anyone else do anything unlawful. That includes using them to plan, price, document or disguise activity that is illegal where you are or where the work will be done.
You may not use them to harass, threaten, defame or stalk anyone, to impersonate another person or business, or to send unsolicited bulk messages.
You are responsible for meeting the rules that apply to your own trade: building codes, permits, fire and accessibility requirements, licensing, and the safety instructions that come with the hardware and materials you specify. Our tools calculate; they do not certify, and nothing they produce is a substitute for a licensed professional or an inspector.
3. Your account, and keeping it honest
One account per person, with real details, kept to yourself.
- One account per person or workspace. Invite the people who work with you where the product provides for it, rather than passing one set of credentials around.
- Real details. Sign up with an email address you control and details that are true. Do not impersonate somebody else, and do not claim a company affiliation you do not have.
- Keep your sign-in to yourself. Access to your email inbox or your Google account is access to your workspace. Tell us promptly if you think someone else has been in your account.
- No sharing or reselling access. You may not sell, rent, lend or give your account to anyone outside your workspace, and you may not run our tools as a service of your own.
- No evading a suspension. If we suspend or close an account, opening a new one to get around that is itself a breach of this policy.
- Adults only. You must be at least 18, or the age of majority where you live. These are professional shop tools and they are not directed at children.
4. The open beta and the bug reward
The products are free right now, and telling us about a real bug earns you a free month later. Gaming that is the one thing that gets the reward taken away.
Both products are free to use during the open beta. Anyone can sign up and use the full product. The Open Beta Terms set out how the beta works, what the bug reward is worth, and our right to change or end the beta; this section is about conduct, and the two are read together.
There is a bug report button inside the product once you are signed in. Reporting a problem that leads to a fix earns free service after the beta ends, up to a stated cap. That is a genuine offer, and it only works if reports are genuine. So:
- Report in good faith. Tell us what you did, what you expected, and what happened instead. One clear report is worth more to us than ten thin ones.
- Do not pad the count. Filing the same problem repeatedly, splitting one problem into many reports, or filing volumes of low-value reports to reach the cap is abuse of the reward, not participation in it.
- Do not manufacture bugs. Deliberately breaking something, or tampering with the product or its data to produce a defect you can then report, does not qualify and may end your access.
- One person, one set of rewards. Do not open extra accounts, use other people's details, or coordinate a group to submit the same finding, in order to collect more than your share.
- Report privately first. If you find a security problem, send it to us and give us a reasonable chance to fix it before telling anyone else. Do not access other people's data to prove a point, and do not run destructive tests against the live service.
- Promotion codes are for the person they were given to. Do not sell a code, publish one that was given to you privately, or use one you were not given.
Whether a report qualifies for a reward is our decision, made in good faith. We will tell you what we decided.
5. Do not attack or overload the service
No probing, no malware, no hammering the servers, and nothing that degrades the service for the people using it.
You may not:
- probe, scan or test the security of our services, or of the providers we run on, except through the good-faith private reporting described in section 4;
- try to reach an account, a workspace, a project or a record that is not yours, or defeat any access control, permission check or paywall;
- upload or transmit malware, or anything designed to damage, disable or interfere with the service, its data, or another user;
- place automated load on the service beyond ordinary interactive use, including scripted request loops and stress tests;
- work around a rate limit, a usage ceiling or a quota, for example by rotating IP addresses, accounts or API calls to spread the same activity around; or
- interfere with anyone else's ability to use the service.
We apply technical limits to keep the service up and the cost of running it sane. Those limits include ceilings on how often unauthenticated forms may be submitted, counted per caller and across the whole endpoint together, and limits on how much AI assistant usage an account may make. Hitting a limit occasionally in normal use is expected and is not a breach of anything; deliberately engineering around one is.
6. No scraping, no reselling
The catalogues and the guides took real work. Read them, use them in your projects, do not harvest them.
You may not crawl, scrape, spider, harvest or bulk-extract content or data from our services, or use an automated tool to collect it, whether or not you were signed in when you did it. That covers the material and hardware catalogues we supply, the pricing data, the guides and articles, the help content, and the structure of the tools themselves.
You may not copy, republish, mirror, sell, license or redistribute what we supply, or use it to build or populate a competing product, catalogue or dataset. Using the tools for your own client work, and giving your clients the drawings, cut lists and quotes that come out of them, is exactly what they are for and is not restricted by this section.
You may not remove, obscure or alter any notice, credit or mark we place in the service or in its output.
7. No reverse engineering
Do not take the engine apart to rebuild it somewhere else.
You may not reverse engineer, decompile or disassemble our services, or attempt to derive their source code, their geometry and cut list logic, their prompts, or the models behind the AI assistant. You may not extract or reconstruct our software or data by observing its behaviour in bulk.
This section does not restrict anything the law expressly allows you to do regardless of contract, such as an interoperability right you hold under applicable law. If you believe you have such a right, tell us before you start and we will discuss it.
8. What belongs to whom
Your designs are yours. Our software and catalogues are ours. Other people's work is theirs.
Yours. The projects, rooms, cabinets, dimensions, standards, pricing and customer records you create stay yours. We claim no ownership of them, we do not sell them, and we do not train AI models on them. The Privacy Policy explains what we do with them, which is to store and process them so the tools work for you.
Ours. The software, the geometry and cut list engines, the interface, the catalogues we supply, the guides we publish and the product names are ours or licensed to us. Your account gives you the right to use them, not to own or copy them.
Other people's. Do not upload, enter or generate content that infringes someone else's copyright, trademark, trade secret or other rights. That includes uploading a competitor's catalogue or a manufacturer's proprietary data into your workspace, and it includes using our tools to produce a knowing copy of somebody else's protected design.
If you believe something in our services infringes your rights, tell us at support@cabdesign.app for CabDesign, or support@stackdesign.app for StackDesign, with enough detail to find it, and we will look into it.
9. Using the AI assistant responsibly
The assistant guesses, and it can be confidently wrong. Check what it tells you, and do not try to trick it into misbehaving.
Our products include an AI assistant that helps you plan a space, set up cabinets, pick materials and hardware, and drive the tools. What it is, what it can and cannot do, and where the numbers actually come from are set out on the AI Transparency page. Two things from that page matter for conduct:
- You check the output. Any measurement, specification, quantity, clearance, code question, price or product recommendation that comes out of the chat is a suggestion to verify, not a measurement to cut against. Cut lists come from our geometry engine rather than the chat, and even those depend entirely on the inputs you gave.
- Do not present it as something it is not. If you pass AI-assisted output to a client, an inspector or a colleague as verified professional advice without checking it, that is on you, not on the assistant.
You may not:
- try to bypass the assistant's safety limits, or extract its system instructions or the prompts behind it;
- use it to generate unlawful, infringing, deceptive or harassing content;
- use its output, or conversations with it, to build, train, fine-tune or evaluate a competing model or dataset; or
- run automated conversations against it to harvest output at volume.
Please do not paste anything into the assistant that you would not want processed by a third-party AI provider, including other people's personal information you have no right to share.
10. Other people's personal information
You can store your customers' details. That comes with responsibilities, and they are yours.
Our tools let a shop keep contact records and job notes about its own customers. Those records are yours, and we hold them for you rather than for ourselves. In privacy terms you are the controller and we are the processor.
So you may only enter personal information about another person if you have the right to. You decide what to collect and why, you tell your customers what you do with it, and you keep it accurate and no longer than you need it. If a customer asks you to correct or delete their record, you can do that yourself inside the product.
Do not enter sensitive personal information into our products. We do not ask for it and we do not want it: no government identifiers, no health data, no financial account numbers, no precise location, no biometric data. The Notice at Collection lists what we do collect, and the Privacy Policy explains how the controller and processor relationship works.
11. How we enforce this policy
We start with a message, not a ban. The response fits what happened.
Most breaches of this policy are accidents or misunderstandings, and they are settled with an email. We match the response to what actually happened, how serious it was, whether it was deliberate, and whether it has happened before. In rough order:
| Step | What it looks like | When we use it |
|---|---|---|
| 1. We ask | An email explaining what we saw and what needs to change. | A first, minor or probably accidental problem. This is where most things end. |
| 2. We limit | A temporary ceiling on one feature, such as AI assistant usage or form submissions. | Load or usage that is affecting the service, while we sort it out with you. |
| 3. We remove | Taking down specific content, or reversing a reward that was not earned. | Content that breaches this policy, or a bug reward obtained by gaming section 4. |
| 4. We suspend | Access paused while we investigate or wait for you to fix the problem. | A serious breach, a repeat after step 1, or a security or legal risk to other users. |
| 5. We close | The account is terminated and access ends. | Deliberate, repeated or severe abuse, or a breach we cannot resolve any other way. |
When we skip steps. We may act immediately, up to and including suspension, if waiting would put other users, their data or the service at risk, or if the law requires it. Where it is reasonable and lawful to do so, we tell you what we did and why, and we give you a chance to put it right.
Law enforcement. If we see a real risk of harm to a person, we may contact or cooperate with the appropriate authorities. We do not hand over customer data on request without a lawful basis for doing so.
Discretion. Not enforcing this policy on one occasion does not waive our right to enforce it later, and does not make the conduct acceptable.
12. Reporting a problem, and appealing a decision
One address for both. A person reads it.
To report abuse of our services, or content you believe breaches this policy, email support@cabdesign.app for CabDesign, or support@stackdesign.app for StackDesign. Tell us what you saw and where, and include anything that helps us find it.
To report a security problem, email the same address with "Security" in the subject line. Give us a reasonable chance to fix it before you tell anyone else, and we will keep you posted on what we find.
To appeal a suspension, a closure, a removal or a reward decision, write to the same address from the email on your account and tell us why you think we got it wrong. A person reviews it, and we reply. We are a small shop, so there is no appeals board and no ticket number, but there is also nobody hiding behind one.
13. Changes to this policy
If we change something that matters, the date at the top changes and we tell account holders.
We will update this policy as the products and the law change. The effective date at the top of the page always shows the current version. If we make a change that materially expands what is prohibited, we will post it here before it takes effect and tell account holders by email or by a notice in the product.
14. How to reach us
Email is fastest. The postal address is here because a policy page should carry it.
Bespoke Woodcraft Studio LLC, a California limited liability company
688 N Rimsdale Ave
Covina, CA 91722, United States
Email: support@cabdesign.app for CabDesign, or support@stackdesign.app for StackDesign, answered within one business day.