Loopcam

Privacy policy

Last updated: 2026-08-18

Loopcam is a looping-video camera and sharing app, run as a personal project by its developer. It is currently in development and pre-launch: the service is not yet publicly available. This page describes what the Loopcam service — this site and the API at loopcam.lol/api — stores, what it does with it, and what it deliberately does not do.

What Loopcam stores

  • Account. Your username, your email address, a hash of your password if you set one (never the password itself), your Apple user identifier if you use Sign in with Apple, an optional avatar image and bio, the counts shown on your profile (loops, followers, following, LOLs, comments), and when your account was last active. An account created with Sign in with Apple whose email Apple did not report as verified has no email address on file.
  • Content you create. The loops you upload — the original video file plus the renditions the server transcodes from it (an MP4, a preview image, and a GIF), stored in object storage — along with captions and tags, your comments, your LOLs, who you follow, and @-mentions of other users.
  • Activity. A notification entry when someone follows you, LOLs or comments on one of your loops, or mentions you.
  • Devices and sessions. A push-notification token for each device that enables push notifications, and a session record for each device you sign in on. The session token itself is stored only as a SHA-256 hash, alongside an optional device name and when the session was last used.
  • Safety. Reports you file about loops, comments, or users, and the list of users you have blocked.
  • Abuse prevention. Short-lived counters used to rate-limit sign-in and sign-up attempts and uploads. Some of these are keyed by IP address or email address; they cover windows of between fifteen minutes and an hour and are reset as the windows roll over.

Face data

Two of the camera’s stickers, Pump and Fantom, replace your face with an animated character. While one of them is selected — and only then — the app runs Apple’s on-device ARKit face tracking (ARFaceTrackingConfiguration, the API family Apple refers to as the TrueDepth API) on the front camera. Frame by frame it reads an expression: a set of blend-shape values (how open the mouth is, whether the eyes are closed, and so on), the head’s position and orientation, and roughly how much of the frame the head spans.

  • What it is used for. Animating the character, on the device, in real time — nothing else. The values pose the character that stands in for your face in the viewfinder and in the loop you record. Face data is not used for identification, authentication, advertising, profiling, or any other purpose.
  • Storage, retention, and deletion. Face data is processed in memory and discarded as each frame is replaced by the next. It is never written to disk on the device, never stored on any server, and none of it remains once you switch stickers or leave the camera.
  • Sharing and transmission.Face data never leaves your device and is not shared with anyone, including Loopcam’s servers and any third party. ARKit’s processing happens on the device itself. The only thing Loopcam ever uploads is the finished video — the rendered frames in which the character has replaced your face — and only if you choose to post the loop.

What Loopcam does not do

  • No analytics, no tracking. There are no analytics SDKs, no advertising identifiers, and no third-party trackers anywhere in the app or on this site. These web pages set no cookies; the API authenticates with bearer tokens, not cookies.
  • No ads, no selling of data. Loopcam shows no advertising and does not sell or share your data for advertising or any other commercial purpose.
  • No Facebook Login, no Meta SDKs. Loopcam does not use Facebook Login and holds no data obtained from Meta.

Passwords and security

Passwords are stored only as scrypt hashes, never in plain text. Session tokens are stored only as SHA-256 hashes, so a leaked database could not be used to sign in as anyone. Sessions are per device and can be revoked individually. All traffic to the production service goes over HTTPS.

Where your data lives

In production, Loopcam runs on cloud infrastructure: Vercel hosts the site and the API, uploaded video and its renditions live in Vercel Blob object storage, and account and social data live in a hosted Postgres database. Push notifications are delivered through Apple’s Push Notification service. These providers process data on Loopcam’s behalf on their own infrastructure; Loopcam does not currently make any data-residency commitments. The hosting platform also keeps standard request logs (IP address, requested URL), as any web host does.

Sign in with Apple

The server supports Sign in with Apple, but it is not currently enabled in the app. When it is used, Loopcam verifies the identity token with Apple and stores your Apple user identifier, plus your email address only if Apple reports it as verified.

Moderation

Users can report loops, comments, and other users, and can block users. Moderation can remove loops and comments and suspend accounts. Content removed by moderation is hidden from the service but retained, marked as removed, while the report about it is handled.

Timestamping a loop

You can ask for one of your loops to be timestamped on a public blockchain. It never happens on its own: nothing about a loop is fingerprinted until you choose Timestamp on Bitcoin from its share sheet, one loop at a time.

What goes on the blockchain is a single 32-byte number derived from the loop’s files. No video, no image, no username, no account and no device information is written there, and the number reveals nothing about what it covers. Its purpose is narrow: it fixes the date, so that neither you nor Loopcam can claim afterwards that the loop existed earlier or later than it did.

The loop’s public proof page shows the file hashes, the time we received them, and a random value stored with them. Deleting the loop or your account deletes that stored value, which makes the record impossible to reproduce — so the entry on the blockchain, which cannot be removed by anyone, stops meaning anything. One honest caveat: if somebody downloaded the proof file while the loop was public, their copy keeps working afterwards. That is true of every timestamp there is, and it is worth knowing before you ask for one.

A private loop cannot be timestamped, and a timestamped loop that you later make private or delete stops having a public proof page.

Retention and deletion

Your content stays until you delete it or your account. Deleting a loop removes its database records and its stored video files. Uploads that are never turned into a loop are pruned automatically after 24 hours. Deleting your account removes everything attached to it — see Data deletion for exactly what that covers and how to do it.

Changes and contact

This policy will change as the project develops; the date at the top reflects the latest revision. Questions about it, or about your data, go to me@torrauden.com.

Loopcam is a personal project and is currently pre-launch. This page is written to describe the system accurately, but it is not legal advice and has not been reviewed by a lawyer. It should be, before any public launch.