Privacy Policy

Last updated: November 18, 2026

The short version

  • We collect what we need to send your reports, plus pseudonymous usage data that helps us improve Morning Pulse. You can turn usage data off in Settings.
  • Your analytics data is fetched, processed, and emailed to you. We don't sell it. Ever.
  • We use industry-standard encryption and security practices.
  • You can export or delete your data at any time.
  • When you connect a Shopify store, we request read-only access to orders — nothing else.
  • Our website sets no cookies of its own, so there is no cookie banner.

Read on for the legally complete version.

Morning Pulse ("we," "us," or "our") respects your privacy and is committed to protecting your personal data. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our website and service (the "Service").

This policy applies to all users of Morning Pulse, regardless of location. Where specific regulations apply (such as the GDPR for EU/EEA users or the CCPA for California residents), additional provisions are noted below.

1

Information We Collect

1.1 Information You Provide Directly

  • Account Information: Your name, email address, and password when you create an account.
  • Report recipients: Email addresses you add as extra recipients of your daily email (Pro). We use them only to send the verification email, your reports and alerts, and delete them when you remove the recipient or delete your account.
  • Billing Information: Payment method details (credit card number, billing address) processed securely through our third-party payment processor. We do not store full card numbers on our servers. If you install Morning Pulse via the Shopify App Store, billing is handled entirely by the Shopify Billing API — Shopify charges your account on our behalf, and we never see your payment card data in that flow.
  • Preferences: Your selected metrics, delivery time, timezone, and notification preferences.
  • Communications: Any messages or feedback you send to our support team.
  • Email Health (optional): If you turn on Email health for an app, you give us an email domain and, optionally, DKIM selectors. You can also paste the headers of an email you sent so we can find its DKIM selector: we read only the selector and do not keep the headers. Every day, and whenever you ask for a new check, we read the domain’s public DNS records (MX, SPF, DKIM, DMARC, MTA-STS, TLS reporting and BIMI) and check the domain, and the addresses of your own mail servers, against DNS blocklists. We never connect to your mail servers or read your email.
  • WhatsApp Number (optional): If you are a paid Pro subscriber billed through Stripe and turn on the WhatsApp morning brief, your WhatsApp phone number and WhatsApp ID, a record of your consent, and the delivery status of your briefs. See Section 16 for our complete WhatsApp Morning Brief disclosure.

