Original guide and reference
Written for the app that started it.
This is the original TimeLapsed guide, kept intact for photographers and space fans who still use the first-generation app.
From the original TimeLapsed
The historical privacy policy for TimeLapsed version 1.0.
Original guide and reference
This is the original TimeLapsed guide, kept intact for photographers and space fans who still use the first-generation app.
Version 2026-08-08.1 · Effective August 8, 2026
This policy describes what TimeLapsed collects, why, where it goes, and how to get rid of it. It is written to be specific rather than reassuring — if a section sounds narrow, that is because it is meant to be.
ShutterSpeed Apps is the data controller. Reach us at privacy@shutterspeedapps.com.
Account information. If you sign in, we store a user record: an email address, a display name if you give one, and the identifier Apple or Google gives us for you. If you use Apple's Hide My Email, we only hold the relay address. Signing in with Apple or Google means we never receive a password.
Session tokens. We store hashed refresh tokens so you stay signed in. They are scoped per app, so a TimeLapsed session cannot be used against our other apps. They are hashes — we cannot read them back into a usable token.
Purchase records. When you buy something, Apple gives us a signed receipt. We store the Apple transaction identifier, the product identifier, the environment (sandbox or production), the purchase and expiry dates, and the amount and currency Apple reports. This includes the older TimeLapsed Full Version purchase, which is how we know to restore it to you. We never receive your card number, and Apple does not give us your billing address.
AI usage counters. To meter Analyze Scene we store how many analyses you have used in the current period, plus an audit row per request recording the feature, the model, token counts, latency, and whether it succeeded. We keep a history of closed monthly periods so we can answer "why did my credits reset" without guessing.
Purchased credit ledger. For consumable packs we store what was granted, what has been spent, and the Apple transaction that granted it.
AI Scene Analysis results. When you use Analyze Scene we store the analysis: the camera settings you had, the settings we suggested, the reasoning, confidence, tips, the device model and its capability limits, and any rating you give the result. See the AI Use document for the frame itself, which is handled differently.
Consent records. When you accept Terms, this policy, or the AI Use document, we store which version you accepted and when. These records are append-only — that is the point of them.
Diagnostics. Crash and performance diagnostics come to us through Apple, in aggregate, and only if you have enabled sharing in your iOS settings. We cannot tie them to you.
This is the part most people are asking about, so it is spelled out.
A timelapse is built by capturing many frames and assembling them. All of that happens on your device, on its GPU. The frames and the finished movie live in device storage and are written to the destination you choose — your photo library, or your own iCloud storage if you enable Cloud Sync. Your captures do not pass through our servers.
The single exception is AI Scene Analysis, and it is opt-in per use: nothing is sent unless you tap the button. Details are in the AI Use document.
Trips group your shoots so you can find them later. They live on your device and, if you enable Cloud Sync, in your own iCloud account — not on our servers.
The sun and moon calculations are astronomical math run locally against the coordinates you choose. Nothing about where you shoot is sent to us to make them work.
If you enable Cloud Sync, your profiles, trips and app settings are stored in your iCloud account using Apple's CloudKit, in a private database only you can read. We cannot see the contents of your private CloudKit database. Deleting the app or signing out of iCloud removes our access entirely.
We also publish two things into a *public* CloudKit database, which contain no personal data at all: these legal documents, and the subscription product catalog. That is so the app can display them without depending on our API being reachable.
We share data with a small number of processors, each for exactly one purpose:
We do not sell your personal information. We do not share it for cross-context behavioral advertising. There is no fourth column here labeled "advertising partners".
We will disclose data if we are legally compelled to, and we will tell you unless we are prohibited from doing so.
Our servers and database run in the United States on Amazon Web Services. If you use TimeLapsed from outside the US, your data is transferred there. For transfers out of the UK, EU or Switzerland we rely on the European Commission's Standard Contractual Clauses.
Wherever you live, you can ask us to:
Email privacy@shutterspeedapps.com. We will respond within 30 days. We will not charge you, and we will not treat you differently for asking.
Deleting your account removes your account record, sessions, scene analyses, chat transcripts and usage counters. It does not remove purchase records or consent records, which we are required to keep — those are retained with your account identifier reduced to a number that no longer resolves to a person.
If you are in the EU or UK you may also complain to your national data protection authority. If you are in California, the rights above are your CCPA rights; we do not sell or share personal information as those terms are defined there.
TimeLapsed is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has given us personal information, email us and we will delete it.
We will publish a new version of this document when it changes and the app will ask you to accept it. We keep a record of which version you accepted.