Privacy Policy
This is a structured working draft, not final legal advice.
[REVIEW REQUIRED] Confirm the controller’s legal name, registered address, company/registration number, applicable law, effective date and supervisory authority before publication.
1. Who is responsible
[REVIEW REQUIRED] Data controller: legal entity name and postal address. Privacy contact: janbandzak@gmail.com.
2. Data handled by this website
When you contact support, we receive the information you choose to send, such as your email address, product and environment details, redacted example rows and error messages. The hosting environment may also create routine server and security logs containing an IP address, request time, requested URL, browser information and error details.
[REVIEW REQUIRED] Confirm the hosting provider, log fields, purposes, lawful basis and retention period. This draft does not claim that analytics or newsletter services are used.
3. Plugin workflow data
Grosik B2B Order Import processes order-file rows, product identifiers, quantities and validation results inside the merchant’s WordPress and WooCommerce installation. The merchant operating that store decides which customer and order data is uploaded and is responsible for its own notices, lawful basis, access controls and retention.
Optional Free diagnostic logging is off by default. If a merchant enables it, short-lived WordPress transients can hold references, counts and error types for troubleshooting. Support submissions should be redacted and must not contain passwords.
4. Cookies and third-party content
The theme does not set its own analytics, advertising or newsletter cookies and does not load third-party marketing scripts or embedded media. WordPress can set essential cookies for administrators who sign in through the private administration route. A Freemius checkout, once a verified link is enabled, is an external service governed by its own cookie and privacy notices.
[REVIEW REQUIRED] Re-audit active WordPress plugins, hosting controls and embedded content immediately before publication and update this section and any consent mechanism to match the live site.
5. Freemius
The B2B plugin is configured to use Freemius for paid-plan licensing. If you start a paid checkout or connect a licensed installation, Freemius may process account, purchase, licensing, site and technical data under its own notices and terms.
[REVIEW REQUIRED] Confirm the exact enabled Freemius features, legal roles, international transfers, subprocessors, retention and link to the applicable Freemius privacy notice. Do not describe Freemius as Merchant of Record unless contractually verified.
6. Purposes and lawful bases
[REVIEW REQUIRED] Map each confirmed operation to its purpose and lawful basis. Likely categories to review include answering support requests, providing and licensing software, protecting the service, meeting legal obligations and establishing or defending legal claims.
7. Recipients and transfers
[REVIEW REQUIRED] List the confirmed hosting, email, support, payment/licensing and professional-service providers. Document any transfer outside the EEA/UK and the safeguard relied on.
8. Retention and security
[REVIEW REQUIRED] Insert verified retention periods for support correspondence, server logs, customer records, invoices and licensing records. Describe only security measures that are actually in place.
9. Your rights
Depending on applicable law, you may have rights to access, correct, erase, restrict or receive your data, object to processing, withdraw consent where consent is used, and complain to a supervisory authority.
[REVIEW REQUIRED] Confirm the applicable jurisdiction, response procedure, identity-verification process and authority contact.
10. Changes
[REVIEW REQUIRED] Add an effective date and describe how material changes will be communicated.