Skip to content
KE Digital
  • Products
  • Studio
  • Contact
Get in touch

Privacy Policy: AllPix

AllPix is available on Google Play. This policy describes how the service works, including its encrypted storage format (version 1), and it applies from the first time you use AllPix.

Last updated: 27 October 2026 (Send to computer, in sections 3, 4, 7, 8 and 9)

This policy explains what data AllPix holds, why, who processes it, and what your rights are under the EU General Data Protection Regulation (GDPR). If something here is unclear, or you spot a contradiction with how the app behaves, email support@kedigital.dev. The terms of service cover the rest of the agreement.

1. Who is responsible (the controller)

AllPix is operated by Koray Elbek, a private developer in Copenhagen, Denmark. KE Digital is the name of the studio, not a registered company. For privacy questions, access requests or deletion requests, contact support@kedigital.dev.

2. The short version

Your photos, videos, thumbnails and the facts about them (when, where, what file) are encrypted on your phone before they leave it. We cannot see them. The same is true of Railway and Backblaze, who host the service, and of anyone who breaks into either. The exceptions are listed in sections 4 and 5, because they matter.

3. What we hold

Data Why Readable by us?
Account: your email address, the name on your Google account, and your plan Sign-in, billing status, notices Yes
Items: how many, their sizes, when each was uploaded, and whether it is a photo or a video Backup scheduling, storage limits, Trash Yes
Photos, videos, thumbnails, file names, dates, places and albums The service itself No. Only ciphertext and random ids
Sign-in history and account events (new device, with its name, such as the phone model; a copy of your library started; your account data downloaded; deletion requested) Security notices Yes
Copies of your library that you start (section 8): when, how many items and how many bytes your library held then, and how far the download links were handed out. Never the photos or their names Allowing one copy at a time and two new copies a month Yes
Subscription status from Google Play To give you the plan you bought Yes. Google handles your card, we never see it
IP addresses of requests Operating the service Only in hosting logs, kept for the hosting provider’s log retention
Messages you send from Contact support: what it is about, your message, the email address to answer, the app version and your phone model and Android version, and your account if you are signed in Answering you Yes
Photos you send to a computer (section 8): the code the computer showed, which items you sent and their total size, the computer’s browser as its name gives it (for example “Chrome on Windows”), and when. Until the computer collects it, also the sealed package with the keys to those photos, which only that browser tab can open. Never the photos, their names or your key, and no IP address Getting the photos to that browser, and the security notice Yes, except the sealed package
Crash reports, sent by the app the next time it starts after a crash: what kind of crash it was, the error type, the places in the app’s code where it happened, when, whether the app was on screen, the app version, Android version and phone model. Never the error message, your photos, file names or paths, your account, a device id or your IP address. Sent without your account, so nothing in it says who sent it Finding and fixing bugs Yes

Upload time roughly tracks when photos were taken. We keep it because backup scheduling, quotas and Trash need it.

AllPix also shows the photos and videos that are on your phone, including ones that are not backed up yet. That reading happens on your phone. Nothing leaves it unless you have backup turned on, or you choose a photo to back up.

4. Keys, and the one way your photos can be exposed

Your encryption key is created on your phone and never leaves it in plain form. It can be unlocked three ways:

  1. This phone. The key is wrapped by a key that never leaves the phone’s secure hardware (Android Keystore).
  2. Google recovery. A copy of your key, wrapped, is stored in a hidden folder in your own Google Drive and in your phone’s Google backup. We hold the other half needed to open it, and release it only to you when you sign in. On a new phone that happens after a wait of one day, and we email you when someone asks, so you can stop it if it was not you. Google holds the wrapped key but cannot open it. We hold our half but cannot see the Drive file. If someone takes over your Google account, they can restore your library once the wait is over. Use two-step verification on your Google account.
  3. Recovery key. 24 words shown when you sign up. They open your library right away, on any phone, without the wait. Keep them somewhere safe, and never type them anywhere but in the app. If you lose your phone, the 24 words and access to your Google account, your library cannot be recovered by anyone.

A malicious update to the app itself could also read your photos, as with any encrypted app that you trust to run on your phone. Builds are produced by CI from a public commit. The same holds for the page that receives photos you send to a computer (section 8): a malicious version of it could read the photos sent to it while it is open, but never your key or any other photo.

5. Importing from Google Photos

If you import a Google Photos library, the import runs on our server, in its own service. This is the one place a server sees photos in the clear:

  • You export with Google Takeout and share the folder with the import service’s Google account. The service reads it in place.
  • While the import runs, the service sees each photo and its Takeout metadata (file names, dates, places, captions, album names), because it must encrypt them. It gets a key for that one import from your phone, holds it in memory only, and wipes it when the job stops.
  • It stores counts, sizes and states. Everything else about a photo is sealed under a key derived from your import key, so the database cannot read it.
  • Removing access in the app removes the service account’s permission on your Google Drive folder.

6. Who processes your data (sub-processors)

