Privacy Policy

Last updated: November 17, 2026

This Privacy Policy explains how SpriteSplit ("we", "us") at https://spritesplit.com handles information when you use the website or the SpriteSplit Android app.

Your images

All image processing happens locally in your web browser. Images you open, paste or drop into SpriteSplit are not uploaded to our servers or to anyone else. We cannot see, store or share them.

Settings stored on your device

We save your tool settings (such as grid size and file naming) in your browser's local storage so they are remembered next time. This data stays on your device, and you can clear it in your browser settings.

So that the tools open quickly and work offline, your browser also keeps a copy of the website's own pages, scripts and icons (a "service worker" cache). It never contains your images. Clearing the site data in your browser removes it.

My photos (your photo purse)

Photos you keep in 👛 My photos are saved only in your browser's storage on this device (IndexedDB), at their original size, so you can use them again in any tool. They are never uploaded to SpriteSplit or anyone else. Delete them in the My photos panel (one at a time or Clear all); clearing this site's data in your browser also deletes them.

The Android app

The SpriteSplit app on Google Play (package com.spritesplit.app) opens this same website in a secure Chrome window, so everything on this page applies to it too. The app asks for no special Android permissions, has no account or sign-in, and does not collect contacts, location, camera or microphone data. Photos you pick are read on your phone only. Uninstalling the app removes its data from your phone.

Google Drive backup (optional)

Some business tools, such as the customer discount card, let you back up your own list to your Google Drive. This is optional and only happens if you tap Connect Google Drive and allow it in Google's window.

  • What we ask for: only the permission drive.appdata. It lets SpriteSplit use its own hidden app folder in your Drive. It does not let SpriteSplit see, open or change any of your other Drive files.
  • Where your data goes: the backup goes directly from your browser to your own Google Drive. SpriteSplit has no server for this and never receives, sees or stores your backup or your Google sign-in. The access token from Google is kept only in your browser's memory while the page is open.
  • Counter Billing backups are locked: Counter Billing locks (encrypts) every Google Drive backup with a backup password the shop chooses, before it leaves the browser (AES-GCM, 256-bit, with a key made from the password by PBKDF2-SHA256). The password is never stored or sent anywhere; only the key made from it is kept on the shop's own device, so daily backups need no typing. Without the password nobody can open these backups, not even SpriteSplit, and we cannot recover a lost password.
  • What we keep on your device: only a note that you connected Drive and when you last saved, in your browser's local storage (and, for Counter Billing, the backup key described above).
  • How to disconnect: tap Disconnect in the tool, or go to your Google Account, then Security, then Third-party connections (apps with access to your account), choose SpriteSplit and remove its access. To delete the backup itself, open Google Drive on the web, go to Settings, then Manage apps, find SpriteSplit and choose Delete hidden app data.
  • Google API Services User Data Policy: SpriteSplit's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The data is used only to provide the backup and restore feature you asked for. It is never sold, never used for advertising, never shared with anyone, and no human reads it.

Print Drop (sending files to a print shop)

With Print Drop, a customer sends files from their browser straight to a print shop's browser over a direct, encrypted connection (WebRTC). The files are never uploaded to SpriteSplit or stored on any server. To help the two browsers find each other, a public connection service (the PeerJS cloud server) and a Google STUN server see only technical connection details, such as a random counter ID and network addresses, never the files, names or notes. On the shop's computer the files are kept only in the open page's memory and are deleted after the shop taps Printed ✓, after the time the customer chose (after printing, 30 minutes or 1 hour), or when the page is closed. The shop's browser stores only its counter ID, shop name and settings, and, for its "Done today" list, each job's token number, the name the customer typed, the number of files and the times (never the files themselves); this list clears itself every morning at 4 am or when the shop taps Clear. The customer's browser remembers the last shop and the name they typed. If a shop fills in its optional shop card (a banner photo, services and prices, an offer line, timings, a phone number and a Google Maps link), the card is kept only in the shop's browser and is sent from the shop's computer straight to the phones of customers who scan its QR; it is not stored on our servers.

