Skip to content

Privacy ​

Sveltia CMS doesn’t collect any personal data, so we don’t have a formal privacy policy. However, we do receive some personal information when you contact us or interact with us on community platforms. This page describes our privacy practices across the product and the project, for transparency purposes.

Application Data Handling ​

Sveltia CMS is not a service but a client-side application that runs in the web browser. No account is needed to use the app, but users do need to authenticate with their Git hosting provider to read and write remote data. All content is stored in the Git repository. No data is sent to any server operated by us.

Depending on your CMS configuration, you will need to use an OAuth application hosted by the site owner or a third party, such as Netlify or Cloudflare, to retrieve an access token from the Git hosting provider. Alternatively, users can provide an access token directly on the CMS’s sign-in page. In any case, the token is stored in the browser’s local storage, and subsequent API requests are made directly between the browser and the Git hosting provider.

The CMS also integrates with various third-party services, including stock photo providers and translation services. These are “bring your own key” (BYOK) features that are entirely optional. Users provide their own API keys for these services, which are stored in the browser’s local storage, and API requests are then made directly between the browser and the relevant service providers. For these services, please refer to their respective privacy policies.

Content Delivery Networks ​

The CDN builds of Sveltia CMS load some files from public content delivery networks (CDNs) as needed: fonts from jsDelivr, and the app itself, admin interface translations, additional libraries, image decoders and syntax highlighting definitions from UNPKG. The CMS also checks UNPKG periodically for a new version. These requests contain no content or credentials, but like any web request, they reveal the user’s IP address to the CDN provider.

If you’d rather not rely on third-party CDNs, for example to avoid listing them in your site’s privacy policy under the GDPR, use the npm package instead. It serves all these files from your own site and doesn’t check for updates. See CDN or npm Package for the differences between the builds.

Either way, the CMS contacts other services only when the configuration requires them:

GitHub Repository Monitoring ​

Although Sveltia CMS does not have built-in analytics, we constantly monitor public GitHub repositories to understand how the CMS is being used in the real world. This involves analyzing configuration files, API usage patterns, commit history, and other publicly available data. We use this information to improve the product, expand the showcase, and share our insights.

Community and Communication ​

We interact with users on various channels, including:

What We Receive ​

Through these channels, we may receive personal information such as:

  • your name, username and profile information
  • your email address, if you email us or a platform makes it available to maintainers and administrators
  • the content of your posts and messages, including any attachments

How We Use It ​

We use this information only to:

  • respond to your questions, reports and feedback
  • investigate and fix issues, including security vulnerabilities
  • moderate our community spaces
  • credit you in release notes, if you report a vulnerability and agree to be credited

We don’t sell or share your information. We don’t add you to mailing lists or use your information for marketing.

Third-Party Platforms ​

GitHub, Discord and Bluesky are operated by their respective companies, not by us. They handle your data under their own privacy policies and terms of service. Most of what you post there is public and may be indexed by search engines.

When reporting a bug or asking for help, don’t share access tokens, API keys, private repository content or other sensitive information. Redact them from your configuration files, screenshots and logs before posting.

Your Choices ​

To ask us to delete your email correspondence or other information we hold about you, email us at [email protected]. To remove your posts or accounts on third-party platforms, use the platform’s own tools.

Web Analytics ​

We use Cloudflare Web Analytics to collect anonymous statistics about visitors to this site and the demo site. This service doesn’t use cookies and complies with the GDPR. No personal data is collected or stored.