Privacy Policy Generator

Drafts a clear, regulation-aware privacy policy for any website or app from your business details.

// prompt
You are a senior privacy and data-protection counsel who drafts plain-language privacy policies aligned with GDPR, CCPA/CPRA, PIPEDA, and similar regimes. Write a complete, ready-to-customize privacy policy for the business below. ## Business Inputs - **Company / Legal Entity**: {{company_name}} - **Product**: {{website_or_app_name}} ({{business_type}} — e.g. e-commerce, SaaS, mobile app) - **Operating Regions & Audience**: {{operating_regions}} - **Personal Data Collected**: {{types_of_personal_data_collected}} - **Third-Party Services**: {{third_party_services}} (e.g. analytics, payments, hosting, email) - **Privacy Contact**: {{privacy_contact_email}} - **Effective Date**: {{effective_date}} ## How to Draft 1. Infer the lawful bases and user rights that apply to the stated regions; flag any region where extra clauses are needed. 2. Use clear, non-technical language at roughly an 8th-grade reading level; define jargon on first use. 3. Be specific to the inputs — never invent data practices not implied by them. Where a detail is missing, insert a bracketed TODO for the business to confirm. ## Required Sections 1. **Introduction & Scope** — who you are, what this policy covers, effective date. 2. **Information We Collect** — data provided by users, automatically collected data (cookies, IP, usage), and third-party sources. 3. **How We Use Information** — purposes and matching lawful bases. 4. **How We Share Information** — service providers, legal disclosures, business transfers; confirm whether data is sold or shared for ads. 5. **Data Retention & Security** — retention logic and safeguards. 6. **Your Rights** — access, deletion, correction, portability, opt-out, and how to exercise them. 7. **International Transfers**, **Children's Privacy**, **Cookies**, **Policy Updates**, and **Contact**. ## Output Format Deliver the policy as clean Markdown with numbered headings. End with a short, clearly labeled checklist of items the business must verify and a one-line disclaimer that this draft requires review by qualified legal counsel before publication.
Fill in the variables

Example run

Generated by Claude Opus 5.5 with web search on September 23, 2026

Inputs used

Company name
Northbridge Wellness Technologies, Inc.
Website or app name
DailyRhythm
Business type
Mobile app (subscription-based habit-tracking and wellness app)
Operating regions
United States (all states, including California and Colorado), European Union and UK, and Canada; app is available for download worldwide but marketing is focused on North America and Western Europe
Types of personal data collected
Account data (name, email address, password hash, date of birth); profile and health-adjacent data users voluntarily enter (sleep hours, mood logs, weight, fitness goals); device and usage data (device model, OS version, IP address, app open/session events, crash logs); approximate location derived from IP address (city-level, not precise GPS); payment metadata via Stripe (last 4 card digits, billing zip code — full card numbers never touch our servers); customer support messages and email correspondence; cookies and mobile ad identifiers (IDFA/AAID) for limited in-app analytics
Third-party services
Google Analytics for Firebase (app analytics), Stripe (subscription billing and payment processing), Amazon Web Services (cloud hosting, US and EU regions), SendGrid (transactional and marketing emails), OneSignal (push notifications), Sentry (crash and error reporting), Apple App Store and Google Play (in-app purchase billing)
Privacy contact email
privacy@northbridgewellness.com
Effective date
November 1, 2026

Privacy Policy: DailyRhythm

Northbridge Wellness Technologies, Inc. Effective Date: November 1, 2026 Last Updated: [TODO: date of publication]


1. Introduction and Scope

1.1 Who we are

Northbridge Wellness Technologies, Inc. ("Northbridge," "we," "us," or "our") makes DailyRhythm. DailyRhythm is a subscription mobile app that helps you track habits and wellness goals. Our registered address is [TODO: full legal address, including state of incorporation].

For people in the European Union (EU) and the United Kingdom (UK), Northbridge is the controller of your personal data. A controller is the company that decides why and how your information is used.

1.2 What this policy covers

This Privacy Policy explains how we collect, use, share, and protect personal information when you:

  • download, sign up for, or use the DailyRhythm app;
  • buy or manage a subscription;
  • contact our support team or receive emails from us; or
  • visit [TODO: website URL, if any] (together, the "Services").

"Personal information" (also called "personal data") means any information that identifies you or could reasonably be linked to you.

This policy does not cover third-party services that we don't control, such as the Apple App Store or Google Play. Those companies have their own privacy policies.

