Structural draft · not legal advice

This page lays out the sections a privacy policy like Huzlly's typically needs and what each one is for. It does not contain finished legal language. Every section below has a dashed placeholder block marking exactly where real legal copy needs to go — have that copy reviewed before this page goes live.

1. Overview

A short, plain-language summary of what this policy covers and who it applies to — visitors to huzlly.com, waitlist signups, and closed-beta users of the product.

Your legal language goes here

Scope statement, effective date, and who this policy covers.

2. Information We Collect

What Huzlly collects directly (name and email from the waitlist and signup forms, account details) and what it collects through use of the product (proposal, contract, and payment workflow data; usage and device data).

Your legal language goes here

Itemized list of data categories collected, and whether each is required or optional.

3. How We Use It

The purposes data is used for — running the proposal-to-project flow, communicating about the waitlist and beta, improving the product, and legal or security purposes.

Your legal language goes here

Purpose-by-purpose breakdown, and the legal basis for each if you're addressing GDPR-style requirements.

4. Sharing & Third Parties

Which third parties data passes through to make the flow work — e.g. payment processors, e-signature providers, hosting and infrastructure, email delivery — and the circumstances under which data would ever be shared beyond that.

Your legal language goes here

Name the actual processors once they're locked in, plus your stance on sale of data (typically: none).

5. Data Retention

How long data is kept — while an account is active, after cancellation, and for waitlist entries that never convert to an account.

Your legal language goes here

Concrete retention periods or the criteria used to determine them.

6. Your Rights

What people can ask for — access, correction, deletion, export — and how to submit that request.

Your legal language goes here

Rights language for whichever regions you're targeting (e.g. GDPR, CCPA), and the request process.

7. Cookies & Analytics

Whether the site or product uses cookies or analytics tooling, what for, and how someone can opt out.

Your legal language goes here

List the actual tools in use once decided (or state plainly that none are used yet).

8. Security

A general statement of the safeguards in place around stored data, and an acknowledgment that no system is guaranteed fully secure.

Your legal language goes here

Security measures you're comfortable committing to publicly.

9. Children's Privacy

A statement that Huzlly is not directed at children and is not knowingly used to collect data from them.

Your legal language goes here

Minimum age statement and what happens if you learn a minor signed up.

10. International Users

Where data is processed and stored, and how cross-border transfers are handled for users outside that region.

Your legal language goes here

Your hosting region and transfer mechanism, if relevant to your user base.

11. Changes to This Policy

How updates to this policy will be communicated, and how someone can tell when it was last changed.

Your legal language goes here

Notice method (e.g. email, banner) and where the "last updated" date will live.

12. Contact

How to reach Huzlly with privacy questions or a data request.

contact@huzlly.com