Privacy Policy

Last updated: August 2, 2026

This policy describes how Splikit (splikit.com) handles data in actual product flows.

1) Core principle

The core splitter is designed for local browser processing so image content does not need to be sent to our servers for the split operation.

2) Data map by feature

A. Image splitting flow

When you upload and split an image in the main tool:

B. Local preferences

We store limited settings in browser storage for convenience.

Current implementation uses browser storage for:

These values stay in your browser unless you clear site data or browser storage.

C. Analytics and diagnostics

To understand reliability and UX issues, we use a third-party measurement script currently including:

This tool may process technical metadata like page path, device/browser info, and interaction events.

We may also record sampled first-party tool-performance events, such as upload started, preview rendered, export completed, error category, Core Web Vitals, and resource-size buckets. These records do not include uploaded image content, file names, email addresses, or exact image dimensions.

When an image fails to load, we may also store technical forensic metadata only (for example: empty-file flag, file-header signature class such as “looks like JPEG/PNG”, whether the declared MIME type roughly matches that signature, and which browser read methods were tried). This still does not include the photo itself, file names, or pixel data.

If image loading fails, you may see an optional control to send that failed file for debugging. This is off by default and only runs if you choose it. When you opt in:

Normal split, preview, and download flows still run in the browser and do not upload your image unless you use this optional report control (or another feature that explicitly asks you).

D. Feedback submissions

When you send feedback from the in-site form, the message is processed by our self-hosted feedback backend on Cloudflare Workers/D1 (feedback-hub.pvb-259.workers.dev). Submitted fields may include your email, message, page URL, language, and basic diagnostic context used to route and reply to feedback. Email notifications are sent through the configured Cloudflare email service.

E. Account data

The public splitter does not require user accounts for the core image splitting flow.

3) What we do not sell

We do not sell your personal data.

4) Why we process limited data

We process limited technical/support data to:

5) Retention

6) Third-party processors

We rely on third-party providers for infrastructure, analytics, diagnostics, and form handling. Each provider has its own policies and terms.

Current third-party processors used by public product flows include:

7) International processing

Some providers may process data in multiple regions. By using the service, you acknowledge this cross-region processing where legally permitted.

8) Your rights and requests

Depending on your jurisdiction, you may request access, correction, deletion, or objection for personal data processed through support channels.

For privacy requests:

9) Children’s privacy

The service is not intended for children under 13, and we do not knowingly collect personal data from children through core flows.

10) Policy updates

We may update this policy as the product evolves. The current version is always published here.

11) Contact

For privacy questions: