Legal

Legal

FleeceForge™'s legal documents in one place: the Privacy Notice, the Terms of Service, the Acceptable Use Policy, and the Data Processing Addendum. They cover the websites, the account portal, and the hosted Printpaca and Soapaca service. Never Idle has its own terms and privacy policy.

FleeceForge Privacy Notice

Last updated November 11, 2026

How the documents fit together

FleeceForge has four legal documents, all published together at fleeceforge.com/legal: this Privacy Notice, the Terms of Service, the Acceptable Use Policy, and the Data Processing Addendum.

Website visitors (fleeceforge.com, tools.fleeceforge.com, and status.fleeceforge.com): this Privacy Notice and Part 1 of the Terms of Service.

Waitlist and tool-request senders, and people who use the country interest or Report a Shop form: the same, including the waitlist and tool request terms in Part 1.

Shop owners and their staff: all four. Part 2 of the Terms of Service covers the hosted Printpaca and Soapaca service, and the Acceptable Use Policy and the Data Processing Addendum are part of the Terms.

Shop customers (people who use a shop at <slug>.fleeceforge.net): the shop's own privacy notice governs their information. FleeceForge processes it for the shop under the Data Processing Addendum, as section 3 of this notice explains, and the Acceptable Use Policy applies to their use of the shop.

Never Idle is a separate site with its own terms and privacy policy, and these documents don't cover it.

Effective date: TBD · Version: 0.3 (draft, updated 2026-11-11)

This notice explains how FleeceForge™, a sole proprietorship ATTORNEY: confirm the documents can name the business by its trade name alone, without the owner's legal name., founded in 2024, with its mailing address at 22365 El Toro Rd, Unit 2223, Lake Forest, CA 92630 ("FleeceForge," "we," "us," or "our"), handles personal information. It covers FleeceForge's websites, fleeceforge.com, tools.fleeceforge.com, and status.fleeceforge.com (the "websites"); the account portal at my.fleeceforge.com; and the hosted Printpaca and Soapaca service, including each shop's own site at <slug>.fleeceforge.net (together with the account portal, the "service"). It covers:

Website visitors: people who visit the websites.
People who use our forms: people who send a tool request or join the waitlist on tools.fleeceforge.com, or use the country interest form or the Report a Shop form on my.fleeceforge.com.
Shop owners: you, if you have a FleeceForge account, and the staff you give logins to.
End customers: people who use a FleeceForge-hosted shop's public pages, upload files, request quotes, or receive invoices. We handle their information on behalf of the shop, as explained in section 3.

Questions about this notice go to legal@fleeceforge.com.

1. The short version

We collect what we need to run your account, bill you, and keep the service secure. On the websites, we collect only what you enter in the forms, as listed in section 4, plus a hashed form of your network address that limits how often a form can be sent.
FleeceForge doesn't add advertising trackers or other tracking to shops. Our websites have no ads or tracking pixels, and they count visits with Cloudflare Web Analytics, which sets no cookies. The websites set no cookies of their own, apart from the status page's theme choice (section 4), and the account portal and shop admin apps set only sign-in cookies. We track whether shop owners open our own emails to them (billing notices, trial reminders, and other notices). We don't track which links they click. Emails a shop sends to its own customers aren't tracked. See section 4. Counsel: risk register P2 cookies and tracking, shop-supplied images can still load from other sites.
We don't sell or share personal information for advertising. We never sell shop data, and we never use it to train AI. FleeceForge has no AI features. ATTORNEY: placement; see question 17.
Every form that collects personal information (the suggestion box, the waitlist, the country interest form, and the Report a Shop form) is closed until the legal review is finished, and nothing is collected through them yet.
Each shop's data lives in its own isolated container, database, and storage bucket. FleeceForge can access that data, only for the purposes in section 9.
Your shop owns its customers' data. We process it only to provide the service to the shop.
When an account ends, we keep its shop data for 30 days so that the owner can export it, and then we delete it.
To see or delete what you sent us, email legal@fleeceforge.com (section 10).

2. Information about shop owners

We're responsible for this information (the "controller," in privacy-law terms).

What	Examples	Why we use it
Sign-up details	Email address, shop name, shop address (slug), chosen plan	To create and identify your account and shop
Account sign-in	Single-use sign-in links (stored only as hashes), a session cookie on `my.fleeceforge.com` that lasts 30 days	To let you sign in securely
Billing details	Your name, US billing address, the plan and its status, invoices, and payment status. Stripe collects your card details; we don't receive or store your card number, card brand, last 4 digits, or expiry date. We read only the country that issued your card, from Stripe, at sign-up and at each renewal, to check eligibility, and we don't store it. At sign-up we also read a fingerprint of your card (a Stripe identifier that doesn't reveal the card number) and compare it, and your email address, with earlier sign-ups to enforce one free trial per business TBD: hosting — confirm the one-trial check is live before launch	To bill you, calculate sales tax through Stripe Tax, check at sign-up and at each renewal that your billing address is in the 50 states or DC and your card was issued in the United States, and handle failed payments and disputes.
Shop settings	Custom domain names, your shop's time zone, your SMTP relay host and user name, and your SMTP relay password (stored encrypted)	To run your shop as you configured it
Shop logins	Your and your staff's shop user names, email addresses, and password hashes, stored in your shop's database	To let you and your staff sign in to your shop
Support and email	Messages you send us, records of email we send you (welcome, trial, billing, and deletion notices), and whether you opened each one	To answer you, keep you informed about your account, and confirm that important notices reach you.
Security and operations	IP addresses, request logs, rate-limit counters, bot checks (Cloudflare Turnstile) on sign-up, sign-in, and the Report a Shop form, and an audit log of changes to your account	To prevent abuse, fix problems, and keep a record of what changed and why

We don't ask for sensitive information such as government ID numbers, health information, or precise location.

3. Information about end customers

When an end customer uses a FleeceForge-hosted shop at <slug>.fleeceforge.net, the shop decides what information to collect and how to use it. The shop is responsible for that information, and FleeceForge processes it on the shop's behalf under our Data Processing Addendum. In privacy-law terms, the shop is the "business" or "controller," and FleeceForge is its "service provider" or "processor." ATTORNEY: from the website notice: advise how this notice treats shops at <slug>.fleeceforge.net; their customer data falls under this section and the Data Processing Addendum now that the notices are merged. See question 21.

What a shop may hold: a customer's name, email address, phone number, billing address, shipping address, state or province, country, and notes, as entered by the shop's staff; the name, email address, and note that a customer types into a shop's order or quote-request form; the file, material, quantity, weight, and print time a customer submits on a Printpaca quote request (Soapaca shops don't have that form); quotes, invoices, credit notes, and payment records that the shop creates, including the customer's name, email address, addresses, and any free text the shop types; records of the emails the shop sends, including the recipient's address; and staff user names. The shop decides what to enter. The apps don't collect a customer's card details, IP address, or browser details in the shop's records.
What we do with it: we store, back up, and transmit it so that the shop works. We don't use it for our own purposes, sell it, share it for advertising, or combine it with other shops' data.
Payments: shops take payment through their own processors. FleeceForge doesn't receive end customers' payment card details.
Email: a shop sends email to its end customers through its own email relay, under that provider's terms. TBD: update when the managed email add-on launches.
Your requests: if you're an end customer, contact the shop directly to see, correct, or delete your information. If you contact us instead, we'll pass your request to the shop and tell you we did. A shop may keep some of your information after a deletion request where the law requires it, such as the name and tax details on an invoice it has already issued. Counsel: risk register item 10, legal-retention exception to erasure.
Uploaded files and requests: files uploaded with a Printpaca quote request (Soapaca shops don't have the file upload) are deleted automatically after the shop finalizes the request: G-code files after 30 days and any other file, such as a 3D model, after 180 days. The quote request itself is kept until the shop deletes it, unless the shop turns on automatic deletion of closed requests in its settings. Then a closed request is deleted, with its file, the number of days after it was closed that the shop chooses (7 to 3,650 days), but not while its invoice is still a draft. Counsel: risk register P2, upload and request retention wasn't disclosed.

4. Information about website visitors and people who use our forms

Forms are closed for now. The suggestion box, the waitlist, the country interest form, and the Report a Shop form are closed until the legal review is finished, and show "Awaiting legal counsel." Nothing is collected through them yet. Until the Report a Shop form opens, send reports to legal@fleeceforge.com. The descriptions below say how each form works once it reopens. fleeceforge.com and status.fleeceforge.com have no forms.
Tool requests. When you send the suggestion box form on the tools.fleeceforge.com home page, we store your craft or hobby, what you'd like the tool to do, what you use today (the options you tick), your email address, and the time you sent it.
The waitlist. When you join the waitlist on the tools.fleeceforge.com pricing page, we store your email address, which of Printpaca, Soapaca, the Performance add-on, and the Invoice Email add-on you want to hear about (you pick at least one), the plan you're interested in if you pick one, and the time you first joined. We then email you a confirmation link, and you're on the waitlist only after you confirm. We record when you confirmed and when we last sent you a confirmation email. We send at most 3 confirmation emails for one entry, at least 10 minutes apart. If you don't confirm within 7 days of joining, we delete the entry. If you join again with the same email address, we email you a new confirmation link, and your choices change only after you confirm it; we keep the first join time. Confirmation links stop working after 7 days or when a newer link is sent. Counsel: waitlist retention, owner decision 2026-11-08; now 2 years, see section 8.
Country interest. On the sign-up site's "available in the United States only" page, you can leave your email address, your country, and an optional note. We don't store your network address with it. If you send it again with the same email address and country, we update the entry. Counsel: question 15.
Report a Shop. On my.fleeceforge.com/report, anyone can report a shop for breaking our rules. The form collects the shop address, a reason, the details you write, an optional email address for a reply, and a one-way hash of your network address, which limits repeat submissions and helps us review abuse of the form. We use the report to review the shop against our rules and, if you gave an email address, to reply to you. We keep reports for 2 years (section 8). For a Report a Shop report, we don't tell the shop's owner who reported it. If you send a copyright or other rights complaint, we forward it to the shop's owner, including your name and contact details, as the law expects. Counsel: confirm the 2-year retention for abuse reports. Counsel: confirm that withholding the reporter's identity from the shop owner is acceptable, including when law or a legal request requires disclosure. ATTORNEY: from the website notice: confirm that withholding the reporter's identity from the shop owner is acceptable.
A hashed network address. The forms limit how often one network can send them, and the way they count differs by form. The tool request form and the waitlist accept up to 5 sends an hour from one network. To count them, the website combines your IP address (the full address for IPv4, or its first 64 bits, the /64 network, for IPv6) with a secret value and keeps only a one-way hash of the result. For a tool request, the hash is stored with the request. For the waitlist, the hash is kept in a separate record with only a time rounded down to 10 minutes, never linked to your email address. The country interest form accepts up to 10 sends an hour from one network. It keeps a keyed hash of the network address (the full IPv4 address, or the /64 network for IPv6) in a rate-limit record that is deleted within about two hours of being written, and never with your entry. Sign-up and sign-in on my.fleeceforge.com are limited the same way: to count attempts, the account portal keeps keyed hashes of the network address, of the email address, and of the sign-in email together with a browser key, in a send log that a nightly cleanup deletes after 30 days. TBD: hosting — deploy before launch These keyed hashes use HMAC-SHA-256 with a key derived from a server secret, so they can't be reversed or matched without that secret. The Report a Shop form accepts up to 10 reports a day from one network and stores a keyed hash of the network address (HMAC-SHA-256, with a key derived from a server secret) with the report. We never store the IP address itself.
Email you send us. If you write to us, we keep your message and your address so that we can reply.
FleeceForge doesn't add advertising or behavioral tracking. We don't add advertising cookies, session recording, or tracking pixels to our websites or to shop pages. Apart from Cloudflare Web Analytics, the websites load nothing from other websites. A shop can add its own content, such as images or a logo loaded from another website, to its pages and emails; the site that hosts that content can see when it loads, and that's the shop's responsibility. Counsel: risk register P2 cookies and tracking, the CSP and email logo URL allow outside images.
Website analytics. Cloudflare Web Analytics counts visits on fleeceforge.com and tools.fleeceforge.com only. It doesn't run on the status page, the account portal, or shops. Cloudflare adds its measurement script at the edge. Cloudflare says Web Analytics doesn't use any client-side state, such as cookies or localStorage, to collect usage metrics. Cloudflare also says it doesn't fingerprint visitors for analytics. For each page view it records the website name and the page path (Web Analytics doesn't log query strings, so nothing after a ?), the website that sent you, your country, your browser, operating system, and device type, the type of navigation, and how fast the page loaded (page-load timing and Core Web Vitals). Cloudflare keeps the unsampled records for 7 days and then keeps an aggregated sample of around 10 percent of the original volume; the dashboard shows up to six months. Cloudflare processes this data for us as our hosting provider. ATTORNEY: from the website notice: review this Cloudflare Web Analytics section. Counsel: confirm the disclosure wording; see question 20.
Theme choice on fleeceforge.com and tools.fleeceforge.com. The light and dark theme switch on both sites saves your choice in your browser's local storage, under the key theme. It stays on your device and is never sent to us.
Email open tracking. The emails FleeceForge sends to shop owners (billing notices, trial reminders, and other notices) go through SMTP2GO, which adds a tracking pixel that tells us whether you opened the email. We don't track clicks: links in these emails aren't rewritten through SMTP2GO, and we collect no click events. We use open tracking only to confirm that important notices reach you. ATTORNEY: see question 16. FleeceForge doesn't add tracking to the emails a shop sends to its own customers, but an image the shop includes, such as a logo loaded from another website, can show that site when the email is opened.
Network and security data. Cloudflare, which hosts our websites and shops, processes IP addresses and request details (such as the page requested, the time, and the browser type) to deliver pages, block attacks, and enforce rate limits. The request logs written by our account, sign-in, and shop-routing services (Cloudflare Workers Logs) are kept 7 days and may include IP addresses, for example in shop access logs and sign-in rejection lines. We don't redact them. Cloudflare keeps its own edge and security logs under Cloudflare's own privacy policy and doesn't publish a retention period. Counsel: risk register item 12, log retention unstated. The two websites (fleeceforge.com and tools.fleeceforge.com) keep no Workers Logs.
Cookies. Our websites set no cookies, apart from the status page's theme cookie below. The account portal at my.fleeceforge.com and each shop's admin app set only the sign-in cookies below. We use only the cookies below. ATTORNEY Counsel: risk register P2 cookies, the known-device and theme cookies weren't disclosed; see question 13.

