DRAFT POLICY · Replace and review against actual data practices before launch.
Publication draft

Privacy Policy

Do not publish as written. This draft contains placeholders and assumptions. Have qualified counsel review it and update every section to match the real company, website, vendors, product, and data practices.

Effective date: [Month Day, Year]
Business: [Legal business name]
Website: [Live website domain]

Information we collect

Describe the information actually collected through website visits, demo or support requests, account registration, billing, and service use. The current local contact form and support widget do not transmit or store submissions. Remove any information category that the live service does not collect.

How we use information

Describe the actual reasons for using information, such as responding to requests, providing the service, maintaining security, support, billing, and legal obligations. State whether demo request details are used for marketing follow-up.

Business messaging data

Explain what contact details, SMS/MMS content, consent records, and delivery information the service processes; whether the company acts as a service provider for customer data; and how export, deletion, and retention work.

Cookies, analytics, and advertising

List the analytics, conversion tags, advertising pixels, cookies, and consent controls used on the live site. The local preview does not include external analytics or advertising scripts. Update this section before adding them.

Service providers and sharing

Identify actual hosting, form, payment, messaging, support, analytics, and advertising vendors and explain their roles. Describe any other data sharing that applies.

Retention, security, and privacy requests

State the actual retention schedule, safeguards, request process, and any applicable location-specific rights and appeal steps: [Insert verified details].

Text-message consent

Explain how the platform processes opt-in and opt-out records, if applicable. Clarify customer responsibilities and avoid implying that software alone ensures legal compliance.

Contact

[Legal business name]
[Business mailing address]
[Working privacy email]

Before collecting leads: connect a secure form, publish a verified privacy policy, and make sure the form’s consent language matches the actual follow-up process.

← Return to Loopline