A clear welcome. A small data footprint.
DoorSignal is a hackathon prototype for managing guest, delivery, and service arrivals. The public judge demo uses fictional events in a separate workspace.
What is saved
Expected visits, visitor-provided names and visit types, door-event metadata, host actions, notification states, and operational timing measurements. DoorSignal does not use facial recognition or claim to verify a person’s identity.
Camera images
In live mode, an authorized Ring image may be sent to Amazon Nova through Bedrock for coarse scene information. Image bytes are processed in memory and are not stored or included in application logs. Ring and AWS retain data according to their own service terms. Live video is receive-only and stays subject to Ring’s session limits and watermark requirements.
Retention and deletion
Live operational records expire after seven days; judge demo records expire after 24 hours. Future expected visits can remain until their arrival window ends plus one day. Expired records are hidden immediately and removed asynchronously by DynamoDB TTL. Hosts can delete their workspace’s active records in Settings. Short-lived operational logs expire after seven days. Infrastructure backups and service logs may have separate retention; this prototype does not enable DynamoDB point-in-time recovery.
Access and notifications
Operator controls require Cognito sign-in. Judge sessions cannot access live accounts, use Ring credentials, invoke Bedrock, or send external email. A visitor can read only their own check-in status through an expiring signed link. Email notifications go only to a configured host recipient; opening a link cannot acknowledge an arrival.
Before real-world use
The prototype needs site-specific privacy notices, verified operator access, participant consent, and operational evaluation before deployment with real visitors. For this hackathon, use the official Ring playground and fictional data.