1. What is Publii?
2. How is Publii different from WordPress?
3. Is Publii free?
4. Can I use Publii offline?
5. What hosting options does Publii support?
6. Do I need coding knowledge to use Publii?
7. What is a static site?
8. What kind of site can be created with a static website?
9. What are the differences and benefits between a dynamic and a static website?
10. What is a static CMS?
11. What are the differences between a Static Site Generator and Static Site CMS?
12. Privacy-focused website - what does it mean?
13. Is a static CMS a good choice if you want a privacy-oriented website?
14. What does "serverless" mean?
15. What is Headless technology?

What is Publii?

Publii is a free, open-source desktop application for creating fast, secure static websites. It runs directly on your computer — Windows, Mac, or Linux — and works completely offline.

Think of it as WordPress without the complexity. You get the same visual interface for writing posts, managing pages, and customizing your site. But instead of building pages dynamically with databases and server code, Publii generates clean HTML files that you deploy to any hosting platform.

The result? Websites that load instantly, stay secure without constant updates, and cost almost nothing to host. You build everything locally on your machine, preview it before publishing, then push the finished files with one click.

How is Publii different from WordPress?

The biggest difference: Publii generates static HTML files while WordPress builds pages dynamically every time someone visits.

With WordPress, you need web hosting with PHP and MySQL. Your content lives in a database on a server. When someone visits your site, WordPress queries the database, processes PHP code, assembles the page, and sends it to the browser. This happens for every single page view.

Publii skips all that overhead. You work on your site locally on your computer. When you publish, Publii generates finished HTML files and uploads them to your host. No database. No server-side processing. Just clean files that load instantly.

What this means in practice:

• Speed — Publii sites load 3-5x faster because there's no database processing
• Security — No WordPress vulnerabilities to patch, no plugins to update, minimal attack surface
• Hosting — You can use free hosting like GitHub Pages or cheap CDN storage
• Offline work — Build your entire site without internet, publish when ready
• Privacy — No backend collecting visitor data, GDPR compliance built in

The tradeoff? WordPress offers more interactivity and dynamic features. But for content-focused sites — blogs, portfolios, business pages — Publii gives you everything you need with way less complexity.

Is Publii free?

Yes. Completely free, forever.

Publii is open-source software under the GPL-3.0 license. There are no premium versions, no paid upgrades, no hidden costs. Every feature is available to everyone. All future updates are free.

You don't even need paid hosting. Publii works with free platforms like GitHub Pages, Netlify. Or you can use affordable cloud storage like AWS S3 or Google Cloud. The choice is yours.

Can I use Publii offline?

Absolutely. That's one of Publii's biggest advantages.

Publii runs as a desktop application on your computer. You can write posts, edit pages, customize themes, and preview your entire site without any internet connection. Your content stays on your machine until you're ready to publish.

Internet is only needed when you deploy your site to a hosting platform. Everything else — writing, editing, designing, previewing — works completely offline. This makes Publii perfect for working on planes, in cafes with spotty WiFi, or anywhere you want privacy and control over your content.

What hosting options does Publii support?

Publii supports one-click deployment to multiple platforms:

• Amazon S3 — Industry-standard cloud storage with excellent performance
• Google Cloud Storage — Affordable CDN hosting with global distribution
• Netlify — Free tier with automatic deployments and custom domains
• GitHub Pages — Free hosting for static sites, perfect for personal projects
• GitLab Pages — Alternative to GitHub with built-in CI/CD
• FTP/SFTP — Any traditional web hosting that supports file uploads

You can also manually export your site and upload files to any host you want. Publii generates standard HTML files that work anywhere — no special server requirements needed.

Want to switch hosts? No problem. Just change your deployment settings and push to a new platform. Your site files are portable and host-agnostic.

Do I need coding knowledge to use Publii?

Nope. Publii is designed for anyone who can use WordPress or basic desktop software.

The interface gives you visual editors, drag-and-drop features, and settings panels with clear options. You write posts in a WYSIWYG, Block or Markdown editor — what you see is what you get. No markdown syntax. No terminal commands. No config files to edit.

That said, if you DO know HTML, CSS, or JavaScript, you can customize everything. Publii uses Handlebars templating, which is easy to learn and powerful for developers. But customization is optional — the available themes and tools work great out of the box.