To show customers a ✓ Verified badge, the shop's browser makes its own signing key and keeps it on that computer; only the public part of the key is shared with the customer's phone, which uses it to check it reached the real shop computer. The customer's browser keeps a random sender ID (no name or number) that goes with each job, so a shop can block one sender for the day; the shop's browser keeps the IDs it blocked until the next day. Report misuse: [email protected].

Document Drop (customers sending documents to an agent or service centre)

With Document Drop, a customer sends documents (for example Aadhaar, PAN, photos, bank statements or certificates) from their browser straight to the browser of the office that shows the QR, over a direct, encrypted connection (WebRTC). The documents are never uploaded to SpriteSplit or stored on any server, and we never see them. As with Print Drop, a public connection service (the PeerJS cloud server) and a Google STUN server see only technical connection details, never documents, names or checklists. On the office computer the documents are kept only in the open page's memory and are deleted when the office taps Done ✓, after its delete time (30 minutes to 4 hours after the customer's last document, or the customer's shorter choice), or when the page is closed. Documents the office saves (as a ZIP or into a folder) are then on the office's own computer. The office's browser keeps its counter ID, name, settings and checklists, and for the day each open token's number, the customer name typed, the service and the checklist (never the documents), plus a "Done today" list that clears itself at 4 am and daily counts for its reports. The customer's browser remembers the last office, the language and the name they typed. The office that collects the documents decides why and how it uses them and is responsible for them under the law that applies to it (in India including the Aadhaar Act, 2016 and its regulations and the Digital Personal Data Protection Act, 2023).

Shop reports (Order Drop, Print Drop and Photo Drop)

The 📊 Reports section of Order Drop, Print Drop and Photo Drop keeps only counts and totals on the shop's own device (in the browser's storage) for 400 days: for example the time, token number, items and bill total of an order, the number of files, pages and copies of a print job, or the number of photos and the amount paid. No customer files, file names, names or phone numbers are kept. To count repeat print customers, the random sender ID is turned into a scrambled code (a salted hash) that cannot be turned back into the ID. None of this is sent to SpriteSplit (only the anonymous daily count described below under Anonymous daily count from business tools). If the shop chooses Back up to Google Drive, the report goes straight from the browser to the shop's own Google Drive, as described above; the shop can also download a backup file instead.

Khata Book (udhaar register for shops)

The Khata Book keeps the shop's customers (name, optional phone number and note), their credit and payment entries, optional bill photos and the shop's own details (name, phone, UPI ID) only on the shop's device, in the browser's storage. Nothing is sent to SpriteSplit. The data leaves the device only when the shop chooses to: a WhatsApp reminder opens WhatsApp with the message for the shop to send, a statement PDF is shared by the shop, and a backup goes to a file the shop downloads or to the shop's own Google Drive as described above. The optional PIN is stored only as a salted scrambled code (SHA-256) on the device.

Counter Billing (billing counter for stalls and shops)

Counter Billing keeps items, bills and reports only on your device, in the browser's storage (IndexedDB): the shop's details (name, phone, address, UPI ID, GSTIN or VAT number), the menu with prices and any item photos the shop adds, every bill (items, amounts, tax, payment method and, only if the shop types them, the customer's name and phone number), voids with their reasons, day-close reports and an activity log. None of this is sent to SpriteSplit (only the anonymous daily count described under Anonymous daily count from business tools). The data leaves the device only when the shop chooses to: printing, a WhatsApp bill (WhatsApp opens with the text for the shop to send), a receipt QR or link (the bill is packed into the link itself and opens on the customer's phone without any server), a downloaded PDF, picture or CSV, or a backup to a file the shop downloads, to a folder on the shop's computer, or to the shop's own Google Drive as described above. Google Drive backups are always locked with the shop's backup password; backup files and folder copies are locked too when the shop turns that on (it is on by default in pharmacy mode). SpriteSplit cannot read these backups or recover the password. UPI QR codes are made on the device; SpriteSplit never sees or handles payments. The optional owner PIN is stored only as a salted scrambled code (SHA-256) on the device and is not included in backups.

