What crosses the boundary
The contact protocol asks for a name, work email, optional organisation, inquiry category, time horizon and the problem or consequence you choose to describe. It does not accept attachments.
Limited technical signals are processed to resist automated abuse, including request timing, a short-lived hashed rate-limit key and a reCAPTCHA Enterprise risk assessment. Inquiry text and contact details are not written to application logs or a site database.
One message, bounded uses
Information is used to assess and respond to the inquiry, maintain the security of the contact channel, meet legal obligations and establish correspondence if both sides choose to continue. It is not sold, used to build advertising profiles or enrolled in a marketing list.
Hosting, bot-assessment and message-delivery providers process only the data required for those functions. Processing may occur outside Singapore under the applicable provider safeguards.
No shadow contact database
The website does not retain a second copy of a submitted brief. A message that reaches the private intake queue is kept only for the response and relationship it initiates. Inquiries that do not progress are reviewed for deletion within 30 days, unless a longer period is needed for security, legal or record-keeping reasons.
Ephemeral rate-limit records expire automatically. Operational logs are designed around outcome codes rather than message bodies, names or addresses.
Privacy and DPO channel
Use the dedicated privacy category to ask what is held about you, request a correction or deletion, withdraw consent where applicable, or raise a data protection concern. This separates public accountability from the founder’s operational identity.
Formal privacy and DPO correspondence may also be sent to the deliberately public role address privacy@deepvertical.ai. It is not the founder’s sign-in identity or the general contact channel.
OPEN THE PRIVACY CHANNEL