Privacy Policy

Last revised: 16 October 2026

Your recorded video, audio, and finished videos are not sent to our server.

What you record and create stays on your device. Creating a video sends downscaled still images and numbers to AI. Action events go to Google Analytics. If you contact us in the App, your message, selected images, device details, and diagnostic log go to support. This policy explains where each item goes and how long it is kept.

1. What stays on your device

The following is stored on your device. Downscaled images sent when making a video and images you select for a support inquiry are exceptions:

video and photos recorded in the App
videos created from a day's material
edits you make to those videos (trim points, order, volume, text)
per-video playback and sharing records used on your device
app state such as whether permissions have been requested

Recorded video and audio, finished videos, and your edits are not sent to our server. Sections 5 and 6 explain video creation and analytics.

2. Reading your Photos library

To assemble material selected by place, your own clips, or date into one video, the App reads your Photos library.

Material read to create a video is processed on your device, apart from the downscaled stills described in section 5 and images you select for an inquiry as described in section 9. You can revoke Photos access at any time in your device settings, or grant access to selected photos only.

3. iCloud Photos (an exception)

If you use iCloud Photos, some material may live in iCloud rather than on your device. To use it, the App fetches it, which means network traffic occurs between your device and Apple's services.

This exchange takes place entirely within your own Apple account. We are not involved and receive nothing. It is governed by Apple's privacy policy.

4. Place names (an exception)

Each finished video is named after a place, such as "Kamakura". To find place names, the App passes approximate coordinates for places where you spent time or possible trips to your device's mapping service (Apple).

The App makes these requests when naming a video or finding trips by filming location. Multiple candidate places may mean multiple requests.
Coordinates are normally rounded to three decimal places; trip searches use the centre of a coarser grid cell. Exact capture locations are not sent.
No footage, photos, finished videos, or capture times are sent.
This is a request to Apple's service. We are not involved and receive neither the coordinate nor the name.
With no network the App does not look anything up, and the video is named by date instead. You can rename any video by hand at any time.

5. The request made when you create a video

To pick the highlights of your video, to choose music and a colour treatment that suit it, and to write short captions, the App asks OpenAI through a server we run when you tap "Create". The current version has no separate control to stop AI sharing. Our server also manages creation counts.

What is sent: downscaled still images made from the material for that video (512 pixels on the long edge at most, one per item, up to 20), together with the time each was taken, its brightness, and how much movement it contains.
To pick highlights, the App sends downscaled still images of the usable video clips (three frames from each clip (near its start, middle and end, leaving out the first and last tenth), each downscaled to 320 pixels on the long edge at most and placed side by side or stacked in a single image; one image per clip, up to 40) with the time each was taken and its length. For the clips chosen as highlights only, it also sends timestamped stills taken from that clip (320 pixels on the long edge at most, up to 6 per clip, up to 6 clips) to decide which part is the highlight.
This AI request does not send the video, audio, original photos, or finished video.
From those stills, the AI writes the short captions shown on screen ("walking over", "lunch", and so on). It is instructed not to write who anyone is, or anything that could identify a person — their features, names, phone numbers, addresses, or a transcription of text visible in the frame. The captions stay on your device, and you can rewrite them afterwards.
Our relay server does not persist the images. It sends requests to the OpenAI API with response storage disabled. API data is not used to train models. The provider's abuse-monitoring logs may contain content for up to 30 days in the ordinary case, and may be kept longer where required by law.
To count creations, our server stores a random per-install identifier, plan, purchase expiry, monthly creation counts and related records. The identifier is kept in the device Keychain and may remain after reinstalling the App.
To confirm purchases, our server verifies Apple-signed transaction information and stores the original transaction ID, plan, and expiry. We do not receive payment-card details.
Without a connection, the App may be unable to check the creation limit and create a video.

6. Measuring how the App is used

