Mailbox Alert · Erbacci LLC

How data flows through Mailbox Alert

From a Ring motion event to the notification on your phone — every hop, every store, and every retention window.

1. Event processing flow

Ring camera event signed webhook (HMAC) AWS Lambda ingress signature verify · dedupe fast acknowledge SQS queue async worker + DLQ Vision analysis Qwen 3.5 (our GPU) → Bedrock fallback two-stage · inference-only Derived event category · carrier type · confidence DynamoDB (90-day auto-purge) Alert snapshot private S3 bucket · encrypted auto-deleted after 90 days Customer notification push, or email fallback (Resend, sending-only) Web dashboard HTTPS API · session auth timeline, mail status, settings All hops encrypted in transit (TLS 1.2+). All stores encrypted at rest (AWS-managed encryption).
  1. Motion event. Ring sends a signed webhook to our AWS Lambda endpoint. The HMAC signature is verified on the raw body before any processing, and duplicate deliveries are discarded.
  2. Queue. The event is placed on an SQS queue for asynchronous processing (with a dead-letter queue for failures), so the webhook is acknowledged within Ring's time limit.
  3. Snapshot. The worker retrieves a single still image for that event via the official Ring Partner API.
  4. Vision analysis. Analysis is inference-only. The snapshot is classified by a first-party open-weights model, Qwen 3.5 (9B), served on a GPU workstation owned and operated by Erbacci LLC in Dubai, United Arab Emirates. It is reached over TLS through an Erbacci-managed relay server in Germany, which terminates TLS and forwards over an encrypted tunnel but performs no analysis and stores nothing; on the workstation the image is held in memory only and never written to disk, and only a short text label is returned. If that model does not return a usable answer — error, timeout, or a reply that fails validation — the snapshot is analyzed instead by Anthropic Claude Haiku 4.5 through Amazon Bedrock inside AWS (United States, inference-only; the provider does not train on our traffic), so no event is ever dropped by an outage. The output is an activity classification: mail delivered, package drop-off, mailbox visited, or nothing relevant, plus a confidence score. We do not report a carrier brand. The model is instructed to never identify individuals and never read text, addresses, or license plates.
  5. Store. The derived event record goes to DynamoDB (auto-purged after 90 days). For events that generate an alert, the single analyzed still is stored in a private, encrypted S3 bucket (auto-deleted after 90 days) so the customer's timeline can show what happened.
  6. Notify. The customer receives a push notification (mobile app), or an email fallback when no push token is registered — per their notification settings.
What never happens: continuous video is never stored; no facial recognition or biometric analysis is performed; no individual — including delivery drivers — is ever identified or tracked; no text, address, name, or license plate is read; customer media is never sent to any third-party analysis service — the only analysis systems are our own Erbacci-operated model and, as a fallback, Amazon Bedrock, both inference-only and neither retaining the image; nothing is used to train AI models.

2. Data storage locations and systems

System (AWS us-east-1)What it storesRetention
DynamoDB — usersAccount record: Ring account link, encrypted OAuth tokens, email, notification settings, per-camera mail statusUntil unlink or account deletion
DynamoDB — eventsEvent records: timestamp, device ID, category (mail delivered / package / mailbox visited), carrier type, confidence, labelAuto-expire after 90 days; deleted earlier on unlink/deletion
DynamoDB — sessions / nonces / dedupLogin sessions, one-time linking nonces, webhook de-duplication keysShort-lived / TTL-expired
S3 — snapshots (private bucket)One still image per alert-worthy event (public access blocked, encrypted at rest)Auto-deleted after 90 days; purged immediately on unlink/deletion
Lambda bundle (static site)This site, the web dashboard, privacy policy, terms — no customer datan/a
CloudWatchApplication logs (system events, processing outcomes — no media, credentials redacted)Per logging configuration
Ring camera videoNot stored. Only the single analyzed still per alert event is kept (see S3 row); continuous video never touches our systems—

User, event, and session tables have point-in-time recovery enabled. Encryption at rest uses AWS-managed keys; all traffic is TLS 1.2+. Access is restricted to least-privilege IAM roles; no human review of customer media occurs.