Think of it like using Microsoft Word. Anyone can write a document. Power users can create complex templates. But you don't need to be a power user to get professional results.

What is a static site?

Think of a static site as a collection of ready-made web pages sitting on a server, waiting to be served. When someone visits your site, the server simply hands them the files — HTML, CSS, JavaScript — without building anything on the fly.

It's like having a printed book versus generating each page when someone asks to read it. Static sites use simple HTML, CSS, and JavaScript files that look the same for everyone. No databases, no server processing. Just clean, fast files served straight to your browser.

What kind of site can be created with a static website?

Static sites work great for blogs, portfolios, business websites, documentation, and landing pages. Basically anything where you're sharing information rather than running complex interactions. You know — the kind of sites where content matters more than real-time user features. If you're building the next Facebook with real-time chat and user-generated content? Probably not. But for 80% of websites out there? Static is perfect.

What are the differences and benefits between a dynamic and a static website?

Dynamic sites like WordPress build pages on demand using databases. They're flexible but need constant maintenance, security updates, and decent hosting. Static sites skip all that — pages are pre-built and just sit there waiting to be served. The result? Faster load times, lower costs, better security, and way less headache. The tradeoff is less interactivity, but honestly, most websites don't need database-driven content generation.

Want to explore the differences in more depth? See the full static vs dynamic CMS comparison.

What is a static CMS?

A static CMS gives you the content management experience you know from WordPress — writing posts, uploading images, customizing designs — but outputs static files instead of dynamic pages.

You work in a nice interface with visual editors and preview options. When you're ready to publish, the CMS generates clean HTML files and pushes them to your server. No databases to manage. No server-side code running on your host. Just fast, secure files.

Publii is a static CMS that runs right on your computer. You build your entire site offline, preview everything locally, then deploy finished files with one click. The result? WordPress-like simplicity with static site speed and security.

What are the differences between a Static Site Generator and Static Site CMS?

Both create static sites, but the experience is completely different.

Static Site Generators (like Jekyll or Hugo) are command-line tools for developers. You write content in markdown files, configure settings in YAML, run terminal commands to build your site. It's powerful if you're comfortable with code. If you're not? It's overwhelming.

Static CMS platforms give you buttons, editors, and visual tools. No terminal commands. No config files to debug. You manage everything through an interface — like using an app instead of writing scripts.

Think of it this way: Static Site Generators are like building furniture from raw materials. Static CMS is like IKEA — you still get to customize, but someone else handled the hard parts.

Privacy-focused website - what does it mean?

A privacy-focused website respects visitors by collecting minimal data and being transparent about what it does collect.

You're not tracking every click. Not selling visitor data to advertisers. Not using invasive analytics that follow people across the web. You use HTTPS for secure connections. You're clear about any data collection. And you follow regulations like GDPR not because you have to, but because it's the right thing to do.

In 2025, privacy isn't optional anymore. Visitors expect it. Regulations require it. And honestly, it's just good practice. Static sites make this easier because there's no backend collecting and storing user data by default.

Is a static CMS a good choice if you want a privacy-oriented website?

Absolutely. Static CMS platforms are naturally privacy-friendly because they don't need to collect user data to function.

There's no login system storing passwords. No database tracking visitor behavior. No server-side code processing personal information. You're just serving files — HTML, CSS, JavaScript — that display the same for everyone.

This makes GDPR compliance simpler. Less data collection means less risk, fewer disclosures, and easier regulatory compliance. If privacy matters to you or your audience, static is the obvious choice.

What does "serverless" mean?

Serverless doesn't mean no servers — it means you don't manage them. Your hosting provider handles all the infrastructure automatically, spinning up resources when needed and shutting them down when idle.

Traditional hosting means paying for a server that runs 24/7, whether you have zero visitors or 10,000. With serverless, you only pay for actual usage. Your site scales automatically based on traffic without you lifting a finger.

This is perfect for sites with unpredictable traffic. Maybe you get featured on Reddit and suddenly have 50,000 visitors. Serverless handles it. The next day traffic drops back to normal? Costs drop too. The cloud manages everything — you just focus on content.

What is Headless technology?

Headless technology separates your website's frontend (what visitors see) from the backend (where content and logic live). They operate independently but communicate through APIs when needed.