1.2 Information from Third-Party Services

  • Google Analytics 4 Data: When you connect your GA4 account, we request the analytics.readonly OAuth 2.0 scope. This grants read-only access to your GA4 property data — including metrics such as sessions, pageviews, active users, traffic sources, conversions, and revenue data — via the Google Analytics Data API. See Section 14 for our complete Google User Data disclosure.
  • Google Search Console Data: When you connect Google Search Console, we request the webmasters.readonly OAuth 2.0 scope, which is read-only. We list the Search Console properties your Google account can see so you can choose one; that list is shown only to you, kept in memory for at most one minute, and never saved. For the property you choose, we then read only daily site totals: clicks, impressions, click-through rate (CTR) and average position, via the Search Console API. We do not read search queries, page URLs, or any other breakdown, and we cannot change anything in your Search Console. See Section 14 for our complete Google User Data disclosure.
  • Amplitude Data: When you connect Amplitude, you paste your project’s API key and a secret key. We store both keys encrypted at rest and use them only to read daily project totals from the Amplitude Dashboard REST API, in the data region (US or EU) you choose: active users, new users, sessions per user and average session length. We do not read individual events, user IDs, device IDs, user properties or cohorts, and we do not change anything in your Amplitude project. Amplitude secret keys are not limited to reading, so we recommend creating a secret key just for Morning Pulse. Disconnecting Amplitude in Morning Pulse deletes our copy of both keys; to revoke them, delete the secret key in Amplitude.
  • Plausible Analytics Data: When you connect Plausible, you paste a Plausible Stats API key. We store the key encrypted at rest and use it only to list the sites the key can see, so you can choose one (we keep only the site you choose and its time zone), and to read daily site totals for that site from the Plausible Stats API: visitors, visits, pageviews, views per visit, bounce rate and visit duration. We do not read breakdowns by page, referrer or city, and we do not read guest or team data. We do not change anything in your Plausible account. We recommend creating a Stats API key just for Morning Pulse. Disconnecting Plausible in Morning Pulse deletes our copy of the key; to revoke it, delete the key in Plausible.
  • Cloudflare Analytics Data: When you connect your Cloudflare account, you paste a Cloudflare API token, and we read your zone and Web Analytics data with it, with your authorization. This is separate from Morning Pulse’s own use of Cloudflare for morningpulse.app (see Section 4). We store the API token, encrypted (only its last 4 characters stay readable), its expiry date, your Cloudflare account ID, the zone ID and domain name and the Web Analytics site tag and hostname you pick, and daily totals: visits, page views, requests, cache hit rate, threats blocked and bandwidth, plus daily performance aggregates from Web Analytics: the share of page loads with good Core Web Vitals, the 75th-percentile load and response times, and the number of page loads measured. We do not read or store visitor-level data or IP addresses. Disconnecting Cloudflare in Morning Pulse deletes the token and those settings immediately; to revoke the token, delete it in Cloudflare.
  • X Data: When you connect X (Pro plan), X Corp. asks you to allow the tweet.read, users.read and offline.access OAuth 2.0 scopes. X's read permission also lets an app see posts you can see. Morning Pulse only reads your own posts' numbers: your @handle, profile picture and follower count, and once a day the counters of your own posts and quotes from the last 3 days (impressions, engagements, likes, reposts, replies, link clicks and profile visits). We never read or store what your posts say, media, direct messages, who follows you, likes, bookmarks or other people's posts, and we never post, repost, like or follow for you. See Section 17 for our complete X Data disclosure.
  • Instagram Data: When you connect an Instagram Business or Creator account through Facebook, we store your Instagram account ID and username, the access token (encrypted), the Meta IDs that identify your authorization (business ID and system user ID), a daily follower count from the day you connect, and daily account totals: views, reach, likes, comments, shares, saves, interactions and profile link taps. We do not read or store your posts, captions, the text of comments, who follows you, or your profile photo. See Section 18 for our complete Instagram Data disclosure, including how to delete it.
  • TikTok Data: When you connect a TikTok Business account, with your permission we read your TikTok account’s ID and username, and daily totals for followers, new followers, profile views, video views, likes, comments and shares. We store the access and refresh tokens encrypted at rest. We do not read your videos, captions, comments, messages or audience demographics, and we never post. See Section 19 for our complete TikTok Data disclosure.
  • Apple App Store Connect Data: When you provide an App Store Connect API key, we access metrics such as app units, impressions, product page views, in-app purchases, crash counts, and ratings via the App Store Connect API. If you turn on App Store earnings for an app, you also give us your Apple vendor number, which we store, and, only if your first key can’t read financial reports, a second API key with the Finance role, which we store encrypted at rest and use only for earnings. With them we read Apple’s monthly financial reports. They cover every app in your developer account and contain no buyer details; we keep only this app’s monthly totals (net proceeds, refunds and units) and discard the rest without storing it. We never request subscriber-level reports. Apple reports amounts in many currencies, so we convert this app’s totals into the one currency you choose using public reference exchange rates (see Section 4).
  • Google Play Console Data: When you connect Google Play with Google OAuth, we access Android vitals (such as crash and ANR rates), ratings and reviews, and the number of in-app products and subscriptions in your catalog via the Google Play Developer Reporting API and the Google Play Android Developer API. We only read; we never change anything in your Play Console. If you also connect the optional Play reports, we request the read-only Cloud Storage scope (devstorage.read_only) and read only the Play Console bulk report files for installs and store performance in your developer account's reports bucket. If you also turn on Play earnings for an app, we read the monthly earnings report files in the same bucket with the same read-only access. These files list every order in your developer account, including the order number and the buyer’s country, state and postal code. We read them in memory only, add up this app’s monthly totals (net earnings, sales, refunds, Google fees and charges) and keep only those totals; we never store, log or share individual orders or buyer details. We do not read any other bucket or file.
  • Stripe Data: When you provide a restricted API key with read-only permissions, we access metrics such as charges, customer counts, active subscriptions, balance transactions, and revenue breakdowns via the Stripe API. We never gain the ability to create charges, issue refunds, or modify any data in your Stripe account.
  • Shopify Merchant Data: When you install the Morning Pulse Shopify app (or connect your store via OAuth), we request the read_orders scope. This grants read-only access to order-level aggregate metrics — order count, gross sales, refunds, and currency — via the Shopify Admin API. We do not access individual customer PII, product catalogs, inventory, shipping addresses, or fulfillment data. We never request any write_* scopes, so we cannot create, modify, refund, or cancel anything in your store. See Section 15 for our complete Shopify Merchant Data disclosure.

We only request the minimum data scopes necessary to generate your reports. We do not access personal data of your end users, with one exception: the Google Play earnings files described above, which we read in memory only, on your behalf, to compute totals, and never store. For that processing we act as your processor (see our Terms of Service, Data Processing).

1.3 Information Collected Automatically

  • Usage Data: What you do in Morning Pulse, such as signing up, connecting a data source, adding a KPI, opening the app or clicking a link in one of our emails, and what happens to your account, such as a report being sent, WhatsApp reporting a brief as read, or a trial ending. Our servers send these events to Amplitude, our product analytics provider, under a pseudonymous ID: a code that contains no name or email address, which only we can link back to your account. Each event also carries a few details of your account: your plan, subscription status and billing channel (Stripe or Shopify), your sign-up month and method, the types of data source you have connected, which catalog metric a KPI tracks, whether you use a team, the WhatsApp brief or alerts, and counts such as how many apps and KPIs you have, in ranges (for example 2–5) rather than exact numbers. Events never include your KPI values, report contents, connected data, the names of your apps or KPIs, your email address or your IP address. You can turn this off at any time in Settings > Privacy > Share usage data.
  • Device Information: Browser type, operating system, device type.
  • Log Data: IP address, access timestamps, referring URLs, and error logs for security and diagnostics.
  • Cookies: The app uses essential cookies to sign you in. Our website sets none of its own. See Section 8.
2

How We Use Your Information

We use collected information for the following purposes:

Service Delivery

Fetching your analytics data, generating reports, and delivering daily emails (and, if you turn it on, the WhatsApp morning brief).

Account Management

Authentication, billing, subscription management, and customer support.

Service Improvement

Analyzing usage patterns to improve features, performance, and user experience.

Communication

Service announcements, security alerts, billing notifications, and (with consent) product updates.

Security & Fraud Prevention

Detecting unauthorized access, preventing abuse, and maintaining platform integrity.

Legal Compliance

Meeting legal obligations, responding to lawful requests, and enforcing our Terms.

We do not use your analytics data for advertising, profiling, or any purpose other than generating your requested reports.

We use your WhatsApp number only to deliver the WhatsApp morning brief you turned on and the service messages described in Section 16. We never use it for marketing.

3

Legal Basis for Processing (GDPR)

For users in the European Economic Area (EEA), United Kingdom, and Switzerland, we process personal data under the following legal bases:

  • Contract Performance (Art. 6(1)(b) GDPR): Processing necessary to provide the Service you signed up for.
  • Legitimate Interests (Art. 6(1)(f) GDPR): Improving the Service, ensuring security, preventing fraud, and understanding how the Service is used (product analytics), which you can turn off in Settings. We rely on these interests only where they do not override your fundamental rights.
  • Consent (Art. 6(1)(a) GDPR): Marketing communications and the optional WhatsApp morning brief, which you may withdraw at any time. Withdrawing consent for WhatsApp does not affect your email brief.
  • Legal Obligation (Art. 6(1)(c) GDPR): Compliance with applicable laws and regulations.

When we read Google Play earnings files for you, the buyer details in them are personal data that you control; we process them only as your processor, on your instructions, under the data processing terms in our Terms of Service.

4

Data Sharing and Disclosure

We do not sell, rent, or trade your personal information. We share data only in the following limited circumstances:

  • Service Providers: We engage trusted third-party processors to assist with payment processing (Stripe), cloud hosting (Scaleway SAS: application, database and object storage, in Paris, France), transactional email (Scaleway Transactional Email), content delivery, DNS and security for our website, morningpulse.app (Cloudflare, Inc.), website analytics (cookieless Cloudflare Web Analytics), product analytics (Amplitude, Inc., EU data centre), and Shopify, which acts as the data source and billing processor for merchants who install Morning Pulse from the Shopify App Store. If you turn on the optional WhatsApp morning brief, Meta Platforms Ireland Limited delivers it through the WhatsApp Business Platform (see Section 16). Each processor is bound by data processing agreements and may only use your data as instructed by us.
  • X Corp.: If you connect X, X Corp. is the source of your X data. We send X your access tokens to read your own posts' numbers and to revoke our access when you disconnect. X is not our processor: for X data, Morning Pulse acts as an independent controller under X's developer terms (see Section 17).
  • Cloudflare, Inc. (your account): If you connect Cloudflare, your Cloudflare account is the source of that data. We send Cloudflare your API token only to read your analytics. This is separate from our own use of Cloudflare for morningpulse.app, listed under Service Providers above.
  • Meta (Instagram): If you connect Instagram, Instagram is the source of your Instagram data. We send Meta your access token only to read your own account’s numbers, with your authorization. Meta is not our processor for this data; that is different from the WhatsApp brief, where Meta delivers messages for us (see Section 16). Section 18 covers Instagram data in full.
  • TikTok: If you connect TikTok, TikTok is the source of your TikTok data and is not our sub-processor. We send TikTok your tokens only to read your own account’s numbers, with your authorization, to renew our access, and to ask TikTok to revoke it once no Morning Pulse app uses that TikTok account any more. Section 19 covers TikTok data in full.
  • Exchange Rate Providers: To convert App Store earnings into your chosen currency, we look up public exchange rates from the European Central Bank reference rates (through Frankfurter) and, for currencies the ECB doesn’t publish, from the free currency-api dataset served by jsDelivr. These requests contain only currency codes and dates, never amounts, your name or your account details.
  • Public DNS Resolvers and Blocklist Operators: For Email health, the domain names and mail server addresses we check are sent as DNS queries to public resolvers (Quad9 Foundation, Switzerland; Cloudflare, Inc., United States) and to the blocklist operators we query (Spamh_aus and PSBL). These queries contain only the domain or address being checked, never your name, email address or account details.
  • Legal Requirements: We may disclose information if required by law, subpoena, court order, or governmental regulation, or if we believe disclosure is necessary to protect our rights, your safety, or the safety of others.
  • Business Transfers: In the event of a merger, acquisition, or sale of assets, your data may be transferred to the successor entity. We will notify you of any such change and any choices you may have regarding your data.
  • With Your Consent: We may share data with third parties when you explicitly authorize us to do so.
5

Data Retention

We retain your data only for as long as necessary to fulfill the purposes described in this policy:

Data Type Retention Period
Account information Until account deletion + 30 days
Analytics data (reports) While the KPI exists; deleted when you delete the KPI, its app or your account
Monthly financial totals (App Store and Google Play earnings) While the KPI exists; deleted when you delete the KPI, its app or your account. Store report files and Google Play order rows are never stored
Apple vendor number and App Store earnings settings (chosen currency, Finance key if any, encrypted) Until you remove App Store earnings, delete the app or delete your account
Billing records 7 years (legal/tax requirement)
Server logs 90 days
Product usage events (Amplitude) 25 months, then deleted; erasure requested within 30 days of account deletion
Email health results Daily check results for 90 days; the change history while checks are on. Deleted when you stop the checks, change the domain, or delete the app or your account
Support correspondence 2 years after last interaction
OAuth tokens / API keys Until revoked or account deletion
Shopify order aggregates While the KPI exists; deleted when you delete the KPI, its app or your account, or about 48 hours after uninstall (see Section 15.5)
Shopify OAuth tokens Until uninstall or account deletion (then deleted within 48h via shop/redact)
X tokens (encrypted), X user ID, @handle and profile picture link Until you disconnect X, delete the app or delete your account
X tracked posts (post IDs, publish dates, counters) About 3 days, pruned daily; within 24 hours of a post being deleted on X; immediately when you disconnect X
Cloudflare API token (encrypted), its expiry, account ID, zone and Web Analytics site settings Until you disconnect Cloudflare (then deleted immediately), delete the app or delete your account
Instagram account ID and username, access token (encrypted), Meta business and system user IDs; daily follower counts Until you disconnect Instagram or delete the app or your account; the token also goes when you remove Morning Pulse’s access in Meta (see Section 18)
TikTok account ID and username, access and refresh tokens (encrypted) Until you disconnect TikTok or delete the app or your account; then deleted, and TikTok asked to revoke our access, unless the same TikTok account is still connected to another Morning Pulse app (see Section 19)
WhatsApp number and WhatsApp ID (encrypted) While linked, and after you stop the brief or it is paused, until you remove or unlink the number or delete your account
WhatsApp webhook event IDs 30 days (de-duplication), then deleted
Unconfirmed WhatsApp link attempts 24 hours, then deleted

When data is no longer needed, it is permanently deleted or anonymized so that it can no longer be associated with you.

6

Data Security

We implement robust technical and organizational measures to protect your data:

  • Encryption in Transit: All data transmitted between your browser, our servers, and third-party APIs is encrypted using TLS 1.2 or higher.
  • Encryption at Rest: The credentials you give us to connect your sources (OAuth tokens and API keys, including App Store Connect .p8 keys (and the separate Finance key, if you add one for earnings), Amplitude key pairs, Plausible API keys, Cloudflare API tokens, Instagram access tokens and TikTok access tokens), two-factor authentication secrets and WhatsApp numbers are encrypted at rest (Fernet) in our database. Passwords are stored only as bcrypt hashes.
  • Access Controls: Access to user data is restricted to authorized personnel on a need-to-know basis, protected by multi-factor authentication.
  • Infrastructure: We host on Scaleway (Scaleway SAS), in its fr-par region in Paris, France: application, database and object storage.
  • OAuth & API Key Security: Google OAuth refresh tokens and App Store Connect API keys are stored encrypted at rest (Fernet) in our database and are never exposed in logs, client-side code, or to support staff.
  • Incident Response: We maintain an incident response plan and will notify affected users within 72 hours of discovering a personal data breach, as required by applicable law.

While we take every reasonable precaution, no method of electronic storage or transmission is 100% secure. We cannot guarantee absolute security but are committed to protecting your data to the highest commercially reasonable standard.

7

International Data Transfers

Morning Pulse is operated by FRENCHMOB, based in Paris, France. Our application, database and object storage are hosted by Scaleway SAS in Paris, France. Your data may be transferred outside the EEA only when one of our service providers, such as Stripe, Google, Shopify or Cloudflare, processes it to provide the Service.

If you turn on the WhatsApp morning brief, our WhatsApp number is configured with Meta's Cloud API local storage in Germany (EU) for message data at rest. Meta may process data outside the EU in accordance with its data transfer safeguards.

Amplitude stores our product usage events in the EU. Amplitude, Inc. is a US company and may access them from the United States under the EU–US Data Privacy Framework and Standard Contractual Clauses.

For transfers from the EEA, UK, or Switzerland, we rely on:

  • Standard Contractual Clauses (SCCs) approved by the European Commission.
  • Data processing agreements with all sub-processors that include appropriate safeguards.
  • Additional technical measures (encryption, pseudonymization) to ensure an equivalent level of protection.
8

Cookies and Tracking Technologies

8.1 Our Website (morningpulse.app)

Our website, morningpulse.app, sets no cookies of its own and uses no Google Analytics, Google Tag Manager or consent banner.

The website is served through Cloudflare, which handles each request (including your IP address) to deliver and protect the site. Cloudflare may set a strictly necessary security cookie (__cf_bm, or cf_clearance after a security check). These are not used for analytics.

We also use Cloudflare Web Analytics on the website to count page views and measure page speed. It sets no cookies and stores nothing on your device, so it does not ask for consent; Cloudflare uses the request (page address, referrer, browser, device type and country) to produce aggregate statistics and does not use it to identify you.

On the contact page, Cloudflare Turnstile checks that you are not a bot before you can open an email to us. Our pages also load the Alpine.js script from the jsDelivr content delivery network, which receives your IP address to deliver it.

8.2 The App (check.morningpulse.app)

The Morning Pulse app at check.morningpulse.app does not use Cloudflare. It uses only the cookies it needs to sign you in and keep your account secure:

Cookie Purpose
mp_session24 hours Keeps you signed in
mp_csrf24 hours Protects your forms against cross-site request forgery
pending_2fa5 minutes Holds your sign-in while you enter your two-factor code
mp_oauth_state10 minutes Secures sign-in with Google and connecting Google or Shopify
mp_x_oauth10 minutes Secures connecting your X account
mp_team_invite1 hour Holds a team invitation while you sign up or sign in

Amplitude sets no cookies. Usage events are sent from our servers, not from your browser.

We do not use advertising cookies, tracking pixels, or social media trackers of any kind.

9

Your Privacy Rights

Depending on your location, you may have the following rights regarding your personal data:

9.1 Rights for All Users

  • Access: Request a copy of the personal data we hold about you.
  • Correction: Request correction of inaccurate or incomplete data.
  • Deletion: Request deletion of your personal data, subject to legal retention requirements.
  • Data Portability: Request an export of your data in a machine-readable format (JSON or CSV).
  • Withdraw Consent: Where processing is based on consent, withdraw that consent at any time without affecting the lawfulness of prior processing.

9.2 Additional Rights for EU/EEA/UK Users (GDPR)

  • Restriction: Request restriction of processing under certain circumstances.
  • Objection: Object to processing based on legitimate interests.
  • Supervisory Authority: Lodge a complaint with your local data protection authority.

9.3 Additional Rights for California Residents (CCPA/CPRA)

  • Right to Know: Request disclosure of the categories and specific pieces of personal information collected.
  • Right to Delete: Request deletion of personal information collected.
  • Right to Opt-Out of Sale: We do not sell personal information. This right is automatically honored.
  • Right to Non-Discrimination: We will not discriminate against you for exercising your privacy rights.
  • Right to Correct: Request correction of inaccurate personal information.
  • Right to Limit Use of Sensitive Personal Information: We do not collect sensitive personal information as defined by the CPRA.

To exercise any of these rights, contact us at privacy@morningpulse.app. We will respond within 30 days (or sooner where required by law). We may need to verify your identity before processing your request.

10

Children's Privacy

Morning Pulse is not directed to individuals under the age of 18. We do not knowingly collect personal information from children. If we become aware that a child under 18 has provided us with personal data, we will take immediate steps to delete that information.

If you believe a child has provided us with personal data, please contact us at privacy@morningpulse.app.

11

Third-Party Links

The Service may contain links to third-party websites or services that are not owned or controlled by Morning Pulse. We are not responsible for the privacy practices of these third parties. We encourage you to review the privacy policies of any third-party sites you visit.

12

Do Not Track Signals

Morning Pulse does not respond to Do Not Track signals. Our website sets no cookies of its own, and product usage data stops when you turn off Settings > Privacy > Share usage data.

13

Changes to This Policy

We may update this Privacy Policy periodically to reflect changes in our practices, technology, or legal requirements. When we make material changes:

  • We will update the "Last updated" date at the top of this page.
  • We will notify you by email at least 15 days before changes take effect.
  • For significant changes, we may require you to re-acknowledge the updated policy.

We encourage you to review this page periodically. Your continued use of the Service after changes become effective constitutes your acceptance of the revised policy.

14

Google User Data

This section specifically addresses how Morning Pulse accesses, uses, stores, and protects data obtained through Google APIs, in accordance with the Google API Services User Data Policy, including the Limited Use requirements.

14.1 What Google User Data We Access

Morning Pulse requests the analytics.readonly OAuth 2.0 scope, which grants read-only access to your Google Analytics 4 property data. Specifically, we access:

  • Sessions, pageviews, and active user counts
  • Traffic sources and acquisition channels
  • Conversion events and goal completions
  • Revenue and e-commerce metrics (if configured in your GA4 property)

We do not access personally identifiable information about your end users, and we do not request write access to your Google Analytics account.

If you connect Google Search Console, Morning Pulse requests the webmasters.readonly OAuth 2.0 scope. It is read-only and used only to list the properties you can choose from and to read the daily totals of the one property you pick: clicks, impressions, click-through rate (CTR) and average position. We do not access search queries or page URLs, which can contain information about the people searching, and we have no write access to your Search Console.

If you connect Google Play, Morning Pulse requests the playdeveloperreporting and androidpublisher OAuth 2.0 scopes. We use them only to read Android vitals (such as crash and ANR rates), your app’s ratings and reviews, and the number of in-app products and subscriptions in your catalog. Google does not offer a read-only version of androidpublisher; Morning Pulse only calls its read endpoints and never publishes, edits, or replies to anything in your Play Console.

If you connect the optional Google Play reports, Morning Pulse also requests the devstorage.read_only OAuth 2.0 scope. It is read-only and used only to download the Play Console installs and store performance report files from the reports bucket you point us to, and, if you turn on Play earnings for an app, the monthly earnings report files in that same bucket. Earnings files list every order in your developer account with the buyer’s country, state and postal code: we read them in memory only, keep only the connected app’s monthly totals, and never store, log or share individual orders or buyer details. We do not read any other bucket, and we have no write access to your Cloud Storage.

14.2 How We Use Google User Data

Google user data is used exclusively to:

  • Generate your daily and weekly KPI email reports
  • Display metrics on your Morning Pulse dashboard
  • Compute the monthly earnings totals of the app you connected, if you turn on Play earnings

We do not use Google user data for any other purpose. Specifically, we do not:

  • Use Google user data for advertising, retargeting, or any form of ad targeting
  • Sell, rent, lease, or trade Google user data to any third party
  • Use Google user data to train artificial intelligence or machine learning models
  • Use Google user data for credit-worthiness assessments or lending purposes
  • Use Google user data to build user profiles for purposes unrelated to the Service
  • Transfer Google user data to any third party for purposes unrelated to providing or improving the Service

14.3 How We Store and Protect Google User Data

  • OAuth Refresh Tokens: Stored encrypted at rest (Fernet) in our database. Tokens are never logged, exposed in client-side code, or accessible to support staff.
  • Analytics Data: Fetched metrics are stored as KPI values to generate your reports, and deleted when you delete the KPI, its app or your account.
  • Play Earnings Files: Read in memory only, never written to disk, logs or error reports. Only the connected app’s monthly totals are kept; individual orders and buyer location fields are discarded as soon as the totals are computed.
  • Encryption in Transit: All communication with Google APIs uses TLS 1.2 or higher.
  • Access Controls: Only the automated report generation system accesses your Google data. No human has direct access to your raw analytics data.

14.4 How We Share Google User Data

We do not share, transfer, or disclose your Google user data to any third party, except:

  • Cloud Infrastructure Provider: Our hosting provider (Scaleway SAS, in Paris, France) processes data as a sub-processor solely to run our application. They do not have independent access to or use of your Google data.
  • Legal Requirements: We may disclose data if required by a valid legal process (e.g., court order, subpoena).

We do not share Google user data with advertising networks, data brokers, or information resellers.

14.5 Data Deletion and Revocation

You can revoke Morning Pulse's access to your Google data at any time by:

  • Disconnecting Google Analytics or Google Search Console from your app’s page in Morning Pulse. Disconnecting Search Console deletes the token stored by Morning Pulse; to also remove the access at Google, use your Google Account permissions page below.
  • Revoking access via your Google Account permissions page. This removes every Morning Pulse access to that Google account, including Google Analytics, Google Search Console, Google Play, and Play reports. Google Play and Play reports have no Disconnect button in Morning Pulse yet, so this is how you revoke them.
  • Deleting the app in Morning Pulse, which deletes its stored Google Play, Play reports and Search Console tokens
  • Deleting your Morning Pulse account entirely

When you disconnect, delete an app, or delete your account, we delete the stored OAuth tokens immediately and your cached analytics data within 30 days. When you revoke access from your Google Account, the stored tokens stop working immediately and Morning Pulse can no longer read any of your Google data.

14.6 Limited Use Compliance

Morning Pulse's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

15

Shopify Merchant Data

This section specifically addresses how Morning Pulse accesses, uses, stores, and protects merchant data obtained through the Shopify Admin API, in accordance with the Shopify API Terms of Service and the Shopify Partner Program Agreement.

15.1 What Shopify Data We Access

Morning Pulse requests the read_orders scope, which grants read-only access to your Shopify store's order data via the Shopify Admin API. Specifically, we read order-level aggregate metrics:

  • Order count
  • Gross sales
  • Refunds
  • Currency

We do not access customer PII, products, inventory, shipping addresses, or fulfillment data. We never request any write_* scope, so we cannot create, modify, refund, or cancel anything in your store.

15.2 How We Use Shopify Data

Shopify merchant data is used exclusively to:

  • Generate your daily and weekly KPI email reports
  • Display metrics on your Morning Pulse dashboard

We do not use Shopify merchant data for any other purpose. Specifically, we do not:

  • Use Shopify data for advertising, retargeting, or any form of ad targeting
  • Sell, rent, lease, or trade Shopify data to any third party
  • Use Shopify data to train artificial intelligence or machine learning models
  • Use Shopify data for credit-worthiness assessments or lending purposes
  • Use Shopify data to build merchant or user profiles for purposes unrelated to the Service
  • Transfer Shopify data to any third party for purposes unrelated to providing or improving the Service

15.3 How We Store and Protect Shopify Data

  • OAuth Access Tokens: Stored encrypted at rest (Fernet) in our database. Tokens are never logged, exposed in client-side code, or accessible to support staff.
  • Order Aggregates: Fetched order aggregates are stored as KPI values to generate your reports, and deleted when you delete the KPI, its app or your account, or after uninstall as described in Section 15.5.
  • Encryption in Transit: All communication with the Shopify Admin API uses TLS 1.2 or higher.

15.4 How We Share Shopify Data

We do not share, transfer, or disclose your Shopify merchant data to any third party, except:

  • Cloud Infrastructure Provider: Our hosting provider (Scaleway SAS, in Paris, France) processes data as a sub-processor solely to run our application. They do not have independent access to or use of your Shopify data.
  • Legal Requirements: We may disclose data if required by a valid legal process (e.g., court order, subpoena).

We do not share Shopify merchant data with advertising networks, data brokers, or information resellers.

15.5 Data Deletion, Uninstall, and GDPR Webhooks

You can revoke Morning Pulse's access to your Shopify data at any time by:

  • Uninstalling the app from your Shopify Admin (Apps → Morning Pulse → Uninstall)
  • Disconnecting the Shopify integration from your Morning Pulse settings page
  • Deleting your Morning Pulse account entirely

We honor the Shopify GDPR mandatory webhooks as follows:

  • app/uninstalled: On app uninstall, we immediately cancel the subscription and mark the OAuth credential as revoked.
  • shop/redact: Approximately 48 hours after uninstall, Shopify fires this webhook. We then hard-delete all store data, OAuth tokens, and cached order aggregates for that shop. This deletion is permanent and non-recoverable.
  • customers/data_request and customers/redact: These webhooks are received, verified, and acknowledged. Because Morning Pulse stores no Shopify customer PII, there is nothing to return or redact — the response is a logged no-op, recorded for the compliance trail.

If you need immediate deletion before the 48-hour shop/redact window, email privacy@morningpulse.app and we will purge your data on request.

15.6 Compliance with Shopify Policies

Morning Pulse's handling of Shopify merchant data adheres to the Shopify API Terms of Service and the Shopify Partner Program Agreement.

16

WhatsApp Morning Brief

