Last updated: June 30, 2026 — operated by Erbacci LLC (Wyoming, USA) · How your data moves through TimeStack and where it lives.
Your Ring snapshots are read on the schedule you set, stored only in a private AWS account in the EU (eu-west-1), and compiled into time-lapse reels you view through short-lived private links. Ring camera media stays in AWS, with one disclosed exception: the “your time-lapse is ready” email embeds a single still frame from your camera, which is sent to our email provider to deliver that message. The data sent to a third party is the address and content of two transactional emails, plus that one embedded still frame (delivered by Resend).
1 · Link You add TimeStack in the Ring app and tap "Connect with Ring". A one-way, server-to-server OAuth token exchange links your account. We read your account's verified email from Ring's Users API (GET /v1/users/me) — you never type it. We never see your Ring password.
2 · Capture On your chosen cadence and working-hours window, our backend (AWS Lambda, eu-west-1) requests still snapshots from Ring's recording-derived Image Snapshots API for the cameras you designated. No live video, no audio.
3 · Store Snapshots are written to a private Amazon S3 bucket (all public access blocked, SSE-AES256 at rest). Project/config metadata lives in DynamoDB (encrypted at rest).
4 · Compile A scheduled job stitches your snapshots into daily and cumulative MP4 reels with ffmpeg (deterministic sequencing/encoding only — no AI, no detection).
5 · View The dashboard fetches reels via short-lived presigned URLs (6-hour expiry). Media is never public.
6 · Notify When a reel is ready, a notification email is sent via Resend (address, dashboard link, and one still frame as a preview).
| Data | Location | Leaves AWS? |
|---|---|---|
| Ring snapshots (JPEG) | Private S3, eu-west-1 | No — except one frame embedded in the reel-ready email |
| Compiled reels (MP4) | Private S3, eu-west-1 | No (only you, via presigned link) |
| Account ID, email, project config | DynamoDB, eu-west-1 | No |
| Ring OAuth tokens | DynamoDB, eu-west-1 (purged on unlink) | No |
| Email address + message content (reel-ready notice / sign-in code) | Sent to Resend to deliver the email | Yes — address, text, and one still frame in the reel-ready email |
The dashboard credential is an opaque, server-issued session token. There are no passwords anywhere.
ts_recover) holds only an HMAC-signed Ring account identifier — no password, no session token, no personal data — and silently re-issues a session on return.Ring applies a standard server-side watermark to all camera media — the Ring logo (top-left) plus the device ID, app name, and timestamp (top-right). It is present on every snapshot and therefore appears in the compiled reels. TimeStack does not add, alter, or remove it.
| Provider | Purpose | What it receives |
|---|---|---|
| Amazon Web Services | Compute (Lambda), storage (S3), database (DynamoDB) — all in eu-west-1 | All processing and storage of Ring media happens here, and only here. |
| Resend (resend.com) | Transactional email delivery: the "reel is ready" notification and the passwordless sign-in one-time code | Recipient email address + message content (a dashboard link, or a 6-digit code). Never any Ring snapshots, reels, or video. |
We share customer data with no other third parties for their own purposes, and we never sell data.
You can delete your account and all data instantly from the dashboard (Settings → Delete account & data): this purges your snapshots, reels, projects, settings, and Ring tokens/session right away. Disabling TimeStack from the Ring app also revokes access and stops capture.