This separation gives you incredible flexibility. You can have a static frontend for blazing speed and security while still pulling in dynamic features when necessary. Need to add e-commerce? Integrate Shopify's API. Want user comments? Connect a service like Disqus. Need a contact form? Use a serverless function.

Your site stays fast and secure because the core is static, but you can layer on dynamic features exactly where you need them. It's like having a lightweight sports car that can tow a trailer when necessary — performance when you want it, capabilities when you need them.

Publii logos

The logo should not be stretched or distorted. It should be used without shadows or borders or any other effects. It should also not be used in a container where there is not enough room for the logo. 

Publii screenshots

Friendly legal reminder

You are about to download a set of graphics that are protected under intellectual property laws. Please make sure to use them correctly so that we can protect our rights.

• Don't use them in a way that would imply an affiliation between your product or service and ours.
• Don't use them as part of your own product or service's name.
• You may not alter them in any way you like, or combine them with other graphics without written consent from TidyCustoms.

Download Press Kit

If you've created a plugin or theme for Publii that you feel would be helpful for other users, you may submit it to the Publii Marketplace via the following process:

1. Create a site where the plugin or theme is described in detail, and may be downloaded by Publii users; this can be your own site or a GitHub repo.
2. Submit your plugin or theme for review; the submission should include a screenshot and a short but concise description/feature list. For plugins, an icon should also be included that will be displayed on the Plugin Marketplace; this is not required for themes.
3. Our core team will review the plugin or theme to ensure it meets our quality criteria.
4. After review, if accepted, a description page will be added to the Publii Marketplace with a link to your extension page that you provided when submitting the plugin or theme for review.

Plugin Submission Requirements

As noted above, four elements are required for plugin submissions; a Download Location, a Screenshot, an Icon, and a Description with a Feature List. These elements should contain the following:

• Download Location - This should be either your own personal site, or a GitHub or similar page where users will be able to download your plugin. 
• Screenshots - Screenshots should be of high-quality in .png format (min. 144dpi). At a minimum, a single screenshot of the options screen is required to maintain a standard layout with other Publii plugins. However, if the plugin provides visual elements or effects on a page, then a screenshot of the plugin in use should be included instead.
• Icon - The icon will be used when displaying the plugin in the list of plugins on the Publii marketplace.
• Description with Feature List - This section should follow the standard used by other plugins on the marketplace; a short, single-paragraph description of the app concept and function, and a short unordered list of available features and options.

Additional technical requirements for plugins

To ensure consistency and offline compatibility across installations, submitted plugins must:

• Avoid external dependencies at runtime – Plugins should not rely on third-party CDNs (e.g., jsDelivr, unpkg, Google Fonts, etc.). Instead, include all required JS/CSS files locally within the plugin directory.
• Avoid using "Publii" in the plugin name – Plugin names must not include the word "Publii" to prevent confusion with official core plugins. Use descriptive, generic names instead.

Theme Submission Requirements

Theme submissions for the marketplace generally require the same elements as the plugin submissions, with some minor differences. The required content includes: a Download Location, a Screenshot, and a Description. These elements should include the following:

• Download Location - As with the plugin submissions, the download location should be your personal site, or a GitHub or other similar page where users will be able to download the theme file.
• Screenshot - The screenshot should be high-quality in .png format (min. 144 dpi) . Usually, this should include the main elements of the frontpage, such as the header and post listings if relevant. The intention is to communicate the core design philosophy of the theme.
• Description - The description should be one or two paragraphs covering the features and design of the theme, and the target demographic e.g. it may mention that the theme is useful for portfolio or personal blog sites.

Additional technical requirements for themes

Theme submissions should also follow similar principles:

• Use only locally hosted assets - Any JS, CSS, or font files used in the theme must be stored inside the theme’s directory structure. External CDN resources are not allowed.
• Do not use "Publii" in the theme name - To avoid confusion with official themes, the theme name should not include the word "Publii". Instead, use creative or descriptive names that reflect the theme's purpose or style.

Submission Review

When reviewing submitted plugins, the main factors that our team will look for is functionality and ease-of-use; does the plugin provide a feature or function that will be useful to our users? Are the available options sufficiently explained? Does the plugin conform to the standards established by the core plugins?

For themes, the criteria will be focused more on layout and stylings, included features, and efficient code to ensure minimal load impact on sites that choose to utilize the theme.

