Privacy Policy
Effective date: November 11, 2026
In this policy, "we" means Boxlapse, which is responsible for the data described here.
Your photos and projects stay on your device unless you turn on cloud sync
Everything you create in Boxlapse — your projects, your daily photos, and the timelapse videos stitched from them — is stored on your device. There is no Boxlapse account, and we hold no copy of your photos, projects or videos; the contents of your frames are never tracked, analyzed, or shared.
The one thing that sends your photos anywhere is cloud sync, and you decide whether it happens. Sync is off until you pick a destination — Google Drive or, on iPhone, iCloud — and switch it on for a project. When you do, the project's files are copied to your Drive or your iCloud, under your own account, and from there to your other devices that sync the same project; they never pass through us. Both are described in detail below, and turning sync off stops any further copying.
No ads, no behavioral analytics, no Boxlapse account
Boxlapse contains no advertising and no product analytics. Nothing records which screens you open, which features you use or what you photograph, and there is no Boxlapse account to create — the app works fully without signing in to anything. The only sign-in in the app is the optional Google sign-in for Drive sync, described below.
A few things do leave your device without you asking, and to be exact about them. The main one is crash reporting: as well as sending a report when the app actually errors, it sends a short anonymous session record each time the app starts and stops — including when you come back to it after it has been in the background for more than about half a minute — so we can tell what share of sessions ended in a crash. Because that record is tied to your installation, it does tell us how often that copy of the app is opened; what it does not tell us is anything about what you did while it was open. Crash reporting below describes both of them in full. The others are plain requests: two for the app's own upkeep — it asks whether there is an update to its own code each time it starts, and it fetches the music library's list of tracks when you open the screen where a video is made — and, on Android, a single report, sent once, of how the app was installed. Other requests the app makes describes those.
Google user data (Drive sync)
Syncing with Google Drive is opt-in. If you choose it as your sync destination, Boxlapse
asks you to sign in with your Google account and requests a single OAuth scope,
https://www.googleapis.com/auth/drive.file. That scope grants an app access
only to files it creates itself in your Drive. Boxlapse therefore cannot see, list, open or
modify any other file in your Google Drive, and it asks for no other Google scope.
For each project you switch sync on for, Boxlapse keeps these files in your Drive:
- the project's files — the photos you captured, the originals kept behind any edits, the base copies an edit is redone from, the intro clip if you added one, and, for a video project, its clips — copied byte for byte, not re-encoded;
-
in a
devicesfolder, one small JSON file for each device that syncs the project. It lists the project's files (each one's path, its size, an MD5 hash of its content, and the time it last changed), the files that device has deleted and when, and the project's record: its name, its dates, its settings, and the per-frame edit details the app needs to rebuild it. The file is named after an identifier the app generates once for that installation, made of the time it was generated and a few random characters. That identifier is used for nothing else, and it is sent nowhere but into your own cloud folder.
These are kept in a normal, visible folder called boxlapse.app sync in your Drive,
one subfolder per project. Earlier versions of the app, which only backed projects up,
named that folder Boxlapse Backups; the app renames it to the new name and keeps
what is in it. A subfolder from that time may still hold the manifest.json and
index.json files the backup wrote, which the app leaves in place. A device
still running one of those earlier versions makes a new Boxlapse Backups folder and backs
up into that until the app is updated there.
The purpose is only this: so that you can open and continue the same project on several of your own devices, and so that a lost, wiped or replaced phone doesn't take a years-long series with it. Boxlapse does not use this data for advertising, does not sell it, does not transfer it to anyone else, and no human reads it. The email address shown as "connected as" in the app is read from Google purely to display which account is linked, and is stored only on your device.
Sync works in both directions. The app uploads what is new or changed on a device and downloads what your other devices have added or changed, so that every device that syncs a project comes to hold the same files and the same project record. Deletes are synced too: a frame you delete in the app on one device is removed from the folder in your Drive and, the next time they sync, from your other devices that sync that project. To continue a project on another device, you connect the same Google account there and add the project from the list the app reads from this folder; a project added that way is switched on for sync on that device.
Retention is in your hands: the files live in your own Drive, owned by your account, for as long as you keep them. Turning sync off for a project stops further copying and leaves what is already in your Drive in place, and so does deleting the whole project in the app. You can delete a project's subfolder, or the whole boxlapse.app sync folder, from Drive yourself at any time; turn sync off for the project first, because a device that still syncs it will upload its copy again. Disconnecting the account in the app stops all further syncing, asks Google to revoke the app's access and clears the stored credentials from your device; you can also revoke that access yourself from your Google account permissions page.
Boxlapse's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
iCloud sync
On iPhone you can choose iCloud instead. It is opt-in in exactly the same way, and it keeps exactly the same files — the project's photos, originals, base copies, intro clip and clips, and the JSON file for each device — in Boxlapse's own app container in your iCloud Drive, shown there as "Boxlapse", where they belong to your Apple account. iCloud moves them between your devices and Apple's servers on its own schedule. Boxlapse does not read anything else in your iCloud Drive, the data is used only to sync your projects between your own devices and to bring them back onto a device, and turning sync off stops further copying and leaves what is already in iCloud in place. It works in both directions here too, so a frame you delete in the app on one device is removed from the container and from your other devices that sync that project, and you can delete Boxlapse's data from iCloud Drive yourself. Apple's handling of what is stored in your iCloud account is covered by Apple's privacy policy.
Crash reporting
To find and fix bugs, Boxlapse sends an automatic diagnostic report when the app crashes or hits an unexpected error, using Sentry. These reports are hosted in the European Union (Sentry's EU region). A report contains only technical diagnostics: the error and its stack trace, your device model and operating-system version, and the app version. It never includes your photos, your projects, or anything you create, and it isn't linked to your identity or used to track you. File paths that could reveal a name are stripped before a report leaves your device. See the Sentry privacy policy for how they process this diagnostic data.
Crash reporting also measures release health — the share of app sessions that end in a crash — and that is the one thing it sends when nothing has gone wrong. Each time the app starts, stops, or comes back from the background after more than about half a minute, it sends a session record. The fields it carries are: a randomly generated session id, and whether this is the first record for that session; an anonymous installation identifier, tied to the installed copy of the app rather than to you or to any account; when the session began, when the record was sent, and how long the session had lasted; whether it ended normally, in a crash, or was cut short, and how, if it was; how many errors happened during it; the app version and which kind of build it is; and, as with any request over the internet, the IP address it was sent from. Those are all of its fields — unlike a crash report, a session record carries no device model and no operating-system version. It contains no photos, no project data, no screen or feature usage, and no history of what you did in the app. What it does show is how often a given installation is opened, which is what release health is worked out from: whether a release is crashing more than the one before it.
Reporting a problem
Where the app offers a Report a problem screen, you can write to us about something that went wrong. Nothing is sent until you press Send. A report contains the message you wrote; the technical diagnostics a crash report carries (your device model, its operating-system version and the app version); and a description of your phone's cameras: which cameras it has and which manual controls each one supports. It contains no photos and no project data, and file paths in your message that could reveal a name are stripped before the report leaves your device. As with any request over the internet, it arrives with the IP address it was sent from.
Problem reports are handled the same way as crash reports: they are processed by Sentry and hosted in the European Union. A report is not linked to your identity, but we do read what you write, so leave out anything you would not want us to see. After a report is sent, the app shows a reference for it. Quote that reference to support@boxlapse.com and we will delete the report.
Other requests the app makes
Update check. Each time the app starts, it asks an update service run by Expo (650 Industries, Inc.) whether a newer version of the app's own code is available, and downloads it if there is one. The request says which platform the app is running on (iOS or Android), which version of the app's code is installed and which release channel it follows, and it carries a randomly generated identifier that is created on your device and kept with the installed copy of the app — tied to that installation, not to you or to any account. As with any request over the internet, Expo also sees the IP address it was sent from. It contains no photos, no project data, and nothing about what you do in the app. See the Expo privacy policy for how they handle that data.
Music library. The list of tracks in the app's music library is fetched from
media.boxlapse.app, Boxlapse's own media storage, which is hosted and delivered
by Cloudflare. The app requests that list when you open the screen where a video is made,
whether or not you add music, and it downloads a track and its cover art from the same place
when you preview or choose one. The app adds no identifier to these requests: nothing in
them says who you are or which copy of the app sent them. What they do reveal, as any
request over the internet does, is the IP address they were sent from, and the address
requested — so a request for a track shows that someone at that IP address fetched that
track. See the
Cloudflare privacy policy for how
they handle that data.
Install source (Android). Once after the app is installed on an Android phone, it
asks Google Play how it was installed — Google calls this the install referrer — and
reports the answer to api.boxlapse.app, Boxlapse's own server, which is hosted
by Cloudflare. The answer says whether the app was installed through one of our download
links and, if so, which campaign that link was for (a poster, say, or a post on social
media), or that it was installed some other way. The report carries that answer, the time
the app was installed, and whether it is a store build or a test build — nothing else. It
carries no identifier: nothing in it says who you are or which copy of the app sent it. As
with any request over the internet, it arrives with the IP address it was sent from; we keep
only the country that address is in, not the address. We use these reports only as totals:
how many installs each campaign led to. Once a report has gone through, the app never sends
another; if it could not be sent, the app tries again the next time it starts. On iPhone
the app sends no such report.
None of these requests is linked to your identity, and we do not use any of them to track you or to build a picture of what you do in the app.
Subscriptions
If you subscribe to Boxlapse Pro, the purchase is processed by the store you bought it from (Apple's App Store on iPhone, Google Play on Android); we never see your payment details. To know whether your subscription is active, the app uses RevenueCat, which processes your purchase receipt and a random app user ID — created for your installation, and not tied to your name or your email address — plus, as with any request over the internet, your IP address. It receives nothing about your photos. See the RevenueCat privacy policy for how they handle that data.
This website and our download links
This website and our download links (on get.boxlapse.app) show no ads, set no
cookies and run no tracking scripts. We may count how they are used — for example, how often
a link is followed, on what kind of device, and from which country or campaign — but only as
anonymous totals, never with your IP address or anything else that identifies you. Both are
delivered by Cloudflare, which sees the IP address of each request in order to deliver it;
see the Cloudflare privacy policy.
On Android, the app's install report lets us count how many
of a campaign's clicks became installs, again only as totals.
Your choices and requests
Because there is no Boxlapse account and the app never learns who you are, the crash reports, session records, install reports and purchase records described above are not filed under your name, your email address or anything else we could look you up by. That has a consequence worth being plain about: we cannot look up, export or delete "your" crash reports or purchase records, because we have no way to tell which ones are yours. The one exception is a problem report you sent yourself, which we can find and delete by the reference the app showed you. What is yours to control, you control directly. Your photos and projects are on your device. A synced project is also in your own Google Drive or iCloud, and you delete it there. A subscription is managed in the store you bought it from. For any question about your data, write to support@boxlapse.com.
Changes and contact
If this policy ever changes, the update will be posted here with a new effective date. Questions? Email support@boxlapse.com.