Privacy
Collection and delivery boundaries.
This notice describes behavior evidenced by the application and identifies external privacy facts that require independent operator verification.
01 — Notice at collection
Application evidence first. External facts stay explicit.
- 01
Form data
The operations diagnostic collects a work email, company, workflow, approximate volume, systems involved, desired outcome, optional timing context, and explicit follow-up consent. The SEO audit collects a website URL, email, optional company, and explicit consent. Both forms also use a hidden decoy field and form-load timestamp for abuse screening.
- 02
Provider acceptance
A production success message means only that the configured mail provider accepted the API request. It does not confirm inbox delivery, reading, assignment, or a response. Provider rejection, unavailability, or an ambiguous timeout returns a failure and the application does not retry automatically. An explicitly configured local-development transport is labeled as local and contacts no provider.
- 03
Site assistant
The anonymous assistant conversation is retained for up to 24 hours. The browser sends one new message at a time and cannot supply authoritative history. When the assistant is enabled, eligible turns send the new message and bounded prior conversation to the configured model provider to select an allowlisted response action. Security-sensitive, abusive, and out-of-scope turns can be answered locally without a model request. Do not include passwords, credentials, secrets, or sensitive personal information. No contact detail or phrase automatically sends a transcript to a person. A transcript is sent for human follow-up only after the visitor reviews the visible conversation, opens the handoff control, provides an email address, and explicitly consents. The assistant panel can delete the active server session and cookie, but deletion cannot cancel a provider request that has already started.
- 04
Abuse controls and identifiers
Public form submissions, assistant session creation and turns, and transcript handoffs use a BotID automation signal before any model or mail provider call and fail closed when that signal is unavailable. BotID provider processing, retention, and deployed settings require external verification. Public forms, assistant turns, and transcript handoffs use minute and 24-hour abuse quotas. On Vercel, the application uses the platform-resolved IP address only for those quotas. The address is normalized and pseudonymized with a keyed HMAC before quota storage; raw addresses are not placed in application logs, events, or Redis keys. Local execution ignores forwarding headers. Anonymous session and idempotency records expire no later than 24 hours. IP-derived quota keys expire no later than 24 hours.
- 05
Operational events
Runtime events contain only a schema version, canonical UTC ISO timestamp, event name, request ID, coarse route, latency, and optional provider outcome and error classes. They exclude prompts, replies, form text, email addresses, and full IP addresses. External sink retention, restricted-access ownership, alert routing, and named primary and backup owners require independent operational evidence before the event path is treated as release-ready.
- 06
Measurement surfaces
The application includes Vercel Analytics and Speed Insights. This notice does not infer their deployed provider settings, cookie behavior, or retention period from the installed components.
- 07
Provider retention and escalation
Assistant conversation content is processed by the configured model provider, and form or consented-transcript content is sent to the configured mail provider. Form content is not separately retained in the application session store. Model-provider retention and deletion, mail-provider and inbox retention, deletion completion, and the named incident-escalation owners require private operational evidence before those provider-dependent paths are treated as ready; this application cannot prove those external controls by configuration alone.
Privacy and deletion requests
Privacy or deletion requests can be sent to hello@zaydream.com. Deleting the anonymous assistant session does not delete a message already accepted by a mail provider. Receipt, identity verification, provider or inbox deletion, and completion are governed by the applicable verified production procedure.