In the case that a submission is rejected, our team will be able to provide a general reason as to why, but we won't be able to go into finer detail about build/functionality/aesthetic issues, as doing so wouldn't be maintainable as the number of submissions grow.

Premium Plugins and Themes

Premium plugins or themes that require payment may be submitted to the Publii Marketplace. However, please be aware that the Publii Marketplace will only showcase the plugin or theme, and provide a link for users to visit your site for purchase. Processing of payments, invoicing, post-purchase support and other sales-related requirements will be the responsibility of the plugin or theme developer; Publii will not provide any support in this area.

Accepted Submissions

Once a submission of a plugin or theme is accepted, you will be notified and the plugin or theme will be uploaded to the respective Publii Marketplace. Accepted plugins will use the submitted icon to display the plugin in the marketplace, with the screenshot, short description and feature-list included on the main plugin page.

For themes, the screenshot will be used to display the theme on the marketplace, with the one or two paragraph description and screenshot included on the main theme page.

Additional screenshots, features and a detailed description of your extensions should be included on the theme or plugin page of your website.

Support for User-Submitted Plugins and Themes

As a small team, it will not be possible for us to provide support for submitted plugins or themes to our users. Each plugin/theme author will thus be responsible for troubleshooting or assisting users with their queries or issues as they arise.

Conclusion

In this way, we hope to greatly expand the functionalities available in Publii, while also maintaining a standard of quality so that Publii remains an inviting, welcoming solution for all users, especially those with less experience of web development.

Submit extension by sending it to:  contact [@] getpublii.com

Through the getpublii.com website, you can download the Publii app free of charge, download free themes or plugins, as well as purchase premium themes or plugins available for a fee.

Now, let's get's down to business. First, the registration data of the Publii app provider and administrator of the getpublii.com (also available at getpublii.eu) website is as follow: TIDYCUSTOMS Boguslaw Mitro, ul. Ludowa 22, 33-380, Krynica- Zdrój, Poland, TIN: 7342553332.

Below you will find the terms and conditions, which include information about the rules for using the service, how to purchase a theme or plugin, access to updates, and technical support.

Remember that you can contact us at any time by writing an e-mail to contact@getpublii.com 

We wish you a pleasant experience with Publii!

Best regards,
Publii Team

1. Definitions
2. Preliminary provisions
3. Technical Requirements
4. Application
5. Free Themes and Plugins
6. Purchasing a Theme or Plugin
7. Updates
8. Technical Support
9. Copyright
10. Withdrawal from the contract
11. Newsletter
12. Contact Form
13. Administrator's Liability and Complaints
14. Privacy
15. Final provisions

1. Definitions

For the purposes of these Terms and Conditions, the following definitions apply:

1. Administrator - TIDYCUSTOMS Boguslaw Mitro, Ludowa Street 22, 33-380 Krynica Zdrój, TIN: PL 7342553332, email: contact@getpublii.com
2. Application – software created by the Administrator to aid in the creation of websites, distributed by the Administrator under the name "Publii",
3. Consumer - a natural person who enters into a contract with the Administrator that is not directly related to the person's business or professional activity,
4. Theme – a set of design files that define the appearance and structure of a website; the Theme controls the visual elements of the website, such as layout, typography, colors, and other style aspects; the Themetypically consists ofHandlebars, CSS and, optionally,JavaScript files; the Theme is used to give a unique style to the website, allowing for quick changes to the appearance without the need to interfere with the content or structure of the website; the Theme constitutes digital content,
5. Plugin – an additional software component that can be installed in the Application to add new functions or extend existing capabilities; a Plugin usually consists of JavaScript files but may also include HTML, CSS, and configuration files; the Plugin constitutes digital content,
6. Entrepreneur with consumer rights (PNPK) – a natural person who enters into a contract with the Administrator that is directly related to the person's business activity, when the content of the Agreement shows that it is not of a professional nature for that person, resulting in particular from the subject of his business activity, made available on the basis of the provisions on the Central Register and Information on Economic Activity (CEIDG) in Poland,
7. Terms - these Terms and Conditions available at: https://getpublii.com/terms-and-conditions/
8. Website - the website operating at: https://getpublii.com, https://getpublii.eu and subdomains of the indicated addresses,
9. User - a natural person with full legal capacity, a legal person, or a legal entity invoking their consumer rights, who are using the Website, including Consumer or Entrepreneur.

