Privacy Policy

This is a reference translation. The Japanese text is the authoritative version of this Policy; where the two differ, the Japanese governs.

Peeksy (the “Service”) respects your privacy and handles personal information appropriately. This Policy explains what information the Service collects and how it is used.

1. Information we collect

Account information — when you sign in with Google or Apple, we receive your name, email address, and profile image.
Content you create — recommendation cards extracted from a screen recording (thumbnail images, video titles, channel names), the canvas image composed for sharing, snapshots, notes (comments), group information, and reactions.
Saved discoveries (“Save it”) — we store identifiers for the source post and image, the area selected within the image, information identifying the image revision, and the save date, linked to the saver’s account. If you choose “Tell them you enjoyed it,” we also store the date of that action. We do not create additional server copies of images, read text, or poster names for saved discoveries.
Text read from a canvas — to provide features such as search on canvas posts, we store text read from the canvas image after privacy processing (masking), along with its approximate position on screen. Reading is always performed on the masked image, so text from areas you hid is never included. For how the original of a hidden area is handled, see clause 4.
Recording data — the screen-recording video may be uploaded to the server temporarily in order to extract recommendation cards. The original video file is deleted once posting completes, and files left unprocessed are deleted after roughly seven days. What is retained long term after posting is the data needed for extraction and sharing — the extracted recommendation cards, the composed canvas image, and the text described above — together with the original image of any area hidden using a recent version of the app, stored so that it is linked to the poster alone (see clause 4).
Trace (search action) information — when you search for a video from another person’s canvas post, for example by double-tapping a title, we record that action (the post concerned, the title searched, its approximate position on the canvas, its category classification, the number of times, and the most recent timestamp) linked to your account. For who can see this, see clause 3.
Notification token — if you allow push notifications, your device’s notification token is stored on the server so that notifications can be delivered.
Location (optional) — only if you explicitly enable the feature that adds a coarse area label to a post do we obtain a coarse location at roughly municipality level (about 1 km accuracy). It is off by default, and the Service works without granting it.
Holiday calendar (optional, on-device only) — only if you explicitly enable the feature that distinguishes “weekdays” from “days off” for fixed-observation reminders do we read only the dates in your device’s holiday calendar. The reading happens entirely on the device; we do not read the contents of any event, and the dates read are never sent to or stored on the server. It is off by default, and the Service works without granting it.
Device and session information — we obtain your device’s model name in order to manage sign-in sessions.
Usage and quality information (analytics) — to improve the Service and detect faults, usage information such as screen transitions and key actions, an account identifier, and device information may be sent to external analytics and crash-detection services (PostHog, United States; Firebase, Google). We are not sending this at present; if it is enabled in future, this Policy will say so in advance.

2. How we use it

Providing the Service (sharing and displaying snapshots, canvas search, aggregated trace displays, and showing the poster their own search history)
Storing the original image of hidden areas (kept for the poster’s own benefit; see clause 4)
Reopening and searching saved discoveries, returning to their source records, and displaying feedback you explicitly choose to send
Delivering push notifications (reactions, follows, and similar)
Operating and maintaining the Service, improving quality, and fixing faults
Preventing misuse, including handling reports

3. Who can see trace information

Trace information is not public. Only the poster of the post on which the action occurred can see it. The poster may be shown, as a recent search history, up to 20 entries containing the searching user’s name and user ID, the title searched, the number of times, and the most recent timestamp. This search history is shown even when fewer than three people have searched.

Separately, the poster may be shown aggregate views: the most-searched titles, which participants searched, and the distribution of approximate positions on the canvas. Those aggregate views appear only when three or more users have searched, and they never tie a per-title count to a user’s name. Searches by the poster themselves, searches by users in a blocking relationship, and actions on X and Threads posts are excluded from both the poster’s search history and the aggregate views.

4. About hidden (masked) areas

When you hide part of a canvas at posting time, that part is not included in any published image or in any text read from it. For areas hidden using a recent version of the app, the original image is stored linked to the poster alone. Deleting the post also deletes the original of the hidden areas, and deleting your account deletes everything. Areas hidden using older versions of the app, and areas hidden in past posts, were discarded completely before storage as before and cannot be recovered. A stored original of a hidden area may, in future, be something the poster can explicitly choose to reveal (for example a feature that shows it to particular people or for a limited time). It is never shown to a viewer unless the poster chooses that. We will give notice before any such feature launches. Originals of hidden areas are never used for search, trace aggregation, analytics, or AI training.

