Service policies
Privacy Policy
Orders and communication
The order form requires a name, selected design and a way to reply: email for Email, or contact details for WhatsApp/Telegram. Email is optional for messenger requests. Event title, event date, preferred ready-by date and message are optional. The interface language and a submission identifier are stored with the request. Older records may also contain phone and event type. Order records include status, agreed price, delivery arrangements and owner notes. Manual payment/refund records contain amounts, currency, dates, methods, references, notes and correction history; the website does not offer a card checkout. These records support preparation, communication and manual payment management.
Invitation materials
The service stores invitation texts, selected languages, event timezone, dates, places, links and submitted images used in enabled invitation sections. Images are processed into private display and thumbnail files; the application does not retain public original uploads. Data records are stored in PostgreSQL and image derivatives in private application storage. Production hosting location and providers still need confirmation.
Guests and visibility
Guest RSVP records contain a name, attendance choice, party size, optional comment, answers to configured questions and submission time. Every successful submission is a separate response; guests have no account or edit link. The owner can read responses and manually share them and totals with the customer. A published, unexpired invitation and its enabled images are accessible to anyone with its public link, which can be forwarded. Guest responses are not displayed on the public invitation.
Optional private customer links
If issued, a separate secret customer link grants read-only access to event RSVP history and totals. Anyone holding it may gain access, so it must be kept private. This access can remain available after invitation expiry or unpublication until the owner revokes or replaces the link or deletes the event. It does not grant invitation editing or owner access. Linked order price snapshots, agreed amounts and net payment summaries are also visible through this private access.
Storage and expiry
Invitation expiry or unpublication stops public page and image access; RSVP closure stops new responses. Neither automatically deletes stored invitation data, images, orders or existing responses. The current application has no automatic business-data retention schedule. Owner deletion of an event removes its invitations and RSVP records and triggers related image cleanup, while linked order/payment history is preserved. Deleted public slugs remain permanently reserved. Data, backup and log retention periods and deletion procedures remain to be decided.
Technical data and other services
Session records include an IP address, browser user-agent, activity time and session state, used for sessions and security. Short-lived abuse limits use IP-derived keys. Hosting logs and backups require a production inventory. Optional Google Analytics and Yandex Metrica integrations are available. If enabled, they load only after consent on the homepage, catalog and service-category pages. The application does not send names, contact details, request text, photographs or RSVP data to analytics. Full URLs with query strings and referrers are excluded; session replay, click maps and automatic link tracking are disabled in the Yandex integration. Technical visit data may be processed by Google and Yandex under their policies. Provider settings, recipients, transfers and retention must be reviewed before activation; see the Cookie Policy. Order email notifications can be enabled only after configuration; production email recipients/providers and delivery are not yet verified. Following external map or contact links takes you to services with their own policies.
Questions and decisions still required
Use the contact page for a privacy question or request. The responsible operator, privacy contact, legal bases, applicable rights and complaint route, hosting/email recipients, international transfers and retention/deletion rules must be confirmed before this draft becomes a final notice. This draft does not promise an unconfirmed response deadline.