This section explains how Morning Pulse handles your data if you turn on the optional WhatsApp morning brief. The feature is available only to paid Pro subscribers billed through Stripe (not Pro billed through Shopify, Free, Starter or Pro trial users), is offered for phone numbers from EU countries, India and Canada, and is off unless you turn it on.

16.1 How You Turn It On

In Morning Pulse, go to Daily email → WhatsApp, then:

  • Tick the consent box, which is unticked by default. It reads: "Send my Morning Pulse brief to my WhatsApp number every morning, around 7:00 AM my time. I can reply STOP at any time to turn it off. Messages are delivered by WhatsApp, a Meta service."
  • Re-enter your password or your two-factor authentication code.
  • Send the single-use code we show you, valid for 15 minutes, from your WhatsApp to our business number +33 7 69 38 32 88.
  • Confirm your number when asked "Is this your number?"

We record when you gave your consent and which version of the consent wording you agreed to.

16.2 What We Send You

Each brief contains:

  • A daily summary of the metrics from the apps you have connected to Morning Pulse (for example revenue, sessions or downloads), compared with the same day last week
  • A link to your full brief on our website. The link carries a signed token, works for 7 days, and stops working if you unlink your number or turn WhatsApp off.

We do not send marketing or promotional content over WhatsApp. Apart from the brief, we send only service messages about the feature, such as a one-line confirmation when you link your number or stop the brief.

16.3 What We Store

  • Your Number: Your WhatsApp phone number and WhatsApp ID, encrypted at rest, plus a keyed hash of each that we use only to look you up.
  • Consent Record: The time you gave consent and the version of the consent wording.
  • Verification: A hash of your link code and its expiry time, and the time your number was verified. Link attempts you do not confirm are deleted after 24 hours.
  • Delivery Status: The ID and delivery status (sent, delivered, read or failed) of your latest brief message, and a count of failed deliveries.
  • Opt-Out: The time you stopped the brief, if you did.
  • Webhook Events: The IDs of the events Meta sends us about messages, stored with a keyed hash of your WhatsApp ID so that we process each event only once. They are deleted after 30 days.

We do not read or store the content of messages you send to our WhatsApp number. We only recognise a link code, a stop word (see Section 16.5) or a tap on the "Turn off" button. We never fetch photos, files, locations or any other media you send.

16.4 How Meta Delivers the Messages

Messages are delivered through the WhatsApp Business Platform (Cloud API), operated by Meta Platforms Ireland Limited. Meta processes your phone number, the message content and delivery metadata to deliver the messages.

Our WhatsApp number is configured with Meta's Cloud API local storage in Germany (EU) for message data at rest. Meta may process data outside the EU in accordance with its data transfer safeguards.

Your own use of WhatsApp is also governed by WhatsApp's terms of service and privacy policy.

16.5 How to Stop and Remove Your Number

You can stop the WhatsApp brief at any time by:

  • Replying STOP to our WhatsApp number. We also accept arret, arrêt, unsubscribe, cancel, end, quit, stopp and desinscrire.
  • Tapping "Turn off" in any brief
  • Clicking "Remove number" in Daily email → WhatsApp
  • Clicking "Unlink" in Settings

If 3 briefs in a row cannot be delivered, we pause the WhatsApp brief and tell you by email.

After you stop the brief or it is paused, we keep your encrypted number so we can show you its status and you can relink it. Your number is deleted when you click "Remove number" or "Unlink", or when you delete your Morning Pulse account.

16.6 Legal Basis

We process your data for the WhatsApp brief on the basis of your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time as described in Section 16.5, without affecting the lawfulness of prior processing or your email brief.

17

X Data

This section explains how Morning Pulse handles data from X Corp. if you connect an X account to one of your apps. X is available on the Pro plan only and is off unless you connect it.

17.1 What We Access

When you connect X, you sign in on x.com and X asks you to allow Morning Pulse the tweet.read, users.read and offline.access permissions. In plain words: read posts and profile information, and keep that access until you remove it. X's read permission also lets an app see posts you can see. Morning Pulse only reads your own posts' numbers. We also ask you to agree, with a checkbox, that Morning Pulse reads these numbers from X once a day.

  • Your profile: your X user ID, @handle, profile picture and follower count.
  • Your recent posts: once a day, the running counters of your own posts and quotes published in the last 3 days: impressions, engagements, likes, reposts and quotes, replies, link clicks and profile visits. Replies and reposts are not counted.

17.2 What We Never Read or Store

We never read or store what your posts say, their media, your direct messages, who follows you or whom you follow, your likes, your bookmarks, or other people's posts. Morning Pulse never posts, reposts, likes or follows for you.

17.3 What We Store

  • Tokens: your X access and refresh tokens, encrypted at rest (Fernet). They are never logged or shown to anyone.
  • Account: your X user ID and @handle. The @handle is shown only to you, on your own app pages.
  • Profile picture: the link to your X profile picture, used as the app's icon unless you picked another one. We keep only the link, refresh it once a day and delete it when you disconnect X. The icon is shown to you and to teammates you share that app's KPIs with.
  • Tracked posts: the IDs, publish dates and counters of your posts from the last 3 days, which we need to work out each day's numbers. They are pruned every day, and a post you delete on X is removed within 24 hours.
  • Daily totals: each day's totals across your recent posts, and your follower count at the end of each day (UTC), stored as the values of your X KPIs.
  • Post checks: we count the X posts we check for your account to apply your monthly allowance. If you buy extra checks, purchases are processed by Stripe; we keep the payment reference, pack, amount and date.

