This policy must be reviewed and approved before public launch. The final hosting configuration, email provider, retention choice, and business contact arrangements still require confirmation.
Information you choose to share
The quote and contact forms collect your name, a usable email address or phone number, preferred contact method, company if applicable, and the project or inquiry details you provide. A quote request may include your role, category, requested work, city and ZIP code, optional street address, description, timing, stage, optional budget, and conditional information about the project.
The Work for Us form collects your name and contact information, whether you are an individual or subcontracting business, company name when applicable, city, optional ZIP code, selected trades, experience, availability, and any service area, credentials, or business website you choose to share. Do not submit government identifiers, birth dates, financial details, identity documents, or other people’s private contact information.
Do not include payment-card details, identification documents, sensitive personal records, access credentials, or information unrelated to the request. File uploads are not enabled in this version. If plans or photographs are needed, a suitable transfer method can be arranged later.
Why the information is used
Detroit Crews uses inquiries to review the requested work, communicate about the request, manage follow-up, and maintain project records. Work for Us information is used to review trade experience and availability and discuss potential work or subcontracting opportunities; an application does not guarantee selection or work. The form acknowledgment permits a response about your inquiry. It is separate from marketing; the website does not subscribe you to a marketing list.
Storage and access
This WordPress edition is intended for a separate Detroit Crews installation on Bluehost shared hosting. Inquiries, private notes, notification state, and limited audit events are stored in the WordPress MySQL database in dedicated Detroit Crews tables. Owner access uses native WordPress authentication and explicitly assigned Detroit Crews account capabilities. A typed email address does not grant access. The actual hosting account and backup arrangements must be confirmed before launch.
Administrative actions are recorded in an audit trail with minimal event details. Status, private notes, and notification state may be recorded with an inquiry. CSV exports are available to authorized users; an exported copy is then the recipient’s responsibility. Approved public project photographs may be added through the native WordPress Media Library by an administrator. Those files are public website assets after host protection is removed; private inquiry plans and documents must not be placed there.
Email notifications
The system stores an inquiry independently of email. The website uses a Resend HTTPS email adapter when enabled in private server configuration with an authenticated business sender. If sending is disabled or a notification fails, the saved inquiry or work application remains available to authorized users.
When approved and configured, Resend receives the recipient address and message content needed to send a notification or acknowledgment. Business notifications contain a reference, inquiry or application category, general location, and a secure owner-dashboard link. They do not include the full project description or applicant experience. An acknowledgment is sent only when the visitor supplied an email. The final sender, account, and Resend data practices must be reviewed before activation. Provider acceptance is recorded separately from confirmed delivery; delivery-event processing is not implemented in this version.
Security and abuse controls
The server checks request size, field types, required information, origin, submission timing, and duplicate requests. A hidden anti-spam field and rate limits help reduce automated abuse. Security-related request information may be processed to enforce those controls. These measures reduce risk without guaranteeing prevention of every misuse.
The theme and companion plugin do not install marketing analytics or tracking pixels. Native WordPress sign-in uses authentication cookies. The public form uses a short-lived, HttpOnly, same-site security cookie and server-side form token to help prevent forged submissions. A hashed network identifier is used for rate limiting; unnecessary raw addresses are not added to inquiry records. Bluehost and WordPress may process operational server logs; the actual log and backup retention must be confirmed before launch.
Retention, deletion, and backups
Authorized owners can configure inquiry retention, delete records, and export data. The initial setting is 365 days and can be changed from 30 to 3,650 days. An authorized owner must apply the saved retention setting to delete eligible records; this version does not schedule automatic deletion. The period and process must be approved for launch. Deletion from the active database does not automatically remove independent exports or backups; backup retention and restoration procedures must be confirmed separately.
Ask about your information or request a correction or deletion by contacting Marc Masiarczyk at Marc@DetroitCrews.com or 248-500-3763. Identity may need to be verified before a record is disclosed or changed.
External websites and changes
Links to manufacturer resources and other websites take you to services with their own privacy practices. This policy may be revised when the website’s actual data practices change. The approved publication date and any material changes should be recorded with the final policy.