Frames, projects and exports are written to your phone. There is no account and no server of ours to send them to.
Clap-to-shoot measures loudness in memory and throws every sample away. Nothing is written to storage.
No sign-up and no advertising in the app. Two things do leave your phone — a crash report when the app crashes, and basic usage statistics — and neither one carries your photos or your project names.
We run no cloud service and hold no copy of your projects. On Android they exist only on your phone; on iPhone they are also in your own device backup, if you make one. Export the videos that matter.
Stopmo Studio is a stop-motion and time-lapse app developed and operated by Milos Micunovic, an independent developer based in Montenegro. For the purposes of applicable data-protection law, including the GDPR, Milos Micunovic is the data controller for the limited information described in this policy.
You can reach us any time at mmicunovic1@gmail.com. This policy explains what the app does and does not collect on Android and on iPhone, where your content lives, and the choices you have.
Stopmo Studio is often used to record deeply personal moments — a child growing month by month, a body changing over time, a model taking shape on a workbench. The app is built so that this content is private by default and stays under your control.
The app collects two things: crash reports and basic usage statistics, each described in its own section below. Along with them go a small number of identifiers we do not choose the values of:
Because of those identifiers the usage and crash data is not fully anonymous, and we say so rather than claim otherwise. Beyond what is listed above, the app does not ask for or transmit:
Two indirect exceptions are worth naming honestly, because they are not run by us:
The app uses Firebase Crashlytics, a crash-reporting service run by Google. When the app crashes, or runs into an internal error it has been written to report, a report is sent to Crashlytics — usually the next time the app starts.
A report contains:
A report never contains your photos, frames, exported videos or audio, the names you give your projects, the names of files you export, or the photos you pick for import. The app's logging is written so that no text you typed and no photo you chose can reach a report, and the release build discards its detailed debug logging before anything can be attached.
About the installation identifier. It is a random value, not tied to your Google account, your advertising ID or your hardware, and it is used only to tell how many installations a given crash affects. It is reset when you uninstall the app or clear its data (on iPhone, when you delete the app and reinstall it).
Storage and retention. Reports are stored by Google on our behalf, on servers that may be outside your country. Crashlytics keeps them for 90 days and then deletes them. Google processes this data for us under the Firebase terms; see Google's Firebase privacy page.
One thing crash reporting now also does. Because the app also includes Firebase Analytics (see the next section), a crash additionally records a plain app_exception marker in the usage statistics. It carries no detail about the crash beyond the fact that one happened.
No opt-out switch, said plainly. The current version has no setting to turn crash reporting off.
The app uses Google Analytics for Firebase to collect basic statistics about how Stopmo Studio is used — how often it is opened, how long a session lasts, which screen is on display, and when the app or the operating system is updated. We read these in aggregate, to see which parts of the app people actually use and where to spend our time.
We send no events of our own. The app contains no code that reports what you do inside a project. Only the standard, automatic measurements the Firebase library makes on its own are collected — things like first open, session start, screen view and app update. The app is deliberately built so that it has no way to attach a name, a project title, a photo or anything you typed to a statistic; the screens are identified by an internal class name that is fixed at build time.
These statistics travel with the identifiers named under Information we collect: the resettable installation identifier, an app-instance identifier generated by the analytics library, on Android your device's advertising ID, on iPhone the identifier for vendor, and a city-level location derived from your IP address. They are not linked to your name, and we have no way to work back from them to a person — but they are per-installation rather than fully anonymous, which is why we name them.
How you found the app. On Android, the analytics library asks Google Play where the install came from — the referral link or ad you tapped, if there was one, and the times of the tap and the install. On iPhone, the analytics library registers the app with SKAdNetwork, Apple's privacy-preserving system that lets an ad network learn that one of its ads led to an install; Apple sends that signal to the ad network without any identifier for you or your device, and the iPhone app uses no advertising identifier. We run no ad campaigns, so in practice there is nothing to attribute.
Your controls. On Android you can reset or delete your advertising ID under Settings → Privacy → Ads. On iPhone there is no advertising identifier to manage; deleting the app and reinstalling it resets the app-instance identifier. Neither version has an in-app switch to turn usage statistics or crash reports off.
Storage and retention. The statistics are processed by Google on our behalf, on servers that may be outside your country, under the Firebase privacy terms. Google deletes the per-installation records after the retention window configured on our property; the aggregate figures we look at remain.
The sentences below describe both apps; where they differ, the iPhone detail is given after the Android one.
Everything the app creates is written to your own device:
We operate no cloud service. There is no Stopmo Studio server holding your projects, and no way for us to retrieve or view them.
On Android, the app opts out of Android's own backup. Your frames and project data are excluded from Google account backup and from the phone-to-phone transfer that runs when you set up a new device, because the backup quota Android allows is far too small for a library of full-resolution frames. On Android, if you lose your phone, uninstall the app, or move to a new phone, your projects do not come with you. Some device makers handle phone-to-phone transfer with their own tools; the app asks the system not to copy its data, but we cannot promise that every manufacturer tool honours that request.
On iPhone, the app does not opt out of Apple's device backup. If you back up your iPhone to iCloud or to a computer, your projects are part of that backup and come back when you restore it or set up a new iPhone from it. That backup is made and held by Apple under your own settings and Apple's privacy policy, not by us; we cannot see or restore it. If you have no backup, or you delete the app, your projects are gone.
Exported videos follow whatever backup your photo library uses — iCloud Photos, Google Photos, another gallery app, or nothing. That is your setting, outside the app. Export the videos that matter to you.
The app asks only for the permissions a feature actually needs, at the moment you first use that feature. You can revoke any of them later in your system settings. The list below is for Android; the iPhone permissions follow it.
On iPhone:
You can revoke any iPhone permission in Settings → Stopmo Studio.
Stopmo Studio is a general-audience creative tool. It is not directed at children under 13 (or the equivalent age in your country) and is not designed for use by them. The app collects nothing from anyone beyond the crash reports and usage statistics described above, and none of that can be linked to a person, so we hold no children's data. The app has no age check and no account; it is rated 4+ on the App Store because it supplies no objectionable content, which is not the same as being aimed at children.
Many projects contain photos of children, of people's bodies, or of a private home. That content stays on your device and is never processed by us. If you are creating a project that includes another person — especially a child — you are responsible for having the right to photograph them.
The app contacts no server of ours. It uses two third-party services directly, and a small number of platform services sit around them, each with its own privacy policy:
This site is a set of static pages hosted on Firebase Hosting (Google). It sets no cookies and runs no analytics. As with any web host, Google may process standard server request data such as your IP address and browser user-agent for delivery and security purposes, under Google's own policies.
The pages load the Montserrat and Raleway typefaces from Google Fonts, so your browser makes a request to Google's servers when you visit. If you would rather avoid that, a content blocker will stop it and the pages stay fully readable.
Because your content lives on your device, you stay in control of how long it is kept:
We hold no copy of your content, so there is nothing for us to retain or delete on your behalf. Crash reports are deleted by Crashlytics after 90 days, and per-installation usage records are deleted by Google after the retention window set on our property; because neither carries anything that identifies you, we have no way to find and delete the ones that came from your device sooner. Support emails are kept only as long as needed to handle your request.
If you are in the European Economic Area, the United Kingdom, or another region with comparable law, you have rights of access, rectification, erasure, restriction, objection and portability over personal data a controller holds about you.
In our case the honest answer is that we hold no data we can link to you. Crash reports and usage statistics are tied to a resettable, per-installation identifier and cannot be matched to a person, so in practice there is nothing for us to disclose, correct or erase — unless you have emailed us, in which case those messages are the only records that exist. Write to mmicunovic1@gmail.com and we will confirm what we have and delete it on request. You also have the right to complain to your local data-protection authority.
For data held by Google in connection with Google Play or your gallery, please use Google's own privacy tools and policies — we have no access to it.
We may update this policy as the app evolves. If the app ever starts collecting something, or sending anything off your device, this page will say so before that version ships. When we update it we will revise the date at the top of the page and, for material changes, note them in the app. Continuing to use Stopmo Studio after an update means you accept the revised policy.