Several counters. When a shop links a second phone, tablet or PC as another counter, the counters talk to each other directly, browser to browser, over an encrypted connection (WebRTC with DTLS; the main counter proves its identity with a key and both screens show the same 3 pictures). A public connection service (PeerJS) and Google's STUN servers only help the two devices find each other; bills, menu, prices, staff and orders go straight from one device to the other and are not stored by SpriteSplit or anyone else. Staff PINs travel only as salted scrambled codes over this encrypted connection so staff can log in on every counter; they are never put in backup files. The main counter keeps a copy of every bill from every counter.

Owner view. If the shop pairs the owner's phone, the main counter puts a copy of its bills and reports in the shop's own Google Drive (the hidden app folder of the Google account the shop signed in with), encrypted (AES-GCM, 256-bit) with a key that only the owner phones paired at the counter get. The files in Drive contain only that encrypted data plus a version number and time; even someone with the shop's Google account cannot read them without a paired phone, and removing a phone makes a new key at once. SpriteSplit never sees this data. While the owner's phone can reach the counter, today's numbers go to it directly over the same kind of encrypted connection. The owner view on the phone is read-only and keeps what it downloaded only in that phone's browser.

If the shop turns on Café mode, the same device also keeps the tables and their running orders, kitchen tickets, staff names and roles (each staff PIN only as a salted scrambled code, never put in a backup), shift cash counts and cash in / out entries with their reasons, credit notes (refunds), the names and phone numbers the shop types for customers who buy on credit, table reservations, and stock quantities. All of this stays on the device and goes into the shop's own backup like the bills; none of it is sent to SpriteSplit. When the shop chooses to write a credit sale into Khata Book, it is saved in Khata Book's storage on the same device. A kitchen screen (another phone or tablet the shop links by scanning a QR) receives only the open kitchen tickets (table, items, quantities and notes, no prices or customer details) directly from the counter's browser over an encrypted WebRTC connection; as with Order Drop, the PeerJS connection service and a Google STUN server see only technical connection details, never the tickets. The kitchen device keeps the last tickets in its own browser storage so they stay on screen if the connection drops.

Pharmacy mode. If a medical store turns on Pharmacy mode, the same device also keeps the shop's drug licence numbers and the registered pharmacist's name and registration number (printed on every bill), the medicine list (brand, salt, manufacturer, HSN, GST rate, pack, MRP, schedule, rack, barcode), batches with expiry dates and stock, purchases and returns to suppliers with the suppliers' names, GSTIN, licence numbers and phone numbers, and, for prescription medicines (Schedule H and H1), the patient's name, age and address and the doctor's name and registration number or clinic that the pharmacist types for that bill. These prescription details are health-related personal data: they are saved only inside that bill on the shop's device and in the shop's own backups (a backup file the shop downloads, a backup folder on the shop's computer, the backup copy in the shop's own Google Drive, and the copy on the shop's main counter when several counters are linked). These backups are encrypted with the shop's own backup password (always for Google Drive; for backup files and folder copies by default in pharmacy mode). SpriteSplit never has the password, cannot read the backups and cannot recover a lost password. A CSV of the H1 register that the shop exports is a plain file the shop must keep private. They are never sent to SpriteSplit, never put in WhatsApp bills or receipt QR links, and are left out of the owner view unless the owner turns that on at the main counter. The shop, not SpriteSplit, decides what to record and is responsible for that data under the Digital Personal Data Protection Act, 2023 and the drug laws. Price lists the shop imports (CSV or Excel files) are read on the device; to read an Excel file the browser loads the open-source SheetJS library from cdnjs once, and the file itself is never uploaded.

Photo Drop and Photo Studio Drop (photographers and studios sending photos to customers)