The App sends predefined action events (app opened, recording started, video created, shared, deleted, purchase outcomes, and so on) to Google Analytics (GA4) through Firebase Analytics in the App; we use them to learn where the App becomes hard to use. From version 1.5.0, the App sends them from the moment it is opened, and there is no setting in the App to turn this off. Versions 1.2.0 to 1.4.0 send them only if you allow analytics in the App. Earlier versions send them through our relay server.

Not sent for analytics: recorded video, photos, or audio; finished videos; video names; filming locations or GPS coordinates; or imported music titles.
Approximate region: Firebase Analytics sends the network IP address to GA4; older versions use our relay to determine an approximate location. GA4 uses it to infer the city, region, country and approximate city coordinates, then discards the IP address without logging or storing it. We do not send filming locations or the device's GPS coordinates. The inferred region may differ from where you actually are.
Alongside an action we send only a short word from a fixed list, or a number (for example: "photo" or "video"; the length of a video in seconds; why a video could not be created). No free-form text can get through.
Identifier for each App installation: Firebase Analytics sends a pseudonymous app instance ID to Google. In older versions, our server derives a different identifier from the device ID before sending it. In versions released on or after 16 October 2026, so that our own and the developer's devices can be left out of the figures, the App also sends the random per-install identifier described in section 5 itself, and whether the App came from the App Store or from App Review or TestFlight. Because that identifier is also used for creation counts, purchases and inquiries, Google Analytics records can be linked to the records on our server. This can link use of the same App installation over time and is not fully anonymous.
We also send your plan, and whether camera, microphone, Photos, and notifications are permitted, so that we can tell which conditions make the App harder to use.
Whether you installed from an App Store ad: from version 1.5.0, the App asks Apple's attribution service (AdServices) whether it was installed from an App Store search ad. We use this to learn how well our own ads work, and we send Google only whether the App was installed from an ad or not. We do not send which ad or which search term it was.
The App shows no ads, and we do not follow you across other apps or websites. The App uses no advertising identifier.
Firebase Analytics also automatically records events such as first open, session start and screen views, plus device model, OS and App version. In versions 1.2.0 to 1.4.0, the SDK is not initialized before you allow analytics, and collection stops when you withdraw permission.

Event-level information in GA4 follows the Analytics retention setting. Records relating to events relayed by older App versions may also remain on our server side. We are checking the current settings and cannot promise a single deletion period. Contact us using section 14 to discuss deletion.

7. Opening our terms and policy pages (an exception)

Opening the Terms of Use, this Privacy Policy, or the help page from the App's "About this app" screen fetches that page from the web, and only then.

Those pages are fetched only when you tap one of the items. Launching the App alone does not fetch them.
All that is sent is the request for the page. No footage, photos, finished videos, or record of what you did in the App is included.
The pages are hosted on Cloudflare Pages, which keeps the ordinary access log any website keeps (IP address, time, page viewed, browser). We do not use it to identify you, and it cannot be tied to anything inside the App.
The page opens inside the App, using the browser view built into your device. The App cannot read what you do there.
With no network the App does not try to open it, and simply says so.

8. Notifications

If there are at least eight clips from a day, the App may send at most one on-device reminder after 9 p.m. This reminder is composed on your device.

If you allow notifications for support replies, we send the first 160 characters of the reply and conversation routing information to Apple Push Notification service. You can still read unread replies in the App if you deny notifications.

We count how often the App is opened from the evening reminder within the limits in section 6. You can turn notifications off in device settings at any time.

9. In-app support and what reaches us

If you send an inquiry in the App, we receive its category and message, up to 20 images you select, device model, OS and App version, a per-install identifier, and a diagnostic log recorded since launch. The log records times and the outcomes of launching, recording, creating, exporting, and network requests. It may contain personal information. If the log cannot be read, the inquiry can still be sent without it. Videos, audio, and finished videos are not attached automatically.

Messages, images, device details, and diagnostic logs are also copied to a dedicated support Slack channel. We delete conversations and attachments from our server 30 days after they are sent. Slack copies follow Slack's separate retention settings and are not removed by our server's deletion process. Contact us using section 14 to request deletion.

Because the App is distributed on the App Store, Apple may also provide us with:

statistics such as download counts, and
reports about unexpected terminations (crash reports).

Apple aggregates these so that individuals cannot be identified. We cannot learn who you are or what you recorded. Apple determines the scope and method; you can stop sharing this with Apple in your device's analytics settings.

10. Sharing with third parties

We use the following external services:

To the AI provider: the downscaled still images and numbers used to pick the highlights, to choose music and a colour treatment, and to write the on-screen captions (section 5).
To Google (Analytics): predefined action and purchase-outcome events, an app instance ID, the per-install identifier, whether the App came from the App Store or from App Review or TestFlight, your plan, permission states, whether the App was installed from an App Store search ad, device and App information, and the network IP address used to determine an approximate region (section 6).
To Slack: support messages, selected images, device details, diagnostic logs, and replies (section 9).
To Apple's notification service: if you allow reply notifications, the first 160 characters of a reply and conversation routing information (section 8).

Recorded video and audio, finished videos, video names, and filming place names are not sent.

The App uses none of the following:

in-app advertising or advertising identifiers
any mechanism for following you across other apps or websites

The App does not track you.

11. Deleting what is stored

Delete one video: open its card on the App's home and delete it. The original material is not deleted.
Delete on-device content: remove the App. Its local videos and logs are removed.
Items saved to Photos: these remain after the App is removed. Delete them from the Photos app.

There are no accounts, so there is no account-deletion process. Our server stores a per-install identifier, plan, original transaction ID, monthly creation counts and related records; currently these have no automatic deletion deadline. Deleting the App does not erase server-side or provider records. To request deletion, contact us using section 14. We will identify the records and assess deletion of data under our control and requests to providers individually.

We delete support conversations, images, and diagnostic logs from our server 30 days after they are sent. Slack copies follow a separate retention setting. Contact us using section 14 about deleting those copies.

12. Children

The App is not directed at any particular age group and is not designed for children.

13. Changes to this policy

If we change this policy we will update this page and change the revision date at the top. If a change would mean collecting something, we will revise this page before releasing the version that makes that change.

14. Contact

Provider: Appelier
Contact: yuya.yoshida.official@gmail.com

Revision history

Date	Change
16 October 2026	Added to section 6 and the list of what is shared with third parties that the per-install identifier, and whether the App came from the App Store or from App Review or TestFlight, are sent to Google Analytics so that our own and the developer's devices can be left out of the figures
10 October 2026	Updated section 6 and the list of what is shared with third parties because, from version 1.5.0, the App checks whether it was installed from an App Store search ad and adds that to analytics.
10 October 2026	Updated section 6 and the summary because, from version 1.5.0, usage analytics starts when the App is opened without asking for permission, and the in-app setting to turn it off is removed
28 September 2026	Updated section 5 because the still image sent to pick highlights now shows three frames from each clip in one image instead of a single frame.
27 September 2026	Now that the AI also picks the highlights of a video, added to section 5 and "Sharing with third parties" the downscaled stills sent for that, including a few stills taken from each highlight clip
25 September 2026	Updated identifier, purchase and analytics retention, and deletion; disclosed IP transfer for approximate location and direct collection through the Firebase Analytics SDK, including the app instance ID and automatic device and App data
22 September 2026	Stated in sections 1, 5 and 8 that the AI also writes the short captions shown on screen, and what it is instructed never to write
20 September 2026	Added section 6 on measuring how the App is used. Also set out, in a new section 5, the requests made to our server and to the AI when a video is created, rewrote "Sharing with third parties" to match what the App actually does, and renumbered the sections that follow
3 September 2026	Added section 5 on the request made when you open our terms or policy pages from the App, and renumbered the sections after it
3 September 2026	Added section 4 on place-name lookup, now that finished videos are named after a place
2 September 2026	First version