Legal
Privacy policy
Last updated: April 2026 · Placeholder for MVP frontend
Introduction
This policy explains how Elevate Prospect (placeholder entity name) would handle personal and business data when the product is fully deployed. This is not legal advice. Replace every section with counsel-reviewed language before production.
When you use our marketing site or demo dashboard, no backend persistence is assumed in this static build—but your live system should describe actual processing activities accurately.
1. Data we collect
Examples of categories you may need to disclose:
- Account and profile data (name, email, business name, role).
- Communication content (SMS, chat transcripts, templates, logs).
- Technical data (IP address, device type, approximate location from IP, cookies or similar technologies).
- Integration configuration when users connect telephony, AI, or billing providers.
2. How we use data
Typical purposes include providing the service, billing, security and fraud prevention, product improvement, support, and—where allowed—marketing. Each purpose should map to a lawful basis and retention rule in your final policy.
AI features may send prompts to subprocessors; list them clearly and describe opt-outs or controls where required.
3. Legal bases (GDPR-style framing)
Processing may rely on contract performance, legitimate interests (e.g. securing accounts and improving reliability), or consent where required—such as non-essential cookies or certain marketing messages.
4. CASL, TCPA, and similar rules
Commercial electronic messages and telemarketing are heavily regulated. Your live product should document consent, honor STOP and unsubscribe requests promptly, and maintain evidence of consent and message purpose. This demo UI surfaces STOP language as a reminder only.
5. Retention & security
Describe how long messages, logs, backups, and account data are kept; encryption in transit and at rest; access controls; incident response; and subprocessors with links to their policies.
6. Your rights
Depending on jurisdiction, users may have rights to access, correct, delete, export, or restrict processing of their data, and to object to certain processing. Explain how to exercise those rights and expected response times.
7. Contact
privacy@example.com (placeholder)
Data protection officer or EU representative (if applicable)—add when real.