Privacy notice
DAPPWEB LIMITED, operating as DappWeb, publishes this notice to describe information collected through dappweb.ai, why it is used, how long it is retained, and how to request access, correction, or deletion.
01
DappWeb limits collection to website operation, attribution, project qualification, communication, and security.
The project form can collect project type, target chain or stack, repository URL, commit hash, launch date, budget range, contact channel, name or team, work email, optional contact handle, scope summary, landing page, first external referrer host, selected service, an optional answer about how you found us, campaign parameters, and advertising click identifiers when present.
DappWeb records first-party events such as page views, project-button clicks, contact-channel clicks, pricing and case views, and form progress. A random browser-session identifier connects events to a submitted inquiry within one session. Separate first and latest visit snapshots, selected service, campaign and ad-click parameters (including X's twclid when present) are retained in browser session storage so an inquiry remains attributed after navigation. Missing referral information remains unknown.
X advertising tracking is disabled until configured. When available, the Marketing preferences control lets you allow or decline it. With your permission, the X Pixel receives page visits and a conversion reference only after a project inquiry is successfully saved; an X click identifier may link that conversion to an ad. The application does not pass your name, email, project brief, phone number, or repository to the Pixel. Your choice is stored in this browser. Withdrawal stops future application calls and prevents the Pixel from loading on subsequent pages; it cannot undo information already sent.
The lead service receives normal request headers and creates a one-way IP hash that rotates daily for rate limiting. The raw IP address is not stored in the lead database by the application.
If you contact DappWeb through email, Telegram, WhatsApp, WeChat, or LinkedIn, that provider processes information under its own terms and privacy practices.
If you pay through Stripe Checkout, Stripe processes the contact, billing, and payment details you provide under its privacy policy. DappWeb's checkout service records verified payment references, amount, currency, and payment time for reconciliation and service delivery. The checkout service does not store your card number, security code, or a copy of the webhook request body.
02
Information is used to operate the site, respond to inquiries, scope technical work, attribute campaigns, measure conversion paths, prevent abuse, and maintain records of communication.
DappWeb uses Cloudflare for website, Worker, security, and database infrastructure, and Stripe for hosted checkout and payment processing when available. Information may also pass through the communication provider you choose. DappWeb does not sell project inquiry information or website event data.
Website event records are automatically deleted after 13 months. Project inquiries are automatically deleted after 24 months unless they are part of an active engagement, required for security or dispute handling, or retained for another documented business requirement.
DappWeb uses input validation, origin restrictions, rate limits, rotating one-way IP hashes, least-privilege infrastructure bindings, and access-controlled Cloudflare services. No internet service can guarantee absolute security.
DappWeb works with global teams and infrastructure providers. Information may be processed in locations different from your own, subject to provider safeguards and applicable requirements.
03
Contact [email protected] to request access, correction, deletion, or a copy of project inquiry information associated with your email address.
You can use email or a listed messaging channel instead of the project form. Do not submit private keys, seed phrases, API secrets, or unnecessary personal information through any public channel.
DappWeb may update this notice when the site, data flows, or service providers change. The reviewed date at the top identifies the current published version.
