Privacy Policy

Last updated: October 8, 2026

This policy describes how Image Splitter handles data in actual product flows. It covers:

1) Core principle

The core splitter — on the website and in the Chrome extension — is designed for local browser processing so image content does not need to be sent to our servers for the split operation.

Chrome extension (Split Image)

Chrome Web Store reviewers and users: this section is the disclosure for the Split Image extension. The rest of this page covers the website.

What the extension does

The extension crops and splits one photo into a grid (for example 3×3 or a 1-row carousel) on your device. You can drop a file into the side panel or popup, or right-click an image on a webpage and choose “Split this image.” Tiles are generated in the browser and saved with your browser’s download dialog. The toolbar can also open the splitter in a tab or a window. After a split, IG Preview can show those tiles on a mock profile grid. If you then open Instagram, a small “Split preview” control on instagram.com lets you hover a profile grid and see the same tiles. That script runs only on Instagram.

What the extension does not collect

The extension does not:

Image bytes are processed in memory on your computer. We cannot see the photo you split because it never reaches us.

Permissions and why they exist

Chrome requires every permission to be explained here:

PermissionWhy it is requestedWhat it is not used for
contextMenusAdds the “Split this image” item when you right-click an image, plus Open in tab / Open in window on the toolbar iconWatching other menu use, or reading the page
sidePanelOpens the splitter beside the current tab when you click the toolbar iconInjecting into the page, or reading the site you are viewing
storageRemembers your last grid size on this browser; briefly holds an image URL you right-clicked so the side panel can open it; and, after you split, keeps those tile images on this browser for a short time so Instagram hover-preview can show themSyncing photos to our servers, or tracking you
Optional access to the site that hosts the image you clickedOnly if you right-click an image and the extension needs to fetch that image file so it can split it locally. Chrome asks you to allow this for that site. Drag-and-drop / file-picker splits do not need this permissionScraping the rest of the site, injecting ads, tracking you across the web, or reading cookies
instagram.com content scriptAfter you split tiles and open Instagram, adds a “Split preview” toggle on profile grids so you can hover and see your tilesReading your feed, DMs, cookies, or running on any other website

If you refuse the optional site access, the right-click path may fail for that image. You can still split a file you choose yourself in the popup.

If you open the website from the extension

The side panel includes links to splitimage.im (the full editor and related tools). Following a link is a normal website visit. The website sections below then apply (including analytics and diagnostics on the site). That click does not send your split photo to us.

On first install, the extension opens splitimage.im in a new tab so you can find the website editor. That visit is the same as typing the address yourself. Removing the extension later may open the contact page once; we do not receive your photos that way.

Uninstall

Removing the extension from Chrome removes it from your browser. Chrome may open the contact page once. We do not keep an extension-side copy of your photos on our servers, because we never received them.

2) Data map by feature

A. Image splitting flow (website)

When you add and split an image in the main website tool:

The Chrome extension uses the same local model. See Chrome extension.

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 (website only)

These tools run on the website. They are not bundled in the Chrome extension.

To understand reliability and UX issues on the site, we use third-party measurement/diagnostic scripts currently including:

These tools 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 request is processed through a form endpoint (currently api.web3forms.com) and includes the fields you submit (such as email and message).

E. Account data

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

If you sign in (Google or email) we store your name, email, hashed password if you chose email login, session cookies, credit balance, and Stripe customer id. That account is used for daily AI trials, paid credits, My works, and billing.

F. Paid AI tools (upload or prompt)

These pages do send data to our servers so we can run a safety check and a named model:

Local split, PDF, rotate, flip, blur, and similar tools still run in your browser and do not use this upload path. The full model table is in the Terms of Service — AI models.

When you use a paid AI tool:

If a safe photo or prompt is blocked, use Feedback in the top bar or email contact@splitimage.im.

Google sign-in, email accounts, and paid credit packs apply only to this AI path, not to local split tools.

G. Payments

Packs ($5.99 / 150 credits) and the monthly plan ($9.99 / 300 credits) are charged by Stripe. Stripe receives the email and payment details you enter on Checkout. We store the Stripe customer id, session/invoice ids, plan, amount, and paid status so we can grant credits and handle refunds. We do not store card numbers on splitimage.im.

Refund rules are in the Terms of Service — billing and refunds. Email refund requests to contact@splitimage.im.

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 website product flows include:

The Chrome extension does not load these processors. If you later open splitimage.im in a tab, the website processors above may apply to that visit.

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. We do not allow child sexual exploitation material. Report suspected CSAM as described in the Terms — user reporting section (describe the URL and time; do not email illegal image files).

10) Policy updates

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

11) Contact

For privacy questions, refunds, and content reports:

That address is also in the site footer on every page.

Sign in to see your account

Credits, saved enhances and billing stay with this account. Sign in with email or Google.

Forgot password?

or

Continue with Google