# Privacy Policy for TaskPilot
**Effective Date:** [Effective Date]
**Last Updated:** [Last Updated Date]
---
## 1. Introduction
Welcome to TaskPilot, a cloud-based project management platform ("TaskPilot," the "Service") operated by [Company Legal Name] ("we," "us," or "our"), a company registered in [Jurisdiction] with its principal place of business at [Company Address].
This Privacy Policy explains how we collect, use, disclose, and protect personal information when you access or use TaskPilot, our website at [Website URL], or any related services (collectively, the "Service"). TaskPilot is designed primarily for small marketing agencies and their team members in the United States and the European Union.
By creating an account or using TaskPilot, you acknowledge that you have read and understood this Privacy Policy. If you do not agree with its terms, please do not use the Service.
---
## 2. Information We Collect
We collect the following categories of personal information:
**2.1 Account Information.** When you or your organization registers for TaskPilot, we collect your full name, email address, company or agency name, job title (if provided), password (stored in hashed form), and account preferences.
**2.2 Billing Information.** Payments are processed by our third-party payment processor, Stripe, Inc. ("Stripe"). We do not store full payment card numbers on our servers. We receive limited billing details from Stripe such as your billing name, billing address, last four digits of your payment card, card brand, expiration date, subscription plan, and transaction history.
**2.3 Content You Submit.** We collect the projects, tasks, comments, files, and other content you upload or create within TaskPilot ("Customer Content").
**2.4 Usage and Analytics Data.** We use Mixpanel to collect information about how you interact with the Service, including pages viewed, features used, clicks, session duration, referring URLs, device type, browser type, operating system, and approximate geographic location derived from IP address.
**2.5 Log and Technical Data.** Our servers automatically record information such as IP address, access times, error logs, and API request metadata for security and diagnostic purposes.
**2.6 Communications.** If you contact our support team or respond to surveys, we collect the content of those communications and any information you voluntarily provide.
**2.7 Cookies and Similar Technologies.** See Section 10 below.
---
## 3. How We Use Information
We use personal information for the following purposes:
- To create and administer your user account;
- To provide, maintain, and improve TaskPilot features and functionality;
- To process subscriptions, invoicing, and payments through Stripe;
- To analyze usage patterns and product performance via Mixpanel;
- To communicate service announcements, security alerts, and administrative messages;
- To send marketing communications (where permitted by law and subject to your ability to opt out);
- To provide customer support and respond to requests;
- To detect, investigate, and prevent fraud, abuse, and security incidents;
- To comply with legal obligations and enforce our Terms of Service.
---
## 4. Legal Bases for Processing (EEA/UK Users)
If you are located in the European Economic Area ("EEA") or the United Kingdom, we rely on the following legal bases under the General Data Protection Regulation ("GDPR") and UK GDPR:
**4.1 Contract.** Processing is necessary to perform the contract under which we provide the Service to you or your employer (Article 6(1)(b)).
**4.2 Legitimate Interests.** Processing is necessary for our legitimate interests, such as improving the Service, securing our systems, and preventing fraud, provided those interests are not overridden by your rights (Article 6(1)(f)).
**4.3 Legal Obligation.** Processing is necessary to comply with applicable law (Article 6(1)(c)).
**4.4 Consent.** Where required, we rely on your consent (for example, for non-essential cookies or marketing emails) (Article 6(1)(a)). You may withdraw consent at any time.
For customers who use TaskPilot as their team's workspace, we generally act as a **data processor** for Customer Content on behalf of the customer (the "controller"). For account and billing data, we act as a **data controller**.
---
## 5. How We Share Information
We do not sell personal information. We share personal information only as follows:
**5.1 Service Providers (Subprocessors).** We share information with trusted vendors who perform services on our behalf, including:
- **Amazon Web Services ("AWS")** – cloud hosting (US and Frankfurt, Germany regions);
- **Stripe** – payment processing;
- **Mixpanel** – product analytics;
- [Other subprocessors, e.g., email delivery, customer support tools].
**5.2 Within Your Organization.** Administrators of your agency's TaskPilot workspace may access account information and Customer Content associated with the workspace.
**5.3 Legal Compliance.** We may disclose information to comply with a subpoena, court order, or other valid legal process, or to protect the rights, property, or safety of [Company Legal Name], our users, or others.
**5.4 Business Transfers.** In connection with a merger, acquisition, reorganization, or sale of assets, personal information may be transferred as part of the transaction, subject to standard confidentiality protections.
**5.5 With Your Consent.** We share information with other parties when you direct us to do so.
---
## 6. Data Retention
We retain personal information for as long as necessary to provide the Service and fulfill the purposes described in this Policy.
- **Account data:** retained while your account is active and for up to [e.g., 90 days] after account closure.
- **Customer Content:** retained according to the retention settings you configure or the terms of your subscription agreement.
- **Billing records:** retained for [e.g., 7 years] to comply with tax and accounting laws.
- **Analytics data:** retained in aggregated or pseudonymized form for up to [e.g., 24 months].
- **Backups:** may persist for up to [e.g., 30 days] after deletion from primary systems.
We may retain information longer when required by law or to resolve disputes.
Generate a Privacy Policy for Your SaaS Product
Tested prompts for saas privacy policy template compared across 5 leading AI models.
You need a privacy policy for your SaaS product, and you need it to actually cover the right things: what data you collect, how you use it, who you share it with, and what rights your users have. A generic template pulled from a random website often misses SaaS-specific clauses like third-party integrations, subscription billing data, or multi-tenant data isolation. That gap can expose you to GDPR fines, App Store rejections, or enterprise customers walking away during security reviews.
The fastest path to a solid first draft is an AI-generated privacy policy built from a prompt that includes your specific product details: what data you collect, which countries your users are in, what third-party services you use, and whether you handle anything sensitive like health or financial data. This page shows you exactly how to do that.
What you get here is a working prompt, four model outputs you can compare side by side, and editorial guidance on what to check before you publish. This is not a substitute for a lawyer reviewing your final document, but it gets you 80% of the way there in under ten minutes instead of starting from a blank page.
When to use this
This approach works best when you are launching or updating a SaaS product and need a structured, customizable starting point for your privacy policy. It is the right tool when your legal budget is limited, when you need a draft fast for an App Store submission or investor due diligence, or when you want something more tailored than a generic boilerplate template.
- Early-stage SaaS founders preparing for a public launch who need a policy before going live
- Developers submitting to the Google Play Store or Apple App Store, which require a linked privacy policy
- Startups entering enterprise sales cycles where prospects request a privacy policy in their security questionnaire
- Existing SaaS products adding a new feature that collects new data types, requiring a policy update
- Non-US founders building for US or EU users who need GDPR and CCPA clauses included
When this format breaks down
- Your product handles health data subject to HIPAA: AI-generated drafts routinely miss HIPAA-specific requirements like Business Associate Agreement language, and an error here carries federal penalties.
- You are already in litigation or have received a regulatory inquiry: do not use an AI draft as a response document in any legal proceeding.
- Your SaaS serves children under 13 in the US or under 16 in the EU: COPPA and GDPR-K requirements are nuanced enough that a template approach is high-risk without direct legal review.
- Your enterprise contracts already contain negotiated data processing addenda: the AI output will not reflect those custom terms and could create contradictions.
The prompt we tested
You are a legal writing assistant specializing in SaaS privacy policies. Generate a comprehensive, ready-to-use privacy policy template for the SaaS product described below. Instructions: Write in clear, professional legal English at a plain-language reading level, using numbered sections and short paragraphs. Tailor the clauses to the specific SaaS product, data types, and jurisdictions provided, and include GDPR and CCPA compliance language by default. Use bracketed placeholders for any company-specific details and end with a disclaimer that the template should be reviewed by qualified legal counsel before use. SaaS Product Details: Our SaaS product is called TaskPilot, a cloud-based project management tool for small marketing agencies based in the US and EU. We collect user account data (name, email, company), usage analytics via Mixpanel, and billing info via Stripe. We use AWS (US and Frankfurt) for hosting and need the policy to cover GDPR and CCPA. Produce the full privacy policy template now, using clear section headings and bracketed placeholders (e.g., [Company Name], [Effective Date], [Contact Email]) wherever company-specific information must be filled in. Include all standard sections: Introduction, Information We Collect, How We Use Information, Legal Bases for Processing, How We Share Information, Data Retention, Data Security, International Data Transfers, Your Rights (including GDPR and CCPA rights), Cookies and Tracking Technologies, Children's Privacy, Third-Party Services and Subprocessors, Changes to This Policy, and Contact Us.
Model comparison
| Model | Quality | Cost | Latency | Tokens |
|---|---|---|---|---|
| Claude Opus 4.7 | 7 | $0.1616 | 27.4s | 535 / 2048 |
| Claude Haiku 4.5 | 7 | $0.0106 | 19.5s | 355 / 2048 |
| GPT-5.4 | 7 | $0.0315 | 38.8s | 306 / 2048 |
| Gemini 2.5 Pro | 1 | $0.0008 | 19.5s | 307 / 85 |
| Grok 4.1 Fast Reasoning | 7 | $0.0007 | 16.0s | 454 / 1303 |
Outputs
# PRIVACY POLICY
**TaskPilot**
**Effective Date: [DATE]**
---
## 1. INTRODUCTION
[Company Name] ("we," "us," "our," or "Company") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and otherwise process personal information in connection with TaskPilot, our cloud-based project management platform (the "Service"), and the choices you have regarding your information.
This Privacy Policy applies to all users of the Service, including those in the United States and European Union. We comply with applicable privacy laws, including the General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA), and other relevant regulations.
If you do not agree with our privacy practices, please do not use the Service.
---
## 2. INFORMATION WE COLLECT
### 2.1 Information You Provide Directly
**Account Registration Information:** When you create a TaskPilot account, we collect your name, email address, company name, job title, phone number (optional), and password.
**Billing Information:** When you subscribe to a paid plan, we collect billing name, address, and payment information. Payment processing is handled by our third-party payment processor, Stripe, and we do not directly store full credit card numbers.
**Profile Information:** You may optionally provide additional profile details, such as a profile picture, bio, or team information.
**Communications:** When you contact us via email, chat, or contact forms, we collect the content of your messages, your email address, and any attachments.
**Support Requests:** If you submit support tickets or participate in customer support communications, we collect the information you provide in those requests.
### 2.2 Information Collected Automatically
**Usage Analytics:** We use Mixpanel to collect analytics data about how you interact with the Service, including:
- Features you access and how frequently
- Project and task creation data (non-content)
- Session duration and frequency
- Device and browser information
- IP address and approximate geolocation
**Server Logs:** Our web servers (hosted on AWS) automatically log:
- IP address
- Browser type and version
- Pages accessed and referral sources
- Date and time of access
- Device identifiers
**Cookies and Tracking Technologies:** We use cookies and similar technologies to recognize you, remember preferences, and understand how you use the Service. See Section 10 for details.
### 2.3 Information from Third Parties
**Stripe:** Payment information is processed by Stripe and shared with us as necessary to fulfill your subscription.
**AWS Infrastructure:** We may receive log data and system information from AWS related to your use of the Service.
**Third-Party Integrations:** If you connect third-party applications or services to TaskPilot (e.g., calendar apps, communication tools), we may receive limited information necessary to facilitate the integration.
---
## 3. HOW WE USE INFORMATION
We use the information we collect for the following purposes:
### 3.1 Service Delivery and Improvement
- Providing, maintaining, and improving the Service
- Creating and managing your account
- Delivering customer support and responding to inquiries
- Sending service-related announcements and updates
- Troubleshooting and debugging technical issues
- Analyzing usage patterns to enhance features and user experience
### 3.2 Billing and Payments
- Processing subscription payments
- Generating invoices
- Managing billing disputes
- Communicating about billing matters
### 3.3 Marketing and Communications
- Sending promotional emails about new features, special offers, or events (with your consent or as permitted by law)
- Conducting surveys or requesting feedback
- Personalizing your experience based on preferences
### 3.4 Legal and Compliance
- Complying with legal obligations and law enforcement requests
- Enforcing our Terms of Service and other agreements
- Protecting against fraud, abuse, and security threats
- Establishing, exercising, or defending legal claims
### 3.5 Analytics and Research
- Conducting statistical analysis and research
- Creating aggregated, de-identified reports about Service usage
- Improving marketing effectiveness
---
## 4. LEGAL BASIS FOR PROCESSING (GDPR COMPLIANCE)
Under the GDPR, we process personal information on the following legal bases:
### 4.1 Contractual Necessity
We process your account information and billing data because it is necessary to provide the Service and fulfill the contract with you.
### 4.2 Legitimate Interests
We process usage analytics and system logs based on our legitimate interest in:
- Improving and optimizing the Service
- Preventing fraud and abuse
- Understanding user behavior
- Maintaining network security
You have the right to object to processing based on legitimate interests (see Section 8).
### 4.3 Consent
Where required by law, we obtain your explicit consent before processing certain information, such as:
- Marketing communications
- Optional cookies beyond those necessary for the Service
- Non-essential analytics
### 4.4 Legal Obligations
We process information when required by applicable laws, regulations, or legal proceedings.
---
## 5. HOW WE SHARE INFORMATION
### 5.1 Service Providers and Subprocessors
We share information with the following third parties who act as data processors or service providers:
**Mixpanel:** Analytics and user behavior tracking. Mixpanel is certified under the EU-U.S. Data Privacy Framework and processes data under data processing agreements.
**Stripe:** Payment processing and billing. Stripe is certified under the EU-U.S. Data Privacy Framework and processes payment information according to its own privacy policies and PCI compliance standards.
**Amazon Web Services (AWS):** Cloud hosting and infrastructure. AWS processes data in the United States (Virginia) and European Union (Frankfurt) regions and is certified under the EU-U.S. Data Privacy Framework.
**[Additional Subprocessors]:** [List any other subprocessors, such as email service providers, customer support platforms, etc.]
All subprocessors are subject to written data processing agreements ensuring compliance with GDPR, CCPA, and other applicable privacy laws.
### 5.2 No Sale of Personal Information
**We do not sell, and have not sold in the past 12 months, personal information of California residents or other users to third parties for monetary or other valuable consideration.** However, we may share information with service providers who assist in delivering the Service; this may constitute a "sale" under the CCPA. California residents have the right to opt out (see Section 8.3).
### 5.3 Business Transfers
If we are involved in a merger, acquisition, bankruptcy, dissolution, reorganization, or similar transaction or proceeding, your information may be shared as part of that transaction. We will provide notice before your information becomes subject to a different privacy policy.
### 5.4 Legal Requirements and Protection
We may disclose information if required by law, or if we believe in good faith that disclosure is necessary to:
- Comply with legal obligations, court orders, or government requests
- Enforce our Terms of Service and other agreements
- Protect the safety, rights, and property of [Company Name], our users, and the public
- Prevent or detect fraud or security threats
### 5.5 Aggregate and De-Identified Information
We may share aggregated or de-identified information that cannot reasonably be used to identify you with third parties for research, marketing, analytics, and other purposes without restriction.
---
## 6. DATA RETENTION
We retain personal information for as long as necessary to fulfill the purposes outlined in this Policy, unless a longer retention period is required or permitted by law.
### 6.1 Specific Retention Periods
**Account Information:** We retain your account information for as long as your account is active. After account deletion, we retain data for [90 days] to assist with account recovery and to comply with legal obligations.
**Billing Information:** We retain billing and payment information for [7 years] as required by tax and accounting regulations.
**Analytics Data:** Usage analytics via Mixpanel are retained for [12 months] unless you request deletion earlier.
**Cookies:** Most cookies expire within [12 months]. See Section 10 for details.
**Support Communications:** We retain support tickets and communications for [2 years] to assist with future support and to maintain service records.
**Server Logs:** AWS server logs are retained for [90 days] for security and troubleshooting purposes.
### 6.2 Deletion Requests
You may request deletion of your personal information at any time by contacting [Privacy Contact Email]. We will comply with deletion requests as required by law, except where retention is necessary for legal, regulatory, or legitimate business purposes.
---
## 7. DATA SECURITY
### 7.1 Security Measures
We implement technical, organizational, and administrative measures designed to protect personal information against unauthorized access, alteration, disclosure, and destruction. These measures include:
- **Encryption:** Data in transit is encrypted using SSL/TLS protocols. Data at rest is encrypted using industry-standard encryption methods.
# Privacy Policy for TaskPilot **Effective Date:** [Effective Date] **Last Updated:** [Last Updated] This Privacy Policy explains how **[Company Name]** (“**Company**,” “**we**,” “**us**,” or “**our**”) collects, uses, discloses, and protects personal information in connection with **TaskPilot**, our cloud-based project management software-as-a-service platform designed for small marketing agencies in the United States and European Union (the “**Services**”). This Privacy Policy applies to personal information we collect through TaskPilot, our website, related communications, customer support interactions, and any other services that link to this Privacy Policy. By using the Services, you acknowledge that you have read and understood this Privacy Policy. ## 1. Introduction 1.1. We are committed to protecting your privacy and handling your personal information in a transparent and lawful manner. 1.2. This Privacy Policy describes: - what information we collect; - how we use that information; - the legal bases we rely on where required by law; - how we share information with third parties; - how long we retain information; - the rights available to individuals under applicable privacy laws, including the **EU General Data Protection Regulation (“GDPR”)** and the **California Consumer Privacy Act, as amended by the California Privacy Rights Act (“CCPA”)**. 1.3. If you are using TaskPilot on behalf of an organization, such as your employer or agency, that organization may act as the controller of certain data you submit to the Services, and we may act as a processor or service provider on its behalf. In such cases, your organization’s privacy practices may also apply. ## 2. Information We Collect We collect personal information directly from you, automatically when you use the Services, and from third-party service providers. ### 2.1. Information You Provide Directly We may collect the following account and business contact information: - full name; - email address; - company name; - account login credentials or authentication-related information; - communications you send to us, including support requests, feedback, and inquiries; - any other information you choose to provide through the Services. ### 2.2. Billing and Payment Information If you purchase a paid subscription, payment processing is handled by **Stripe**. We may collect or receive billing-related information such as: - billing contact name; - billing email address; - billing address; - subscription plan details; - invoice and transaction metadata; - payment status; - limited payment method details provided by Stripe, such as card type, last four digits, expiration date, or payment token information, where applicable. We do **not** typically store full payment card numbers on our own systems unless expressly stated otherwise. ### 2.3. Usage Data and Analytics When you use TaskPilot, we may automatically collect information about how the Services are accessed and used. This may include: - IP address; - device type; - browser type; - operating system; - referring URLs; - pages or screens viewed; - clickstream data; - session duration; - feature usage; - date and time of access; - user identifiers; - approximate location derived from IP address. We use **Mixpanel** to help us understand product usage, improve functionality, and analyze user behavior. ### 2.4. Information Stored in TaskPilot by Customers In the course of providing the Services, users may upload, submit, store, or otherwise make available information and content within TaskPilot, such as: - project information; - task details; - comments; - attachments; - team collaboration data; - client or campaign-related information entered by users. The nature of this information depends on how customers use TaskPilot. To the extent this information contains personal data, we process it on behalf of the relevant customer, subject to applicable agreements. ### 2.5. Cookies and Similar Technologies We use cookies and similar technologies to operate the Services, maintain sessions, remember preferences, improve performance, and collect analytics data. More details are provided in Section 12. ## 3. How We Use Information We use personal information for the following purposes: 3.1. **To provide and operate the Services**, including account creation, authentication, project management functionality, and customer administration. 3.2. **To process subscriptions and billing**, including payments, renewals, invoicing, fraud prevention, and account management. 3.3. **To communicate with you**, including sending service-related notices, administrative updates, security alerts, billing communications, and support responses. 3.4. **To provide customer support**, troubleshoot issues, diagnose technical problems, and respond to requests and feedback. 3.5. **To improve and develop the Services**, including analyzing how TaskPilot is used, enhancing performance, developing new features, and understanding user needs. 3.6. **To monitor security and prevent misuse**, including detecting unauthorized access, abuse, fraud, spam, and other harmful or unlawful activities. 3.7. **To comply with legal obligations**, including accounting, tax, recordkeeping, compliance, and lawful requests from regulators, courts, or law enforcement. 3.8. **To enforce our legal rights**, including our Terms of Service, contractual rights, and dispute resolution processes. 3.9. **To send marketing communications**, where permitted by applicable law. You may opt out of non-essential marketing communications at any time. ## 4. Legal Bases for Processing (GDPR) If the GDPR or similar laws apply to our processing of your personal data, we rely on one or more of the following legal bases: 4.1. **Performance of a contract.** We process personal data as necessary to provide the Services, manage accounts, process payments, and fulfill our contractual obligations. 4.2. **Legitimate interests.** We process personal data for our legitimate interests where those interests are not overridden by your data protection rights. These interests may include: - operating and improving TaskPilot; - securing our systems and Services; - analyzing usage trends; - providing support; - preventing fraud and abuse; - managing business operations. 4.3. **Compliance with legal obligations.** We process personal data where necessary to comply with applicable laws, regulations, legal processes, or lawful government requests. 4.4. **Consent.** We rely on consent where required by law, such as for certain cookies or marketing communications. Where processing is based on consent, you may withdraw consent at any time, although withdrawal will not affect prior lawful processing. ## 5. How We Share Information We do not sell personal information in the traditional sense. We may share personal information in the following circumstances: ### 5.1. Service Providers and Subprocessors We share information with trusted third-party vendors that help us operate TaskPilot and our business, such as: - **Amazon Web Services (AWS)** for cloud hosting and infrastructure, including hosting in the United States and Frankfurt, Germany; - **Stripe** for payment processing and billing support; - **Mixpanel** for product analytics and usage insights; - [Other Subprocessors]. These providers process personal information on our behalf under contractual terms designed to protect it. ### 5.2. Within Our Corporate Group We may share information with our affiliates, subsidiaries, or parent company, if any, for internal administrative, operational, legal, or support purposes, subject to this Privacy Policy. ### 5.3. Business Transfers We may disclose or transfer personal information as part of a merger, acquisition, financing, reorganization, sale of assets, bankruptcy, or similar corporate transaction. If this occurs, we will take reasonable steps to ensure your information remains protected. ### 5.4. Legal Compliance and Protection We may disclose personal information where necessary to: - comply with applicable law, regulation, legal process, or court order; - respond to lawful requests from public authorities; - protect our rights, privacy, safety, property, or those of our users or others; - investigate, prevent, or address suspected fraud, security issues, or illegal activity; - enforce our agreements and policies. ### 5.5. With Your Direction or Consent We may share information with third parties when you request, direct, or consent to the disclosure. ## 6. Data Retention 6.1. We retain personal information for as long as necessary to fulfill the purposes described in this Privacy Policy, including to provide the Services, comply with legal obligations, resolve disputes, and enforce our agreements. 6.2. Account information is generally retained for the duration of the account relationship and for a reasonable period afterward for backup, audit, legal, tax, fraud prevention, and compliance purposes. 6.3. Billing and transaction records may be retained for longer periods as required by tax, accounting, and financial reporting laws. 6.4. Usage analytics data may be retained for as long as reasonably necessary for analytics, product improvement, and security purposes, subject to applicable legal requirements and our internal retention schedules. 6.5. Customer-submitted content stored in TaskPilot will generally be retained according to the customer’s subscription settings, instructions, contractual terms, and applicable law. Upon valid request and subject to legal obligations, we will delete or return such data in accordance with our agreements. 6.6. We may retain de-identified or aggregated information for longer periods or indefinitely where permitted by law. ## 7. Data Security 7.1. We implement reasonable and appropriate technical, administrative, and organizational measures designed to protect personal information against unauthorized access, disclosure, alteration, and destruction. 7.2. These measures may include, as appropriate: - access controls and authentication measures; - encryption in transit and, where appropriate, at rest; - secure cloud infrastructure; - monitoring and logging; - vendor due diligence; - employee confidentiality obligations. 7.3. Despite our efforts, no method of transmission over the internet or method of electronic storage is completely secure. We therefore cannot guarantee absolute security. 7.4. You are responsible for maintaining the confidentiality
Of course. Here is a comprehensive, ready-to-use privacy policy template for TaskPilot, tailored to your specifications.
***
### **Privacy Policy for TaskPilot**
**Effective Date:** [Effective Date]
**Last Updated:** [Date of Last Update]
### **1. Introduction**
Welcome to TaskPilot. This Privacy Policy explains how [Company Name] ("we," "us," or
# Privacy Policy for TaskPilot
**Effective Date: [Effective Date, e.g., January 1, 2024]**
## 1. Introduction
[Company Name] ("we," "us," or "our") operates TaskPilot, a cloud-based project management tool designed for small marketing agencies. We are committed to protecting your privacy. This Privacy Policy explains how we collect, use, share, and protect your personal information when you use our service.
This policy applies to users in the United States (including California under the California Consumer Privacy Act, or "CCPA") and the European Union (under the General Data Protection Regulation, or "GDPR"). By using TaskPilot, you agree to the practices described here.
For questions, contact us at [Contact Email].
## 2. Information We Collect
We collect the following types of information:
- **Account Data**: When you create an account or subscribe, we collect your name, email address, company name, and payment details (processed via Stripe).
- **Usage Data**: As you use TaskPilot, we collect data on your interactions, such as project creation, task assignments, and feature usage. This helps us improve the service.
- **Analytics Data**: We use Mixpanel to gather anonymized usage analytics, like page views and session duration.
- **Billing Data**: Subscription and payment information, handled securely by Stripe.
- **Device and Log Data**: IP address, browser type, device information, and access times.
We do not collect sensitive personal data, such as health or financial account details beyond billing.
## 3. How We Use Information
We use your information to:
- Provide and maintain TaskPilot services, including project management features.
- Process payments and manage subscriptions via Stripe.
- Analyze usage to improve our product (e.g., via Mixpanel).
- Communicate with you about your account, updates, or support.
- Comply with legal obligations and prevent fraud.
- Send marketing emails (with opt-out option).
Under CCPA, we do not "sell" personal information as defined by the law.
## 4. Legal Bases for Processing (GDPR)
For EU users, we process personal data based on:
- **Contract**: To deliver TaskPilot services.
- **Consent**: For marketing emails or cookies (you can withdraw consent anytime).
- **Legitimate Interests**: For analytics, security, and service improvements, balanced against your rights.
- **Legal Obligation**: For billing and compliance.
## 5. How We Share Information
We share information only as needed:
- **Service Providers**: Mixpanel (analytics), Stripe (billing), and AWS (hosting in US and EU regions).
- **Business Transfers**: In a merger or sale of assets.
- **Legal Requirements**: If required by law, subpoena, or government request.
- **With Consent**: For any other sharing.
We do not sell your data to third parties.
## 6. Data Retention
We keep your data only as long as needed:
- Account data: While your account is active, plus 1 year after deletion for backups.
- Billing data: 7 years for tax purposes.
- Analytics data: 12-14 months via Mixpanel.
You can request deletion at any time (see Section 9).
## 7. Data Security
We use reasonable security measures:
- Encryption for data in transit (TLS) and at rest (AWS).
- Access controls, regular audits, and employee training.
- Incident response plan for breaches (we'll notify you if required by law).
No system is fully secure; we cannot guarantee absolute protection.
## 8. International Data Transfers
TaskPilot hosts data on AWS servers in the US and Frankfurt, Germany (EU).
- EU data may transfer to the US under Standard Contractual Clauses (SCCs) with AWS and other providers.
- US data stays in compliant regions or transfers with safeguards.
For GDPR, we ensure adequacy or equivalent protections for transfers.
## 9. Your Rights
You have rights regarding your data. To exercise them, contact [Contact Email]. We'll respond within 45 days (extendable if needed).
**GDPR Rights (EU Users)**:
- Access, correct, or delete your data.
- Restrict or object to processing.
- Data portability.
- Withdraw consent.
**CCPA Rights (California Residents)**:
- Right to know categories of data collected, sources, purposes, and sharing (last 12 months).
- Right to delete data.
- Right to opt-out of "sales" (we do not sell data; no opt-out needed).
- Non-discrimination for exercising rights.
Verify identity before fulfilling requests. Agents can submit with authorization.
## 10. Cookies and Tracking Technologies
TaskPilot uses cookies and similar tools for functionality, analytics (Mixpanel), and preferences.
- Essential cookies: Required for service.
- Analytics cookies: Opt-out via browser settings or Mixpanel tools.
Manage cookies in your browser. Our Cookie Policy [link if available] has details.
## 11. Children's Privacy
TaskPilot is not for children under 16 (or 13 in the US). We do not knowingly collect children's data. Parents can contact us to remove data.
## 12. Third-Party Services and Subprocessors
We use trusted partners:
| Service | Purpose | Location | Privacy Policy |
|---------|---------|----------|---------------|
| AWS | Hosting | US/EU | [aws.amazon.com/privacy] |
| Stripe | Billing | US/EU | [stripe.com/privacy] |
| Mixpanel | Analytics | US | [mixpanel.com/legal/privacy-policy] |
Full list available on request. Subprocessors are GDPR-compliant with SCCs.
## 13. Changes to This Policy
We may update this policy. Changes post on our site and email subscribers. Continued use after changes means acceptance.
## 14. Contact Us
Questions? Email [Contact Email] or write to:
[Company Name]
[Company Address]
[Company Phone]
**EU Representative**: [EU Representative Name and Contact, if applicable].
**DPO**: [Data Protection Officer Contact, if applicable].
---
**Disclaimer**: This is a template privacy policy for TaskPilot. It is provided for informational purposes only and does not constitute legal advice. [Company Name] must have this reviewed and customized by qualified legal counsel before use to ensure compliance with applicable laws. Laws change, and specifics vary by jurisdiction.
What makes these work
-
01List your actual third-party services
The most common reason a generated privacy policy is too generic is that the prompt just says 'we use analytics tools' instead of naming Mixpanel, Segment, Intercom, or whatever you actually use. Each vendor has its own data practices that users are legally entitled to know about. Name them in your prompt and the output will include the right disclosures.
-
02Specify your user geography upfront
GDPR, CCPA, PIPEDA, and Australia's Privacy Act each require different clauses. If you put 'users in the US and EU' in the prompt, the model will include both GDPR lawful bases and a CCPA section. If you leave geography vague, you will get a watered-down policy that may not satisfy either regulation.
-
03Define the data controller vs. processor relationship
B2B SaaS products almost always act as a data processor for their customers' end-user data. If you do not clarify this in your prompt, the output will default to treating you as the controller, which produces the wrong legal framing. Tell the AI explicitly whether you are a processor, controller, or both, and for which data categories.
-
04Ask for a version with placeholders marked
Request that the AI flag every section requiring customization with brackets like [COMPANY NAME] or [DATA RETENTION PERIOD]. This turns the output into a true working template rather than a document that looks finished but contains wrong specifics you will miss on a quick read.
More example scenarios
Write a privacy policy for a B2B SaaS project management tool called TaskFlow. We collect names, work email addresses, IP addresses, and project data uploaded by users. We use Stripe for billing, Mixpanel for analytics, and AWS for hosting. Users are in the US and EU. We do not sell data. Include GDPR and CCPA sections.
A policy covering: identity and contact data collection, usage data via Mixpanel, payment data handled by Stripe as a processor, AWS data residency options, lawful bases for processing under GDPR, a CCPA 'Do Not Sell' disclosure, data retention periods, user rights requests process, and contact details for a data controller. Approximately 800-1200 words.
Generate a privacy policy for a SaaS tool called Lettercraft that lets creators build and send email newsletters. We collect subscriber email addresses on behalf of our customers, track email opens and clicks, and use SendGrid for delivery. Customers are global. We need to address the data processor vs. data controller distinction.
A policy that distinguishes Lettercraft as a data processor for subscriber data and a data controller for customer account data. Covers tracking pixel use, third-party sharing with SendGrid, opt-out rights for end subscribers, and a pointer to the customer's own privacy policy for their subscribers. Includes GDPR Article 28 processor obligations summary.
Write a privacy policy for HireAI, a SaaS tool that uses AI to screen job applicants. We process resumes, which may contain age, address, and education history. Employers are our customers; applicants are data subjects. We operate in the UK and EU. We use automated decision-making in shortlisting.
A policy including a section on automated decision-making and profiling under GDPR Article 22, applicant rights to human review, special category data handling, lawful basis as legitimate interest or contractual necessity, data retention limits for rejected candidates, and a UK ICO registration reference placeholder. Flags that employers must provide applicants a separate fair processing notice.
Create a privacy policy for CodeSnap, a freemium SaaS that lets developers save and share code snippets. Users sign in via GitHub OAuth. We collect GitHub username, email, and public profile data. We show Google Ads to free users. We are US-only and do not target EU residents.
A policy covering OAuth data collected from GitHub, advertising data shared with Google Ads including cookie identifiers, opt-out options via NAI and DAA, no-sale disclosure under CCPA for California residents, free vs. paid account data differences, and snippet visibility settings explaining public versus private data exposure.
Write a privacy policy for WealthDesk, a SaaS CRM for independent financial advisors. We store client financial data entered by advisors, including portfolio values and social security numbers. We are subject to SEC and FINRA regulations. Data is stored on Azure in the US.
A policy noting collection of non-public personal financial information, Gramm-Leach-Bliley Act compliance obligations, SSN encryption and access controls, Azure US data residency, data sharing limits with third parties, customer rights to access and correct records, a breach notification commitment, and a disclaimer that advisors using the platform are responsible for their own client disclosures under applicable securities law.
Common mistakes to avoid
-
Using the output without customizing retention periods
AI models default to vague phrases like 'as long as necessary.' GDPR requires you to specify actual retention periods by data category. Before publishing, replace every vague retention reference with a real number based on your product's logic and any applicable legal minimums or maximums.
-
Forgetting to update after adding new integrations
You generate a policy at launch, then six months later you add Intercom, a payment processor change, or a new analytics tool. Your policy still lists the old stack. This creates a direct legal exposure because your stated disclosures no longer match your actual data flows. Treat the privacy policy as a living document and regenerate or update it when your tech stack changes.
-
Publishing a policy that contradicts your Terms of Service
The privacy policy and Terms of Service reference each other, and inconsistencies between them create exploitable ambiguity. For example, if your ToS says you can share data with partners but your privacy policy says you never share data, you have a conflict. Review both documents together before publishing.
-
Skipping the lawyer review before enterprise sales
Enterprise procurement teams and their legal departments will read your privacy policy carefully. A document with obvious AI boilerplate, missing DPA provisions, or incorrect lawful basis claims will fail security review and stall deals. At minimum, have a lawyer do a one-hour review before you enter any enterprise pipeline.
-
Not hosting it at a stable, linkable URL
Google Play, the App Store, and most enterprise security questionnaires require a direct link to your privacy policy. If it lives at a dynamic URL, behind a login, or on a page that changes URLs when you update your site, you will fail submission checks. Host it at something permanent like yourapp.com/privacy and keep that URL stable.
Related queries
Frequently asked questions
Is an AI-generated privacy policy legally binding?
A privacy policy is legally binding based on its content and your users' acceptance, not how it was drafted. An AI-generated policy that accurately describes your data practices and is properly presented to users carries the same weight as one written by a lawyer. The risk is in accuracy, not authorship. If the policy misrepresents what you actually do, that is the legal problem, regardless of who wrote it.
Do I need a separate privacy policy for GDPR and CCPA?
No. Most SaaS companies publish a single privacy policy with clearly labeled sections for GDPR rights (EU users) and CCPA rights (California residents). This is the standard approach and is accepted by regulators in both jurisdictions. The AI prompt examples on this page use that structure by default.
What is the difference between a privacy policy and a data processing agreement?
A privacy policy is a public-facing document explaining your data practices to users. A data processing agreement (DPA) is a contract between your business and another business that processes personal data on your behalf, required by GDPR Article 28. If your B2B SaaS processes EU personal data, enterprise customers will ask you to sign a DPA in addition to your published privacy policy. An AI-generated privacy policy does not replace a DPA.
How long should a SaaS privacy policy be?
Most well-written SaaS privacy policies run 800 to 2,000 words. Shorter than 800 words and you are likely missing required disclosures. Longer than 2,000 words and users stop reading, which undermines the transparency goal. The right length depends on how many data types you collect, which regulations apply, and how many third-party services you use.
Can I use the same privacy policy for my web app and mobile app?
Usually yes, with one addition: mobile apps often collect device identifiers, push notification tokens, and location data that web apps do not. If your mobile app collects anything the web app does not, add a mobile-specific section to your shared policy rather than maintaining two separate documents. Both the App Store and Google Play accept a single policy URL that covers all your platforms.
How often should I update my SaaS privacy policy?
Update it any time you add a new data category, change a third-party service, enter a new geographic market with different regulations, or change how you use existing data. Most SaaS companies end up updating their policy one to three times per year. When you update it, notify existing users by email if the changes are material, which is required under GDPR and considered best practice everywhere else.