What we store for alerts and billing
The server stores your watches, their settings and private management keys or key hashes. If you choose email alerts, it stores your email address and confirmation state. If you connect browser alerts, it stores the push endpoint and the keys needed to deliver to that browser. We also store delivery state, delivery attempts and watch-management audit records.
For billing, we store Stripe customer and subscription IDs, subscription status, billing-period dates and cancellation state, associated with an owner identifier and a hash of the management key. We do not receive or store your card number: Stripe handles card details under its own privacy policy.
What stays in your browser
Saved movies and theatres, remembered theatre and format choices, and this device’s copies of management keys are kept in browser storage. Bookmarks are not alert subscriptions and are not uploaded as a saved list. Management keys are sent to our server when you use them to access watches or billing; they are not browser-only secrets. Optional location coordinates are used in browser memory to find nearby theatres; the site sends theatre identifiers, not those coordinates, to the server.
You can clear saved movies and theatres from the saved-items drawer or remove local data through your browser settings. Clearing local data does not delete server watches or cancel billing.
Connections to other services
Movie and theatre images can load from AMC’s image CDN, including amc-theatres-res.cloudinary.com. Maps load tiles from OpenStreetMap. These browser requests reveal your network address to the image or map service. Ticket links take you to AMC.
Subscribe and Manage billing take you to Stripe-hosted pages. Browser alerts use your browser’s Web Push service. Email alerts and confirmation messages are sent through our configured email provider; that provider receives the destination address and message. These services handle data under their own policies. The site does not include advertising, analytics scripts or tracking pixels.
Request logs and network addresses
The application’s request log records the time, request identifier, HTTP method, route, response status, duration and archive-source category. It does not put management keys, email addresses, request bodies or network addresses into that structured log. The application uses network addresses in memory to limit request rates. These statements describe the application, not the separate logging practices of your network or third-party providers.
Retention and deletion
Watches and their delivery settings remain stored until deleted. Deleting a watch removes its current subscription, associated channel registration, observation baseline and delivery events. Watch-management audit records can remain; the application keeps a bounded audit history. Short-lived hashed email-confirmation request records are cleaned during delivery processing. Completed delivery history is pruned during processing after 90 days; pending delivery work can remain longer.
Deleting a watch does not delete billing records or cancel your paid plan. Billing records remain stored; there is no automatic billing-record deletion schedule in the application. Cancel the plan with Manage billing to stop renewal. For privacy or deletion questions, contact Vibe Frontier, LLC. We do not promise that deleting an item removes every historical record held by a payment or delivery provider.