1. Information we receive
| Activity | Information | Purpose |
|---|---|---|
| Creator applications | Creator or studio name, email, product category, description, submission time, application reference, and review status. | Review your request, contact you, and manage onboarding. Applications are stored on the server, not just in your browser. |
| Payments | Product or section identifiers, user reference supplied to checkout, payment-session and transaction references, provider, payment status, IP address, and approximate country. Provider notifications may contain additional transaction details. | Initiate and reconcile payments, record the result, investigate issues, and maintain transaction records. |
| Website requests | IP address, requested URL, time, browser and device request headers, and technical error information. | Deliver the website, protect its operation, and diagnose failures. Actual logging depends on hosting and service configuration. |
| Messages and reports | Your email, message, and information you provide about an application, product, transaction, or complaint. | Respond to you, investigate reports, resolve disputes, and enforce our rules. |
| Saved products | Product identifiers stored in your browser. | Remember your saved list on the same browser and device. |
Do not submit full card numbers, card security codes, passwords, sensitive identity documents, or unnecessary information about other people in applications or messages. Our website does not provide a form for collecting card numbers; payment details are entered through the payment provider's checkout.
2. Purposes and legal bases
Information is used to provide requested features, review creator applications, process payment-related requests, offer support, maintain security, investigate abuse, and meet applicable legal obligations. An application submission is not permission to send unrelated marketing.
Where a legal basis is required, processing may be necessary to take steps you request before entering a contract, perform a contract, comply with a legal obligation, or pursue legitimate interests such as service security and resolving disputes. Those interests must be balanced against your rights. Where consent is required for a particular activity, it must be obtained before that activity. Reading this policy or merely visiting the site is not consent.
3. Browser storage and cookies
Saved products use local storage under makershelf.saved.v1. Product IDs remain until you remove saved items, clear site data, or your browser removes them. The current favorites feature does not submit this list to MakerShelf's server.
An earlier creator form saved browser drafts under makershelf.creator-draft.v1. The current form no longer reads or saves those drafts. A previous draft may remain on your device until you clear it.
Session and anti-forgery cookies may be used to protect forms and carry submission confirmations. Blocking them may prevent submission. Payment services may use their own cookies or storage as described in their policies. The current storefront does not include a separate advertising or audience-analytics integration.
4. Payment services and other recipients
When you initiate payment, transaction information is exchanged with the selected provider. The storefront currently offers Stripe, PayPal, and Lava. Existing integrations may also process payments initiated through separately supplied links, depending on their configuration.
The payment page currently loads client-side resources from Stripe, Pandabase, and Airwallex. Their servers may receive connection information when these resources load, even if you select a different payment method. The page also contacts ipify and ipapi to obtain your IP address and approximate country. This is network-based information, not GPS location.
Providers determine their own processing practices for their services. Review the policies of Stripe and PayPal, and the privacy information in any other provider's checkout before proceeding.
Hosting, infrastructure, database, and email providers may process information needed to operate the service. Relevant information may also be shared where necessary to handle a complaint, protect rights and security, or comply with a valid legal requirement. Viewing a creator's profile does not, by itself, send that creator an application or payment record.
5. Retention
Retention depends on the purpose, the status of the application or transaction, accounting and legal requirements, and outstanding disputes. Creator applications and payment records currently have no automatic deletion schedule in the application. Deletion of server records therefore requires manual review; this policy does not promise an automatic expiry period.
Information should be retained only while necessary for its purpose or an applicable legal requirement. Contact us to request deletion or information about retention for a particular record. Information needed to resolve disputes, prevent abuse, or meet legal obligations may have to be retained despite a deletion request. Hosting logs, backups, and provider records may follow separate retention arrangements.
6. Security and international processing
Access to application and transaction information should be limited to people and services that need it for the purposes described here. Do not share private payment links or transaction references publicly. No method of transmission or storage can be guaranteed completely secure.
External services may process information outside your country. Locations and safeguards depend on the provider and hosting arrangement. Where cross-border transfer rules apply, appropriate legal conditions and safeguards must be satisfied. Contact us for information about a specific transfer.
7. Your rights and choices
Depending on applicable law, you may have rights to access, correct, erase, or obtain a copy of your information, restrict processing, object to processing, or request portability. Where processing relies on consent, you may withdraw it without affecting earlier lawful processing. You may also have the right to complain to a relevant data protection authority.
Send requests to [email protected] with enough information to identify the relevant application or transaction. Proportionate identity verification may be necessary before information is disclosed or changed. Applicable legal response periods govern privacy requests; the 24-hour creator-application response target is not a guarantee for completing a privacy request.
Clear this site's browser data to remove saved products and any legacy draft on that device. This does not delete applications already submitted to the server, payment records, or data held by a provider.
8. Children and prohibited submissions
Creator applications and purchases are intended for adults aged 18 or older. Do not knowingly submit a child's personal information. If you believe a child has provided personal information, contact us so we can review and take appropriate action.
Do not submit stolen data, private information without a lawful basis, or content prohibited by our Terms of Use. Reports about unlawful content should describe the concern without redistributing prohibited material.
9. Updates and contact
This policy will be updated when relevant features or practices change. The date above identifies the current version. Material changes will be communicated through the website or another appropriate channel.
For privacy questions or requests, contact [email protected].