Effective date: 2026-10-07
This policy explains what personal data Stitchen collects through stitchen.app, the tools on it and the Stitchen app, what happens to that data, and the choices you have. "Stitchen", "we" and "us" mean Stitchen LLC, 317 E 830 S, Farmington, UT 84025. You can reach us at support@stitchen.app.
The policy has two parts. "What happens today" describes the services as they run now. "Planned features" describes features that don't exist yet. Nothing in that part applies until a feature launches, and we will update this policy before it does.
The short version
- The website tools run in your browser. Your charts, images and files stay on your device. The one exception is a clean print, one you buy or one made with a print code, which sends the chart to our print server. The print server doesn't keep the chart.
- The website has no advertising, analytics or tracking scripts, and it sets no cookies.
- Our hosting provider receives your IP address and browser details when it sends you a page.
- If you create an account, in the app or on the website, we keep your email address and a few account details with Amazon Web Services in the United States. If you buy something, we also keep a record of the purchase, and Stripe takes the payment.
- If you list patterns in the pattern shop, your shop name, profile and listings are public, and we keep the files you upload to check them.
- We don't sell your personal data or share it for advertising.
If this summary and the rest of the policy ever disagree, the rest of the policy applies.
What happens today
Visiting stitchen.app
Pages and downloads are delivered by Amazon CloudFront from storage in Amazon S3. To send you a page, CloudFront receives what any web server receives: your IP address, your browser's user agent, the address you asked for and, usually, the page that sent you there.
We don't keep logs of these requests.
The pages load no third-party scripts, fonts, analytics, advertising or tracking pixels. The website sets no cookies.
The pattern designer and stitch tracker
The designer saves your projects in your browser's local storage on your device. A project holds the chart, its layers, colorways and progress, and which threads you have marked as owned or blended. If the designer finds a saved project it can't read, it keeps a recovery copy in the same storage rather than discarding it. None of this is sent to us or to anyone else, except the parts of a chart that a clean print sends (see "Prints made with a print code" and "Clean prints you buy" below).
When you convert an image into a chart, your device decodes the image. It isn't uploaded. If you create a project from the image, or add it to a chart as an overlay, the designer saves a small copy of the image with the project, one pixel for each stitch. A project created from an image is also named after the image's file name. The copy and the name both travel with the project: into the OXS files you export, into that project's backup, and into Back up all projects. To leave the image out of a file you share, click Remove source overlay in every project the file will contain. If you'd rather not share a project's name, rename it first. A project created from an image also keeps a larger copy of the cropped image, up to 1024 pixels on its long side, to print as the pattern's first page. That copy goes into the project's backups but never into an OXS file.
Whatever you type in a project's Author and "Copyright / permission" fields, such as your name, is saved with the project, written into the OXS files you export and printed on the pattern pages.
Prints made with a print code
A print code lets you make a clean print without an account, in the designer or in the app in a browser or on a computer. The Android and iOS apps don't take print codes. When you check a code, the designer or the app sends the code to our print server. When you print with it, it sends the code and the chart's stitches, threads, title, author and copyright line. It doesn't send your photo, layers or progress. The server makes the PDF, sends it back to you and doesn't keep the chart.
What a code print keeps. For each print, we keep the code, a fingerprint of the chart and when it was printed, in Amazon DynamoDB. The fingerprint is a hash of the chart: it shows whether two prints are of the same chart, but the chart can't be read back from it. Each print's record is set to expire 30 days after the print, and our database deletes expired records automatically. We also keep a count of the prints each code has used.
Limiting abuse. To stop people guessing codes, the server counts the requests from your IP address in each hour, and how many of them gave a code that doesn't exist. To count them, we store a scrambled (hashed) form of your IP address with the hour, never the address itself. Each count is set to expire an hour after the hour it counts, and our database deletes expired counts automatically. The print server's log records which request it answered, the result and how long it took, but not your IP address, and is kept for 14 days.
The OXS file checker and the fabric calculator
Both work on your device. A file you check isn't uploaded, and the numbers you enter in the calculator aren't sent anywhere.
The release email signup
The website has a form for release news. If you sign up, we store your email address, the time you signed up and which form you used, in Amazon DynamoDB. We use your address only to send release news. We keep it until you ask us to remove it. Our service logs record a shortened form of the address, such as jo***@example.com, and are kept for 14 days.
The Stitchen app
The app runs in a browser at stitchen.app/app/ and as a preview for Windows.
Your library. Charts, progress photos, recently opened charts, and your thread and pattern inventory are stored on your device. In the browser they are kept in the browser's storage for stitchen.app. On Windows they are kept in a folder in your user profile. They aren't uploaded, except the parts of a chart that a clean print sends (see "Prints made with a print code" above and "Clean prints you buy" below).
Files and photos you open. PDFs, images and OXS files you open are read on your device and aren't uploaded.
Camera. Where the app uses your camera, such as the thread barcode scanner, the images are processed on your device and aren't sent to us.
Stitchen accounts
You can create an account in the app or on the website. You don't need one to use the website tools or the app. You need one to list patterns in the pattern shop. Once Stitchen's own products are on sale, you will also need one to buy a clean print or any other of them, and to print what you bought. An account also holds your email address ready for cloud sync when it launches.
What you give us. To sign up, you give an email address and a password, confirm that you are old enough to have an account, and agree to our terms. In the app you can also add a display name. To sign in, you give your email address and password. The first time you sign in, you also give the code we email you, which confirms the address is yours. To reset a password, you give your email address, the code we email you and a new password.
Where it goes. The app and the website send these details over HTTPS to api.stitchen.app. Our sign-in service passes your password to Amazon Cognito, which checks it and stores it in a protected form. We don't keep your password in our own database.
What we store. In Amazon Cognito: your email address, whether it is confirmed, and a field reserved for a payment-provider customer number. An account created before we started confirming email addresses also has its display name there. In our account database (Amazon DynamoDB): an account ID, your email address, your display name, the time you signed up, the version of our terms you agreed to, the time you agreed to them and confirmed your age, the time you confirmed your email address, a random value that planned cloud sync will use for encryption, a scrambled (hashed) form of an account recovery code that the app doesn't use yet, and fields for plan status and payment-provider references. If you don't give a display name, we use the part of your email address before the @. When you buy Pro or a Stitchen Pass, the account record also notes when you bought it and which purchase it came from, and for a Pass, when the Cloud time it includes ends. The payment-provider fields stay empty until subscriptions are sold.
On your device. After you sign in, the app keeps your account ID, email address, plan status and sign-in tokens on your device. On Windows they are kept in an encrypted file in your user profile that only your Windows account can unlock. In a browser they are kept in the browser's storage, so sign out when you finish on a shared computer. They stay on your device until you sign out. When you sign in on the website, the only sign-in detail kept in your browser's storage for stitchen.app is the token that renews your sign-in. The sign-in token itself stays in the page's memory until you close the page. The sign-in token works for 60 minutes, and the token that renews it works for 30 days. Signing out removes them from your device and cancels the renewal token on our servers.
Emails. Account emails, such as the code that confirms your address and a password reset code, are sent for us by Amazon Cognito.
Logs. Our API keeps a request log that doesn't include your IP address. Our sign-in services keep logs too. They record your account ID and, when you sign up or ask for a password reset, a shortened form of your email address, such as jo***@example.com. Both are kept for 14 days.
Clean prints you buy
A clean print has no watermark. Our print server makes it, so buying one or making one sends your chart to us. For now, only testers can buy clean prints. You need to be signed in to buy a clean print and to print one you bought. A print made with a print code needs no account and is described under "Prints made with a print code" above.
What is sent. When you buy a clean print, and each time you print it, the designer or the app sends the chart's stitches, its threads, its title, its author and its copyright line. Your photo, the chart's layers and your progress are never sent. The print server makes the PDF in memory, sends it back to you and doesn't keep the chart.
What we keep. For each clean print you buy, the purchase record described under "Payments" also holds a fingerprint of the chart (a hash of its stitches and threads), how many times you've printed it and an identifier for the latest print.
What your device keeps. So that a print after you edit the chart can be checked against the chart you bought, the print server signs a copy of the chart's stitches and threads as bought, with your account ID, and sends it to your device. The designer and the app keep it with the project, and the print server keeps no copy. In the designer it goes into the project's backups, but never into an OXS file.
Limiting use. To stop the print server being overloaded, we count each account's print requests in each hour. Each count is set to expire an hour after its hour ends, and our database deletes expired counts automatically.
Logs. The print server's log records which request was made, the result and how long it took. It never records the chart. It is kept for 14 days.
Payments
Stitchen's own products, such as a clean print, are paid for on Stripe's checkout page. Stripe is a payment company, and its checkout page is part of its own website, under its own privacy policy. You give your payment details to Stripe there, and we never receive your full card number. When we open the checkout, we send Stripe your account ID, the order number, what you're buying and the version of the checkout terms you accepted. Stripe tells us whether the payment succeeded, the amount and currency, and its references for the checkout and the payment, and later whether the payment was refunded or disputed.
What we keep. For each order, our purchase record holds your account ID, the order number, what you bought, when you ordered, the version of the checkout terms you accepted and when, the price and currency, when you paid, whether the payment was refunded or disputed, and Stripe's references for the checkout and the payment. Our checkout and payment services log the order number, what was bought and the payment's status, and keep those logs for 14 days.
Designers in the pattern shop
The pattern shop at stitchen.app/shop lists patterns by independent designers. For now it is a directory: each listing links to the designer's own shop, where you buy from the designer, and Stitchen is not part of the sale. To list patterns, you need a Stitchen account and must accept our designer agreement on stitchen.app/sell.html.
Your designer profile. You give us a profile address, a shop name, your country, and optionally a short bio and up to five links to your own websites. When you accept the designer agreement, we keep the version you accepted, when you accepted it and when you confirmed you are an adult. We don't ask for your legal name, postal address, phone number, tax number or identity documents.
Your listings. For each listing you give us its title, description, tags, the price shown, its license, how it was made, where its artwork came from and any credit for it, the link to buy it in your own shop, and a note on each new version. If you import listings from the file Etsy exports, we read each listing's title, description, price, currency, tags and any link to it from the file, and keep only the drafts it makes and the row each came from. We don't keep the file, and we send nothing to Etsy.
Your files. Your browser uploads each listing's pattern PDF, an optional OXS file and up to 10 photos to our storage at Amazon Web Services. Uploads are deleted after 2 days. Our listing processor, which runs at Amazon Web Services with no access to the internet, reads them to check and describe the pattern. It keeps the PDF as you uploaded it, including the details stored inside it, such as an author name and the program that made it. It also keeps a copy of the chart without your stitching progress or where the file was on your computer, previews of the chart and your photos with their photo details (EXIF), including any location, removed, and a report of what it found. We keep the files of every version of a listing until you delete your account. If someone sends a notice about one of your listings, we also keep a copy of its files with the notice until we decide it.
Checks before a listing goes live. When you publish a listing, we compare fingerprints of its chart and photos with other designers' listings, compare its title, description and tags with a list of licensed character and brand names, and, for a listing you say you made yourself, look in the chart and the files' details for signs that an AI tool made it. If a check finds something, a person at Stitchen reviews the listing before it goes live. We tell you the reasons, and you can change the listing. If we remove a listing, or suspend or close your designer account, you can appeal. If you appeal, we keep your explanation with our decision as the record of the appeal for three years after that decision. We also keep the fingerprints of each listing you publish, to compare later listings with it.
What is public. A listing's page shows your shop name, its title, description, tags, price, license, how it was made and its artwork credit, the link to buy it, your photos, a coarse watermarked preview of the chart, the chart's size, colors and threads, when it was listed, and the date and note of its latest version. Your designer page shows your shop name, bio and links, and your listings. Search engines can find these pages, and our sitemap lists them. Your email address, your country, your account ID and your pattern files are never public.
The designer perk. While the shop shows at least one of your listings, your account record notes that you have Pro as a designer.
Limiting use. We count the files each account uploads in each hour. Each count is set to expire two hours after the last upload it counted.
Logs. Our designer services log your account ID with what they did, and our listing processor logs the names of the files it reads. Both are kept for 14 days. Messages between our services that name your account ID are kept for up to 14 days.
Notices about pages on Stitchen
The form at stitchen.app/report.html lets anyone tell us about a page on stitchen.app. You can send a copyright notice, a notice that a page is illegal for another reason, or a counter notice asking us to put back a listing we removed. You don't need an account to send one.
What a notice keeps. Every notice keeps the address of the page, your name and email address, which kind of notice it is, when we received it and a reference number. The form shows you the reference number when the notice is sent. We don't email you a receipt. A copyright notice also keeps your postal address and phone number, your description of the work you own and what on the page copies it, the name you type as your signature, and that you confirmed its good faith and accuracy statements. An illegal content notice also keeps your explanation of why the page is illegal and that you confirmed its good faith statement. A counter notice also keeps your postal address and phone number, the name you type as your signature, and that you confirmed its good faith statement and consented to the court's jurisdiction. The form sends only the details the kind of notice you chose asks for, and we keep only those. If the page belongs to a listing in the pattern shop, the notice also records which listing. When we decide a notice, we add the decision, the reasons for it and when it was made.
Why we keep it. We use a notice to decide whether to remove the page, and we keep it as the record of what we received and what we decided, under U.S. copyright law (17 U.S.C. 512) and the EU Digital Services Act (Regulation (EU) 2022/2065).
Who sees it. Notices are stored in Amazon DynamoDB, and the people at Stitchen who handle notices read them in our moderation tools. If you send a counter notice, we forward it, with your name, postal address, phone number and email address, to the person who sent the notice that led to the removal, as U.S. copyright law provides (17 U.S.C. 512(g)(2)(B)).
How long we keep it. We keep a notice until we decide it, and then for three years after our decision, the time U.S. copyright law allows for a claim about it. Then our database deletes the notice automatically. Backups keep a copy for up to 35 days after that. A notice isn't linked to a Stitchen account, so deleting an account doesn't delete a notice you sent.
Limiting abuse. The form accepts at most 10 notices an hour from one internet connection. To count them, we store a scrambled (hashed) form of your IP address with the hour, never the address itself. Each count is set to expire two hours after the last notice it counted, and our database deletes expired counts automatically. The service's log records the kind of notice and its reference number, not your details, and is kept for 14 days.
When you email us
If you email support@stitchen.app, we keep your message, your address and our reply, so we can answer you and keep a record of privacy and deletion requests. We keep them for three years after our last reply, or longer if the law requires it.
When you email support@stitchen.app or security@stitchen.app, or reply to an order email from orders@stitchen.app, Amazon Web Services receives the message for us, keeps a copy in Amazon S3 for 365 days and forwards it to the mailbox we read, which Google hosts (Gmail). The forwarded copy is kept like any other email you send us.
Who receives your data
We use these companies to run the services. They handle personal data only to provide their service to us, under contracts that bind them to follow our instructions and keep it secure.
| Company | What it does for us | Data it handles |
|---|---|---|
| Amazon Web Services, in the US East (N. Virginia) region | Hosts the website, downloads and the pattern shop (CloudFront, S3), runs our API, sign-in, checkout, print server and listing checks (API Gateway, Lambda, Cognito), stores accounts, designer profiles, listings, purchase records, notices and print code records (DynamoDB), stores designers' files (S3), keeps logs (CloudWatch Logs), sends account emails (Cognito), receives mail sent to our addresses at stitchen.app (SES, S3) | Hosting request details, account details, designer profiles, listings and their files, charts sent for a clean print while the print server handles them, purchase records, notices, print code records and request counts, logs, emails you send us |
| Google, through Gmail | Hosts the mailbox where we read and answer email sent to our addresses at stitchen.app | Messages you send us and our replies |
| Stripe | Takes payments for Stitchen's own products on its checkout page | Your payment details, and the account ID, order number, item and checkout terms version we send it |
GitHub builds our releases, but you download them from stitchen.app, so GitHub receives nothing from you.
We don't sell personal data. We don't share it for cross-context behavioral advertising, and we don't show ads. We disclose personal data to others only when the law requires it, to protect people's safety or our legal rights, or as part of a sale or merger of Stitchen. In a sale or merger, we pass on personal data only to a buyer that agrees to follow this policy for the data it receives.
How long we keep data
| Data | How long |
|---|---|
| Projects, library and files on your device | Until you delete them, or your browser or system clears them |
| Hosting request details | Not kept |
| Account records | Until you delete your account. Restorable database backups keep a copy for up to 35 days after that |
| Sign-in tokens on your device | Until you sign out. The sign-in token stops working after 60 minutes and the renewal token after 30 days |
| A chart sent for a clean print | Not kept. The print server holds it only while it handles the request |
| Purchase records | No set deletion date. Deleting your account doesn't delete them |
| The hourly count of your account's print requests | Set to expire an hour after its hour ends. Backups keep a copy for up to 35 days |
| A designer profile, its listings, their files and fingerprints | Until you delete your account. Unpublishing a listing takes it out of the shop but keeps it. After you delete your account, old copies of the files are kept for up to 180 days, and backups keep a copy of the records for up to 35 days |
| Files you upload for a listing | 2 days in our upload storage |
| Pictures in the pattern shop | Until the listing leaves the shop. Browsers and our delivery network can keep a copy for up to a year after that |
| An appeal and our decision on it | Three years after our decision. Deleting your account doesn't delete it |
| The count of files your account uploads each hour | Set to expire two hours after the last upload it counted. Backups keep a copy for up to 35 days |
| API, sign-in, print, payment and designer service logs | 14 days |
| Messages between our services | Up to 14 days |
| Emails you send us and our replies | Three years after our last reply, or longer if the law requires it |
| Email sent to support@stitchen.app, security@stitchen.app or orders@stitchen.app | 365 days in Amazon S3. The forwarded copy, three years after our last reply |
| Release email list | Until you ask us to remove your address. Backups keep a copy for up to 35 days after that |
| Notices sent with the form at stitchen.app/report.html | Until we decide the notice, then set to expire three years after our decision. Backups keep a copy for up to 35 days. Deleting an account doesn't delete them |
| The hashed count of notices from one connection | Set to expire two hours after the last notice it counted. Backups keep a copy for up to 35 days |
| A print made with a print code: the code, the chart's fingerprint and when it was printed | Set to expire 30 days after the print. Backups keep a copy for up to 35 days |
| The hashed count of print code requests from one connection | Set to expire an hour after the hour it counts. Backups keep a copy for up to 35 days |
Your choices
Data on your device. You control it, and we can't see or delete it for you. The website designer has no delete button yet. To remove its projects, including any recovery copies it kept, clear the site data for stitchen.app in your browser. The same step removes the browser app's library and sign-in details. In the browser app you can also remove one project at a time with Remove saved project. The Windows app is a folder you unpacked. Deleting that folder doesn't remove your library or sign-in details, so also delete the folder Stitchen in your Windows AppData\Roaming folder.
Your account. To delete your account, open your account in the app and choose Delete account, or open your account page at stitchen.app and choose Delete my account, then enter your password. If you haven't confirmed your email address yet, the app asks you to confirm it first. Deleting removes your sign-in details from Amazon Cognito and your account record from our database straight away. If you confirmed your email address, it also takes that address off the release email list. Purchase records stay, as the record of each sale. Restorable database backups keep a copy of the account record for up to 35 days, and our logs, which hold your account ID and a shortened form of your address, are kept for 14 days. You can also delete the account by emailing support@stitchen.app from the address on your account, and we complete that within 30 days. To get a copy of your account data or correct it, email support@stitchen.app from the same address. We confirm an emailed request comes from you by replying to the account's email address.
Your designer profile and listings. On stitchen.app/sell.html you can change your profile, except its address, and change or unpublish each listing. Unpublishing takes the listing's page and pictures out of the shop, and the listing, its files and its fingerprints stay with your account. Deleting your account deletes your designer profile, your listings, their files and their fingerprints, and takes your pages out of the shop. After that, old copies of your files are kept for up to 180 days, and an appeal is kept for three years after our decision on it.
Release emails. Email support@stitchen.app to be removed from the list.
Children
Stitchen is not aimed at children under 13. Without an account, the website tools collect no personal data beyond what hosting requires and, for a print made with a print code, the request count described above. You must be 13 or older to create an account, and 18 or older to list patterns in the pattern shop. We don't knowingly collect personal data from children under 13. If you believe a child under 13 has given us personal data, email support@stitchen.app and we will delete it.
Your rights in US states
Several US states, including California, Colorado, Connecticut and Virginia, give residents rights over their personal data. You have these rights with us wherever you live:
- to know what personal data we hold about you and get a copy of it;
- to correct it;
- to delete it;
- to opt out of the sale of personal data, targeted advertising and profiling. We do none of these;
- not to be treated differently for using these rights;
- to appeal if we turn down a request. Reply to our decision and we will review it.
To make a request, email support@stitchen.app. We answer within 45 days, or tell you within that time if we need longer and why. An authorized agent can make a request for you if you confirm to us that you gave them permission. If your browser sends a Global Privacy Control signal, we treat it as a request to opt out, although we have nothing to opt you out of. We don't track you across other websites, so a Do Not Track signal has nothing to switch off either.
In the past 12 months we have collected these categories of personal data: identifiers (name, email address, postal address, phone number, account ID, IP address), internet activity (the hosting request details described above), commercial information (the purchase records described above), the designer profiles, listings and files described above, including a designer's country, and account sign-in details (email address and password), which California treats as sensitive personal information. We collect them from you and your device. We use them to provide and secure the services. We disclose each category to our service provider, Amazon Web Services, to host and run the services. If you buy something, we also disclose your account ID and what you're buying to Stripe, which takes the payment. If you email us, we also disclose your email address and message to Amazon Web Services, which receives it for us, and to Google, which hosts our mailbox (Gmail). If you list patterns, we publish your designer profile and listings in the pattern shop, where anyone can see them. If you send a counter notice, we disclose it to the person who sent the notice that led to the removal. We use sensitive personal information only to sign you in and keep your account secure, so there is no other use to limit. We keep each category for the periods in the table above. We have not sold or shared any of them.
Your rights in the EU and the UK
Stitchen LLC is the controller of your personal data.
We rely on these legal bases:
| Processing | Legal basis |
|---|---|
| Your account | Performing our contract with you (GDPR Article 6(1)(b)) |
| Your designer profile and listings | Performing our contract with you, the designer agreement (Article 6(1)(b)) |
| The checks before a listing goes live, and keeping fingerprints of listings | Our legitimate interest in keeping copied, infringing and mislabeled patterns out of the shop (Article 6(1)(f)) |
| Clean prints you buy, payments and purchase records | Performing our contract with you (Article 6(1)(b)), and keeping records of sales that the law requires (Article 6(1)(c)) |
| Hosting request details, service logs and the hourly count of each account's print requests | Our legitimate interest in delivering and securing the services (Article 6(1)(f)) |
| Prints made with a print code, and the request counts that stop codes being guessed | Our legitimate interest in giving the prints a code allows and keeping codes from being guessed (Article 6(1)(f)) |
| The release email list | Your consent (Article 6(1)(a)), which you can withdraw at any time |
| Answering your emails and privacy requests | Meeting our legal obligations (Article 6(1)(c)) and our legitimate interest in answering you (Article 6(1)(f)) |
Projects and settings stored on your device never reach us, except the parts of a chart that a clean print sends, so apart from those we don't process them. Keeping them, and your sign-in tokens, on your device is strictly necessary to provide the service you asked for, so it needs no consent (ePrivacy Directive, Article 5(3), and the UK's Privacy and Electronic Communications Regulations). You need to give an email address and a password to have an account, and without them we can't create one.
You have the right to access your personal data, correct it, erase it, restrict how we use it, receive it in a portable format, and object to processing based on legitimate interests. Where we rely on consent, you can withdraw it at any time. You can also complain to your data protection authority. In the UK that is the Information Commissioner's Office.
Your personal data is stored and processed in the United States, where Stitchen is based. You send it to us there directly when you use the services.
We don't make decisions about you by automated means that have legal or similarly significant effects. Automated checks can hold a designer's listing for review, but a person makes every decision about it.
Security
Every connection to stitchen.app and api.stitchen.app uses HTTPS. Our account database is encrypted at rest. Sign-in tokens expire as described above. No system is perfectly secure. If a breach affects your personal data, we will tell you as the law requires.
Planned features
None of the following exists today. Each will change what we collect, so we will update this policy before any of them launches.
Cloud sync. Sync would copy your charts and progress between your signed-in devices. As planned, the app encrypts chart contents on your device (AES-256-GCM) before uploading them to Amazon S3. Project titles would be stored unencrypted so the app can list them. For each device we would keep its name, its platform, when it last connected and a push notification token. Uploaded snapshots would be deleted 90 days after upload.
Purchases in the apps. Purchases in the Apple App Store or Google Play would be handled by Apple or Google, and we would receive confirmation of the purchase.
Mobile apps. Apps for Android and iOS would ask for camera and photo library access, to scan thread labels and photograph paper patterns.
Crash reports and usage statistics. We may add crash reporting and usage statistics. We would describe them here first. Any collection of chart images to improve pattern reading would be opt-in.
Selling in the pattern shop. Today the shop is a directory, described under "Designers in the pattern shop" above. Once patterns can be bought on Stitchen, buying one would need an account. For each order we would keep what you bought, the price and tax, and the evidence of your country that tax law requires, which in the EU means keeping it for 10 years. To answer payment disputes, we would also keep the IP address, device and time of each download. Every pattern you buy would carry your name, email address and order number on each page, and its order number in the file's details, so a shared copy can be traced to its order. Stripe would take payments and check designers' identities and bank details. Designers who sell as a business would give us their trader details, which would be public on their pages and kept for 180 days after they delete their account. When a payment dispute concerns a pattern, we would keep a copy of it until the dispute closes. Reviews would be public. We would count listing views as daily totals, with no record of who viewed. Before selling opens, this policy will describe each of these and how long we keep it.
Changes to this policy
We will post changes here and update the effective date. If a change materially affects how we use personal data we already hold, we will email account holders before it takes effect.
Contact
Stitchen LLC
317 E 830 S, Farmington, UT 84025
support@stitchen.app