With Photo Drop, a photographer sends photos from their browser straight to a customer's browser over a direct, encrypted connection (WebRTC). The photos are never uploaded to SpriteSplit or stored on any server. To help the two browsers find each other, a public connection service (the PeerJS cloud server) and a Google STUN server see only technical connection details, such as a random ID and network addresses, never the photos or names. On the photographer's device the photos are kept only in the open page's memory and are cleared when the photographer taps Done, after one hour (event galleries: when the event is ended or the page is closed), or when the page is closed. The photographer's browser stores only their name, phone number, UPI ID, logo and settings, which are shown to their customers. The customer's browser keeps the received photos only in the open page until the customer saves them, and remembers a random ID for that photo link so their ❤ picks stay the same if they reconnect. With Photo Studio Drop, which works the same way, a photo studio also uses a fixed counter QR: the customer types a token number and a 4-digit PIN, which are checked only by the studio's open page and are never stored or sent to SpriteSplit; the PIN is never put in a link. If the photographer or studio sends a customer's link by WhatsApp, the mobile number it types is kept only in that open page's memory for that customer and is passed to WhatsApp (wa.me) when the studio taps Send on WhatsApp; it is not saved or sent to SpriteSplit.

DashDrop (between two phones)

With DashDrop, photos, videos and files go from one phone's browser straight to another phone's browser (for example iPhone to Android), over a direct, encrypted connection (WebRTC). They are never uploaded to SpriteSplit or stored on any server. As with PC Drop, a public connection service (the PeerJS cloud server) and a Google STUN server see only technical connection details, never the files or their names. Big received files are kept in the browser's own private storage on that phone until you save them, and are cleared when you leave. In TV mode (a TV or big screen shows the QR and several phones send to it), the photos and videos are kept only in that TV browser's own storage while the page is open and are deleted when it is closed; nothing is uploaded.

PC Drop (between your phone and your computer)

With PC Drop, files go from your phone's browser straight to your computer's browser, or the other way, over a direct, encrypted connection (WebRTC). The files are never uploaded to SpriteSplit or stored on any server. To help the two browsers find each other, a public connection service (the PeerJS cloud server) and a Google STUN server see only technical connection details, such as a random ID and network addresses, never the files, their names or your device names. Received files are kept only in the open page's memory until you save them, and are gone when the page is closed.

So that the QR stays the same and your phone can reconnect, the computer's browser stores a random computer ID, a secret link key, the name you gave the computer, its own signing key (used to show the picture code, and never shared; only the public part goes to your phone), and a list of the phones you allowed (a random phone ID, the phone's name and the date it last connected). Your phone's browser stores a random phone ID, the phone's name, and the link and name of the last computer it connected to. All of this stays in your own browsers. To remove it, tap Forget next to a phone on the computer, Make a new QR on the computer, or Forget this computer on the phone; clearing the browser's site data also removes it.

Trip Expense Splitter

The Trip Expense Splitter keeps your trips (names, expenses, payments, optional UPI IDs and bill photos) only in your own browser, never on SpriteSplit's servers. If you share a trip live, the expenses go over direct, encrypted connections (WebRTC) to the friends who opened your link, through the trip creator's browser; the PeerJS cloud server and a Google STUN server only help the browsers find each other and see technical details such as a random ID and network addresses, never the expenses. A trip file or trip link you send holds the trip's names and expenses, and goes wherever you send it. Bill photos are never shared. Delete a trip in the tool, or clear the browser's site data, to remove it.

Trip Drop (friends sharing trip photos)

With Trip Drop, one friend starts a trip room and the others join it. Photos and videos go from each friend's browser to the room creator's browser and on to the friend who asked for them, over direct, encrypted connections (WebRTC). They are never uploaded to SpriteSplit or stored on any server. To help the browsers find each other, a public connection service (the PeerJS cloud server) and a Google STUN server see only technical connection details, such as a random room ID and network addresses, never the photos, their names or your names. The room creator's browser passes small previews and the files friends ask for, and keeps the list of who is in the room and the previews only in the open page's memory. Full files that you receive are kept only in your open page until you save them. When the room ends or the page is closed, all of it is gone.

The room creator's browser makes a new signing key for each room, used only to show the picture code; it is never shared, only the public part goes to friends' phones. Your browser remembers only the name you typed, in its local storage, so you need not type it again. Clearing the browser's site data removes it.

Wedding Drop (guests sending photos to the couple or host)

