The editor has no server-side component. The whole thing — the layout engine, the filters and the image export — is JavaScript running on your device. That is not a policy promise; it is how it is built. The single exception is confirming a payment, which is described in Paying for it below, and which never touches a photo.
Nothing. There are no accounts, no analytics, no tracking pixels, no advertising and no cookies.
| Stored | Where | Why |
|---|---|---|
| The photos you add | IndexedDB, on your device | So a collage survives a reload without re-picking every photo. |
| The current project — layout, framing, styling | localStorage, on your device | Autosave, so you return to the collage you were building. |
| Your saved templates and appearance setting | localStorage, on your device | To reuse layouts and keep light or dark mode. |
| Your unlock code, if you have one | localStorage, on your device | So the studio can tell it is unlocked without asking anything, anywhere. |
| How many exports you have used | localStorage, on your device | To keep the studio's own count. It is a number, and it is never sent. |
None of it leaves the browser. Clearing your browser's site data for nextcollage.com deletes all of it permanently, and "New project" in the studio clears the saved project immediately.
Loading the page fetches the application files themselves — HTML, JavaScript, CSS and icons — from nextcollage.com. After that the studio makes no network requests at all: no fonts, no CDNs, no third-party scripts. Once loaded, it works offline.
There is exactly one exception, and it happens at most once ever: the moment you come back from
a completed checkout, the studio asks license.nextcollage.com to confirm it. Using
the app after that — including checking that it is unlocked, on every later visit — makes no
request at all. That check is arithmetic against a key already inside the page.
The checkout itself runs on the payment provider's own site, not this one. Whatever you type there — card details, billing address, email — is theirs, under their privacy policy, and none of it is ever visible to NextCollage.
When you return, one request goes to license.nextcollage.com carrying the order
reference the provider gave you, and nothing else. It answers with a short signed code that
says a sale happened, when, and an unreadable eight-character digest of the order number. There
is no name in it and no email address in it. That code is what gets stored on your device, and
it is the same code you can carry to the phone app or to another browser.
That service keeps no database. It holds no record of who bought what — the payment provider and the app stores already have that, and duplicating it would only create somewhere else for it to leak from.
Exported images and .collage project files are generated in your browser and saved
straight to your device with the browser's own download mechanism. They are never transmitted.
NextCollage collects no personal data about anybody, including children. If you buy the app, the payment provider and the app store collect what they need to take the payment; nothing about you reaches NextCollage.
If this ever changes — if some feature genuinely requires a server — the change will be described on this page before it ships.