17.4 Who Sees Your X Numbers

Your X numbers appear like your other KPIs: to you, to teammates you invite, to the report recipients you add, and in your WhatsApp brief if you turned it on. Your @handle never appears in emails, the WhatsApp brief or teammates' views. Your X data is never sold, never used for advertising, and never used to train AI models.

17.5 Disconnecting and Deletion

  • Disconnect X on your app's X page in Morning Pulse. We delete your tokens and tracked posts and ask X to revoke our access.
  • Deleting the app or your account does the same.
  • Revoking on X: you can also remove Morning Pulse in X under Settings and privacy > Security and account access > Apps and sessions. Morning Pulse then stops reading your numbers.

As with every other source, the daily totals already stored as KPI values are kept until you delete the KPI, its app or your account, so your past reports stay complete.

17.6 Our Role

X Corp. is the source of this data, not our processor. For X data, Morning Pulse acts as an independent controller under X's developer terms, and handles it as this policy and those terms require.

18

Instagram Data

This section explains how Morning Pulse handles Instagram data if you connect an Instagram account to one of your apps, and how to delete it. Instagram is off unless you connect it.

18.1 What We Access

You connect a Business or Creator account through Facebook: you sign in on facebook.com with the account that manages your Instagram and choose the Instagram accounts to share. Facebook asks you to allow Morning Pulse the instagram_basic and instagram_manage_insights permissions: your basic profile and your account insights. Morning Pulse uses them to read your account’s numbers once a day from Meta’s Graph API. Facebook also asks for the business_management permission: Morning Pulse uses it only to look up which Instagram account you chose, and never changes your business settings, its people or its assets.

Facebook also lists instagram_manage_messages, because Meta includes it in every Instagram connection and it can’t be removed. Morning Pulse never reads or sends your messages.

18.2 What We Store

  • Account: your Instagram account ID and username, and the Meta IDs that identify your authorization (your business ID and the ID of the system user Meta creates for the connection). If you share several Instagram accounts, we keep their IDs, usernames and follower counts only until you choose one.
  • Token: your access token, encrypted at rest (Fernet). It is a Meta system user token that doesn’t expire, so it is never refreshed.
  • Followers: a daily follower count, from the day you connect.
  • Daily totals: your account’s daily views, reach, likes, comments, shares, saves, interactions and profile link taps, stored as the values of your Instagram KPIs.

We do not read or store your posts, captions, the text of comments, who follows you, or your profile photo. Morning Pulse never posts, comments or likes for you, and never reads or sends your messages.

18.3 How Long We Keep It

We keep this data until you disconnect Instagram or delete the app or your Morning Pulse account. The Instagram connection data, including the token, and the follower counts are then deleted. If you remove Morning Pulse’s access in Meta, we delete the token on our next daily read and ask you to reconnect; the rest stays until you disconnect Instagram or delete the app. If you sign in on Facebook but never confirm the account in Morning Pulse, that connection data is deleted after 7 days. As with every other source, the numbers already in your KPI history stay until you delete those KPIs or your account, or ask for your Instagram data to be deleted (see 18.4).

18.4 How to Delete Your Instagram Data

You can ask us to delete your Instagram data in any of these ways:

  • In Morning Pulse: delete your Instagram KPIs (their history goes with them), or delete the app or your account. Disconnecting Instagram deletes the connection data and follower counts but keeps your KPI history.
  • In Meta: go to Meta Business Settings > Integrations > Connected apps and remove Morning Pulse. We see it on our next daily read, delete the token and ask you to reconnect; disconnect Instagram in Morning Pulse to delete the rest. If you ask Meta to delete the data Morning Pulse received, Meta sends us a data deletion request and we delete the Instagram connection data, the follower counts and the Instagram KPIs, with their history, for the Instagram accounts Meta names, in every Morning Pulse account they are connected to.
  • By email: write to privacy@morningpulse.app (see Section 20) and tell us which Instagram account to delete.

18.5 Our Role

Instagram is the source of this data, and Meta is not our processor for it: we read your own account’s data with your authorization. This is different from the WhatsApp brief (Section 16), where Meta delivers messages for us.

19

TikTok Data

This section explains how Morning Pulse handles TikTok data if you connect a TikTok account to one of your apps. TikTok is off unless you connect it.

TikTok is your provider, not our sub-processor. With your permission we read your TikTok account’s ID and username, and daily totals for followers, new followers, profile views, video views, likes, comments and shares. We never read your videos, captions, comments, messages or audience demographics, and we never post. Access and refresh tokens are stored encrypted. Disconnecting TikTok, or deleting the app or your account, deletes that app’s connection. When no other Morning Pulse app uses the same TikTok account, we also delete the tokens and ask TikTok to revoke our access. If another Morning Pulse app still uses it, including one added under another Morning Pulse account by someone who signed in to TikTok as that account, the tokens stay until that app disconnects too. Numbers already stored stay as KPI history.

To delete that history, delete your TikTok KPIs, the app or your account, or write to privacy@morningpulse.app (see Section 20).

20

Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy or your personal data, please reach out:

Morning Pulse — Data Protection

Email: privacy@morningpulse.app

Website: morningpulse.app

For GDPR-related inquiries, you may also contact our Data Protection Officer at dpo@morningpulse.app.

We aim to respond to all privacy-related requests within 30 days. If you are not satisfied with our response, you have the right to lodge a complaint with your local data protection authority.