Information we collect
The public inquiry form asks for your name, email, and a description of what's happening. Company and current tools are optional. We use those details to review the inquiry and reply.
If a project moves forward, private Project Fit and Client Onboarding workflows may collect additional project, system, owner, access, measurement, and delivery context needed to evaluate or operate the engagement.
Do not send passwords, API keys, MFA codes, payment-card information, customer exports, or other credentials through these forms.
How we use it
We use inquiry information to receive and review your request, determine fit, reply, and maintain the reasonable business record needed to handle the opportunity. Submitting an inquiry does not subscribe you to a newsletter or marketing list.
For client work, we may use information you provide to prepare scope, coordinate access and approvals, operate the engagement, measure agreed work, support handoff, and maintain necessary operational records.
Services and analytics
We use Cloudflare Turnstile on the public inquiry form to reduce automated abuse. Verification happens on the server and is limited to the form-security purpose.
We may use Resend to deliver transactional messages such as inquiry confirmations and project communications. Delivery status such as sent, delivered, failed, or bounced may be recorded in our internal operations system.
The public site uses Vercel Web Analytics for site traffic measurement. We do not use Google Analytics, advertising pixels, session replay, or chat tracking in the launch site.
Private Project Fit, Client Onboarding, and internal operations pages do not load the public marketing analytics component.
Data handling
Accepted inquiries and operational client information are kept in controlled systems with access limited to the work that requires it. Credentials and secrets belong in the designated credential manager rather than forms, project notes, or analytics.
Private form links may use signed or one-time tokens. Where the system stores a token verifier, it stores a one-way representation rather than a recoverable copy of the private token.
Retention
Retention depends on the purpose and type of record. Security rejection telemetry is configured for short-lived retention. Accepted inquiries, transactional records, and client operational records may be retained longer when needed for the opportunity, engagement, support, security, or recordkeeping.
We do not publish a fixed retention period here where the operational schedule has not been finalized. We update this notice when the underlying retention practice changes.
Questions or requests
For privacy questions or requests about information you submitted, emailhello@sentndelivered.com. We may need to verify your identity or relationship to the relevant company before acting on a request.