With Wedding Drop, guests send photos, videos and an optional short message from their browser straight to the collector's browser (the couple, a family member or the host), over direct, encrypted connections (WebRTC). Guests only send; they never see each other's photos. Nothing is uploaded to SpriteSplit or stored on any server. To help the browsers find each other, a public connection service (the PeerJS cloud server) and a Google STUN server see only technical connection details, such as a random event ID and network addresses, never the photos, their names, messages or anyone's name. On the collector's device, received photos, videos and messages are kept only in the open page's memory until the collector saves them, and are gone when the page is closed.

So that a printed QR keeps working on the day, the collector's browser stores the event name and welcome line, a random event ID and link key, its own signing key (used to show the picture code; only the public part goes to guests' phones), and the random guest IDs it allowed or blocked. A guest's browser stores only the name they typed and a random guest ID (no number or email), so they need not type their name again and the collector can block one phone. All of this stays in your own browsers. Tapping End this event or Start a different event removes the event; clearing the browser's site data removes everything.

Order Drop (food orders at a stall or restaurant)

With Order Drop, a customer's browser gets the menu straight from the stall's browser and sends its order back, over a direct, encrypted connection (WebRTC). Menus and orders are never uploaded to SpriteSplit or stored on any server. To help the browsers find each other, a public connection service (the PeerJS cloud server) and a Google STUN server see only technical connection details, such as a random counter ID and network addresses, never the menu, the orders or anyone's name. SpriteSplit does not process payments: customers pay the stall at the counter, and the page never asks for money or card details. Sample dish photos are loaded from SpriteSplit like any other picture on the site.

The stall's menu, item photos, settings, its signing key (used to show the picture code; only the public part goes to customers' phones) and the list of phones it blocked stay on the stall's device. Today's orders (token number, items, total, the name, table number and note the customer typed, the time, the status and a random phone ID) are kept on the stall's device, so the stall can see and download them; orders from earlier days are removed when a new day starts, except orders not finished yet. A customer's name, table number and note are sent only to the stall. The customer's browser keeps a random phone ID (no number or email), the name and table number they typed, the last stall link, the items in their cart and their tokens for the day, so a reload shows the token again. Clearing the browser's site data removes all of it.

Class Drop and Slides Drop (a teacher or speaker sharing files with many people)

With Class Drop and Slides Drop, a teacher or speaker shares files from their browser straight to the browsers of the students or the audience who scan their QR, over direct, encrypted connections (WebRTC). The files are never uploaded to SpriteSplit or stored on any server. To help the browsers find each other, a public connection service (the PeerJS cloud server) and a Google STUN server see only technical connection details, such as a random ID and network addresses, never the files, their names or anyone's name. On the sharer's device the files are kept only in the open page's memory and are gone when the page is closed.