Cookie	Where	What it does	How long
Account portal session (`__Host-ff_session`)	`my.fleeceforge.com`	Keeps you signed in to the account portal	30 days from sign-in; it doesn't extend with use. Sign-in links work for 15 minutes.
Shop login session (`printpaca_session`, for both Printpaca and Soapaca)	Your shop's admin pages	Keeps you and your staff signed in to the shop	30 days from sign-in, with no idle timeout; it doesn't extend with use
Known device (`printpaca_device`)	Your shop's admin pages	Lets the sign-in page recognize a browser that has signed in before, so that someone else guessing passwords from the same network can't lock you out. It doesn't sign you in.	90 days from when it's set; the cookie is HttpOnly, Secure, and SameSite=Strict
Public theme (`pp_theme`)	A shop's public pages	Remembers the visitor's display theme choice, light or dark. It's set only when the visitor picks a theme, and the server reads it so the page shows the right theme.	1 year
Status page theme (`theme`)	`status.fleeceforge.com`	Saves your light or dark choice, only if you change it. Your display preferences are kept in your browser's storage. Neither is sent to anyone else or used for tracking.	1 year
Cloudflare security and bot checks	Our websites and shops	Blocks attacks and bots, including Cloudflare Turnstile on sign-up, sign-in, and the Report a Shop form on `my.fleeceforge.com`. If Cloudflare's bot protection challenges a request, Cloudflare may set `__cf_bm` or `cf_clearance` to tell people from automated traffic. `cf_clearance` records that a challenge was passed. Turnstile on its own sets no cookie by default; it issues a one-time token. We don't use features that set `_cfuvid`.	Set by Cloudflare. `__cf_bm`: 30 minutes of continuous inactivity, per Cloudflare. `cf_clearance`: 30 minutes (the Challenge Passage setting). Bot Fight Mode is on for shops on fleeceforge.net, so Cloudflare may challenge shop visitors and set `__cf_bm`; it's off on fleeceforge.com. TBD: the bot-check key is set before sign-up opens

Because these cookies are needed for the service to work or only remember a choice the visitor made, we don't show a cookie banner. ATTORNEY

Do Not Track. Browsers can send a Do Not Track signal. Our websites don't track you across other sites, so they treat every visit the same way whether or not the signal is on.

5. How we use information

We use personal information only to:

