PRIVACY DRAFT
This draft explains the intended launch data practices for WestKYDigital’s website and request workflow. It must be checked against the final hosting, email, analytics, form, retention, and service setup before publication.
REVIEW STATUS
This language is operational planning, not legal advice and not a claim about a workflow that has not yet been activated.
Confirm the actual form fields, Hostinger mailbox, Elementor behavior, private-request plugin, email delivery provider, analytics and cookie settings, backup locations, retention schedule, and any third-party remote-support tools. Obtain appropriate legal review.
DRAFT CONTENT
A help request may include name, email, optional phone number, preferred contact method, customer type, service category, description, impact, city, optional ZIP code, preferred service method, and timing. Do not submit passwords, one-time codes, recovery keys, payment details, Social Security numbers, or sensitive customer records.
Information is intended to review a request, communicate about fit and scheduling, provide and document authorized services, prevent abuse, improve operations, meet legitimate accounting or legal obligations, and protect the site or its users. It is not intended for sale.
The launch plan stores requests as private WordPress records that are excluded from public archives, search, and public APIs. Access should be limited to authorized administration. Exact backups, logs, hosting locations, and technical safeguards must be verified before this statement is published.
A customer may receive one immediate confirmation. The owner is intended to receive one scheduled morning digest rather than an email for each request. Hosting, email, anti-spam, delivery, analytics, and support vendors may process limited information as configured; the final vendor list must be confirmed.
Request records, communications, service notes, and business records should be retained only as long as reasonably needed for service, security, legal, tax, warranty, and dispute purposes. A concrete retention schedule and deletion process must be adopted before launch.
A person may ask about, correct, or request deletion of information, subject to identity verification and legitimate retention obligations. The final contact mailbox and response procedure must be established before publication.
Reasonable safeguards reduce risk but no website, email system, remote session, device, or storage service can be guaranteed completely secure. Sensitive credentials should never be sent through a general form or ordinary email.
The service is not designed to collect information directly from children. A parent or guardian should make requests involving a minor. Material policy changes should be reflected with an updated effective date after review.
QUESTIONS OR FEEDBACK?
The public version will identify a verified mailbox and effective date after the operational workflow is confirmed.