Processor Role What it sees
Railway Corp. Hosts the API and the database Account data, item counts and sizes, ciphertext metadata
Backblaze, Inc. Stores the encrypted photos and videos Ciphertext and random ids only
Google LLC Sign-in; hidden Drive folder for recovery (your account); Takeout import folder (your account); Play billing As described in sections 4 and 5; subscription status
Scaleway Sends notice and reminder emails Your email address and the message text
Resend, Inc. Delivers the messages you send from Contact support to our support inbox Your message, the email address to answer and the details listed in section 3
GitLab Inc. Source code and build hosting No end-user data

Where data is stored. The encrypted files are stored with Backblaze in its EU Central region. Railway runs the API and the database, and its region is not pinned. Railway, Backblaze, Google and Resend are US-based companies, so transfers to them rely on the EU-US Data Privacy Framework where the provider is certified, or on Standard Contractual Clauses (GDPR Art. 46).

7. How long we keep it

Data Retention
A photo or video you delete In Trash for 30 days, then removed. Hidden storage versions are removed after 30 days
Your account Until you delete it. A free account that hasn’t been used for 18 months is deleted after two email warnings (60 and 14 days before) and the 7-day undo
A deleted account 7-day undo window, then your keys are destroyed, every object and every version is removed, then your database rows. A deletion receipt with no personal data is kept
Database backups Expire within 30 days, so deleted rows leave the backups too
An ended paid plan with more than the free 2 GB stored Read-only for 180 days (view, export, delete), then ordinary account deletion starts
The record of a copy you started (section 3) Until you delete your account
A message you send to support 1 year, then removed from our database. Deleting your account removes it sooner. The copy in our support mailbox is kept while we need it to help you
A crash report 90 days, then removed from our database
Photos sent to a computer The sealed package is deleted as soon as the computer collects it; the rest of the record a day after the send ends

8. Your rights

You can access, rectify, erase, restrict, object to and port your data, and lodge a complaint with Datatilsynet.

  • Save a copy of everything: in the app, under Account, “Save a copy of everything” writes your whole library, decrypted and with the real file names, into a folder you choose on your phone, an SD card or a USB drive. The copy is made on your phone, because only a phone that has your key can read your photos. AllPix does not build or keep the copy: each photo goes from storage straight to your phone. The photos in your Safe and Bin are included, in folders of their own. Where a photo has lost its capture date or place (a Google Photos import can leave them in a separate file), AllPix writes them back into JPEG, PNG and WebP files; dates and places a file already has are never changed. Every file’s date and place is also listed in a file called metadata.json beside the photos, together with your account data (see the next point) as account-data.json. It runs in the background and picks up where it stopped after a restart or a lost connection, and it never replaces a file already in the folder. The copy is not encrypted: anyone who can open that folder can see the photos in it. It works for an account whose plan has ended and for one waiting out a deletion. One copy can run at a time, and each account can start two new copies a month.
  • Save single photos: select photos and videos in the timeline and share them to save the decrypted originals, with their real file names, up to 100 at a time.
  • Send photos to a computer: on the computer, open send.allpix.kedigital.dev and sign in with Google; the page shows a code. On your phone, pick photos, tap Share, then Send to a computer, scan the code with the phone’s camera and confirm with your screen lock. Your phone gives that one browser tab the keys to just those photos, sealed so that only the tab can open them. The browser downloads the encrypted originals and unlocks them itself, so we cannot read them on the way. Your phone only accepts a code made by your own account, so a code on someone else’s screen does not work. The tab keeps the keys in memory only, and they are gone when everything is saved, after 30 minutes, or when you close the tab. Saved files are ordinary, unencrypted files on that computer, with anything the camera stored inside them, such as the place. Google sees the computer’s sign-in, as it sees the app’s. Photos in the Bin, the Safe or a locked album are never sent. A send counts once toward your monthly download allowance when your phone sends it, and we email you every time photos are sent to a computer.
  • Export what we hold in plain text: your profile, plan, usage, sign-in history, payments (without the purchase token) and the messages you sent to support are available from the account export, and are saved into every copy of your library as account-data.json.
  • Delete your account: see Delete your AllPix account.
  • Anything else: email support@kedigital.dev. We aim to reply within 30 days.

9. Notices we send

We email you about account events that look like a takeover (a new device unlocking your library, a recovery change, a deletion request, a bulk delete, a copy of your library being started, photos sent to a computer), about backups that stopped, about payment and plan changes, and about storage limits. Security emails cannot be turned off. We also email you before an unused free account is deleted. Our emails never ask for your recovery words and contain no links to click, with one exception: the emails about an unused free account have a “Keep my photos” link, for people who no longer have the app. The page it opens has one button and asks for nothing, not even a sign-in.

10. Payments

Plans are bought through Google Play. Google collects the payment and handles card details. We receive the subscription status only.

11. Children

AllPix is not directed at children. We do not knowingly hold data from children.

12. Changes to this policy

When we change this policy materially, we update the date above and tell signed-in users in the app.

13. Contact

Koray Elbek, AllPix support@kedigital.dev Copenhagen, Denmark

© 2026 KE Digital · No analytics. No cookies.

  • LingoDrive privacy
  • AllPix privacy
  • AllPix terms
  • Delete your LingoDrive account
  • Delete your AllPix account