2. Preliminary provisions

1. Through the Website, the Administrator provides electronic services to the User, enabling the User to:
   1. browse the publicly - available content of the Website free of charge,
   2. download the Application and free Themes or Plugins free of charge,
   3. purchase a premium Theme or Plugin, download the purchased Theme or Plugin, and use technical support relating tothe purchased Theme or Plugin,
   4. subscribe to the newsletter free of charge,
   5. send a message to the Administrator via the contact form free of charge.
2. Browsing the content of the Website is possible anonymously, i.e., without the need to provide personal data. Purchasing a Theme or Plugin, subscribing to the newsletter, and sending a message using the contact formrequiresproviding personal data necessary to achieve the given purpose.
3. It is prohibited for the User to provide unlawful contentto the Website or Administrator, especially by sending such content through the forms available on the Website.
4. Prices shown on the Website may be expressed in various currencies, depending on the User's location. If the User does not conduct activity as a business entity, the price provided on the Website may include Value-Added Tax. The final gross price is presented at the stage of placing an order.
5. In every case where the User is informed of a price reduction of a Theme or Plugin, the Administrator will display information about the reduced price, as well as information about the lowest price of the Theme or Plugin that applied during the 30 days prior to the reduction. If a given Theme or Plugin has been available for purchase for less than 30 days, the Administrator will display information about the reduced price, as well as information about the lowest price that applied to the Theme or Plugin from the date of release until the day the reduction was applied. 
6. The Administrator makes every effort to ensure that data transmission over the Internet caused via use of the Website is safe, i.e., that the transmitted information is confidential, complete, and accurate. However, the Administrator is not responsible for unauthorized access to the transmitted data resulting from circumstances on the User's side, such as spyware installed on the User's device.
7. To ensure the User's security, the Administrator takes technical and organizational measures appropriate to the degree of threat to the security of the provided services, in particular, measures to prevent unauthorized persons from acquiring and modifying personal data.
8. The Administrator makes every effort to ensure that the Website operatesundisturbed and without interruption.
9. The Administrator is entitled to temporary breaks in the operation of the Website for technical reasons. If the User has a user account on the Website, the Administrator will notify the User about the planned technical outagevia email.
10. Temporary breaks in the operation of the Website may also be unplanned, particularly due to malfunctions and technical failures beyond the Administrator's control.
11. The Administrator takes actions to ensure that the Website functions properly, but cannot guarantee that the User will not encounter various technical problems while using the Website. The User should inform the Administrator about any irregularities or interruptions in the functioning of the Website.
12. The Administrator is not responsible for limitations or technical issues in the IT systems used by the User, which prevent or hinder the use of the Website.
13. The Administrator may at any time decide to suspend or terminate the operation of the Website. The Administrator may also decide at any time to change, withdraw, or add new functions to the Website. The termination of the Website's operation does not deprive the User of any rights resulting from contracts concluded via the Website, in particular, in terms of access to updates and technical support, and those services may be provided outside of the Website. The suspension or termination of the Website's operation also does not affect any licenses granted for the use of the Application, Themes, or Plugins.
14. The Administrator is entitled to enlistthe assistance of third parties in connection with the functioning of the Website, in particular, to ensure the proper functioning, development, and operation of the Website.

3. Technical Requirements

1. To use the Website, it is not necessary for the User's computer or other device to meet any special requirements. The following are sufficient:
   1. Internet access,
   2. a standard and up-to-date operating system (Windows, Linux, Mac OS X),
   3. a standard and up-to-date web browser (Safari, Chrome, Firefox),
   4. an active email address.
2. Use ofthe Application requires its installation on the User's computer with an operating system that meets the requirements described on the Website.
3. Themes and Plugins are compatible only with the Application. The Administrator does not ensure that Themes or Plugins function correctly with any software other than the Application.
4. To ensure the proper functioning of Themes and Plugins, it is necessary to regularly update the Application. The Administrator is not responsible for the incorrect functioning of Themes or Plugins if the User does not use the latest version of the Application.
5. Themes and Plugins are compatible with the latest, stable versions of browsers: Firefox, Google Chrome, Safari, Microsoft Edge, in their newest versions. The Administrator is not responsible for the malfunction of Themes and Plugins in outdated browser versions, or browsers other than those mentioned.

4. Application

