What this page covers
This acceptable-use policy applies to anyone using Makerstead to make or operate record pages, public care pages, or QR-channel owner messages, and to anyone moving a record between makers through the desk. It sits alongside the privacy policy (the data-handling backbone) and the terms of service (subscription mechanics and ownership). Where those three overlap, this page owns the “what’s allowed” question.
Data you handle through the platform
Makerstead holds the records you publish, the photos and summaries attached to each one, your service-log entries, the owner messages that arrive through the QR channel, the public care pages owners scan into, and the founder / transfer events that move a record between makers. What that means in storage terms, what we don’t store, and how long things stay around lives on the privacy page.
Using Makerstead alongside your other tools
Makerstead is the after-sale record for the work you hand off. It is not your business-in-a-box. The desk is built to sit next to the CRM, scheduling, invoicing, payment, and customer-service tools your bench already runs — whatever they are, whoever made them. Use those tools together. The rights and limits below apply everywhere those tools are running with Makerstead data in them.
- Businesses may use their normal CRM, scheduling, invoicing, payment, and customer-service systems alongside Makerstead.
- Move the records you store on Makerstead into spreadsheets, CRMs, or any other legitimate business software. The export is yours for that purpose.
- Take customer payments through your normal payment processor. Makerstead does not broker customer-to-maker payments; subscription billing for the platform itself stays separate.
Your responsibilities as a maker or business
- Honour what you wrote on the public care page. If you told an owner you’ll refinish on a three-year cycle, the record’s service log should reflect that — not a hidden guess.
- Treat the QR handoff as the customer’s first contact. The owner scanned it because they wanted to reach your bench — take their message as the opening of a relationship, not as another ticket in some other queue.
- Transfer records cleanly. Use the desk’s transfer flow when a record moves between makers, so the new owner inherits the care history with no gap.
- Don’t bypass the desk. The platform’s subscription is what keeps the QR resolving, the care page live, and the export available — going around it undermines the things that make the service worth using.
Prohibited use
You may not use Makerstead to do any of the following. This list is explicit but not exhaustive — the spirit of the rule is “care record service,” and anything that fights that spirit can be treated as a violation.
- Unauthorized access to another account. Don’t sign in as another maker or business, and don’t try to access records, care pages, or owner messages that do not belong to your bench.
- Scraping records belonging to other businesses. Per-record viewing by a real visitor is fine; bulk collection — of the platform, the public care pages, or the founders directory — is not.
- Misuse or resale of personal information. The customer data on your records is yours to act on in the ordinary course of your business, not to compile, enrich with outside sources, or resell.
- Spam or unlawful marketing. The QR handoff is the owner asking to reach your bench; it is not a channel for blasts, third-party promotions, or any outreach the owner did not agree to.
- Impersonation.Don’t register a business name, copy, or trade fields that belong to another maker or business, and don’t pretend to be Makerstead itself.
- Fraudulent records.Care pages must describe the piece you actually delivered. Don’t publish or accept transfers for counterfeit claims, fabricated provenance, or work you did not make or install yourself.
- Malware or harmful uploads.Any attachment on a care request or in the service log is treated as content. Don’t upload files designed to damage other people’s devices or data.
- Evading subscription limits.Shared logins across seats, expired-trial tricks, or any pattern aimed at paying for one seat and using many. Fair-use volume may apply; the rules are on the fair-use page.
- Illegal, abusive, or dangerously misleading content. Don’t publish material that is unlawful where you or the owner sit, that infringes someone else’s IP, or that presents a serious risk of harm if an owner acted on it. The no-train promise in the terms runs in both directions: scraping or model-training on Makerstead content counts here too.
- Abuse of the QR handoff. Use the channel to talk to owners about their requests, not to send abusive, harassing, or threatening messages. The channel exists because owners asked for it; abusing it ends the seat.
- Probing the platform.Don’t scan, fingerprint, or try to extract non-public Makerstead infrastructure — undocumented endpoints, internal identifiers, or other surfaces not meant for the published app.
What Makerstead does when a violation is found
When the desk identifies a clear violation, we move in this order: a written warning first, then takedown of the offending record or care page, then action on the account if the behaviour continues or is severe enough on the first pass. We reserve the right to cooperate with lawful process where a violation also implicates outside law, and to publish anonymised summaries of repeat patterns so the rest of the desk can recognise them.
Reporting violations
Email makerstead@polsia.app if you see a record, a care page, or an owner message that breaks the rules above. Include the record URL, the offending text or screenshot, and how you came across it. We acknowledge within two business days and follow up with the action taken (or the reason none was) within a reasonable window after that.
Changes to this policy
Material changes get a sign-up-screen notice and at least fourteen days’ notice before effect. Continued use of Makerstead after the effective date is acceptance of the updated policy; if a change is one you can’t accept, cancel from the billing surface and export your records before it lands.