Last updated: 27 August 2026
FramePull is made by Carlo Oppermann. This policy says what the app does with your information. It is short because the app does very little.
What we collect
Nothing. The developer of FramePull receives no data from the app. There is no analytics, no crash reporting, no advertising, no tracking, and no third-party SDK of any kind in the app.
Where your videos and exports live
Your videos stay where they already are — on your device, in your photo library, or in a folder you chose. FramePull reads the video you pick, does its work on your device, and writes the stills, clips, GIFs and grids you export to the place you choose.
Nothing is uploaded. Scene detection, cropping, GIF encoding and grid rendering all run locally using Apple’s own frameworks. The app contains no networking code, so there is no server to send anything to.
Photo library access
On iPhone and iPad, FramePull asks for access to your photo library for two reasons:
- To read the video you pick, so it can analyse and export from it.
- To write your exports into an album named after that video.
Saving into an album needs full library access rather than add-only, because finding the album you used last time is a read. FramePull does not browse, catalogue or transmit your library — it touches the video you select and the album it writes to.
You can withdraw this at any time in Settings → Privacy & Security → Photos. Exporting to Files works without any photo library access at all.
File access
On Mac, and when you choose Files on iPhone or iPad, FramePull can only see the folder you explicitly pick. macOS and iOS enforce this; the app cannot reach anything you have not chosen.
Children
FramePull is not directed at children and collects no data from anyone.
Changes
If this policy changes, the date at the top changes with it.
Contact
mail@carlooppermann.com