Privacy notice

What the application keeps

We keep an internal order reference, a browser-ownership hash, your package and color selection, price, currency, duration, playback mode, requested and confirmed times, a random show seed, and payment and fulfillment status. You may choose to add a short nickname and message, which are private notes.

Payment records also keep Stripe Checkout and payment references, fixed Checkout parameters, a Checkout URL when needed, deadlines, status and error codes, and timestamps. The current application does not copy a billing email, full card number, CVC, or billing address into its order tables.

Payment processing

Card information is entered on Stripe’s hosted Checkout page rather than this website. Stripe processes information under its own privacy notice at https://stripe.com/privacy. We send the selected package, price and duration, internal order and environment references, and return addresses to Stripe. The optional private nickname and message are not included.

Stripe responses and signed notifications are used to verify and fulfill an order. The application stores selected event references, a comparison hash, processing state, error codes and timestamps, rather than the full webhook body. Stripe may process more information on its own hosted page than this application stores.

Cookies and browser storage

A first-party sky_client cookie connects this browser to its private orders for 7 days. An administrator’s sky_admin cookie has an 8-hour lifetime. The server stores hashes of these tokens, their roles, request-protection tokens and expiry times. These cookies are HttpOnly and SameSite=Strict, and use Secure on hosted deployments.

Tab session storage preserves a pending booking request or Checkout attempt so retries use the same order reference. A pending Checkout can include the optional private notes until it is cleared after verified payment or expiry. Administrator booking retries use separate tab session storage. Closing the tab normally clears tab session storage; browser restoration behavior can vary. The current application has no localStorage-based order database.

The timezone displayed for booking is read from your browser. This version has no application analytics, advertising pixels or marketing cookies. Stripe and the hosting provider may have their own operational records; their settings have not been independently audited by this application review.

Checkout abuse prevention

To help prevent repeated or abandoned Checkouts, the application uses a browser-ownership hash, links an order to a hash derived from the connecting IP address, and keeps short-lived request counters. The mapping does not contain a raw IP address. These hashes are pseudonymous rather than anonymous: they can link activity and orders while retained. Hostinger or other network services may independently keep raw connection information.

An order’s anti-abuse mapping is eligible for cleanup 30 full days after its paid show ends or its unpaid Checkout is verified expired, under the same investigation holds as the optional notes described below. Rate-limit counters expire through normal maintenance. This policy does not claim that Stripe or the hosting provider deletes its records at the same time.

Public sky and operator access

The public sky returns the public show identifier, package, palette, start and end time, random seed, source and timeline version. It does not return private order notes, ownership tokens, billing details or internal payment references.

The individual operator can view private order and payment processing records to investigate problems. Manual support records can contain the reason, verification result, operator identity, time and a redacted evidence reference. Do not submit card security data or passwords to support.

Hosting, logs and backups

The deployed application and its database are hosted using Hostinger’s managed website services. The local development version uses SQLite or an isolated MySQL database. Hostinger and network services may process connection data such as IP addresses and technical request information; their exact log fields, storage regions and retention require operator confirmation.

The application stores audit entries for administrative actions and payment processing. Its standard error logger writes error categories rather than request bodies, cookies or payment keys. Database backups can contain private order and operational records and must be restricted. The owner has chosen not to enable a new backup or external alert service. This does not remove any copies or logs maintained by the hosting provider. Such provider retention and support email retention have not been independently verified.

Retention and requests

Expired application sessions and rate-limit rows are removed by maintenance. The order-maintenance task checks at most once per day and can clear the optional nickname and message 30 full days after a paid show ends, or after an unpaid Checkout has been verified expired by Stripe. An unresolved payment or scheduling issue, an unfinished or rejected notification, or any linked support case keeps those notes for investigation. Maintenance runs only when enabled for the deployment’s order schema; it is not a promise that all data is erased after 30 days.

Order ownership, payment and Session references, package and policy snapshots, scheduling records, event processing and support/audit records are retained. They are needed for secure order access, reconciliation, duplicate-prevention and issue handling. We retain necessary transaction and security records for accounting, reconciliation, tax and legal obligations. Retention is reviewed using the related tax return filing and due dates, applicable requirements and investigation holds; core records are not automatically deleted after 30 days. No automatic deletion of Stripe/Hostinger copies, email, browser storage or offline archives is represented here.

Contact support@wetogether.cc for privacy questions or requests. The individual operator handles support. Requests about access, correction or deletion require appropriate ownership verification and consideration of applicable law. This notice does not promise immediate deletion or claim that legal bases, international transfer safeguards or worldwide compliance have been reviewed.