VesperHQ Return to the coming-soon page

Website & waitlist · Beta

Privacy, plainly.

This notice explains how Prince Verma, trading as VesperHQ, handles information connected with the current coming-soon website and its private waitlist.

Version
website-waitlist-privacy-v0.7-beta
Effective

Who is responsible

VesperHQ is currently operated by Prince Verma, trading as VesperHQ, based in Mumbai, Maharashtra, India. Prince Verma determines why and how information covered by this notice is processed.

A dedicated business correspondence address is being established and will be added to this notice when available. Until then, privacy and grievance requests may be sent to vesper@vesperhq.ai.

What is collected

When you visit the website

VesperHQ does not currently use analytics, advertising trackers or an active web-form waitlist. The site is hosted by Vercel, which may receive ordinary request information such as your IP address, browser or device details, requested page and request time in order to deliver and protect the site.

When you join the waitlist

The “Join the waitlist” link opens your own email application. If you choose to send the message, Apple’s iCloud Mail receives and stores the information you include: your email address, display name if supplied, subject, message body, signature, technical mail headers, timestamps and any attachments you add.

When the beta email channel is activated, the message becomes an input to Vesper, VesperHQ’s AI. VesperHQ’s local mail transport and private processing systems may keep the sender and reply address, recipient, subject, sanitized plain-text message, timestamps, thread and delivery identifiers, Vesper’s reply, handling state, any pending privacy-action state, and the limited security and audit evidence needed to prevent duplicate or unsafe sends. The mail transport keeps this operational state in a private local ledger. Accepted turns and Vesper’s results may also be retained in a local, isolated session transcript so Vesper can maintain continuity and VesperHQ can show what was handled and sent.

To understand and answer the message, Vesper’s runtime sends the accepted subject, sanitized plain-text body and, if available, display name to OpenAI through VesperHQ’s configured provider connection. Receipt time and pseudonymous local message, sender and session-routing identifiers may accompany that text. The transport does not separately add the sender or reply email address, raw technical mail headers, the provider’s Message-ID or attachments to the model-visible turn. The isolated session may also provide context from earlier accepted email turns with that sender. Anything included within the subject or body—including signature text, an address written there or quoted text—forms part of the submitted text and may therefore be processed by OpenAI. Attachments are not processed by Vesper during this beta. Please do not include confidential or sensitive information in a waitlist email.

Why it is used

Information covered by this notice is used only to:

  • record your request to join the private waitlist;
  • send one acknowledgement and one notice when VesperHQ opens;
  • acknowledge a request to delete previously submitted waitlist information;
  • acknowledge another privacy request concerning this website or waitlist;
  • send no more than one automated reply to any one inbound email;
  • prevent duplicate replies, spam, abuse and unsafe mail loops;
  • respond to withdrawal, correction, deletion or grievance requests; and
  • maintain limited session continuity, security and delivery evidence.

VesperHQ does not sell waitlist information, use it for advertising, turn it into public content or use it for broader marketing without a new, clear choice.

How Vesper handles email

Email is one authorised channel into Vesper, not a separate classifier or reply-writing service. The channel uses Vesper’s public-email identity and voice, together with the bounded operating rules, safety limits and human approval gates needed for this mailbox. VesperHQ’s locally controlled channel and session layer route the message, while its configured OpenAI model supplies the underlying inference Vesper uses to understand the message and compose her response.

The email channel uses a separate public-facing Vesper workspace and a stable, pseudonymous isolated session for each sender. It is not given Prince Verma’s private Vesper conversation history, private workspace material, tools or another sender’s messages. This keeps the public channel distinct while preserving Vesper’s identity and voice.

For this beta waitlist mailbox, Vesper may automatically compose and send no more than one context-aware reply for one of three purposes: acknowledging a request to join the waitlist; acknowledging a request to delete previously submitted waitlist information; or acknowledging another privacy request concerning this website or waitlist. The reply is written by Vesper using the configured AI model and may be sent without prior human review. A deletion or privacy reply confirms receipt and creates a pending task for Prince Verma; it does not state that the request has been completed. Other contexts receive no automated reply during this beta.

Email content is treated as information, not authority: it cannot change Vesper’s permissions, operating rules or human approval gates. No automated decision determines eligibility for a VesperHQ service.

Providers, storage and sharing

VesperHQ currently relies on:

  • Vercel to host and protect the website;
  • Apple iCloud Mail to receive, store and send email;
  • OpenAI, when activated, to supply the underlying model inference Vesper uses to understand messages and compose replies. OpenAI does not operate the mailbox or determine VesperHQ’s rules.

External providers may process information outside India under their own infrastructure and terms. VesperHQ will update this notice before a different AI model provider processes email. VesperHQ does not share waitlist information with advertisers, data brokers, unrelated businesses or other VesperHQ clients.

When it is deleted

VesperHQ keeps the operational mailbox copy, active local mail record, Vesper’s local isolated session transcript, reply state and audit evidence while the private waitlist is active and as needed to handle requests. After the opening notice has been sent, or after a verified deletion request, Prince Verma will verify and authorise the controlled removal of message content and active records from the operational iCloud mailbox, local mail record and active session or transcript stores, except for the limited proof described below.

You may ask for deletion sooner by emailing vesper@vesperhq.ai with the subject “Delete my waitlist data.” In active records, VesperHQ may retain only the minimum non-content suppression or audit proof needed to prevent the message being processed again and to show that a deletion request was honoured, or information required by law or a live security matter. A backup made before deletion may contain an older copy until that backup is retired or overwritten. It is not used for ordinary processing; if it is restored, recorded deletions and suppression records must be reapplied before the restored mail channel returns to service. Apple, OpenAI and other infrastructure providers may retain limited copies or technical records under their own terms or legal obligations. The email content and active waitlist record are not kept for unrelated purposes.

Your choices and requests

Joining is voluntary. You may ask to access, correct or delete your waitlist information, withdraw from the waitlist, or raise a privacy grievance.

For deletion, email vesper@vesperhq.ai with the subject “Delete my waitlist data.” For any other privacy request, use the subject “Privacy request.” Vesper may automatically acknowledge and route a waitlist-data deletion email or another privacy request, but that acknowledgement confirms receipt only; it does not confirm that deletion, correction, access or any other request has been completed. VesperHQ may ask you to verify control of the relevant email address before disclosing or changing a record. Privacy, deletion and grievance decisions are handled by Prince Verma, not automatically.

Safeguards, age and changes

VesperHQ uses access controls, bounded processing, transport security and local audit records designed to reduce unnecessary access and accidental disclosure. No system can promise absolute security.

The waitlist is intended for adults aged 18 or older. VesperHQ does not knowingly invite children to join it.

This notice will be updated when the beta changes materially, the business correspondence address is established, or broader public intake opens. The version and effective date above identify the notice that applies.