1. Scope and responsible business
This working notice concerns DealDot’s own public website and inquiries to DealDot. It does not replace a contractor client’s privacy notice for that contractor’s website or a separate client-data processing addendum. The responsible legal entity and official privacy contact must be confirmed: $LEGAL_ENTITY and $PRIVACY_CONTACT. In the meantime, privacy questions can be raised through the Contact page.
Descriptions of current application behavior below were checked against the website implementation. Hosting-provider logs, email-provider retention, international transfer arrangements and business retention periods require confirmation before this notice is relied on as a complete production disclosure.
2. Information you provide
Public contact and consultation forms request your name, email and a description of your business. Optional fields may include phone numbers, business name and address, website and social links, competitor or inspiration websites, service interests and budget context. Trade inquiry forms collect a shorter set of business and contact details.
Only provide information needed for your inquiry. Do not include passwords, payment-card information, sensitive identity or health records, or private details about your customers. You may contact DealDot to correct an inquiry. Do not submit another person’s information unless you have an appropriate basis to do so.
3. Technical and security information
Requests necessarily involve technical information such as network address, request details and browser communications. The application uses an IP-derived keyed value for temporary abuse counters, signed form-session tokens, a hidden anti-spam field and input validation. Its abuse counters are temporary memory values rather than a stored contact database.
The reviewed application does not persist submitted inquiries in an application database. Infrastructure and delivery providers may process technical logs and email records under their own practices; the absence of an application database does not mean no information is retained elsewhere.
4. Purposes and delivery
Inquiry details are used to understand your request, assess potential work, communicate with you, send a submission copy where the form confirms that function, and protect the inquiry channels from misuse. An inquiry does not itself authorize unrelated promotional messaging.
When configured and available, the forms send inquiry details through Resend’s email delivery service to DealDot’s configured recipients and a copy to the email address supplied. Email delivery may fail; rely on the displayed submission status. The interface does not request or process payment-card information for a purchase.
5. Providers and disclosures
The reviewed site uses the Sites hosting environment and an email delivery integration. Providers may receive information necessary to host the website, secure requests or deliver email. DealDot may also need to disclose relevant information for a lawful request, an actual dispute, fraud investigation or protection of rights, limited to the circumstances and applicable law.
A complete business inventory of recipients, service providers, processing locations, sharing practices and any sale or targeted-advertising activity remains to be confirmed. This draft does not claim verified absence of every kind of sharing, sale or provider reuse across DealDot’s entire business. Adding analytics, advertising, embedded assistants or other integrations requires an updated inventory and disclosure.
6. Cookies and tracking
The reviewed public application includes no advertising pixels, third-party analytics scripts or embedded public AI chat. The Cookie Notice distinguishes that application behavior from cookies or storage that a hosting, access or external service may use. External websites opened through links operate under their own notices.
Do not treat this draft as a guarantee that a hosting platform never sets cookies. A browser and provider audit is needed to finalize an itemized inventory, purposes and retention periods. Any future optional tracking must be assessed and appropriate controls provided before it is enabled.
7. Retention and security
DealDot should retain inquiry correspondence only for legitimate inquiry, business-record, security, dispute or legal purposes, using a documented retention schedule. The exact schedule is pending confirmation; $RETENTION_SCHEDULE must be completed. Provider retention and backups must be evaluated separately.
The application validates form content, checks request origin and limits misuse. These measures do not guarantee complete security. DealDot must define access controls, authorized recipient access, provider arrangements and incident handling appropriate to the information processed. Public forms are not secure repositories for sensitive records.
8. Choices and requests
Depending on applicable law and the circumstances, you may have rights to request access, correction, deletion, restriction, portability or an objection, and to withdraw consent where consent is the processing basis. Some laws provide additional rights concerning targeted advertising, sale or sharing, appeals or complaints. These rights are not universal and may have lawful exceptions.
Use the Contact page to request the confirmed privacy contact or raise a privacy request. Identify the inquiry and the action requested without sending unnecessary identity records. Identity and authority may need proportionate verification. Response procedures, official contact details, applicable jurisdictions, legal bases and appeals information must be finalized before adoption. Exercising a right should not lead to unlawful discrimination.
9. Children, transfers and updates
The website is directed to business decision makers, not children. Do not submit personal information about a child. If information has been submitted in error, contact DealDot so it can assess appropriate action.
Providers may process information across jurisdictions. Applicable transfer safeguards must be assessed using the actual provider arrangements; this draft does not claim a particular certification or transfer mechanism. Material changes in processing should be reflected in an updated notice with an effective date. Client processing of homeowner or lead data belongs in the client’s notices and relevant data-processing terms.
Unconfirmed operational details are identified rather than presented as established policy.