Concrete limits, not soft promises.

This fair-use policy sets the published numerical limits that govern Makerstead today — file size, file types, per-account storage, photos per record, monthly reminder volume, and monthly customer-message volume. Where a limit is meant to be enforced end-to-end by the cron pipeline or by a route handler (the per-tier published-page cap, photo file type and size on upload), we say so. Where it is currently survey-only for makers (monthly customer messages, monthly reminders), we say that too — the cap will tighten in a follow-up release.

Every Makerstead plan imposes a published-page limit on ACTIVE records only:

• Drafts (records that have not been submitted) do not count.
• Archived records (records the maker has retired) do not count.
• Active published records (approved and not archived) count.
• Restoring an archived record takes an available slot. If restoring would push you over your plan’s cap, the request is rejected — archive a published record instead.
• Deleting a record is not required to free a slot. Archive it; restore later if your bench lines up.

Example: a Solo maker (10 published-care-pages cap) with 8 published and 2 drafts is at 8 of 10. Archiving one of the 8 published drops the active count to 7. Restoring it pushes it back to 8. The drafts do not enter the count at any point. Professional is uncapped and falls under this whole policy in lieu of a fixed ceiling.

Photos uploaded to a care page hero, a service entry, or a care request must be JPEG, PNG, or WebP. Each photo is up to 20 MB. Files outside this allowlist are rejected at upload before they reach storage. Executable content, archives, documents, and videos are not in the allowlist; the platform does not currently store those file types.

Each Makerstead account is allotted 2 GB of photo storage, total across the care-page hero, service entries, and care-request attachments. Storage is currently checked at upload time as an upper bound; we do not yet aggregate the per-photo byte sum into a live read on the dashboard. See the storage tracking disclosure below.

• Care request — 3 photos per submission.
• Service entry — 1 photo per entry.
• Care-page hero — a single primary image; multi-image galleries are a follow-up.

Makerstead runs a maintenance-reminder cadence per product based on the cadence the maker selects. As a published ceiling, Makerstead limits the platform-wide volume to 120 maintenance-reminder emails per maker per 30 days. This row is display-only on the dashboard today; the per-maker throttle that prevents a runaway cron from sending more than the published ceiling is a follow-up release.

Inbound care-request submissions against a single product and against a single maker are bounded as follows over a rolling 30-day window:

• 500 inbound care-request submissions per product per 30 days.
• 5000 inbound care-request submissions per maker per 30 days.

These caps are display-only at publication; throttle enforcement is a follow-up release. A maker whose volume is on the rising edge of either ceiling today will not be cut off mid-send — the row reflects a measured read on the dashboard Usage card.

Bulk imports of care pages, service entries, or owners are not supported in this release. There is no importer endpoint. Migration assistance from a CSV or spreadsheet is available on request — email makerstead@polsia.app.

Scraping the platform, the public care pages, or the founders directory at scale is not allowed. Per-record viewing by a real visitor is fine. Bot traffic that would push a single product past the published monthly customer-message ceiling is governed by the acceptable-use policy and falls under the same response path (warning → takedown → account action).

Photos are validated as JPEG, PNG, or WebP on upload based on the browser-supplied file.type. Files outside the allowlist are rejected at the route before they reach the upload helper. Magic-byte header sniffing (re-checking the file’s internal magic regardless of the browser-supplied content type) is a follow-up release; in the meantime, executable content, archives, and documents are blocked at the upload boundary by MIME type.

Inbound care requests found to breach the acceptable-use policy are reported to the maker and not routed to the maker’s inbox — the maker is never asked to make sense of obviously malicious inbound traffic.

Makerstead does not index every photo’s byte size today. The storage row on the dashboard Usage card shows the published ceiling (2GB per account) and an explicit “tracking not enabled yet” label rather than a real-time sum. Upload-time size checks still gate the platform — the per-photo cap is enforced; the platform ceiling is rhetorical until a later release adds a per-byte index.

Material changes to a published number — for example a change to the per-account storage ceiling, the per-tier published-page cap, or the monthly customer-message ceiling — get a sign-up-screen notice and at least fourteen days’ notice before effect. Continued use after the effective date is acceptance of the updated policy; if a change is one a maker can’t accept, cancel from the billing surface and export records before it lands. Copy edits that don’t move a number (clarifications, citation fixes) roll forward without notice.