5. Sharing with third parties; external services

We do not sell personal information to third parties. A snapshot’s visibility follows the setting you chose (Only You / Friends / Public). A post set to “Friends” is shown to members of the groups you belong to. Account information and post data are stored on a Mac server managed by the operator. Website and API communications use Cloudflare. The Service uses the following external services, each of which applies its own privacy policy: network transport (Cloudflare), sign-in (Google / Apple), push delivery (Apple), and usage analytics and fault detection (PostHog, United States; Firebase / Google — as stated in clause 1, we are not sending this at present).

Saving a discovery alone does not show it to other users or notify the poster. Only if you explicitly choose “Tell them you enjoyed it” do we show that discovery and your profile information to the source poster within the app. You can undo this feedback. Deleting the saved discovery also removes that feedback from view.

When data needed to display a saved discovery is retrieved from the server, we check current visibility, both users’ group memberships, blocks and reports, and changes to the source image. If access to the source record is lost, or its image is changed by an additional mask or another replacement, the discovery cannot retrieve the previous image or text. Search text is read from the currently viewable image area.

When the recording owner selects an image excerpt and uses the iPhone share function, the selected image is passed to the app or service that person chooses. It may include a display name, recording date, and an optional caption. Images sent or saved through that destination are outside Peeksy’s post visibility settings and are not affected by later deletion or masking in Peeksy. Their handling and recipients depend on the destination app or service’s settings and privacy policy.

In addition, a recommendation card’s title and channel name may be sent to the YouTube Data API in order to identify a video. Only that text is sent, as a search query; no other personal information is included.

We take necessary measures, including reviewing providers, contracts, and service terms, so that each provider protects information to a standard equivalent to this Policy.

Details of external transmissions

Cloudflare: the connecting IP address, request information, and data sent or received to provide the Service, including account information and post data, pass through Cloudflare’s network when connecting to the website and API. The Service’s account information and post data are stored on the Mac server managed by the operator.
Google / Apple: authentication information, your name and email address (when you choose to provide them), and authentication results are sent for identity verification and account management.
Apple App Store / APNs: product identifiers, purchase status, and notification tokens are sent for entitlement checks, purchase restoration, and notification delivery.
YouTube Data API: video-title and channel-name text may be sent to identify a video and create a link to it.

We do not use advertising or track you across other companies’ apps or websites. Usage and fault information transmission to PostHog and Firebase is currently disabled. If we enable it, we will update this Policy and provide any notice or consent that is required.

Stopping external transmissions and your privacy choices

You can change optional permissions such as Photos, Calendar, Location, and Notifications at any time in iPhone Settings. Communications that are essential to providing the Service, such as authentication, hosting, and purchase verification, cannot be stopped individually while you continue to use it. To delete your account, or to request access, correction, deletion, or restriction of your data, contact us under clause 10.

6. Retention and deletion

Snapshots are kept until you delete them. You can delete your account from the app under the You tab → Settings → “Delete account”, after confirmation. Deleting it removes the data linked to your account from the server — snapshots, images derived from recordings, text read from canvases, trace information, notification tokens, and follow, reaction, and group-membership information.

You can delete a saved discovery. Doing so deletes its saved reference and associated feedback. Those references and feedback are also deleted if the source post is deleted, or if the saver or source poster deletes their account.

Retention of recording data is as described in clause 1. A notification token is also deleted at the point Apple’s servers tell us the device can no longer receive notifications.

You may withdraw an optional permission or consent at any time. Withdrawal does not affect the lawfulness of handling based on consent before it was withdrawn.

7. Future features

The Service may in future introduce usage analytics, technical development for improving features (including artificial intelligence and machine learning), or integration with new external services. If any of these would involve handling personal information beyond what this Policy describes, we will give notice on the Service in advance and obtain the consent required before doing so. We will not rely on this clause to widen our handling without consent.

8. About YouTube content

Thumbnail images, video titles, and channel names contained in a snapshot belong to YouTube and to their respective rights holders. The Service is not an official YouTube service and has no affiliation with YouTube or Google LLC.

9. Revisions

This Policy may be revised as necessary. We will give notice on the Service when there is a significant change.

10. Contact

For questions about this Policy, please contact [email protected].

Effective: 7 July 2026
Last revised: 13 October 2026