provide, run, secure, and support the service and the websites;
bill you, collect tax, and handle failed payments and disputes;
read tool requests, decide what to build, and reply to the sender about them (there's no newsletter);
send each person on the waitlist one email when sign-up opens for each product or add-on they chose, and nothing else;
email people who asked to hear when FleeceForge supports their country, once, when it does;
review a reported shop against our rules and, if the reporter gave an email address, reply to them;
use hashed network addresses only to enforce the hourly form limits and stop abuse of the forms;
send you messages about your account, such as sign-in links, trial reminders, billing notices, suspension notices, and deletion notices;
prevent fraud, spam, and abuse, and enforce our Terms of Service and Acceptable Use Policy;
comply with the law and respond to lawful requests; and
tell you about material changes to the service, our terms, or this notice.

We don't use personal information for advertising. We don't send marketing email without your permission. We don't plan a product newsletter, and any future newsletter will have its own sign-up. We don't use personal information for automated decisions with legal or similarly significant effects. We never sell shop data, and we never use it, or any customer data, to train AI. FleeceForge has no AI features. ATTORNEY: placement; see question 17.

We share personal information only with the service providers below (our "subprocessors"), only as needed to run the service and the websites, and under contracts that limit their use of it. We also share it when the law requires, to protect our rights or someone's safety, or with a successor if our business is sold or reorganized.

Provider	What it does for us	Information involved
Cloudflare, Inc.	Hosts our websites and every shop (Workers, Durable Objects, Containers), and runs the code behind the website forms. Each shop's SQLite database runs inside its container and is replicated to R2, where uploaded files are also stored. Our account and control-plane records (shop names, owner emails, plan and billing state) are in D1, KV, Queues, and Workflows; D1 also holds the website forms' entries. Also provides DNS, TLS, custom domains, bot checks (Turnstile), website visit counts (Web Analytics), and security; like any web host, it processes request data such as IP addresses and request details when delivering pages	All service data, including each shop's database and files, end-customer data, form entries, and visitors' IP addresses and request details
Stripe, Inc.	Payments, subscriptions, invoices, sales tax calculation (Stripe Tax, on from launch), and the Customer Portal	Shop owners' billing details, including billing address and card country
SMTP2GO	Delivery of our own email from `fleeceforge.com` addresses (account notices come from `setup@fleeceforge.com`), with open tracking only, an email to our inbox for each tool request, waitlist sign-up, and Report a Shop report, and a nightly summary of new country interest entries, containing the details entered in the form	Shop owners' email addresses, message content, and open events, which can include IP address and device details; the details entered in tool requests, waitlist sign-ups, country interest entries, and Report a Shop reports SMTP2GO turns open tracking on or off for each API key, not for each message; FleeceForge sends one-time sign-in and setup links through a separate key with tracking off, and every other notice through the tracked key, which has open tracking on and click tracking off. SMTP2GO's privacy policy says it keeps email headers for 35 days and a sample of message content (one email in a thousand) for 35 days, and gives no retention period for open events, so we can't state one.
Zoho	Our mailboxes: contact@fleeceforge.com, where form notices and any messages you send us arrive; legal@fleeceforge.com; and alerts@fleeceforge.com, where monitoring and ops alerts, Report a Shop notices, and country interest summaries arrive	Support messages, form notices, and owner alerts
VPS Hosting Service (vpshostingservice.co)	Hosts our public status page (`status.fleeceforge.com`) and uptime checks on a server outside Cloudflare, so the page keeps working if Cloudflare is down. The status page runs Gatus on a dedicated VPS at VPS Hosting Service.	Status page visitors' IP addresses and request details; no shop data

We'll update this list before adding a provider that handles personal information. The current list is the table above, published at fleeceforge.com/legal#privacy-6-who-we-share-it-with. Cloudflare's own sub-processors are listed at https://www.cloudflare.com/gdpr/subprocessors/cloudflare-services/. Shops get advance notice under the Data Processing Addendum. Shops' own providers, such as the SMTP relay a shop connects or a payment link a shop adds to its invoices, are the shop's providers, not ours.

7. Where information is stored

At launch, we offer the service only to customers in the 50 United States and the District of Columbia, with a US billing address and a US-issued card. US territories come later. The service isn't offered in the European Union, the United Kingdom, or Canada; sign-up refuses visitors whose connection appears to come from outside the United States, and paid checkout refuses cards not issued in the United States. Counsel: is an availability statement plus blocking enough to keep FleeceForge outside GDPR, UK GDPR, and PIPEDA scope, given that US shops may still have end customers there? Shop data is stored in Cloudflare R2 with a United States location hint. Cloudflare runs shop containers in its network and doesn't let us pin them to one country, so data may be processed outside the United States while a container runs. ATTORNEY: whether this needs more disclosure, given that US shops may have end customers abroad.

8. How long we keep it

Information	How long
Waitlist entries	Deleted automatically 2 years (730 days) after you join. Entries you don't confirm are deleted 7 days after you join. You can ask us to remove yours at any time, and every waitlist email has an unsubscribe link (section 10). TBD: hosting — deploy before launch Counsel: waitlist retention.
Waitlist rate-limit records	Times rounded down to 10 minutes; deleted by a daily cleanup once they're a day old.
Tool requests (the suggestion box on `tools.fleeceforge.com`), including their hashed network address	Kept 2 years (730 days), then deleted automatically.
Country interest entries	Deleted automatically 1 year after your last submission. You can ask us to remove yours at any time.
Abuse reports (Report a Shop)	Deleted automatically 2 years after they're sent. ATTORNEY: from the website notice: confirm the 2-year retention for abuse reports.
Website form entries in database recovery history	A deleted entry can remain in the database's recovery history for up to 30 days. The 90-day nightly exports (row below) cover only the control-plane database. Website forms are stored in a separate database, `ff-tool-requests`, that the export job doesn't cover, so form entries aren't in those exports.
Website visit counts (Cloudflare Web Analytics)	Cloudflare keeps the unsampled records for 7 days, then an aggregated sample of around 10 percent of the original volume; the dashboard shows up to six months.
Unfinished sign-ups (email not confirmed, or Checkout not completed)	Deleted after 8 hours
Sign-in and setup links	Expire after 15 minutes (sign-in), 8 hours (email confirmation), and 72 hours (setup), and are single use
Export download links	Work once, within 15 minutes of being sent TBD: hosting — the full export with uploaded files (plan 8 with the export-link amendments) ships before launch
Your shop's data while your account is active, on trial, past due, or suspended	Kept
Files uploaded with a quote request (Printpaca only)	Deleted automatically after the shop finalizes the request: G-code files after 30 days, any other file, such as a 3D model, after 180 days. Requests that are still open keep their files. Counsel: risk register P2, upload auto-deletion wasn't disclosed.
Quote requests	Kept until the shop deletes them. If the shop turns on automatic deletion of closed requests, a closed request is deleted with its file the number of days after it was closed that the shop chooses (7 to 3,650 days), but not while its invoice is still a draft.
Records and files a shop deletes while its account is active	Removed from the live service at once. Deleted files can stay in storage trash for 30 days, and deleted records can remain in backups until those expire (next row). Deleted database records are overwritten in the live database file; until the next database checkpoint (usually minutes) a copy can remain in its write-ahead log, and copies in backups remain for up to 7 days. Counsel: risk register item 20, deleted-data windows weren't disclosed.
Your shop's data after cancellation or termination	Kept 30 days after the plan ends so that you can request a free export, then deleted. We email you 7 days and 2 days before deletion. Counsel: risk register P2, aligned with the notices hosting sends.
Your shop's data in backups	Deleted as the backups expire, within 7 days after deletion. Counsel: risk register items 9 and 20, backup window unverified.
Account records in our control-plane database (account, sign-up, and shop records)	When a shop is deleted, we keep a minimal record of it: its internal ID, state, dates, Stripe customer and subscription IDs (needed to match tax and payment records), and its subdomain, which stays reserved so an old link never points to a different shop. Two years after deletion, a daily cleanup replaces the shop name and the account email address with placeholders (unless the account still has another shop, a shop deleted less than two years ago, or a sign-up in progress) and deletes remaining sign-in sessions and the original sign-up record. If an account was blocked for fraud or chargebacks, we keep its email address so the block keeps working. Accounts that never got a shop, and sign-up attempts that never became an account, are scrubbed or deleted two years after they were created. Database backups are kept up to 90 days, and point-in-time recovery covers 30 days, so removed data can remain in backups until they expire. TBD: hosting — deploy before launch
Trial-check records	Keyed hashes (not readable as the original values) of the sign-up email address and the card fingerprint, kept 3 years from the trial, so that one trial per business still applies after the 2-year deletion of account records. TBD: hosting — confirm the one-trial check is live before launch
Billing and tax records	Kept as long as tax and accounting law requires ATTORNEY: proposed 7 years. Stripe keeps its own records under its policy.
Audit log and the record that a shop was deleted	Kept while the shop exists. Two years after a shop is deleted, its audit-log entries are deleted, except one entry recording that the shop existed and when it was deleted, and any records of payment disputes (kept so the chargeback rules keep working). The audit log holds internal IDs, not card details or customer names. TBD: hosting — deploy before launch
A custom domain name after a shop leaves	Held for 90 days so that nobody else can claim it right away
Support email, form notification emails, and other messages in our mailbox	Messages to legal@fleeceforge.com (legal, privacy, copyright, security, and abuse matters): 3 years. Messages to contact@fleeceforge.com, including form notices and support: 2 years. Monitoring and ops alerts to alerts@fleeceforge.com (Gatus and ops alerts, Report a Shop notices, and country interest summaries): 1 year, then deleted. We delete older mail once a year, so a message can stay up to a year past its period.
Request logs from our account, sign-in, and shop-routing services	7 days; may include IP addresses, which aren't redacted.
Cloudflare's own edge and security logs	Kept under Cloudflare's own privacy policy; Cloudflare doesn't publish a retention period.

On non-payment, a shop is deleted about 58 days after the first failed charge: about 14 days of payment retries, 14 days suspended, and 30 days of export-only retention.

If FleeceForge shuts down the service, we give shop owners at least 60 days' notice and an export as described in section 19 of the Terms of Service before we delete their data, and we refund the unused part of the current billing period, pro rated, as the Terms of Service (section 21) describe. ATTORNEY: whether this belongs here as well as in the terms; see question 17.

9. How we protect it

Isolation: each shop runs in its own container, with its own SQLite database and its own storage bucket.
Encryption in transit: all traffic to our websites, the account portal, and shops uses TLS.
Encryption at rest: FleeceForge doesn't add its own encryption to shop databases or backups. They rely on the encryption at rest that Cloudflare applies to its storage: Cloudflare states that all objects stored in R2, including their metadata, are encrypted at rest, and that all objects stored in D1, including metadata, live databases, and inactive databases, are encrypted at rest. Cloudflare doesn't document encryption for the disk of a running shop container, which is temporary and holds only a working copy; the durable copy of a shop's data is the replica in R2. Secrets such as your SMTP relay password are stored encrypted.
Credentials: sign-in, confirmation, and setup links are single use and stored only as hashes. We never generate or email a shop password.
Access control: only the owner of FleeceForge has administrative access. Administrative tools sit behind Cloudflare Access, and keys that can change infrastructure or billing are held only by the automated pipeline, scoped as narrowly as each provider allows.
Backups: each shop's database is backed up by continuous replication to the shop's own storage bucket, with a snapshot every 24 hours kept for 7 days, stored separately from the running shop, and we can restore it to any point in the last 7 days (owner decision 2026-11-07). There is no second copy yet, and a monthly restore drill is planned. Counsel: risk register item 9, matches the terms' best-effort backup wording.
Our access to shop data. FleeceForge can technically access your shop's data. Each shop's database is replicated to a storage bucket in FleeceForge's Cloudflare account, and FleeceForge holds the credentials for those buckets, so the owner can restore a shop's database and files from backup and read them. FleeceForge's operator tools can also stop, start, suspend, and restore a shop, replace its database from a backup, and reset the shop owner's password (which signs the owner out and opens setup again). The status and list tools show shop details such as the shop name, plan, and state, but not shop records. Cloudflare, as our hosting provider, can also reach the infrastructure that holds your data under its own terms. Only the owner of FleeceForge has this access. We use it only to provide support you ask for, to restore backups, to keep the service secure and working, to investigate abuse under the Acceptable Use Policy, or when the law requires it. We don't browse shop data for any other purpose. Counsel: confirm wording; see question 19.
Monitoring: each shop's resource use is sampled and the owner gets an alert email when a shop reaches 70% of a limit, a daily reconciliation checks billing against the shops, and a status page host outside Cloudflare publishes service status and emails the owner when a check fails.

No system is perfectly secure. If a security incident affects your personal information, we'll notify you as the law requires.

10. Your privacy rights

Depending on where you live, you may have the right to:

know what personal information we hold about you and how we use it, and get a copy;
correct inaccurate information;
delete your information, subject to exceptions such as billing records we must keep;
limit the use of sensitive personal information (we don't collect any for that purpose); and
not be treated differently for using these rights.

California residents: the California Consumer Privacy Act, as amended by the California Privacy Rights Act (CCPA), may give you these rights. ATTORNEY: whether the CCPA applies to FleeceForge at all, given its thresholds. ATTORNEY: from the website notice: confirm whether the CCPA applies to FleeceForge. This notice offers these rights either way. We don't sell or share personal information, as the CCPA defines those terms, and we haven't in the past 12 months. We don't use or disclose sensitive personal information for purposes that would give you a right to limit it. Through the websites' forms, we don't collect sensitive personal information.

What we collect on the websites, and why: identifiers (your email address and a hashed network address), what you enter in the forms (your craft, your tool idea, your product and plan choices, your country, and the details of a report), and the request details Cloudflare processes to deliver the websites. We collect them from you and your browser, for the purposes in section 5, and disclose them only to the service providers in section 6. Sections 2 and 3 list what we collect for the service.

How to make a request: email legal@fleeceforge.com from the email address on your account, or from the address you used in a form, and say what you'd like: a copy of what we hold, a correction, or deletion. We verify requests by that address, and we respond within 45 days. ATTORNEY: confirm 45 days, and any extension wording, meets the laws that apply. You can name an authorized agent; we'll ask the agent for proof of their authority.

Waitlist: every waitlist email has an unsubscribe link, and unsubscribing deletes your waitlist entry. You can also email us to leave the waitlist.
Forms: on a deletion request, we delete your tool requests, your waitlist entry, and your country interest entry, and the notification emails about them. A waitlist rate-limit record can't be tied to you, so we can't find it on request; it's deleted automatically, as section 8 describes.
Shop owners can also export their shop's data for free. The full export is a ZIP file with the shop's records, settings, and uploaded files. The owner starts it from the account portal, or emails contact@fleeceforge.com while the shop is suspended or within 30 days after the plan ends, and we email a download link that works once, within 15 minutes. A new link can be requested and serves the same file, and a new full export is available every 3 days. While the shop is running, the owner can also download the shop's records and settings directly from Settings in the shop's admin app at any time, as JSON or as CSV files; that download doesn't include uploaded files and isn't limited. TBD: hosting — the full export with uploaded files (plan 8 with the export-link amendments) ships before launch Counsel: risk register item 8, the portal export doesn't exist yet.
End customers: see section 3. Your request goes to the shop, which controls your information.

11. Children

The service is for businesses, and account holders must be at least 18. Our websites aren't directed to children under 13, and we don't knowingly collect their personal information. ATTORNEY ATTORNEY: from the website notice: confirm the age wording. If we learn that we have, we'll delete it. Shops are responsible for their own end customers, including any age rules that apply to what they sell.

12. Changes to this notice

We'll post any change here with a new effective date. For a material change, we'll email account holders at least 30 days before it takes effect ATTORNEY.

13. Contact

FleeceForge, a sole proprietorship 22365 El Toro Rd, Unit 2223, Lake Forest, CA 92630

Email: legal@fleeceforge.com

FleeceForge Terms of Service

Last updated November 11, 2026

How the documents fit together

FleeceForge has four legal documents, all published together at fleeceforge.com/legal: these Terms of Service, the Privacy Notice, the Acceptable Use Policy, and the Data Processing Addendum.

Website visitors (fleeceforge.com, tools.fleeceforge.com, and status.fleeceforge.com): Part 1 of these terms and the Privacy Notice.

Waitlist and tool-request senders, and people who use the country interest or Report a Shop form: the same, including section 3 (the waitlist and tool requests).

Shop owners and their staff: Part 1 and Part 2 of these terms, the Acceptable Use Policy, the Data Processing Addendum, and the Privacy Notice.

Shop customers (people who use a shop at <slug>.fleeceforge.net): the shop's own terms and privacy notice govern their dealings with the shop. FleeceForge processes their information for the shop under the Data Processing Addendum, and the Acceptable Use Policy applies to their use of the shop.

Never Idle is a separate site with its own terms and privacy policy, and these documents don't cover it.

Effective date: TBD · Version: 0.3 (draft, updated 2026-11-11)

Part 1. General terms

Part 1 applies to everyone who uses the websites or the service.

1. About these terms

These terms are an agreement between you and FleeceForge™, a sole proprietorship ATTORNEY: confirm the documents can name the business by its trade name alone, without the owner's legal name., founded in 2024, with its mailing address at 22365 El Toro Rd, Unit 2223, Lake Forest, CA 92630 ("FleeceForge," "we," "us," or "our").

The websites. Part 1 covers your use of FleeceForge's websites: fleeceforge.com, tools.fleeceforge.com, and status.fleeceforge.com (the "websites").
The service. Part 2 adds the terms for the hosted FleeceForge service, including hosted Printpaca (for 3D print shops) and hosted Soapaca (for soap and cosmetic makers), the account portal at my.fleeceforge.com, your shop's pages at <slug>.fleeceforge.net, and related email (together, the "service"). Part 1 also applies to the service.
"You." In Part 1, "you" means anyone who uses the websites or the service. In Part 2, "you" means the person or business that signs up for an account. If you sign up for a business, you confirm that you can bind that business to these terms, and "you" means the business.
Agreeing. By using the websites, you agree to these terms. If you don't agree, don't use the websites. ATTORNEY: see question 28 on whether use alone binds website visitors.
Other documents. For account holders, these terms include the Acceptable Use Policy and, for the personal information of your own customers, the Data Processing Addendum. The Privacy Notice explains how we handle the personal information we control.

Questions about these terms go to legal@fleeceforge.com.

2. The websites

Information only. The websites describe hosted software that FleeceForge is building. What they say about plans, features, and dates is information, not an offer, and it can change before sign-up opens. The pricing page on tools.fleeceforge.com shows the current plans and prices.
No scraping or disruption. Don't scrape the websites, access them in bulk by automated means, or try to disrupt them. The scraping and abuse rules in section 3 of the Acceptable Use Policy also apply to visitors through this section.
Links to other sites. The websites link to other websites, such as Never Idle, the Printpaca demo, and Printpaca on GitHub. Each has its own terms. FleeceForge isn't responsible for the content or practices of sites that others run.

3. The waitlist and tool requests

The waitlist and the suggestion box (tool requests) on tools.fleeceforge.com are closed until the legal review is finished. This section applies once they reopen.
The waitlist doesn't create an account, start a trial, take a card, or make a purchase. It doesn't reserve a price or a plan beyond what the pricing page says.
A tool request doesn't mean FleeceForge will build that tool.
Ideas. What you send as an idea or suggestion is covered by section 4. Don't send anything confidential.
Fair use of the forms. Don't send spam, automated submissions, or unlawful content.

4. Feedback and ideas

If you send FleeceForge feedback, suggestions, or tool ideas, you grant FleeceForge a perpetual, irrevocable, worldwide, royalty-free license to use them for any purpose. FleeceForge has no duty of confidentiality or payment to you for them. This is a license, not a transfer of ownership: you keep ownership of your ideas. ATTORNEY: from the website terms: confirm. ATTORNEY: the two sources differed; the website's license wording is kept as the single clause. Confirm it, or restore the hosted draft's shorter wording; see question 29.

5. Intellectual property and trademarks

Website content. The websites' text, artwork, and code belong to FleeceForge or its licensors. These terms don't give you any rights to them beyond using the websites.
Our software. The hosted service, including hosted Printpaca, hosted Soapaca, the account portal, and the control plane, is proprietary software that FleeceForge owns or licenses. We give account holders a limited, non-exclusive, non-transferable right to use it through the service while their subscription is active. You don't get a copy of the software or its source code.
Restrictions. You may not copy, resell, sublicense, or reverse-engineer the hosted service, or use it to build a competing service, except where the law allows it.
Public Printpaca is separate. The public, open-source Printpaca release (v1.2.x) is a separate product licensed under the AGPL-3.0, and that license, not these terms, governs its code. The hosted service runs different, proprietary builds.
Trademarks. "FleeceForge," "Printpaca," and "Soapaca" are FleeceForge trademarks. They're used as unregistered marks: an official USPTO search on 2026-11-10 found no US application or registration for any of the three names. ATTORNEY: whether to file, and in which classes; similar marks found in mirror searches are FLEETFORGE (pending) and PRINTPAPA (registered, class 40). Trademark policy. Account holders may say, factually, that their shop "runs on FleeceForge" or is "built with Printpaca" or "built with Soapaca." You may not use the names "FleeceForge," "Printpaca," or "Soapaca," our logos, or our alpaca artwork in a way that suggests FleeceForge made, endorses, or sponsors your product, shop, or service. A fork of the public Printpaca release must use a different name, may say that it is "based on Printpaca," and may not use the FleeceForge, Printpaca, or Soapaca names for a hosted service. Don't use a name or domain that is confusingly similar to ours. Send requests for permission to legal@fleeceforge.com. ATTORNEY: review this trademark policy, including whether to keep it inline or publish it separately.
Your marks. Your shop's name, logo, and content stay yours. You give us permission to show them in your shop and in the account portal. We list a shop as a customer on our website only with the shop's opt-in permission.
Feedback is covered by section 4.

6. Disclaimer of warranties

ATTORNEY: from the website terms: confirm this wording, and whether it must be set in capitals. The website terms used plain case; the hosted draft used capitals, kept here.

TO THE FULLEST EXTENT THE LAW ALLOWS, THE WEBSITES AND THE SERVICE ARE PROVIDED "AS IS" AND "AS AVAILABLE." FLEECEFORGE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. WE DON'T WARRANT THAT THE WEBSITES ARE ACCURATE, COMPLETE, OR ALWAYS AVAILABLE, THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, OR SECURE, THAT IT WILL MEET YOUR NEEDS, THAT DATA WON'T BE LOST, OR THAT QUOTES, PRICES, OR TAX FIGURES THE SERVICE CALCULATES ARE CORRECT. YOU'RE RESPONSIBLE FOR CHECKING THE QUOTES AND INVOICES YOU SEND.

Soap calculations, safety data, and labels. THE SOAP-MAKING FEATURES (SOAPACA), INCLUDING THE LYE CALCULATOR, SAPONIFICATION (SAP) VALUES, IFRA FRAGRANCE CHECKS AND LIMITS, INGREDIENT DATA, AND ANY LABEL CONTENT THE SERVICE GENERATES OR HELPS YOU PREPARE, ARE AIDS ONLY. THEY AREN'T PROFESSIONAL, MEDICAL, SAFETY, OR REGULATORY ADVICE, AND THEY MAY CONTAIN ERRORS, INCLUDING ERRORS IN REFERENCE DATA AND IN VALUES YOU ENTER. THE LYE CALCULATOR IS FOR SODIUM HYDROXIDE (NaOH) BAR SOAP ONLY, NOT FOR POTASSIUM HYDROXIDE (KOH) OR LIQUID SOAP. YOU MUST INDEPENDENTLY VERIFY EVERY AMOUNT, LIMIT, AND LABEL AGAINST YOUR SUPPLIERS' DATA AND RELIABLE SOURCES BEFORE YOU MAKE, LABEL, OR SELL A PRODUCT. YOU'RE SOLELY RESPONSIBLE FOR THE SAFETY, LABELING, AND LEGAL COMPLIANCE OF THE PRODUCTS YOU MAKE AND SELL. Counsel: risk register item 3 and lawyer question 1, lye calculator, IFRA, and label injury risk; see question 19.

Tax figures. THE SERVICE CALCULATES TAX ONLY FROM THE RATES AND SETTINGS YOU ENTER. IT DOESN'T DETERMINE WHICH TAXES APPLY TO YOU, YOUR PRODUCTS, OR YOUR CUSTOMERS, OR WHETHER SHIPPING, DISCOUNTS, OR OTHER CHARGES ARE TAXABLE, AND ITS TAX FIGURES AND REPORTS AREN'T TAX ADVICE. YOU'RE RESPONSIBLE FOR CHOOSING THE CORRECT RATES AND SETTINGS AND FOR COLLECTING, REPORTING, AND PAYING ANY TAX YOU OWE. CHECK YOUR LOCAL RULES OR ASK A TAX PROFESSIONAL. Counsel: risk register item 23 and lawyer question 4, flat-rate tax and untaxed shipping could mislead a shop; see question 21.

7. Limitation of liability

ATTORNEY: the proposed cap follows; counsel to confirm the amount, the exclusions, and enforceability. ATTORNEY: from the website terms: confirm.

TO THE FULLEST EXTENT THE LAW ALLOWS:

FLEECEFORGE ISN'T LIABLE FOR LOSS OR DAMAGE CAUSED BY AN OUTAGE, LIMIT, REMOVAL, OR OTHER ACTION OF CLOUDFLARE OR ANOTHER INFRASTRUCTURE PROVIDER THAT WE DON'T CONTROL, OR BY OUR COMPLYING WITH A CLOUDFLARE REQUIREMENT (SECTION 20). ATTORNEY: this research didn't read Cloudflare's liability or SLA terms; confirm the exclusion stands on its own, independent of Cloudflare's terms.
NEITHER PARTY IS LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, REVENUE, BUSINESS, GOODWILL, OR DATA, ARISING FROM THESE TERMS, THE WEBSITES, OR THE SERVICE, EVEN IF TOLD THEY WERE POSSIBLE. ATTORNEY: the website terms' exclusion is one-way ("FleeceForge isn't liable") and also names downtime; the hosted draft's mutual exclusion is kept here. Confirm; see question 29.
FLEECEFORGE'S TOTAL LIABILITY FOR ALL CLAIMS ARISING FROM THESE TERMS, THE WEBSITES, OR THE SERVICE IS LIMITED TO ATTORNEY: choose one; the sources differ, and the draft doesn't pick: (a) hosted draft: THE FEES YOU PAID FLEECEFORGE FOR THE SERVICE IN THE 12 MONTHS BEFORE THE EVENT THAT GAVE RISE TO THE CLAIM; (b) website terms: THE GREATER OF WHAT YOU PAID FLEECEFORGE FOR THE THING THE CLAIM IS ABOUT IN THE 12 MONTHS BEFORE THE CLAIM, OR $50; (c) the owner's proposal: (a) for paid use and $0 for free and trial use (Hobby trial, waitlist, tool requests). See questions 11 and 29. ATTORNEY: the owner proposes a $0 cap for free and trial use (Hobby trial, waitlist, tool requests); is that enforceable for California consumers, or should there be a minimum such as $100? See question 11. ATTORNEY: from the website terms: decide the cap for free use; the owner proposes $0 for free and trial use.
THESE LIMITS DON'T APPLY TO YOUR PAYMENT OBLIGATIONS, TO YOUR INDEMNITY OBLIGATIONS IN SECTION 8, OR TO LIABILITY THAT THE LAW DOESN'T ALLOW TO BE LIMITED. ATTORNEY: whether FleeceForge's data-protection obligations under the DPA need a separate or higher cap. Counsel: risk register item 3 and lawyer question 1, whether this cap holds for personal-injury claims from soap made with the calculator; see question 19.

8. Indemnity

You'll defend and indemnify FleeceForge and its owner against third-party claims, and the resulting losses and reasonable legal fees, that arise from:

your misuse of the websites;
your data or your end customers' uploads, including claims that they infringe someone's rights or are unlawful;
the goods and services you sell, quote, or make, including 3D-printed items and soap and other cosmetic products; Counsel: risk register item 3, extends the indemnity to soap products made with the calculator.
your breach of these terms or the Acceptable Use Policy; or
your dealings with your end customers, including how you collect and use their personal information.

We'll tell you promptly about the claim, let you control the defense, and cooperate at your cost. You may not settle a claim that admits fault for us or binds us without our written consent.

ATTORNEY: whether FleeceForge should give a mutual indemnity, for example for claims that the hosted software itself infringes someone's intellectual property. ATTORNEY: from the website terms: confirm. The website terms asked visitors only to "cover FleeceForge's reasonable costs from claims that arise from your misuse of the websites or your violation of these terms"; the merged clause applies the hosted defend-and-indemnify wording to everyone. Confirm whether website visitors should get the narrower wording; see question 29.

9. Governing law and disputes

ATTORNEY ATTORNEY: from the website terms: confirm.

California law governs these terms, without regard to its conflict-of-law rules.
Any dispute goes to the state or federal courts in Orange County, California, and both parties consent to their jurisdiction and to that venue.
You keep any consumer rights that can't be waived.
Before filing a claim, each party will try to resolve the dispute informally by email for at least 30 days.
ATTORNEY: whether to add arbitration, a class action waiver, or a small claims option.

10. Changes to these terms

We may update these terms. We post the new version at fleeceforge.com/legal with a new last-updated date. If you keep using the websites or the service after that, the new terms apply. For a material change, we email account holders at least 30 days before it takes effect ATTORNEY. If you're an account holder and don't agree, you can cancel before the change takes effect, and section 18 applies.

11. Notices and contact

To you: we send notices to the email address on your account. A notice is received when we send it, unless we learn it wasn't delivered. Notices about billing, suspension, and deletion come from setup@fleeceforge.com.
To us: email legal@fleeceforge.com. Formal legal notices go to legal@fleeceforge.com, or by mail to the address below.
Electronic communications: you agree to receive these terms, notices, and receipts electronically.
Business days. A business day is Monday to Friday, in Pacific time, excluding US federal holidays. Every time period in the Terms of Service, the Acceptable Use Policy, and the Data Processing Addendum that is counted in business days uses this definition.

FleeceForge, a sole proprietorship 22365 El Toro Rd, Unit 2223, Lake Forest, CA 92630 Email: legal@fleeceforge.com

12. General

Entire agreement. These terms, the Acceptable Use Policy, the Data Processing Addendum, and the plan you choose are the whole agreement about the websites and the service. If they conflict, the Data Processing Addendum controls for end-customer personal information, and these terms control for everything else.
Assignment. You may not transfer your account or these terms without our written consent. We may transfer them to an affiliate or to a successor to our business, including a successor entity, and we'll tell you if we do. ATTORNEY
Force majeure. Neither party is liable for delays or failures caused by events beyond its reasonable control, including outages at infrastructure providers, except for payment obligations.
Severability and waiver. If a court holds a part of these terms unenforceable, the rest stays in effect. Not enforcing a term isn't a waiver of it.
Relationship. The parties are independent contractors.
Export and sanctions. You may not use the service in violation of US export control or sanctions laws.

Part 2. The hosted service

Part 2 applies to account holders and adds to Part 1.

13. Who the service is for

The service is for small businesses and hobby sellers who run a 3D print shop, a soap or cosmetic making business, or a similar maker business. It gives you quoting, invoices, client records, and a public storefront. For soap and cosmetic makers, it also gives you a lye calculator, recipe formulation tools, IFRA fragrance checks, and, later, label tools, all subject to the soap disclaimer in section 6. Counsel: brings Soapaca into scope; soap safety risk per risk register item 3.
You must be at least 18 years old and able to enter a contract. ATTORNEY
At launch, the service is offered only to customers in the 50 United States and the District of Columbia. You need a billing address there and a payment card issued in the United States, and we check both when you sign up and again at each renewal. If either fails the check at sign-up, we cancel the sign-up and refund any payment in full. If a renewal fails the check, we cancel your subscription and refund that renewal charge in full. US territories, such as Puerto Rico, aren't supported yet; we plan to add them later.
Regions where the service isn't offered. The service isn't offered in the European Union, the United Kingdom, or Canada; sign-up refuses visitors whose connection appears to come from outside the United States, and paid checkout refuses cards not issued in the United States. Don't sign up for or use the service from them. Counsel: is an availability statement plus blocking enough to keep FleeceForge outside GDPR, UK GDPR, and PIPEDA scope, given that US shops may still have end customers there?
You use the service for your business, not for personal, family, or household purposes. ATTORNEY: many hobby sellers are individuals, so consumer protection law may apply anyway; see question 3.
In these terms, your "end customers" are the people who visit your shop's public pages, upload files, request quotes, or receive invoices from you.

14. Your account

One shop per account. Each account has one shop at launch.
Sign-up checks. We confirm your email address and require a verified payment card issued in the United States before we create your shop.
Sign-in. You sign in to the account portal with a single-use link that we email to you. Keep control of your email account, because anyone who can read your email can sign in.
Your shop's logins. You set your shop's admin password through a one-time setup link. You're responsible for the people you give logins to and for everything done under your account and your shop's logins.
Accurate details. Keep your contact email and billing details current. We send notices about billing, suspension, and deletion to your account email, and we rely on it.
Tell us about misuse. If you think someone has accessed your account without permission, email legal@fleeceforge.com right away.

15. Plans and prices

Prices are in US dollars and don't include taxes.

Plan	Price
Hobby	$19 a month
Shop	$35 a month
Studio	$59 a month

Monthly billing only. All plans are billed monthly. Counsel: annual plans dropped, owner decision 2026-11-07.
Plan features such as custom domains, logins, and storage are listed on the pricing page at tools.fleeceforge.com/pricing. The features of your plan are the ones listed there when you sign up. Custom domains aren't available yet. They're coming after launch, on Shop and Studio only, one domain each, and only as a subdomain of a domain you already own, such as shop.example.com. FleeceForge doesn't register domains, and root domains such as example.com aren't supported. Until custom domains are available, the clauses in these terms about custom domains don't apply.
Add-ons (coming soon). The pricing page lists two add-ons as "Coming soon": Performance ($49 a month, for Shop and Studio only, a larger instance and a database ceiling of 1.2 GB instead of 500 MB) and Invoice Email ($5 a month, send quotes and invoices from an address for your shop at fleeceforge.net, with 500 emails a month and up to 100 a day). Neither can be bought yet, prices don't include tax, and a custom domain is a feature of the Shop and Studio plans, not an add-on. Counsel: question 26 also covers unbuilt features.
Hobby shops sleep. A Hobby shop, including one on the free trial, stops after about 15 minutes with no visitors. The next visitor sees a short waking page and starts the shop with a click, and the first page load can take several seconds. Automated requests, such as uptime monitors, crawlers, and scripted pings, don't wake a sleeping shop. Shop and Studio shops are always on from the first payment, which is at sign-up.
No keep-alive monitoring on Hobby. Don't use automated requests to keep a Hobby shop, including one on trial, awake or to work around sleeping. If you need a shop that's always on, choose Shop or Studio. We may rate-limit or block traffic that does this.
Fair use of storage and database size. Each plan includes the storage listed on the pricing page, and your shop's database counts toward it along with uploaded files. Storage is 1 GB on Hobby, 10 GB on Shop, and 50 GB on Studio, and staff logins are none beyond the owner on Hobby, 4 on Shop, and 14 on Studio. Uploads have their own limits: a visitor's quote-request submission, including any file, is limited to 32 MiB, and visitor uploads together are capped at the smaller of 2 GiB or 25% of your plan's storage, after which a request is saved without its file. Only Printpaca's custom estimate form takes a visitor file. Shop images (items, options, and the hero image) are limited to 5 MiB each, in JPEG, PNG, or WebP format. Each plan also has a database ceiling, listed on the pricing page (Hobby 300 MB; Shop and Studio 500 MB; 1.2 GB with the Performance add-on), so that we can back up and restore every shop reliably; we warn you when your database reaches 70% of its ceiling. Quotes are unlimited, but any quote that is no longer open is archived 3 months after it was last changed: an archived quote leaves your active list and stops counting toward your database ceiling, and you can still search, view, restore, or export it. Counsel: quote archiving, owner decision 2026-11-07. If your shop's database nears that size, we email you and work with you to reduce it, for example by exporting and removing old records. If it reaches the limit, we may stop the shop from adding new records until it's reduced or moved to a plan or arrangement that supports it. Counsel: risk register item 13, a database too large to restore leaves the shop down.
Taxes. Prices don't include sales tax. Where sales tax applies, Stripe Tax calculates it and shows it at checkout before you pay, and on each invoice. Stripe Tax is on from launch. ATTORNEY/CPA: whether California SB 122 requires FleeceForge to collect sales tax on subscriptions from January 2027; see question 22. Counsel: annual plans dropped, owner decision 2026-11-07.

16. Free trial

Hobby only. The free trial is offered only on the Hobby plan. It lasts one calendar month: it ends on the same date in the next month, or on that month's last day if the month is shorter. You need a valid payment card issued in the United States to start it.
When you're charged. Your card is charged for Hobby when the trial ends, unless you cancel before then from the billing page. Your subscription then renews as described in section 17.
Shop and Studio have no trial. Shop and Studio are charged for the first month when you sign up.
Upgrading during the trial. If you upgrade from a Hobby trial to Shop or Studio, the trial ends at once and we charge the new plan's first month immediately. Your monthly billing period starts on that day. If you stay on Hobby, your trial end date doesn't change. If the upgrade charge is declined, you stay on the Hobby trial and your trial end date doesn't change, as with any declined upgrade in section 17.
During the trial, your shop can't send email, and it rests when unused like any Hobby shop (section 15).
We email you 7 days and 2 days before the trial ends, once each. Stripe's own trial-ending reminder email is turned off, so only these two reminders are sent.
You can cancel during the trial from the billing page (the Stripe Customer Portal), and you won't be charged. Your shop's data is then handled as described in section 21.
One trial per business. A shop that returns after canceling doesn't get a new trial. We enforce this by checking the email address and the payment card's fingerprint at sign-up. TBD: hosting — confirm the one-trial check is live before launch We keep keyed hashes of the email address and card fingerprint for 3 years from the trial for this check (Privacy Notice, section 8).

17. Billing and renewal

Payment processor. Stripe processes all payments for FleeceForge. We don't receive or store your full card number. Stripe's terms apply to the payment itself.
ATTORNEY: California automatic renewal law — confirm the renewal acknowledgment, confirmation email contents, and online cancellation path.
Automatic renewal. Your subscription renews automatically at the end of each monthly period, at the then-current price for your plan (subject to section 24), until you cancel. We charge the card on file at the start of each period. Counsel: annual plans dropped, owner decision 2026-11-07.
Cancel anytime. You can cancel from the Customer Portal, which you reach from the account portal. Cancellation stops your next charge and takes effect at the end of the current paid period, and your shop keeps running until then. We don't give partial refunds (section 18).
Changing plans. You change plans in your account settings at my.fleeceforge.com, not in the Customer Portal.
Upgrades. An upgrade takes effect immediately, and we charge the prorated price difference for the rest of the current period to your card at once, rather than on your next invoice. If that charge is declined, your plan stays as it was. ATTORNEY: see question 23.
Downgrades. A downgrade takes effect at the end of the current period. If the new plan doesn't include a custom domain, your custom domain keeps working until then and is removed at the end of the period. We email you 7 days before it's removed. Your fleeceforge.net address keeps working.
Downgrades and plan limits. If your shop has more staff logins than the new plan allows, the logins over the limit are blocked 14 days after the downgrade takes effect, so that you have time to choose which to keep. If your stored files exceed the new plan's storage limit, new uploads are refused until you're back under the limit, but your existing files are kept. Counsel: risk register P2, downgrade behavior wasn't disclosed.
Failed payments. If a payment fails, Stripe retries it for about 14 days, and we email you. Your shop keeps running during the retries. What happens after that is in section 20.

18. Refunds

ATTORNEY: the owner's recommended policy follows; counsel to confirm.

No partial refunds: we don't give partial refunds, for example for the unused part of a month. Canceling stops your next charge, and your shop keeps running until the end of the period you paid for. ATTORNEY: whether to name downgrades and the immediate upgrade charge explicitly; see question 23. Counsel: annual plans dropped, owner decision 2026-11-07.
Trial: you aren't charged during the trial, so there's nothing to refund.
Our mistakes: if we charge you in error, we refund the charge.
Eligibility checks: if your sign-up or a renewal fails the country check in section 13, we refund that charge in full.
Exceptions to "no partial refunds": (a) if we shut the service down, we refund the unused part of your current billing period, pro rated (section 21); (b) if we remove a significant feature and you cancel because of it, we refund prepaid fees for the rest of the period (section 24); (c) if you object to a new subprocessor and we can't address it, you may cancel and receive a pro-rated refund (Data Processing Addendum, section 7); and (d) if a renewal fails the country check, we refund that renewal charge in full (section 13).
Required by law: nothing here limits a refund that the law requires.
Chargebacks: please email us before you dispute a charge with your bank. A dispute suspends your shop at once (section 20).

19. Your data

You own your data. "Your data" means the content and records you and your end customers put into your shop: client records, quotes, invoices, uploaded files, settings, and storefront content. You keep all rights to it.
When we access your data. FleeceForge can technically access your shop's data: it holds the credentials for the storage buckets that hold each shop's backups, so it can restore a shop's database and files and read them, and its operator tools can reset a shop owner's password. We use that access only to provide support you ask for, to restore backups, to keep the service secure and working, to investigate abuse under the Acceptable Use Policy, or when the law requires it. Counsel: confirm wording; see question 27.
Our license to it. You give us permission to host, copy, process, transmit, back up, and display your data only as needed to run, secure, and support the service for you, and as required by law. We never sell your data, and we never use it to train AI models. We don't use it for advertising either. FleeceForge has no AI features. ATTORNEY: placement; see question 24.
Your end customers' data. For personal information about your end customers, you're the business that decides how it's used, and we process it on your behalf under the Data Processing Addendum. You're responsible for giving your end customers a privacy notice, for having a lawful reason to collect their information, and for answering their requests.
Your responsibility for content. You're responsible for your data and for what your end customers upload to your shop, including making sure that you have the rights to it and that it follows the Acceptable Use Policy.
Your records and retention obligations. The law may require you to keep business records, such as invoices, payment records, and tax records, for several years. You're responsible for meeting those requirements, including by exporting and keeping your own copies. The service isn't an archive: we delete your data as described in section 21, including when an account is canceled for non-payment, and we don't keep it for you after that. Counsel: risk register item 7, a shop deleted at day 58 may lose records it must keep for 3-7 years; see question 20.
Export, free on every plan. You can export your shop's data on every plan, at no charge. The full export is a ZIP file with your shop's records (clients, invoices, payments, quotes, orders, storefront items, and categories), settings, and uploaded files. The shop's owner starts it from the account portal, or, while your shop is suspended or after your plan ends, emails contact@fleeceforge.com from your account's email address. We email a download link that works once, within 15 minutes; you can ask for a new link, which serves the same file. A new full export is available every 3 days. While your shop is running, the shop's owner can also download the shop's records and settings directly from Settings in the shop's admin app at any time, as JSON or as CSV files; that download doesn't include uploaded files and isn't limited. Staff can't download exports. You have 30 days after your plan ends to request one (section 21). Exports never include passwords. Archived quotes (section 15) have their own export, from the archived quotes list. An export can't be imported back into the service, or into the public Printpaca release. TBD: hosting — the full export with uploaded files (plan 8 with the export-link amendments) ships before launch Counsel: risk register item 8.
Backups. We back up each shop's database by continuous replication, with a snapshot every 24 hours, kept for 7 days and stored separately from your running shop, and we can restore it to any point in the last 7 days (owner decision 2026-11-07). There's no self-service restore and no guaranteed recovery time. Backups are stored in a bucket in FleeceForge's Cloudflare account, and FleeceForge doesn't add its own encryption to them (Cloudflare states that all objects stored in R2, including their metadata, are encrypted at rest, and that is the encryption that applies). Deleting a backup object is irreversible, but we don't promise secure erasure beyond that. We don't keep a second copy yet. Files you delete while your account is active can stay in storage trash for up to 30 days. Backups protect the service against failure; they aren't a substitute for your own exports, and we don't promise that any particular backup or restore point exists. Backups and restore on request are included on every plan; they aren't a feature of any particular plan. Counsel: risk register item 9, the earlier "daily snapshots" promise isn't yet backed by verified retention.

20. Suspension

We suspend your shop when your account isn't in good standing. While your shop is suspended, its pages show a generic "unavailable" page that doesn't give the reason, and your data is kept. You can still sign in to the account portal to pay, and you can get an export by emailing contact@fleeceforge.com (section 19). Counsel: risk register item 8, a suspended shop can't use the in-app export today.

Non-payment. If a payment still fails after Stripe's retries (about 14 days), we suspend your shop and email you. If you pay, we restart your shop. If you don't pay within 14 days of the suspension, we cancel your subscription, and section 21 applies.
Payment disputes. If you open a dispute or chargeback on a FleeceForge charge, we suspend your shop at once and review the dispute. ATTORNEY: confirm that immediate suspension on any dispute, including one opened in good faith, is acceptable, and how a resolved dispute is handled.
Acceptable use. We may suspend your shop, remove content, or limit features as described in the Acceptable Use Policy, including without prior notice when there's a legal requirement or a risk to the service, to other shops, or to anyone else.
Security. We may suspend your shop or your logins if we reasonably believe your account is compromised.
Cloudflare action. We may remove, restrict, or suspend content or your shop, without prior notice where necessary, when Cloudflare requires it, or when Cloudflare itself removes, blocks, or restricts content, your shop, or FleeceForge's account. We tell you what we did unless the law or Cloudflare forbids it. ATTORNEY: Cloudflare's published pages don't say it forbids us from telling you, and its abuse approach says it generally notifies the website operator; confirm the "or Cloudflare forbids it" qualifier.

21. Cancellation, termination, and deletion

You can cancel at any time, as described in section 17.
We can terminate your account for non-payment as described in section 20, for a serious or repeated breach of these terms or the Acceptable Use Policy, or if the law requires it. We may also stop offering the service entirely. If we do, we give you at least 60 days' notice by email and an export as described in section 19, and we refund the unused part of your current billing period, pro rated. The public Printpaca release is open source and stays available, but an export can't be imported into it. ATTORNEY: see questions 7 and 24.
After cancellation or termination, your shop stops. We keep your data for 30 days so that you can export it, and then we delete it. We email you 7 days and 2 days before deletion, and those emails remind you to export any records you're required to keep (section 19). Counsel: risk register P2 notice timing (hosting sends at 7 and 2 days) and item 7 retention reminder.
What's deleted: your shop's database, uploaded files, settings, custom domain, and shop credentials. Copies in our backups are deleted as the backups expire, within 7 days after deletion. Counsel: risk register item 9, backup window unverified.
What we keep: billing and tax records, for as long as the law requires ATTORNEY: proposed 7 years, as in the Privacy Notice; and a minimal record that the shop existed and was deleted, as the Privacy Notice describes: two years after deletion, the shop name and your email address are replaced with placeholders and the shop's audit-log entries are deleted, except the deletion entry and any payment-dispute records. We keep your email address while your account still has another shop or a sign-up in progress, and if your account was blocked for fraud or chargebacks, so that the block keeps working. TBD: hosting — deploy before launch Your subdomain stays reserved so an old link never points to a different shop. A custom hostname you used stays reserved for 90 days after you leave, so that nobody else can use it right away.
On payment timelines: a shop whose payments fail is deleted about 58 days after the first failed charge: about 14 days of retries, 14 days suspended, and 30 days of export-only retention.
Deletion is permanent. After the 30-day export window, we can't restore your data.
Surviving terms: sections 4 to 9, 11, and 12 in Part 1, and sections 18, 19 (ownership and responsibility), 21, and 25 in Part 2, survive the end of these terms.

22. Acceptable use

You agree to follow the Acceptable Use Policy, and to make sure that your staff and end customers follow it when they use your shop. It's part of these terms.

FleeceForge runs on Cloudflare. You're responsible for your content and for your end customers' use of your shop. Under Cloudflare's terms, FleeceForge is solely responsible to Cloudflare for the acts of its end users, and must not allow third parties to use Cloudflare's services for prohibited activities such as malicious code, phishing, or spam. So don't do anything through your shop that would put FleeceForge in breach of the Cloudflare Self-Serve Subscription Agreement, the Cloudflare Service-Specific Terms (including the Developer Platform terms that cover Workers and R2), or Cloudflare's abuse approach. If Cloudflare's rules and ours differ, follow the stricter rule. ATTORNEY: Cloudflare's terms don't require us to bind end users to them by contract; "follow the stricter rule" is our own choice. Confirm the wording.

Custom domains are a plan feature. If your plan doesn't include one, don't put your own domain in front of your shop, for example with a reverse proxy, a masking or forwarding service, or a frame, so that your shop appears under an address other than its FleeceForge address. A plain redirect to your FleeceForge address is fine. We may suspend a shop that does this until it stops, or ask you to move to a plan that includes custom domains. Counsel: owner decision 2026-11-08; confirm wording and the suspension remedy.

23. Availability and support

Availability target. We aim for 99.5% monthly availability for shops that run all the time. This is a best-effort target, not a guarantee. We don't offer service credits or refunds when we miss it. The startup delay of a sleeping shop isn't counted as downtime.
Outages. When monitoring detects an outage, we aim to start working on it within 4 hours. This is best effort.
Status page. Current status and incident notices are at status.fleeceforge.com.
Support is by email at contact@fleeceforge.com. We aim to reply within 3 business days on Hobby and 2 business days on Shop and Studio (owner decision 2026-11-07). No plan includes a setup call. Business days are defined in section 11. Any community chat or forum has no response promise.
Maintenance. We update the service regularly. Most updates cause no downtime; some restart your shop briefly.
Third parties. The service runs on third-party infrastructure, mainly Cloudflare. Outages at those providers can affect your shop, and we can't control them. Cloudflare outages, limits, and actions (including those in section 20) are outside our control, don't count against the availability target, and are subject to section 7. ATTORNEY: confirm the exclusion in section 7 for Cloudflare outages and actions; see the marker there.

24. Changes to the service and to prices

The service changes. We may add, change, or remove features. If we remove a feature that's a significant part of your plan, we tell you at least 30 days ahead ATTORNEY, and if you cancel because of it, we refund any prepaid fees for the rest of the period.
Price changes. We may change plan prices. We email you at least 30 days before a new price applies to you ATTORNEY. A new price starts at your next renewal after the notice period, and you can cancel before then.
Changes to these terms are in section 10.

25. Third-party services

Your email relay. If you connect your own SMTP relay, your shop sends email through that provider under its terms. We store the relay password encrypted. We aren't responsible for that provider's service or for delivery of mail sent through it.
Your payment processors. Your end customers pay you through your own payment processors, such as a payment link on your invoices. FleeceForge doesn't process, hold, or transmit payments on your behalf, and isn't a party to sales between you and your end customers.
Your domain. If you connect a custom domain, you're responsible for your domain registration and DNS.
Other services. Links to or integrations with other services are governed by those services' terms (see also section 2).

FleeceForge acceptable use policy

Last updated November 11, 2026

How the documents fit together

FleeceForge has four legal documents, all published together at fleeceforge.com/legal: the Terms of Service, the Privacy Notice, this Acceptable Use Policy, and the Data Processing Addendum.

Website visitors (fleeceforge.com, tools.fleeceforge.com, and status.fleeceforge.com), and waitlist and tool-request senders: Part 1 of the Terms of Service and the Privacy Notice. This policy doesn't apply to them, except that anyone may report a shop under it, and the scraping and abuse rules in section 3 also apply to visitors through section 2 of the Terms of Service.

Shop owners and their staff: all four. This policy is part of the Terms of Service.

Shop customers (people who use a shop at <slug>.fleeceforge.net): this policy applies to their use of the shop. FleeceForge processes their information for the shop under the Data Processing Addendum, and the shop's own privacy notice governs it.

Never Idle is a separate site with its own terms and privacy policy, and these documents don't cover it.

Effective date: TBD · Version: 0.3 (draft, updated 2026-11-10)

This policy is part of the FleeceForge terms of service. It applies to you, the shop owner, to your staff, and to anyone who uses your shop, including your end customers who upload files or request quotes. You're responsible for making sure your shop is used in line with it.

FleeceForge™, a sole proprietorship ATTORNEY: confirm the documents can name the business by its trade name alone, without the owner's legal name. is a sole proprietorship doing business as FleeceForge, with its mailing address at 22365 El Toro Rd, Unit 2223, Lake Forest, CA 92630 ("FleeceForge," "we," or "us"). Report a violation to legal@fleeceforge.com.

1. What FleeceForge is for

FleeceForge hosts quoting, invoicing, client records, and storefronts for small maker businesses, such as 3D print shops (Printpaca) and soap and cosmetic makers (Soapaca, which adds a lye calculator, recipe formulation tools, IFRA fragrance checks, and, later, label tools). Use it for that. The soap tools are aids only, not professional, medical, safety, or regulatory advice; the lye calculator is for sodium hydroxide (NaOH) bar soap only, and you must verify every amount, limit, and label independently, as section 6 of the terms of service explains. Counsel: brings Soapaca into scope; disclaimer matches ToS §6, risk register item 3. Everything below is about keeping the platform lawful, safe, and fair to the other shops that share it.

2. Prohibited goods and content

Don't use FleeceForge to offer, quote, make, sell, store, or distribute:

Illegal goods and services: anything that's illegal where you, your end customer, or the item will be, including controlled substances and the equipment specifically designed to use or make them, counterfeit goods, stolen goods, and items made to evade the law.
Firearms, gun parts, and magazines: firearms, frames, receivers, firearm parts, magazines, silencers or suppressors, conversion devices such as auto sears, and digital files for making any of them. This ban applies everywhere, whether or not the item is lawful where you are.
Undetectable or untraceable firearms, including 3D-printed guns without serial numbers where serialization is required, and anything designed to get a weapon past security screening.
Other dangerous items: explosives, destructive devices, and items designed to cause serious harm.
Infringing content: files, designs, images, product listings, or text that infringe someone's copyright, trademark, patent, design right, or other rights. This includes printing and selling licensed characters, logos, or designs without permission, and files whose license forbids commercial use when you sell prints from them.
Counterfeit and impersonation: branding that suggests you're another business, or that FleeceForge endorses you.
Harmful content: child sexual abuse material (which we report to the authorities), content that sexualizes minors, threats, harassment, content that promotes violence or terrorism, and personal information about others posted without their consent.
Hateful content: content that attacks or demeans people based on race, ethnicity, religion, disability, sex, sexual orientation, gender identity, or national origin, including in shop names, shop addresses, and storefront text. Counsel
Sexually explicit content on public storefront pages. ATTORNEY: whether to allow adult products behind an age gate.
Deceptive practices: fraud, scams, fake reviews, or false claims about what you sell.

3. Prohibited uses of the platform

FleeceForge runs on Cloudflare. Under Cloudflare's terms, FleeceForge is solely responsible to Cloudflare for the acts of its end users, and must not allow third parties to use Cloudflare's services for prohibited activities such as malicious code, phishing, or spam. You're responsible for your content and your shop's use, so don't do anything through your shop that would put FleeceForge in breach of the Cloudflare Self-Serve Subscription Agreement, the Cloudflare Service-Specific Terms (including the Developer Platform terms that cover Workers and R2), or Cloudflare's abuse approach, as section 22 of the terms of service explains. Cloudflare may block or remove content that it judges illegal or harmful, and storing such content may result in suspension or termination of Cloudflare services. We may act on that as described in section 7. ATTORNEY: Cloudflare's terms don't require us to bind end users to them by contract; confirm the flow-down wording.

Malware: don't upload, host, or distribute viruses, malware, ransomware, or files designed to exploit software, including in 3D model files, images, or attachments. Don't use your shop to host files for anyone outside your business.
Spam through email: if you connect an SMTP relay, send email only to people who have a business relationship with you or have asked to hear from you, such as quote confirmations and invoices. Don't send bulk marketing, unsolicited messages, or phishing through your shop. Follow the CAN-SPAM Act and your relay provider's terms. Don't send email that pretends to come from FleeceForge or from another shop.
Abuse of public quote and upload endpoints: don't flood any shop's public quote, upload, or contact forms; submit automated or fake quote requests; upload files to use a shop as free storage; or use the forms to send spam or harass a shop. This applies to everyone, not only shop owners.
Scraping: don't scrape, crawl, or harvest data from other shops or from FleeceForge's websites, and don't collect other people's personal information from the platform. You may export your own shop's data with the built-in export, and search engines may index public storefront pages.
Breaking isolation: don't try to access another shop's container, database, files, or account; escape your shop's container; read data you aren't authorized to see; or set cookies or run code that affects other shops.
Attacking the service: don't probe, scan, or test the service's security except as allowed in section 5; don't run denial-of-service attacks or load tests; don't bypass rate limits, bot checks, plan limits, or billing; and don't interfere with the service's operation.
Reselling and misuse of accounts: don't resell, sublicense, or rent the service, share one account among unrelated businesses, create accounts to get repeat free trials, sign up with false information, or get around the sign-up eligibility check, for example with a billing address or card from outside the 50 United States and the District of Columbia. ATTORNEY: see question 13.
Excessive use: stay within your plan's limits, which are listed on the pricing page and described in the Terms of Service (Part 2, plan limits), and don't use compute or bandwidth in a way that degrades the service for other shops. We'll contact you before acting on usage that's high but lawful, unless it's harming other shops right now.
Unlawful use: don't use the service to break any law, including privacy, consumer protection, export control, and sanctions laws, or to collect information from end customers without the notice and consent the law requires.

4. Your responsibilities for your shop

Review what you agree to make. FleeceForge doesn't screen quote requests or uploaded files in advance and doesn't decide whether an item is lawful for you to make. ATTORNEY
Remove content from your shop when you learn it breaks this policy.
Keep your staff logins secure, and remove access when someone leaves.
Respond to our emails about this policy within the time we ask.

5. Security research

You may test the security of your own shop, using your own account, as long as you don't affect other shops, don't access data that isn't yours, and don't run denial-of-service or automated load tests.
Report vulnerabilities privately to legal@fleeceforge.com, and give us reasonable time to fix them before you disclose them. Our websites publish this address in /.well-known/security.txt.
We don't run a paid bug bounty.
We won't take action against good-faith research that follows this section. ATTORNEY: whether a safe-harbor statement is advisable.

6. Copyright and other rights complaints

FleeceForge has registered its designated agent with the US Copyright Office's DMCA Designated Agent Directory (registration DMCA-1085975). Our designated agent to receive notices of claimed copyright infringement is:

Name: Copyright Agent, FleeceForge
Address: 22365 El Toro Rd, Unit 2223, Lake Forest, CA 92630
Phone: 970-387-8681
Email: legal@fleeceforge.com

If you believe content in a FleeceForge-hosted shop infringes your copyright, send a notice to our designated copyright agent at legal@fleeceforge.com with:

your contact details and signature;
what work you believe is infringed;
where the content is (the shop address and page or file);
a statement that you believe in good faith that the use isn't authorized; and
a statement, under penalty of perjury, that the notice is accurate and that you're the rights holder or authorized to act for them.

We'll forward the notice to the shop's owner, including your name and contact details, as the law expects, and we may remove or disable the content.

A shop owner may send a counter-notice to the same address. It must include:

the shop owner's signature;
a description of the content and where it appeared before it was disabled;
a statement, under penalty of perjury, that the shop owner believes in good faith that the content was removed or disabled by mistake or misidentification;
the shop owner's name, address, and telephone number; and
a statement that the shop owner consents to the jurisdiction of the federal court for their address (or, outside the United States, any judicial district where FleeceForge can be found), and will accept service of process from the person who sent the notice.

We send a complete counter-notice to the person who sent the notice. Unless that person tells us within 10 business days after we receive the counter-notice that they have filed a court action, we may restore the content between 10 and 14 business days after we receive it. We terminate the accounts of repeat infringers in appropriate circumstances. ATTORNEY: confirm that this meets 17 U.S.C. §512, and define "repeat infringer."

For trademark and other complaints, email legal@fleeceforge.com with the same kind of detail. We may forward the complaint to the shop's owner, including your name and contact details.

7. Enforcement

We investigate reports and violations we find. To do that, we may look at the reported content and related records in your shop, as the Data Processing Addendum (section 5) describes. Counsel: confirm wording. What we do depends on how serious the violation is, whether it's repeated, and the risk to others. We usually follow these steps, in order:

Notice. We email you about the problem and ask you to fix it within a set time, usually 3 business days (business days are defined in section 11 of the Terms of Service).
Content removal or feature limits. We remove or disable the specific content, file, or listing, or turn off a feature such as your email relay, and tell you what we did.
Suspension. We suspend your shop. Your data is kept, and you can still get a free export by emailing contact@fleeceforge.com.
Termination. We end your account under the terms of service. You get the same 30-day export window as any canceled account, unless the law, a court order, or the nature of the content prevents it (for example, we won't return unlawful material). ATTORNEY

We may skip steps and act at once, without notice, when:

Cloudflare requires it, or Cloudflare itself blocks, removes, or restricts content, your shop, or our account ATTORNEY: confirm the Cloudflare flow-down wording; see section 3.
the law requires it, or a court or authority orders it;
the content is clearly illegal, such as child sexual abuse material or firearm files;
there's an active attack, malware, or spam campaign; or
the violation risks harm to other shops, to end customers, to the platform, or to anyone else.

We may preserve and disclose information to law enforcement when the law requires it or when we believe in good faith that it's needed to prevent serious harm. Unless the law forbids it, we tell you what we did and why.

We don't refund fees for a suspension or termination caused by a violation of this policy. This matches the terms' general rule of no partial refunds (terms section 18). ATTORNEY: see question 12.

8. Appeals

If you think we got it wrong, email legal@fleeceforge.com within 14 days with your explanation. The owner reviews every appeal personally and replies within 5 business days (as defined in section 11 of the Terms of Service).

9. Changes

We may update this policy. For a material change, we email you at least 30 days before it takes effect, unless the change is needed to comply with the law or address a new kind of abuse, in which case it can take effect sooner. ATTORNEY

FleeceForge data processing addendum

Last updated November 11, 2026

How the documents fit together

FleeceForge has four legal documents, all published together at fleeceforge.com/legal: the Terms of Service, the Privacy Notice, the Acceptable Use Policy, and this Data Processing Addendum.

Website visitors, and waitlist and tool-request senders: Part 1 of the Terms of Service and the Privacy Notice. This addendum doesn't apply to them.

Shop owners: all four. This addendum is part of the Terms of Service and covers the personal information FleeceForge processes for the shop.

Shop customers (people who use a shop at <slug>.fleeceforge.net): this addendum governs how FleeceForge processes their information for the shop. The shop's own privacy notice governs the shop's use of it, and the Acceptable Use Policy applies to their use of the shop.

Never Idle is a separate site with its own terms and privacy policy, and these documents don't cover it.

Effective date: TBD · Version: 0.3 (draft, updated 2026-11-10)

This Data Processing Addendum ("DPA") is part of the FleeceForge terms of service between you, the shop owner ("you"), and FleeceForge™, a sole proprietorship ATTORNEY: confirm the documents can name the business by its trade name alone, without the owner's legal name., with its mailing address at 22365 El Toro Rd, Unit 2223, Lake Forest, CA 92630 ("FleeceForge," "we," or "us"). It applies automatically when you accept the terms. ATTORNEY: whether incorporation by reference is enough, or whether shops that need a signed copy should be able to request one.

It covers the personal information that FleeceForge processes on your behalf when it hosts your shop. It doesn't cover your account and billing information, which FleeceForge controls under its Privacy Notice.

1. Definitions

Shop personal data: personal information about your end customers, your staff, and anyone else that you or your end customers put into your shop, and that FleeceForge processes to provide the service. Annex 1 lists the categories.
End customers: people who use your shop's public pages, upload files, request quotes, or receive invoices from you.
Subprocessor: a third party that FleeceForge engages to process shop personal data.
Security incident: a breach of security that leads to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to shop personal data.
Data protection law: every privacy and data protection law that applies to processing shop personal data, including the California Consumer Privacy Act as amended by the CPRA ("CCPA") where it applies. ATTORNEY: whether to name other state laws, or GDPR, explicitly.

Terms such as "business," "service provider," "controller," and "processor" have the meanings given in data protection law.

2. Roles and scope

You're the business (or controller) for shop personal data. You decide what to collect from your end customers and why.
FleeceForge is your service provider (or processor). It processes shop personal data only to provide the service to you.
FleeceForge is a separate business (or controller) for your account and billing information. This DPA doesn't cover that information.
Your responsibilities: you're responsible for having a lawful basis to collect shop personal data, for giving your end customers a privacy notice, for your instructions being lawful, and for what you and your end customers upload. You don't put sensitive information into the service unless the service is designed for it; it isn't designed for health, financial account, or government ID data.
Free-text fields and public forms. Notes, messages, and uploaded files can contain whatever the person entering them chooses, and anyone can submit your public forms with another person's name and email address. FleeceForge doesn't screen this content or verify who submitted it. You're responsible for how you handle it, including deleting sensitive or wrongly submitted information when you find it. Counsel: risk register lawyer question 5, sensitive data in free text and third-party submissions; see question 13.

3. Instructions

FleeceForge processes shop personal data only on your documented instructions. The terms of service, this DPA, and your use and configuration of the service (for example, the settings you choose, the emails you send, and the exports you request) are your complete instructions.
FleeceForge may process shop personal data outside your instructions only when the law requires it. If so, FleeceForge tells you first, unless the law forbids it.
FleeceForge tells you if it believes an instruction breaks data protection law, and may decline to follow it.

4. Service provider restrictions

As required of a service provider under the CCPA, FleeceForge won't:

sell or share shop personal data, as the CCPA defines those terms, and FleeceForge never sells shop data in any other sense either;
keep, use, or disclose it for any purpose other than providing the service to you, including any commercial purpose of its own;
keep, use, or disclose it outside the direct business relationship between you and FleeceForge;
combine it with personal information that FleeceForge receives from or on behalf of anyone else, or collects from its own interactions with a person, except as the CCPA permits; or
use it to train AI models. FleeceForge has no AI features. ATTORNEY: placement; see question 15.

FleeceForge will comply with the CCPA where it applies, provide the same level of privacy protection the CCPA requires of you, and tell you if it can no longer meet these obligations. You may take reasonable steps to stop and remediate unauthorized use of shop personal data. FleeceForge certifies that it understands these restrictions.

5. Confidentiality

FleeceForge is operated by one person, its owner. Only the owner has access to shop personal data, and only as needed to run, secure, support, and restore the service.
If FleeceForge gives anyone else access in the future, such as a contractor or employee, it will first bind them to confidentiality and limit their access to what their work needs.
What access exists. FleeceForge can technically access your shop's data. Each shop's database is replicated to a storage bucket in FleeceForge's Cloudflare account, and FleeceForge holds the credentials for those buckets, so the owner can restore a shop's database and files from backup and read them. FleeceForge's operator tools can also stop, start, suspend, and restore a shop, replace its database from a backup, and reset the shop owner's password (which signs the owner out and opens setup again). The status and list tools show shop details such as the shop name, plan, and state, but not shop records. Cloudflare, as our hosting provider, can also reach the infrastructure that holds your data under its own terms. Only the owner of FleeceForge has this access. We use it only to provide support you ask for, to restore backups, to keep the service secure and working (including fixing a problem), to investigate a security incident or a suspected violation of the Acceptable Use Policy, or when the law requires it. We don't browse shop data for any other purpose. Counsel: confirm wording; see question 17.

6. Security measures

FleeceForge maintains the technical and organizational measures in Annex 2 and may update them, as long as an update doesn't materially reduce the overall protection of shop personal data.

7. Subprocessors

You authorize FleeceForge to use the subprocessors listed in Annex 3.
FleeceForge binds each subprocessor by written contract to data protection terms that protect shop personal data at least as well as this DPA does, to the extent the subprocessor's standard terms allow. For Cloudflare, that written contract is Cloudflare's Customer Data Processing Addendum, which Cloudflare incorporates into its Self-Serve Subscription Agreement (section 6.1) and which requires Cloudflare to bind its own sub-processors. ATTORNEY: confirm this against clause 4.4 of Cloudflare's DPA; large providers offer only their standard DPA. FleeceForge remains responsible to you for its subprocessors' work.
Notice of changes. FleeceForge emails you at least 30 days before it adds or replaces a subprocessor that processes shop personal data ATTORNEY, and keeps the current list in the provider table of the Privacy Notice, at fleeceforge.com/legal#privacy-6-who-we-share-it-with.
Objection. You may object on reasonable data protection grounds within that 30-day period by emailing legal@fleeceforge.com. If FleeceForge can't address the objection, you may cancel the service before the change takes effect and receive a pro-rated refund of any prepaid fees for the rest of the period. ATTORNEY
Emergencies. If FleeceForge has to replace a subprocessor at once for security or continuity reasons, it tells you as soon as it can, and the objection right still applies.

8. Security incidents

FleeceForge notifies you without undue delay, and in any case within 72 hours, after it becomes aware of a security incident affecting your shop personal data. ATTORNEY: the owner proposed 72 hours; see question 1.
The notice goes to your account email and describes, as far as FleeceForge knows at the time: what happened, the categories and approximate number of people and records involved, the likely consequences, and what FleeceForge has done or proposes to do. FleeceForge sends more information as it learns it.
FleeceForge takes reasonable steps to contain the incident, investigate it, and reduce its effects, and keeps a record of it.
FleeceForge helps you meet your own obligations to notify regulators and end customers, but you decide whether to notify them, and you send any notice to your end customers, unless the law requires FleeceForge to.
A notice isn't an admission of fault.
Unsuccessful attempts that don't compromise shop personal data, such as blocked log-in attempts, scans, or denial-of-service attacks, aren't security incidents.

9. Assistance

Requests from end customers. If an end customer asks FleeceForge to see, correct, or delete their information, FleeceForge forwards the request to you without undue delay and doesn't answer it except to say it was forwarded.
Tools. You can view, correct, export, and delete shop personal data yourself through your shop's admin pages. While your shop is running, the shop's owner can download the shop's records and settings from Settings in the admin app at any time, as JSON or as CSV files, without uploaded files; archived quotes have their own export. The owner can also start a full export, with the shop's records, settings, and uploaded files, from the account portal, or by emailing contact@fleeceforge.com from your account's email address while your shop is suspended or within 30 days after your plan ends. FleeceForge emails a download link that works once, within 15 minutes; a new link serves the same file, and a new full export is available every 3 days. TBD: hosting — the full export with uploaded files (plan 8 with the export-link amendments) ships before launch If you can't do something with these tools, FleeceForge helps you within a reasonable time. Counsel: risk register item 8, the portal export doesn't exist yet.
Erasure and legal retention. Your shop's "forget customer" action deletes an end customer's client record (including their phone number, which lives only on the client record), quotes and archived quotes, quote requests matched to the customer's email address (you confirm each) with their uploaded files, draft invoices that have no credit notes, and email reply-log entries. On invoices you've already issued, it keeps the invoice, its lines and payments, the amounts, the customer's name, and the state and country used for tax reporting, and it clears the customer's email address, billing address, and shipping address and blanks the send-log recipient. It doesn't change free text you typed into invoice notes, credit note notes, or line descriptions; the preview says so. Deleted content is overwritten in the live database file, but a copy can remain in the write-ahead log until the next checkpoint and in backups for up to 7 days. Deleted uploaded files can stay in storage trash for up to 30 days. You decide whether the law requires you to keep a record, and for how long. Where it does, you may keep that record despite an erasure request, and FleeceForge keeps it on your instruction under this DPA until you delete it or the service ends (section 10). Counsel: risk register item 10 and lawyer question 3, erasure versus invoice retention; see question 14.
Other assistance. FleeceForge gives you reasonable information and help with data protection assessments and with questions from regulators about the service, to the extent you can't get the information yourself. FleeceForge may charge a reasonable fee for help beyond what the service normally includes. ATTORNEY
Legal requests. If a government or court asks FleeceForge for shop personal data, FleeceForge redirects the request to you where it can, tells you before disclosing unless the law forbids it, and discloses only what the law requires.

10. Deletion or return at the end of the service

Return. You can export your shop's data for free on every plan, as described in section 9 and section 19 of the terms: a ZIP file with your shop's records, settings, and uploaded files, sent as a download link, or a direct JSON or CSV download of records and settings without uploaded files. Archived quotes export separately. You have 30 days after your plan ends to request an export. An export can't be imported back into the service. ATTORNEY: whether the full export (with uploaded files) and the direct download (without them) meet the return obligation; see question 16. Counsel: risk register item 8, the portal export doesn't exist yet.
Your retention obligations. You're responsible for keeping any records the law requires you to keep, such as invoices, by exporting them before deletion. FleeceForge doesn't keep shop personal data for you after the deletion below. Counsel: risk register item 7, shops may have to keep invoices 3-7 years.
Deletion. After your subscription is canceled or terminated, FleeceForge keeps shop personal data for 30 days so that you can export it, then deletes it from the live service. FleeceForge emails you 7 days and 2 days before deletion. Counsel: risk register P2, aligned with the notices hosting sends.
If FleeceForge shuts down. FleeceForge gives you at least 60 days' notice and an export as described in section 19 of the terms of service before it stops the service and deletes shop personal data, and refunds the unused part of your current billing period, pro rated. ATTORNEY: see questions 15 and 16.
Backups. Copies in backups and replicas are deleted as they expire, within 7 days after deletion. Counsel: risk register item 9, backup window unverified. Until then they stay protected by this DPA and aren't used except to restore the service.
Legal holds. FleeceForge may keep shop personal data longer only if the law requires it, and then only for that purpose, under this DPA.
Confirmation. On request, FleeceForge confirms deletion in writing.

11. Audits

FleeceForge answers one written security and privacy questionnaire from you a year, within 30 days, at no charge. ATTORNEY
FleeceForge also answers a questionnaire after a security incident affecting your shop personal data, or when a regulator requires it.
On request, FleeceForge shares the security reports or certifications its main subprocessors publish, where their terms allow.
FleeceForge doesn't offer on-site audits or penetration tests of the shared platform. If the law requires an audit that a questionnaire can't satisfy, the parties will agree on its scope, timing, and cost in advance, and it won't give access to other shops' data. ATTORNEY
Any information FleeceForge provides under this section is confidential.

12. Liability, term, and order of precedence

This DPA lasts as long as FleeceForge processes shop personal data for you, including during the export window and backup expiry after your subscription ends.
Each party's liability under this DPA is subject to the limitation of liability in the terms of service (section 7). ATTORNEY: whether data-protection breaches need a separate or higher cap.
If this DPA conflicts with the terms of service about shop personal data, this DPA controls.
International transfers. At launch, FleeceForge serves only shops in the 50 United States and the District of Columbia. If FleeceForge later accepts shops outside the United States, or if data protection law requires it for a shop's end customers, FleeceForge will add the necessary transfer terms, such as the EU Standard Contractual Clauses. ATTORNEY: the SaaS plan recommends including the Standard Contractual Clauses from day one, because a US shop may have EU end customers.

Annex 1: Processing details

Item	Details
Parties	You, the shop owner, as business or controller. FleeceForge as service provider or processor.
Subject matter	Hosting and operating your shop on the FleeceForge service (hosted Printpaca and Soapaca: quoting, invoices, client records, storefront, and soap formulation).
Duration	The term of your subscription, plus the 30-day export window, plus backup expiry of 7 days.
Nature of processing	Storage, hosting, replication, backup, restore, transmission, display, export, and deletion. Automated processing that the shop configures, such as quote calculation.
Purpose	To provide, secure, support, and restore the service for you.
Data subjects	Your end customers and prospective customers; your staff who have shop logins; and any other people whose information you or your end customers enter.
Categories of personal data	Contact details (for each customer: name, email address, phone number, billing address, shipping address, state or province, country, and notes); the name, email address, and note a customer types into an order or quote-request form; quote requests, order details, and invoices; payment status that you record (FleeceForge doesn't process end-customer card details); files that end customers upload, such as 3D models (Printpaca only), and any personal information in them; messages; staff user names, email addresses, and password hashes; and technical data such as IP addresses in request handling, security checks, and rate limits (kept in request logs and memory, not in the shop's database).
Sensitive data	None intended. The service isn't designed for sensitive personal information, but free-text fields and uploads may contain it if someone enters it (section 2). Counsel: risk register lawyer question 5.
Frequency	Continuous, while your shop runs.
Location	Cloudflare R2 with a United States location hint. Shop containers run in Cloudflare's network wherever Cloudflare places them, which can't be pinned to a country.
Retention	Until you delete it, or until 30 days after your subscription ends, plus backup expiry (section 10). Files uploaded with a quote request are deleted automatically after you finalize the request: G-code files after 30 days and 3D model files after 180 days. Quote requests are kept until you delete them, or, if you turn on automatic deletion of closed requests, the number of days after closing that you choose (7 to 3,650). Deleted files can stay in storage trash for 30 days. Counsel: risk register P2 upload retention and item 20 deleted-data windows.

Annex 2: Security measures

Area	Measure
Isolation	Each shop runs in its own container, with its own SQLite database and its own R2 storage bucket. A per-shop Durable Object ensures only one container writes to a shop's database. The router blocks one shop from setting cookies for other shops.
Encryption in transit	TLS on all public traffic, including custom domains once they're available after launch.
Encryption at rest	FleeceForge doesn't add its own encryption to shop databases or backups; they rely on the encryption at rest that Cloudflare applies to its storage: Cloudflare states that all objects stored in R2, including their metadata, are encrypted at rest, and that all objects stored in D1, including metadata, live databases, and inactive databases, are encrypted at rest. Cloudflare doesn't document encryption for the disk of a running shop container, which is temporary and holds only a working copy; the durable copy of a shop's data is the replica in R2. Shop secrets, such as the shop's SMTP relay password, are stored encrypted.
Credentials	Sign-in, email-confirmation, and setup tokens are single use, expire, are stored only as hashes, and are compared in constant time. No shop password is generated or emailed.
Access control	Only the owner has administrative access, which includes the credentials for each shop's backup bucket and operator tools that can restore a shop and reset its owner's password (section 5). Administrative tools are behind Cloudflare Access. Keys that can change infrastructure or billing are held only by the automated pipeline and are scoped as narrowly as each provider allows. The public portal can't change infrastructure. Multi-factor authentication is on for every provider account: Cloudflare, Stripe, SMTP2GO, Zoho, Forgejo, the domain registrar, and the VPS host.
Abuse controls	Rate limits by IP address and email on sign-up and sign-in. Cloudflare Turnstile on sign-up, sign-in, and the Report a Shop form. Each of a shop's public forms (quote requests, which can carry an upload, and item orders) accepts at most 10 requests per IP address per hour, counting IPv6 addresses per /64 network, and each shop, which runs as its own instance, accepts no new public requests while 500 of its requests are open. Counsel: risk register P2 abuse limits, replaces the earlier TBD.
Backups and recovery	Continuous replication of each shop's database (Litestream) to the shop's own R2 bucket, with a snapshot every 24 hours kept 7 days (and 5-minute and 1-hour compaction levels between snapshots), stored separately from the running shop, and a 7-day restore window; no self-service restore and no guaranteed recovery time (owner decision 2026-11-07); there is no second copy yet, and a monthly restore drill is planned. Counsel: risk register item 9, matches the terms' best-effort backup wording.
Monitoring	Each shop's resource use is sampled (at most every 5 minutes, on real requests) and the owner gets an alert email at 70% of a limit; a daily reconciliation checks billing against the shops; a status page host outside Cloudflare publishes service status and emails the owner when a check fails.
Change management	Every change is deployed to a separate staging environment first. Shop updates roll out in waves and stop on the first failure.
Logging	An append-only audit log of changes to each shop's account, kept while the shop exists. Two years after a shop is deleted, its entries are deleted, except one entry recording that the shop existed and when it was deleted, and any records of payment disputes (see the retention table in the Privacy Notice). TBD: hosting — deploy before launch Request logs from the account, sign-in, and shop-routing services (Cloudflare Workers Logs) are kept 7 days and may include IP addresses, which aren't redacted. Cloudflare keeps its own edge and security logs under Cloudflare's own privacy policy and doesn't publish a retention period. Counsel: risk register item 12, log retention unstated.
Incident response	A written incident response plan exists. It covers detection, containment, assessment, notice to affected shop owners within the time in section 8, repair, and review.
Deletion	Automated deletion after the retention window, recorded in the audit log. Automatic deletion of quote-request uploads 30 days (G-code) or 180 days (3D models) after the request is finalized. Deleting a record in a shop overwrites its content in the live database file (SQLite `secure_delete`). A copy can remain in the database's write-ahead log until the next checkpoint and in backups for up to 7 days. A deleted uploaded file can stay in storage trash for up to 30 days. Counsel: risk register P2 upload retention and item 20.

Annex 3: Subprocessors

Subprocessor	Service	Shop personal data involved	Location
Cloudflare, Inc.	Hosts the shops and sites (Workers, Durable Objects, Containers). Each shop's SQLite database runs in its container and is replicated to R2, which also stores files. D1, KV, Queues, and Workflows hold account and control-plane records, not shop records. Also provides DNS, TLS, custom domains, bot checks, and security; processes request data (IP addresses and request details)	All shop personal data, including files and request data	United States location hint for R2; global network for compute
Zoho	Owner mailboxes: support at contact@fleeceforge.com, legal@fleeceforge.com, and alerts@fleeceforge.com.	Only what you or your end customers send to FleeceForge support. Support mail is kept 2 years, legal mail 3 years, and alerts 1 year, then deleted in a yearly cleanup.	US
SMTP2GO	FleeceForge's transactional email from `fleeceforge.com` addresses (account notices come from `setup@fleeceforge.com`) (open tracking applies to FleeceForge's own emails to shop owners only, and click tracking is off; emails shops send to their customers aren't tracked)	None. FleeceForge sends only its own email through SMTP2GO, to shop owners and to the owner. Shops send their own email, including mail to their end customers, through their own relay.	US

Stripe and the status page host (VPS Hosting Service, which hosts Gatus and sees only status page visitors' IP addresses and request details) don't process shop personal data and so aren't subprocessors under this DPA. They appear in the Privacy Notice. Your own email relay and payment processors are your providers, not FleeceForge's subprocessors.

FleeceForge Privacy Notice

1. The short version

2. Information about shop owners

3. Information about end customers

4. Information about website visitors and people who use our forms

5. How we use information

6. Who we share it with

7. Where information is stored

8. How long we keep it

9. How we protect it

10. Your privacy rights

11. Children

12. Changes to this notice

13. Contact

FleeceForge Terms of Service

Part 1. General terms

1. About these terms

2. The websites

3. The waitlist and tool requests

4. Feedback and ideas

5. Intellectual property and trademarks

6. Disclaimer of warranties

7. Limitation of liability

8. Indemnity

9. Governing law and disputes

10. Changes to these terms

11. Notices and contact

12. General

Part 2. The hosted service

13. Who the service is for

14. Your account

15. Plans and prices

16. Free trial

17. Billing and renewal

18. Refunds

19. Your data

20. Suspension

21. Cancellation, termination, and deletion

22. Acceptable use

23. Availability and support

24. Changes to the service and to prices

25. Third-party services

FleeceForge acceptable use policy

1. What FleeceForge is for

2. Prohibited goods and content

3. Prohibited uses of the platform

4. Your responsibilities for your shop

5. Security research

6. Copyright and other rights complaints

7. Enforcement

8. Appeals

9. Changes

FleeceForge data processing addendum

1. Definitions

2. Roles and scope

3. Instructions

4. Service provider restrictions

5. Confidentiality

6. Security measures

7. Subprocessors

8. Security incidents

9. Assistance

10. Deletion or return at the end of the service

11. Audits

12. Liability, term, and order of precedence

Annex 1: Processing details

Annex 2: Security measures

Annex 3: Subprocessors