1.3 DailyRhythm is not a medical service

DailyRhythm is a wellness tool. It is not a medical device, and it does not diagnose or treat any condition. We are not a healthcare provider, so the U.S. health privacy law HIPAA generally does not apply to us. We still treat the wellness information you enter with extra care, as explained below.

1.4 Region-specific information

Most of this policy applies to everyone. Extra rights and details for certain places are in:

  • Section 7.3: EU and UK residents
  • Section 7.4: California residents
  • Section 7.5: Colorado and other U.S. state residents
  • Section 7.6: Canadian residents (including Québec)
  • Section 7.7: Washington and Nevada residents (Consumer Health Data)

2. Quick Summary

Question Short answer
Do you sell my personal information? No.
Do you use my wellness entries (mood, sleep, weight) for ads? No.
Do you share my data for targeted advertising? [TODO: confirm, see Section 5.4. Our intended answer is No.]
Do you collect my precise GPS location? No. We only estimate your city from your IP address.
Do you see my full card number? No. Stripe, Apple, or Google handles it.
Can I delete my data? Yes. In the app or by emailing privacy@northbridgewellness.com.

3. Information We Collect

3.1 Information you give us

Category Examples Required?
Account information Name, email address, password (we store only a "hash," a scrambled version we can't reverse), date of birth Yes, to create an account
Wellness and profile information Sleep hours, mood logs, weight, fitness goals, and other habit entries you choose to record Optional. You choose what to enter
Payment information (if you subscribe through our website or in-app checkout run by Stripe) Last 4 digits of your card, card type, billing ZIP/postal code, subscription status, transaction history Needed to subscribe this way
Support and correspondence Messages you send our support team, emails, and anything you attach Optional
Communication preferences Whether you want marketing emails or push notifications Optional

About wellness information: Mood, sleep, weight, and similar entries can reveal things about your health. Many laws treat this as sensitive or health data, including the EU/UK GDPR, the California Consumer Privacy Act (CCPA), the Colorado Privacy Act, and Washington's My Health My Data Act. We ask for your explicit consent before we collect it (see Section 4.2). Please don't enter information you aren't comfortable storing with us.

3.2 Information collected automatically

When you use the app, we and our service providers automatically collect:

Category Examples
Device information Device model, operating system (OS) version, app version, language setting
Network information IP address (a number that identifies your device's internet connection)
Approximate location City or region, estimated from your IP address. We do not collect precise GPS location.
Usage information When you open the app, session length, features and screens you use, and in-app events (for example, "completed a habit check-in")
Crash and error information Crash logs, error messages, and device state when a crash happens
Identifiers Mobile advertising identifiers (Apple's IDFA or Google's AAID, which are resettable IDs your phone assigns), Firebase app instance IDs, push notification tokens, and cookies or similar technologies (see Section 10)

About ad identifiers: On Apple devices, we can only access your IDFA if you allow it in Apple's App Tracking Transparency prompt. On Android devices, you can reset or delete your AAID in your device settings. We use these identifiers only for limited in-app analytics. [TODO: Confirm whether IDFA/AAID collection is necessary at all. If it's used only for analytics, consider turning it off; see the checklist.]

3.3 Information from third parties

  • Apple App Store and Google Play: If you subscribe through Apple or Google, they process your payment. They send us limited information, such as a transaction ID, subscription status, product purchased, country, and renewal or cancellation events. We do not receive your payment card details or your Apple/Google account password.
  • Stripe: If you pay through Stripe, it gives us payment metadata (last 4 digits, card type, billing ZIP/postal code, payment status). Full card numbers never reach our servers.
  • Service providers: Tools such as Firebase, Sentry, and OneSignal send us reports about app performance and message delivery.

[TODO: Confirm there are no other sources, such as "Sign in with Apple/Google," wearable or Apple Health/Google Health Connect integrations, referral programs, or data purchased from partners. If any exist, add them here.]


4. How We Use Information

4.1 Purposes and legal bases

Some privacy laws, including the GDPR in the EU and UK, require a "legal basis" for each use of personal data. The table below lists our purposes and the legal basis we rely on for each.

Purpose Data used Legal basis (EU/UK)
Create and manage your account, log you in, and keep it secure Account info, device info Contract. Needed to provide the service you asked for
Provide app features, such as storing, showing, and charting your habit and wellness entries and tracking goals Wellness and profile info Explicit consent (GDPR Art. 9(2)(a)), plus Contract
Verify your age and eligibility Date of birth Legal obligation and Legitimate interests (keeping our Services appropriate for users' ages)
Process subscriptions, including billing, renewals, refunds, and receipts Payment metadata, account info, app store transaction data Contract; Legal obligation (tax and accounting records)
Send service messages, such as receipts, password resets, security alerts, and policy changes Email, account info Contract; Legitimate interests
Send push notifications, such as habit reminders Push token, preferences Consent (given through your device's permission prompt)
Send marketing emails about features, offers, and tips Email, name, preferences Consent in the EU, UK, and Canada. Legitimate interests where the law allows, with an opt-out in every email
Answer support requests Support messages, account info Contract; Legitimate interests
Analyze and improve the app, including which features people use and how to make it better Usage info, device info, identifiers, approximate location Consent where required for non-essential tracking (for example, EU/UK device access rules); otherwise Legitimate interests in improving our product
Fix bugs and crashes Crash logs, device info Legitimate interests in keeping the app working
Prevent fraud and abuse and protect security IP address, device info, account info Legitimate interests; Legal obligation
Follow the law and enforce our terms, including responding to lawful requests and defending legal claims Any relevant data Legal obligation; Legitimate interests
Business transfers (see Section 5.3) Any relevant data Legitimate interests

"Legitimate interests" means we have a real business reason to use your data, and that reason is not outweighed by your privacy rights. You can object to uses based on legitimate interests (see Section 7).

4.2 Extra protections for wellness information

  • Consent first. Before you enter wellness information for the first time, we ask for your explicit, separate consent. [TODO: Build a dedicated in-app consent screen for this. It should not be bundled with acceptance of the Terms.]
  • Limited use. We use wellness information only to provide DailyRhythm's features to you, and to keep it secure.
  • No ads, no sale. We do not sell wellness information. We don't use it for advertising or share it with advertisers, and we don't use it to draw conclusions about you for marketing.
  • Kept out of analytics. [TODO: Confirm engineering practice. Recommended: wellness entry values (such as actual weights or mood scores) are never sent to Firebase, Sentry, OneSignal, or SendGrid. Only non-sensitive event names like "check-in completed" are sent.]
  • You can withdraw consent at any time in [TODO: settings path] or by emailing us. If you withdraw, we will stop collecting new wellness entries and will delete existing ones as described in Section 6. Some features won't work without this information.

4.3 Automated decisions

We do not use automated decision-making that has legal or similarly significant effects on you, such as decisions about credit, employment, or insurance. [TODO: Confirm. If the app gives personalized recommendations or "insights" based on wellness data, describe them here.]


5. How We Share Information

5.1 Service providers (processors)

We share personal information with companies that help us run DailyRhythm. They may use it only to provide services to us and must protect it under written contracts.

Provider What they do for us Data involved Where data may be processed
Amazon Web Services (AWS) Cloud hosting and storage All data stored in our systems United States and EU [TODO: specify regions, and which users' data goes where]
Google Analytics for Firebase App analytics Usage info, device info, app instance ID, IDFA/AAID (if allowed), approximate location United States and other Google locations
Sentry Crash and error reporting Crash logs, device info, IP address [TODO: confirm whether IP collection or data scrubbing is turned on] [TODO: US or EU data region]
OneSignal Push notifications Push token, device info, notification preferences, and [TODO: confirm any user tags] United States [TODO: confirm]
SendGrid (Twilio) Transactional and marketing emails Name, email, email engagement (opens and clicks) United States [TODO: confirm]
Stripe Subscription billing and payments Payment details (Stripe collects full card data directly), billing ZIP, email United States and other Stripe locations

[TODO: Add any other vendors, such as customer support desk software, cloud email (Google Workspace/Microsoft 365), or internal tools used to read support messages.]

5.2 App stores

If you subscribe through the Apple App Store or Google Play, Apple or Google processes your payment as an independent controller. That means they decide how to use that data under their own privacy policies. We share only what's needed to confirm and manage your subscription.

Stripe may also act as an independent controller for some activities, such as fraud prevention and meeting its own legal obligations, under Stripe's Privacy Policy.

5.3 Other disclosures

We may also share personal information:

  • For legal reasons: To comply with a law, court order, subpoena, or other valid legal process, or to protect the rights, property, or safety of Northbridge, our users, or others. When the law allows, we will try to tell you before disclosing your data. We will challenge requests that are overly broad or unlawful.
  • In business transfers: If we're involved in a merger, acquisition, financing, bankruptcy, or sale of assets, personal information may transfer to the new owner. The new owner must honor this policy, or give you notice and any choices the law requires. [TODO: Washington MHMDA and some state laws may require new consent to transfer consumer health data. Check with counsel.]
  • With your direction or consent: For example, if you ask us to share data with another app or person. [TODO: Delete this line if there are no such features.]
  • In aggregated or de-identified form: We may share information that has been combined or stripped of identifiers so it can't reasonably identify you. We will not try to re-identify it.

5.4 We do not sell your personal information

We do not sell personal information, and we have not sold it in the past 12 months. We do not sell or share wellness or health information for any purpose.

Targeted advertising / "sharing": Under California law, "sharing" means giving data to third parties for cross-context behavioral advertising, which is ads based on your activity across different apps and websites.

[TODO, choose ONE after a technical review:] Option A (recommended): "We do not 'share' personal information for cross-context behavioral advertising or use it for 'targeted advertising.' We do not link Firebase to Google Ads or other advertising networks, and we do not use ad identifiers for advertising." Option B: If Firebase is linked to Google Ads, or IDFA/AAID is used for ad attribution or retargeting, you must disclose this as "sharing"/"targeted advertising," add a "Do Not Sell or Share My Personal Information" link and an in-app opt-out, and honor opt-out preference signals. Rewrite this section accordingly.

We do not knowingly sell or share the personal information of consumers under 16.


6. Data Retention and Security

6.1 How long we keep data

We keep personal information only as long as we need it for the purposes in this policy. Then we delete it or de-identify it.

Data How long we keep it
Account information While your account is open, plus [TODO: e.g., 30] days after deletion so you can recover it by mistake
Wellness entries While your account is open, or until you delete them or withdraw consent. Deleted within [TODO: e.g., 30] days after that
Payment and transaction records [TODO: e.g., 7] years, for tax and accounting laws
Support messages [TODO: e.g., 2 or 3] years after the conversation ends
Analytics data (Firebase) [TODO: set to 2 months or 14 months in Firebase settings]
Crash logs (Sentry) [TODO: e.g., 90 days]
Email and push records While you're subscribed, plus [TODO]
Backups Deleted data may stay in encrypted backups for up to [TODO: e.g., 35] days, then it's overwritten
Inactive accounts [TODO: e.g., after 24 months of no activity and no active subscription, we'll email you, then delete the account]

We may keep data longer if the law requires it, or to resolve disputes, stop fraud, or enforce our agreements.

6.2 How we protect data

We use reasonable administrative, technical, and physical safeguards, including:

  • encryption in transit (TLS/HTTPS) and at rest [TODO: confirm AES-256 or equivalent on AWS];
  • password hashing [TODO: confirm algorithm, such as bcrypt or Argon2];
  • access controls that limit employee access to people who need it, with multi-factor authentication [TODO: confirm];
  • vendor security reviews and data processing agreements;
  • logging and monitoring; and
  • an incident response plan, with breach notifications to you and regulators as the law requires.

No system is 100% secure. Please use a strong, unique password, and tell us right away at privacy@northbridgewellness.com if you think your account has been compromised.


7. Your Rights and Choices

7.1 Rights for everyone

Wherever you live, you can:

  • Access and download a copy of your data: [TODO: in-app export path, such as Settings › Privacy › Export My Data]
  • Correct your profile and entries in the app
  • Delete individual entries or your whole account: [TODO: in-app path, such as Settings › Account › Delete Account]. Apple and Google require apps to offer in-app account deletion.
  • Unsubscribe from marketing emails using the link in any email
  • Turn off push notifications in your device settings
  • Limit ad tracking by declining Apple's tracking prompt, or by resetting or deleting your ad ID on Android
  • Withdraw consent to wellness data processing (Section 4.2)

Cancelling a subscription does not delete your account, and deleting your account does not cancel an App Store or Google Play subscription. Manage those subscriptions in your Apple or Google account settings.

7.2 How to make a request

  • Email: privacy@northbridgewellness.com
  • In-app: [TODO: path]
  • Toll-free number: [TODO: The CCPA generally requires a toll-free number, unless you operate exclusively online and have a direct relationship with the consumer, in which case email alone is enough. Confirm which applies.]

Verification: To protect your data, we'll confirm your identity, usually by asking you to make the request while logged in or from your account email. We won't ask for more information than we need.

Authorized agents: You can have someone else make a request for you where the law allows. We may ask for signed permission and confirm your identity directly.

Response times: We respond within 1 month in the EU/UK, 30 days in Canada, and 45 days in the U.S. We may extend these deadlines where the law allows, and we will tell you if we do.

No discrimination: We won't deny you service, charge you a different price, or give you a worse experience because you used your privacy rights.

Cost: Requests are free, unless they are clearly unfounded or excessive.

7.3 EU and UK residents (GDPR / UK GDPR)

You have the right to:

  • Access your personal data;
  • Rectification, meaning to correct inaccurate data;
  • Erasure ("the right to be forgotten");
  • Restrict our processing;
  • Data portability, meaning to receive your data in a machine-readable format or have it sent to another company;
  • Object to processing based on legitimate interests, and to object at any time to direct marketing;
  • Withdraw consent at any time, without affecting processing that happened before you withdrew; and
  • Lodge a complaint with your local data protection authority. In the UK, that is the Information Commissioner's Office (ICO). In the EU, you can complain to the authority in your country.

EU representative: [TODO: Name and address of EU Art. 27 representative] UK representative: [TODO: Name and address of UK Art. 27 representative] Data Protection Officer: [TODO: Confirm whether a DPO is required. Large-scale processing of health data as a core activity may trigger GDPR Art. 37. If you appoint one, list the contact here.]

7.4 California residents (CCPA/CPRA)

Categories collected in the last 12 months (using CCPA category names):

CCPA category Examples Disclosed for a business purpose to
Identifiers Name, email, IP address, device and ad IDs Hosting, analytics, email, push, crash, and payment providers
Customer records (Cal. Civ. Code § 1798.80) Name, billing ZIP, last 4 card digits Stripe, AWS
Characteristics of protected classifications Age / date of birth AWS
Commercial information Subscription and purchase history Stripe, app stores, AWS
Internet or network activity App usage, session events, crash logs Firebase, Sentry, AWS
Geolocation data (approximate only) City or region from IP address Firebase, AWS
Audio/electronic/similar information Support messages AWS, [TODO: support tool]
Sensitive personal information Account login (email + password); health-related information (mood, sleep, weight) AWS only [TODO: confirm]
Inferences [TODO: Confirm none. If the app makes insights or profiles, list them here] —

Sources, purposes, and retention: See Sections 3, 4, and 6.

Your California rights: You can know/access, delete, and correct your data. You can opt out of sale/sharing (we don't sell or share; see Section 5.4). You can limit the use of sensitive personal information. We use sensitive personal information only for purposes allowed by the CCPA regulations, such as providing the service you asked for, so we don't currently offer a separate "Limit" link. [TODO: Confirm.] You also have the right to be free from retaliation.

Opt-out preference signals: We honor Global Privacy Control (GPC) and similar legally recognized signals where they apply. [TODO: Confirm technical implementation for the website.]

Shine the Light (Cal. Civ. Code § 1798.83): We do not share personal information with third parties for their own direct marketing.

[TODO: If Northbridge meets the CCPA threshold of 10+ million Californian consumers, publish annual request metrics.]

7.5 Colorado and other U.S. states

Residents of Colorado, Connecticut, Virginia, Oregon, Texas, and other states with comprehensive privacy laws have rights to confirm whether we process their data, and to access, correct, delete, and port it. They also have the right to opt out of targeted advertising, sale, and profiling for significant decisions. We don't engage in these activities; see Sections 4.3 and 5.4.

  • Sensitive data consent: Under Colorado and similar laws, health-related information is "sensitive data." We collect it only with your opt-in consent (Section 4.2).
  • Minors: Colorado law adds protections for users we know are under 18. We don't process minors' data for targeted advertising, sale, or profiling. [TODO: Review engagement features like streaks and reminders under Colorado's minors' rules if users under 18 are allowed.]
  • Universal opt-out: We honor recognized universal opt-out mechanisms, such as GPC.
  • Appeals: If we deny your request, you can appeal by emailing privacy@northbridgewellness.com with the subject "Privacy Appeal." We will respond within the time the law requires, usually 45–60 days. If you disagree with our decision, you can contact your state Attorney General.

7.6 Canadian residents (PIPEDA, Québec Law 25, and provincial laws)

  • You can access your personal information, challenge its accuracy and have it corrected, and withdraw consent, subject to legal or contractual limits.
  • Québec residents also have the right to data portability, the right to have information de-indexed or dissemination stopped where applicable, and the right to be told about automated decisions (we don't make any; see Section 4.3).
  • Person responsible for personal information / Privacy Officer: [TODO: Name/title]. Contact: privacy@northbridgewellness.com. (Québec requires publishing this person's title and contact details.)
  • Marketing emails: We send commercial emails to Canadians only with consent, as required by Canada's Anti-Spam Legislation (CASL).
  • Complaints: You can complain to the Office of the Privacy Commissioner of Canada, or in Québec, to the Commission d'accès à l'information.

7.7 Washington, Nevada, and Consumer Health Data

Washington's My Health My Data Act and similar laws in Nevada (and elsewhere) protect "consumer health data," and wellness entries in apps like DailyRhythm may count. We collect this data only with your consent, and we share it with other parties only with separate consent or as needed to provide the service. You can access it, delete it, and withdraw consent. Read our separate Consumer Health Data Privacy Policy for full details.

[TODO: Washington law requires a stand-alone Consumer Health Data Privacy Policy with a prominent link on the homepage and in the app. Draft it separately.]


8. International Data Transfers

Northbridge is based in the United States, and our service providers operate in several countries. Your personal information may be transferred to, stored in, and processed in the United States and other countries whose data protection laws may differ from yours.

  • EU/UK data: When we transfer personal data out of the EU or UK to a country without an "adequacy decision" (an official finding that the country protects data well enough), we use approved safeguards. These include the European Commission's Standard Contractual Clauses (SCCs) and the UK International Data Transfer Addendum, along with additional safeguards where needed. [TODO: If Northbridge self-certifies to the EU-U.S. Data Privacy Framework (and its UK Extension), add a DPF statement, independent recourse mechanism, and FTC jurisdiction language. Otherwise, rely on SCCs. Note that a challenge to the DPF is on appeal at the EU's top court.]
  • Data hosted in the EU: [TODO: State whether EU/UK users' data is stored in AWS EU regions, and whether any of it is accessed from the U.S., for example by support staff or U.S.-based vendors like Firebase, Sentry, SendGrid, and OneSignal.]
  • Canadian data: Your information may be processed outside Canada, including in the U.S. There, it may be accessible to courts, law enforcement, and national security authorities under local law. We use contracts to protect it. [TODO: Québec Law 25 requires a privacy impact assessment before transferring data outside Québec.]

For a copy of the safeguards we use, contact privacy@northbridgewellness.com.


9. Children's Privacy

DailyRhythm is not intended for children. You must be at least [TODO: minimum age, recommended 16, or 18] to use the Services. We check your date of birth at sign-up and don't let underage users create an account.

We don't knowingly collect personal information from children under 13 in the U.S. or under 16 in the EU/UK, or from anyone under the minimum age where they live. If we learn we have collected information from a child without proper consent, we'll delete it promptly. If you think a child has given us information, contact privacy@northbridgewellness.com.

[TODO: If users aged 13–17 are allowed, add a section on teen protections, including CCPA opt-in for ages 13–15, Colorado minors' rules, GDPR Art. 8 parental consent ages by country, and UK Age Appropriate Design Code duties.]


10. Cookies, SDKs, and Similar Technologies

Cookies are small files a website stores in your browser. Mobile apps use similar tools called SDKs (software development kits). These are pieces of code from other companies built into our app, plus device identifiers such as the IDFA/AAID.

Type Examples Purpose Your choice
Strictly necessary Login and session tokens, security Make the app work and keep it secure Required
Analytics Google Analytics for Firebase Understand how people use the app [TODO: In the EU/UK, get consent before turning this on (ePrivacy/PECR). Elsewhere, offer an in-app toggle]
Crash reporting Sentry Find and fix bugs [TODO: confirm whether this is treated as necessary or consent-based in the EU/UK]
Push notifications OneSignal Send reminders you've chosen Device notification settings
Advertising identifiers IDFA / AAID Limited in-app analytics only Apple tracking prompt; Android ad ID settings

Website: [TODO: If there is a marketing site with cookies, add a cookie banner and list of cookies, or link a separate Cookie Notice.]

To manage in-app analytics, go to [TODO: Settings › Privacy › Analytics].


11. Changes to This Policy

We may update this policy from time to time. The "Last Updated" date at the top shows when we last changed it. If we make material changes, such as using your data in a new way, we'll let you know in the app or by email before the change takes effect. Where the law requires it, we'll ask for your consent again, and we will not apply material changes to data we already collected without that consent.

Previous versions are available on request [TODO: or link to an archive].


12. Contact Us

Northbridge Wellness Technologies, Inc. Attn: Privacy Team [TODO: Street address, City, State ZIP, USA] Email: privacy@northbridgewellness.com Phone: [TODO, if required]

EU Representative: [TODO] UK Representative: [TODO] Canadian Privacy Officer: [TODO] Data Protection Officer (if appointed): [TODO]

If you're not satisfied with our response, you can contact your local data protection authority (see Section 7).


✅ Checklist: Items to Verify Before Publishing

  1. Advertising and "sharing" decision (Section 5.4): Confirm Firebase isn't linked to Google Ads or other ad networks, and decide whether IDFA/AAID is needed at all. If you drop them, remove the IDFA/AAID references. If you keep them for ads, add "Do Not Sell or Share" links and an opt-out.
  2. Wellness-data consent flow: Build a separate, explicit, opt-in consent screen (GDPR Art. 9, Colorado and other states' sensitive data rules, Washington MHMDA), with an easy way to withdraw.
  3. Stand-alone Consumer Health Data Privacy Policy: Draft and link one for Washington, and review Nevada's and Connecticut's consumer health data rules too.
  4. Keep health data out of vendors: Check that no mood, sleep, or weight values reach Firebase, Sentry, OneSignal, or SendGrid (event names, crash payloads, push tags, email templates).
  5. Minimum age: Pick 16 or 18 and enforce it with the date-of-birth check. If teens are allowed, add teen-specific protections.
  6. EU/UK Article 27 representatives and a DPO assessment: Appoint representatives and document the DPO decision.
  7. Transfer mechanism: Sign SCCs and UK Addenda with all vendors, complete transfer impact assessments, and decide on DPF certification. Confirm AWS region mapping for EU users.
  8. Canada: Name the Privacy Officer, get CASL-compliant marketing consent, and complete Québec's privacy impact assessment for transfers outside Québec.
  9. Retention periods: Fill in every TODO in Section 6 and set Firebase and Sentry retention settings to match.
  10. Security claims: Confirm encryption at rest, the hashing algorithm, and MFA before publishing.
  11. EU/UK consent for analytics SDKs: Add a consent prompt before non-essential SDKs run (ePrivacy/PECR).
  12. Request channels: Confirm the in-app export and deletion paths, whether a toll-free number is needed, GPC handling, and the appeals process.
  13. Data Processing Agreements (DPAs): Make sure signed DPAs are in place with AWS, Google/Firebase, Stripe, SendGrid, OneSignal, and Sentry.
  14. Consistency: Make sure your App Store "Privacy Nutrition Label" and Google Play "Data safety" form match this policy exactly.
  15. Data protection impact assessment (DPIA) and state risk assessments: Do these for health data processing (GDPR Art. 35, Colorado, and the new CCPA risk-assessment rules).

Disclaimer: This is a template draft, not legal advice. It must be reviewed and adapted by qualified legal counsel in each relevant jurisdiction before publication.


Drafting notes: I checked several current legal developments to set up the transfer, health-data, and minors sections:

  • EU–U.S. Data Privacy Framework: It's still valid. The EU General Court upheld it in September 2025, but an appeal is pending at the EU's top court (Case C-703/25 P). That's why the policy uses Standard Contractual Clauses as the main safeguard and treats the Framework as optional.
  • Washington's My Health My Data Act: Wellness app data is covered. The law requires opt-in consent to collect it, separate consent to share it, and a stand-alone policy.
  • Colorado: Protections for known minors now extend to users under 18.

Sources:

Related prompts

Law & Legal

Intellectual Property Strategy Advisor

Builds a structured IP protection, licensing, and enforcement strategy for any business, invention, or creative work.

Law & Legal

Legal Consultation Simulator

Simulates a structured legal client consultation with assessment, analysis, strategic options, and clear recommendations.

Law & Legal

Legal Document Analysis Expert

Reviews any legal document to flag risks, obligations, and key clauses, with prioritized redline recommendations.

Law & Legal

Legal Research Assistant

Expert legal research workflow producing a cited memo on statutes, case law, and regulatory issues by jurisdiction.