1. Through the Website, the User can download a file allowing the installation of the Application on the User's computer.
2. The Administrator provides installation files for different operating systems, according to the list available on the Website.

5. Free Themes and Plugins 

1. Through the Website, the User can download Themes or Plugins which the Administrator has decided to distribute free of charge.
2. The Administrator independently decides which Themes or Plugins are available for free download.

6. Purchasing a Theme or Plugin

1. Through the Website, the User can purchase Themes or Plugins, which the Administrator has decided to sell.
2. The Administrator independently decides which Themes or Plugins are available for purchase.
3. Purchasing a Theme or Plugin requires the filling in and submission ofan order form available on the Website, leading to the establishmentof a contract with the Administrator for the delivery of digital content in the form of a Theme or Plugin.
4. The price for a Theme or Plugin is payable in advance before the delivery of digital content via PayPal or Stripe.
5. If the User wants to receive an invoice, they must select the appropriate checkbox in the order form. In such cases, the invoice is delivered electronically. To access the invoice, the User must log into their account on the Website, then enter the "User Panel." The Administrator will inform the User about the issuing of an invoiceby sending a message to the email address assigned to the User's account.
6. If the User has an individual user account on the Website, they are required to log in to this account before placing an order. If the User does not have such an account, it is automatically created as a result of placing an order as necessary for the delivery of digital content. Instructions for logging into the account are sent to the email address provided by the User.
7. The Theme or Plugin is delivered to the User in the form of digital content immediately after payment,via the individual user account on the Website, to which the User logs in through the Website.
8. The User can download the Theme or Plugin and available updates for the Theme or Plugin for one year from the date of payment for the Theme or Plugin (access period). The User may extend the access period. Renewal is possible within 60 days of the end of the access period and is for one year. After the deadline for extending the access period, regaining access to download the Theme or Plugin or updates for the Theme or Plugin requires the User to repurchase the Theme or Plugin.
9. The Administrator may send reminder messages to the User's email addressnotifying them about the loss of access to the Theme or Plugin.
10. The User has access to technical support regarding the Theme or Plugin under the terms specified in §8 of the Terms and Conditions.

7. Updates

1. The Administrator may provide updates for the Application, Themes, or Plugins.
2. Updates may affect the functions of the Application, Themes, or Plugins.
3. The Administrator independently decides on the direction of development of the Application, Themes, or Plugins, including adding, modifying, or removing functions of the Application, Themes, or Plugins, while preserving the rights previously acquired by the User based on the contract established with the Administrator.
4. Updates for the Application are free of charge.
5. Updates for free Themes or Plugins that the User can download through the Website are available free of charge.
6. Updates for Themes or Plugins purchased by the User are payable. The price paid by the User for the purchase of a Theme or Plugin, or for extending the access period mentioned in §6, paragraph 8 of the Terms and Conditions, includes one year of access to updates for the Theme or Plugin counted from the day of payment.
7. Access to updates may be provided through the Website or via an alternative method, such as via email or file-sharing platforms.

8. Technical Support

1. Technical support is payable. The price paid by the User for purchasing a Theme or Plugin includes three months of access to technical support counted from the dateof payment. Extending the access period mentioned in §6, paragraph 8 of the Terms and Conditions, does not include an extension of access to technical support.
2. Technical support includes assistance in installing, configuring, and using the Theme or Plugin. The Administrator is not obligated to provide support in terms of handling themes or addons purchased from third parties.
3. Technical support consists solely of responding to User's questions sent electronically, using the Website's functions or email to the designated email address provided by the Administrator. In particular, the Administrator is not obligated to:
   1. undertake any actions leading to changing the way the Theme or Plugin operates or looks,
   2. ensure compatibility of the Theme or Plugin with software from third parties,
   3. introduce changes to the graphic design and functionalities of the Theme or Plugin justified by individual needs of the User.
4. The Administrator responds to questions within 5 business days.
5. If the User needs technical support after the period mentioned in §8, paragraph 1 of the Terms and Conditions, or requires assistance from the Administrator beyond the scope of technical support, they may use individual services provided by the Administrator available at: https://getpublii.com/customization-service/, after agreeing on the conditions of service in advance, especially the financial obligations stipulated for the provision of these services.

9. Copyright

1. Copyright to the Application, Themes, and Plugins belongs to the Administrator, though the Application, Themes, and Plugins may contain elements licensed through third parties.All such elements are properly marked in the information accompanying the Application, Theme, or Plugin along with a reference to the license terms. The User is obligated to comply with the terms of these licenses. The Administrator is not responsible for any consequences caused by the User's violation of these license terms.
2. Use of the Application is under a license whose terms the User accepts during the Application's installation.
3. Use ofa Theme or Plugin is under a license whose terms are described below.
4. From the instant a download of a Theme or Plugin is initiated, the Administrator grants the User a non-exclusive license to use the Theme or Plugin in creating websites using the Application and publishing the websites created in this way on the Internet.
5. The license is granted for an indefinite period. The Administrator commits not to exercise the right to terminate the license except in cases where the User violates the terms of the granted license and infringes the Administrator's copyright property rights, and does not cease the violation despite the Administrator's request. In case of violating the license terms, the Administrator can terminate the license with a one-month notice period, effective at the end of the calendar month.
6. As part ofthe use of the Theme or Plugin, the User may make changes to it as justified by the needs of their website.
7. The User is entitled to grant further licenses (sub-licenses) to use the Theme or Plugin to their clients. The User may also use the purchased Themes or Plugins for commercial purposes on behalf of their clients. However, resale or making available for download any Themes or Plugins is prohibited.
8. The license is unlimited in terms of territory, meaning that the User may use the Theme or Plugin worldwide.
9. The Website's content contains works protected by copyright law. The User is entitled to use these works only within the scope of permitted personal use. Violating copyright to these works, especially by further distributing them without the Administrator's consent, may result in civil or criminal liability.

10. Withdrawal from the contract

1. A Consumer or Entrepreneur may withdraw from the contract concluded with the Administrator via the Website within 14 days of its establishment. A statement of withdrawal from the contract may be submitted in any form, in particular via email. The Consumer or Entrepreneur may use atemplate withdrawal form for this purpose.
2. To maintain the deadline for withdrawal from the contract, it is sufficient for the Consumer or Entrepreneur to send information regarding the exercisingof the Consumer's or Entrepreneur's right to withdraw from the contract before the withdrawal period expires.
3. The right to withdraw from the contract does not apply to contracts for the supply of digital content which is not supplied on a tangible medium for whichthe Consumer or Entrepreneur is obliged to pay a price, in cases wherethe Administrator has started the provision with the User's explicit and prior consent, and the User was informedbefore the start of the provision that after the completion of the provision by the Administrator, they will lose the right to withdraw from the contract, and the User accepted the terms, and the Administrator provided the User with confirmation as referred to in Article 21, paragraph 2 of the Consumer Rights Act.
4. In the event of withdrawal from the contract, the Administrator returns to the Consumer or Entrepreneur all payments received from the Consumer or Entrepreneur, immediately, and in any case no later than 14 days from the day on which the Administrator was informed about the decision to exercise the right to withdraw from the contract. The refund is made using the same payment methods that were used in the original transaction unless the Consumer or Entrepreneur has explicitly agreed to a different solution. In any case, the Consumer or Entrepreneur does not incur any fees in connection with this refund.
5. In the event of withdrawal from the contract, the User is obliged to stop using the digital content and making it available to third parties. The User also loses the possibility to download the digital content, access updates for the digital content, and the possibility to use technical support. Moreover, the license mentioned in §9 of the Terms and Conditions expires.

11. Newsletter

1. Through the Website, the User can subscribe to the newsletter.
2. The newsletter involves sending messages to the email address provided by the User, containing information about new products, promotions, products, or services related to the Application.
3. Receiving the newsletter incurs no charges.
4. The User may unsubscribe from receiving the newsletter at any time by clicking the designated link contained in the content of each message sent as part of the newsletter or by contacting the Administrator.
5. The Administrator independently decides on the frequency  of the sending of the newsletter.
6. The Administrator may stop sending the newsletter at any time.

12. Contact Form

1. The User may use the contact form available on the Website to send a message to the Administrator.
2. Use ofthe contact form is free of charge.
3. The Administrator will respondto messages within 5 business days.

13. Administrator's Liability and Complaints

