What stays local and what is sent.

Data stored locally in Chrome

Your AIS email and password, selected countries and cities, date range, polling preferences, successful-booking history, runtime state, and consent record are stored in Chrome extension local storage so the extension can auto-login and operate as configured.

Data sent to ExtensionCrate

After consent, the extension sends your normalized AIS email to check and purchase entitlement. While active, it also sends observed appointment cities and dates so ExtensionCrate can relay sanitized public availability alerts. ExtensionCrate stores email, Paddle transaction and adjustment identifiers, price, amount, currency, entitlement state, webhook audit records, and minimal successful-booking details: schedule identifier, visa class, applicant count, appointment date and time, location, confirmation page path, and an optional confirmation reference.

Data never sent to ExtensionCrate

Your AIS password, AIS session cookies, complete page HTML, and billing card details are not sent to or stored by ExtensionCrate. Paddle processes billing and payment details under its own privacy terms.

Purpose, retention, and deletion

We use transmitted data only to issue and secure access, reconcile payments, relay sanitized public availability and booking alerts, deliver privacy-filtered terminal booking-attempt logs to the private operations channel, record booking success, prevent abuse, and provide support. Terminal attempt logs contain only an attempt ID, appointment location/date, outcome, bounded timing counts, discovery source, and extension version; Extension Crate removes the entitlement email before relaying them. Public Telegram alerts contain appointment city/date and, for confirmed bookings, visa class/residency label and time; they never contain your email, schedule identifier, confirmation reference, or other account details. Entitlement, transaction, refund, dispute, and webhook records are retained as needed for access, fraud prevention, accounting, tax, and legal obligations. Booking details are retained for support and audit purposes. To request deletion of data that is not legally required, email appointmentservices9@gmail.com. Delete locally stored data by removing the extension or clearing its site data in Chrome.

Booking records

After AIS verifies a successful booking, the service stores the appointment location, visa class, appointment date and time, applicant count, schedule identifier, and confirmation reference for support and operational history. Only the sanitized location, visa class/residency label, date, and time are published to the public alert channel.

Security and sharing

Data is shared only with service providers needed to operate the product, including Supabase for backend storage and Paddle for payments, or when required by law. We do not sell personal data or use it for advertising.

Contact

Privacy questions and correction or deletion requests: appointmentservices9@gmail.com.