Privacy policy

Effective and last updated: August 24, 2026 · Maintainer: khs2325

This policy explains the privacy boundary of the production site at sprite-to-aseprite.pages.dev. The core conversion design keeps selected artwork and generated output bytes in the browser. It does not make unrelated hosting requests or voluntary external sharing disappear.

Artwork processing

Files you select or drop are exposed to the page through browser APIs such as File, Blob, typed arrays, image decoding, canvas, and object URLs. Parsing, validation, preview generation, and selected-output encoding run in the tab. The project has no endpoint that receives source artwork for conversion and no remote image-processing fallback.

The generated output files are offered through local browser downloads. The application does not upload them after export.

Static hosting requests

Cloudflare Pages serves the site's HTML, JavaScript, CSS, and other public assets. Loading or navigating the site therefore creates ordinary web requests. The hosting provider may process standard request information—such as IP address, user agent, referrer, requested path, and timing—according to its service and configuration. Selected artwork, embedded project pixels, and generated output should not be part of those static-resource requests.

External links and support

The site links to the public GitHub repository and may link to an optional external support provider. Following a link leaves this site and is governed by that service's terms and privacy policy. Support is optional and does not unlock hidden converter functionality.

Attaching files to a GitHub issue, email, cloud drive, chat, validator, or support page is a separate voluntary disclosure. Do not share private artwork when reporting a bug; make a minimal synthetic reproduction instead.

Advertising

Public pages currently contain Google AdSense account-verification metadata. The repository does not currently load a live AdSense script or display ad units. If advertising is activated later, this policy and the deployed behavior should be reviewed together before launch.

If Google advertising is enabled, the browser may share information such as the visited page URL, IP address, and device or browser information with Google, and Google may set or read cookies for delivery, measurement, fraud prevention, and—where permitted—personalization. Google explains this processing in How Google uses information from sites or apps that use its services.

Third-party advertising vendors, including Google, may use cookies to serve ads if their advertising services are enabled. Google may use advertising cookies to serve ads based on prior visits to this or other sites. Users can manage personalized advertising through Google Ads Settings. These statements describe possible future advertising behavior; they do not state that live ads or advertising cookies are currently active.

Before sending AdSense ad requests for visitors in the European Economic Area, the United Kingdom, or Switzerland, the maintainer must configure a Google-certified consent management platform and provide the required choices. No consent banner is shown now because this deployment does not make AdSense ad requests.

Analytics, error reporting, and payments

The current repository does not add an analytics service, remote error-reporting script, conversion telemetry, or direct payment processing. External hosting and support providers may operate their own systems when their pages are requested. No secret payment information should be entered into this static converter page.

Changes and questions

Material changes to hosting, analytics, advertising, or artwork handling should be reflected here before deployment. For a technical explanation of the current boundary, read How browser-local conversion works. Questions or corrections can be raised through the public issue tracker without attaching private artwork.