1. The Administrator is obligated to provide electronic services with due diligence and to deliver digital content in accordance with the contract.
2. The conformity of digital content with the contract is assessed according to the provisions of the Consumer Rights Act.
3. The Administrator is liable for the lack of conformity of provided digital contentwith the contract that existed at the time of its deliveryor manifested withintwo years from that moment.
4. If the digital content is not in conformity with the contract, the Consumer or Entrepreneur maydemand the bringing  of the digital content into conformity with the contract.
5. If bringing the digital content into conformity with the contract is impossible or would require excessive costs for the Administrator, they may refuse to bring the digital content into conformity with the contract.
6. The Administrator brings the digital content into conformity with the contract within a reasonable time and without excessive inconvenience for the Consumer or Entrepreneur, taking into account its nature and the purpose for which it is used.
7. If the digital content is not in conformity with the contract, the Consumer or Entrepreneur may submit a statement on reducing the price or withdrawing from the contract if:
   1. the Administrator refused to bring the digital content into conformity with the contract,
   2. the Administrator did not bring the digital content into conformity with the contract,
   3. the lack of conformity of the digital content with the contract persists despite the Administrator's attempt to bring the digital content into conformity with the contract,
   4. the lack of conformity of the digital content with the contract is significant enough to justify reducing the price or withdrawing from the contract without first exercising the right to bring the digital content into conformity with the contract,
   5. from the Administrator's statement or circumstances, it is clear that they will not bring the digital content into conformity with the contract within a reasonable time or without excessive inconvenience for the Consumer or Entrepreneur.
8. The Consumer or Entrepreneur cannot withdraw from the contract if the digital content is provided in exchange for payment of a price, and the lack of conformity of the digital content with the contract is insignificant. It is presumed incases where a complaint is made, that the lack of conformity of the digital content with the contract is significant.
9. The User may submit a complaint regarding issues related to the functioning of the Website or the performance of the contract. To facilitate the Consumer or Entrepreneur in exercising the rights related to the Administrator's liability for conformity of digital content with the contract, the Administrator has prepared a model complaint form that the Consumer or Entrepreneur may use.
10. Complaints maybe sent via email.
11. Complaints are processed on an ongoing basis, but will be processed no later than within 14 days from the day of receipt of the complaint.
12. The response to the complaint is sent in the same form in which the complaint was delivered to the Administrator.
13. The Consumer has the possibility of using out-of-court complaint handling and redress mechanisms. Among other things, the Consumer has the option to:
    1. apply to a permanent consumer arbitration court with a request to resolve the dispute arising from the concluded contract,
    2. apply to the regional Trade Inspection inspector with a request to initiate mediation proceedings regarding the amicable settlement of the dispute between the User and the Administrator,
    3. use the assistance of a county (municipal) consumer ombudsman or a social organization whose statutory tasks include consumer protection.
14. For more detailed information on out-of-court complaint handling and redress mechanisms, the Consumer may visit the website of the Polish Office of Competition and Consumer Protection (UOKiK).
15. 15. The Consumer may also use the EU's ODR platform, which serves to resolve disputes between consumers and entrepreneurs seeking an out-of-court settlement of a dispute regarding contractual obligations arising from an online sales contract or service contract.

14. Privacy

1. The Administrator of the User's personal data is the Administrator.
2. The Website uses cookies and other similar technologies.
3. Details regarding the processing of personal data and information collected using cookies or other similar technologies are described in the privacy policy available on the Website.

15. Final Provisions

1. The Administrator reserves the right to introduce and withdraw offers and promotions, and to change prices on the Website without prejudice to the rights acquired by the User, including, in particular, the terms of contracts establishedbefore the change.
2. The law applicable to contracts concluded through the Website is Polish law. This does not deprive the Consumer of the possibility to invoke rights arising from the law of the country in which they reside.
3. Any disputes related to contracts concluded through the Website shall be resolved by the Polish common court with jurisdiction over the Administrator's place of business. This provision does not apply to Consumers and Entrepreneurs, in whose case the choice of court results from the provisions of the law.
4. The Administrator reserves the right to introduce changes to these Terms and Conditions for important reasons such as changes in law, and technological or business changes.Contracts establishedbefore the amendment to the Terms and Conditions are governed by the Terms and Conditions in force on the date of the establishmentof the contract.
5. These Terms and Conditions in their current wording are effective from February 14, 2024.
6. Archived versions of the terms and conditions:
   • Terms and conditions (valid until February 14, 2024)
   • Terms and conditions (valid until February 04, 2021)