So that a printed notice or a "Get the slides" slide keeps working, the sharer's browser stores each class or talk it made: the name, the sharer's name, for talks the one-line bio and links the speaker typed, a random ID and link key, and its own signing key (used to show the picture code; only the public part goes to the receivers' phones). Tapping Forget removes a class or talk. In Class Drop the teacher can ask students for their name and an optional roll number; these are sent only to the teacher's page, which shows them in a register of who got which file for as long as the page is open, and which the teacher can download as a CSV file. Slides Drop asks no name or email: the speaker sees only how many phones got the slides and a count of 👏 taps. A receiver's browser stores only the name and roll number they typed and a random phone ID (no number or email). Files received are kept only in the open page until they are saved. Clearing the browser's site data removes all of it.

Wedding Guest List & Gift Register

The wedding guest list, gift register and moi book keep the events, guests (names, people count, phone numbers, cities, notes, replies) and gifts (names, amounts, envelope numbers, notes) only in your own browser on your device; nothing is sent to SpriteSplit. Contacts are read only when you tap Pick from my contacts, and only the ones you choose. WhatsApp invitations and thank-you messages open WhatsApp with the text for you to send. An optional PIN is stored only as a salted hash. Backups go to a file you download or, if you choose, straight to your own Google Drive as described above. Clearing the browser's site data or tapping Delete this event removes it.

Messages you send us

If you email us, for example through the contact page, we receive your email address and message. We use them only to reply and to improve SpriteSplit, and we don't share them.

Data on your device is under your control

Lists, bills, photos and settings you keep in SpriteSplit's tools live in your browser on your device. Anyone who can use your device or browser may be able to see them, so lock your device and use the PIN option where a tool offers one. Clearing site data deletes them for good.

How devices find each other (Drop tools)

To connect two browsers directly, a free connection service (PeerJS) and Google's connection helpers (STUN) briefly see technical details such as IP addresses. They never see your files. The two connected devices can also see each other's IP address, as with any direct internet connection.

We do not sell data

We do not sell, rent or trade personal data, and we do not build profiles of you.

Security

We design the tools so your files stay on your devices and travel encrypted. No method of storage or transfer is 100% secure, so we cannot promise absolute security.

Analytics

We use Cloudflare Web Analytics, which counts page visits without cookies and without identifying you, to see which tools are used. The data is aggregated.

To count how many different people visit, your browser also keeps the date of your last visit in its local storage. Once a day it tells our statistics server only whether this is your first visit today, this week, this month or ever. No ID, cookie, device details or IP address is stored, so these numbers can't be linked to you. The Android app does the same, because it opens this website.

Anonymous daily count from business tools

Our business tools (Print Drop, Photo Drop, Photo Studio Drop, Order Drop, Counter Billing and PC Drop) send one tiny anonymous message a day to our statistics server, so we can see how many shops use each tool and whether they keep using it. It is sent only on a day the tool is really used (when the first print job, photo delivery, order, bill or file transfer of the day happens), never just for opening the page, and at most once a day per tool.

  • What is sent: which tool it is, a random shop code, roughly how many jobs were done that day (a range such as "1 to 10", never an exact number, and the same range for the last day the tool was used), the tool's language and the tool's version number. Nothing else.
  • What is never sent: your name, shop name, phone number, email, UPI ID, files, file names, photos, orders, bills, amounts, customer details or device details.
  • The shop code: 6 random letters and digits made up by your own browser (for example 7KQ2MX). It is not linked to you, your phone or an account. Each tool's settings show it (for example PD-7KQ2MX in Print Drop), so you can tell it to us if you want help. It is kept in your browser and, in tools with a backup (Counter Billing and the shop reports), in the backup file, so a restored backup keeps the same code; clearing the browser's site data makes a new one. The Android app does the same, because it opens this website.
  • What our server keeps: the code, the tool, the days it was used, the job ranges, the language, the version and the country (two letters, worked out from the connection). The IP address is used only to find the country and is then thrown away; it is never stored. A shop code not seen for 400 days is deleted automatically.
  • How to turn it off: open the tool's settings and switch off Help improve SpriteSplit: send an anonymous daily count. Nothing is sent from that tool after that.

Advertising and cookies

We use Google AdSense to show ads. Third-party vendors, including Google, use cookies to serve ads based on your previous visits to this and other websites.

Google's use of advertising cookies enables it and its partners to serve ads to you based on your visits to this site and/or other sites on the Internet. You may opt out of personalized advertising by visiting Google Ads Settings. You can also opt out of some third-party vendors' use of cookies for personalized advertising at www.aboutads.info.

To learn more about how Google uses data, see How Google uses information from sites or apps that use its services.

Visitors in the European Economic Area, the UK and Switzerland are shown a consent message, and personalized ads are only shown with consent.

Who runs SpriteSplit

SpriteSplit is run by Vabhora Games & Apps, India. For privacy questions, email [email protected] or [email protected].

Children

SpriteSplit is not directed at children under 13, and we do not knowingly collect personal information from children.

Your rights

Depending on where you live, you may have rights to access, correct or delete personal data, or to object to its processing. We do not hold personal data about you beyond what advertising and analytics partners collect through cookies. Contact us with any request.

Changes

We may update this policy from time to time. Changes are posted on this page with a new "Last updated" date.

Contact

Email [email protected].