1. Who this policy covers
This policy applies to the public Doory website at doory.net. The client portal at my.doory.net is operated through Upmind and may present additional account, billing, domain, and support notices. The service provider is Jeff Kershner d/b/a Doory, reachable at the addresses in section 12.
2. Information you choose to provide
The project form requests name, work email, company, current website, team size, service interest, desired timeframe, approximate budget, and message. Do not submit credentials, payment details, private customer records, health data, or other sensitive information.
The website application does not use a database for contact messages. Accepted submissions are forwarded to the configured business recipient through Resend’s HTTPS API. The recipient mailbox and Resend may process or retain delivery and message data under their respective settings and policies.
3. Technical and security information
Cloudflare may process network, browser, request, security, and performance information to deliver the site, apply rate limits, verify Turnstile, and protect services. The application avoids logging contact-message content. Security providers may retain event information under their policies.
4. Analytics
The site supports Google Analytics 4 or Google Tag Manager only when the owner configures an identifier. The local data layer records interactions such as service views, plan selection, portal clicks, domain-tool position, TLD, outcome, and contact completion. Complete searched domains are not sent to third-party analytics by default.
Analytics configuration, consent requirements, retention, and cross-domain measurement for doory.net and my.doory.net must be verified before enabling production tags.
5. Domains and the Client Portal
The embedded Upmind Domain Availability Checker loads only on the homepage and Domains page. Upmind and connected registrar services process search, availability, pricing, premium status, ordering, account, and billing data under their policies. Choosing a result can continue to my.doory.net.
A domain search is not submitted to general analytics in complete form by the Doory data-layer utility. The third-party widget’s own processing must be confirmed in Upmind’s production configuration.
6. Cloudflare Turnstile
The contact form uses Turnstile. The browser loads Cloudflare’s challenge script, and the Worker sends the resulting token to Cloudflare’s Siteverify endpoint. Tokens are validated server-side and are not treated as proof when verification fails.
7. Purposes
Information is used to respond to inquiries, evaluate requested services, operate and secure the website, diagnose failures, measure configured website interactions, meet legal obligations, and maintain business records. Doory does not claim to sell personal information.
8. Retention
Application-level contact storage is not implemented. Email, security, analytics, Upmind, registrar, and vendor systems have separate retention settings. Specific retention periods are still being documented with each provider.
9. Choices and rights
Applicable privacy rights depend on location and law. Requests should be sent to hello@doory.net. Identity verification and legal exceptions may apply. Browser controls may limit cookies or analytics; blocking required security or widget scripts can prevent those tools from working.
10. Data processors and transfers
Current processors: Cloudflare (hosting, security, Turnstile), Upmind and its connected registrar (client portal, billing, domains), Resend (contact-form email delivery), and Google (Workspace business email; Analytics only if an identifier is configured). Provider locations, subprocessors, contracts, and international transfer terms require professional review.
11. Security and limitations
Doory uses reasonable technical measures described on the Security page, but no online transmission or storage system is guaranteed completely secure.
12. Contact and changes
Privacy contact: hello@doory.net. Mailing address: 652 E Rojo Way, Gilbert, AZ 85297. Material changes should update the effective date and, where appropriate, provide additional notice.