Privacy Policy
Updated October 26, 2026Information collected
We collect account name and email, a hashed password, session records, and the contact details, business name, submitted URLs, and messages you provide. With form submissions, we also save the complete submission page URL, its UTM campaign parameters, and any campaign landing page remembered during the same browser-tab session. This helps us understand which pages and campaigns generate inquiries. Form consent is required. Server administrators may also have infrastructure logs. Do not submit identity documents, financial account details, or unnecessary sensitive personal information.
Purpose
We use this information to assess requests, contact you, manage service work, send transactional confirmation and account-access emails, secure accounts, and maintain a history of case activity and understand inquiry sources. Admin notifications include submission attribution. Google Tag Manager is installed; the business manages any tags published through that container separately.
Access
Authorized staff can access CRM records. Signed-in customers can see only requests linked to their account and updates explicitly shared with them. Hosting and other contracted service providers may process information on behalf of the business. Customer ownership is never assigned solely because an email address matches.
Cookies and calls
A necessary session cookie keeps you signed in. Browser session storage remembers the most recent tagged marketing page within the current tab so campaign information can accompany a later form submission. Click-to-call links open your device dialer with the configured business number. The website does not establish whether a call connected, record calls, or automatically synchronize Google Voice calls.
Retention and requests
Records are retained while needed for your service and applicable legal or accounting obligations. Use the contact form to request access, correction, or deletion. Staff must verify your identity before releasing or changing records. Confirmation emails use an email service provider, which receives your email address and the content needed to send the message. Pending customer accounts are activated only after email verification. The business must establish and publish its actual retention schedule and legal entity details before launch.
Security
Passwords are stored as hashes, sessions expire, and access is restricted by role. HTTPS and secure hosting are required in production. No system can guarantee absolute security.