Last updated: November 18, 2026
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.
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.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.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.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.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).
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.
For users in the European Economic Area (EEA), United Kingdom, and Switzerland, we process personal data under the following legal bases:
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.
We do not sell, rent, or trade your personal information. We share data only in the following limited circumstances:
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.
We implement robust technical and organizational measures to protect your data:
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.
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:
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.
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 | Duration |
|---|---|---|
| mp_session24 hours | Keeps you signed in | 24 hours |
| mp_csrf24 hours | Protects your forms against cross-site request forgery | 24 hours |
| pending_2fa5 minutes | Holds your sign-in while you enter your two-factor code | 5 minutes |
| mp_oauth_state10 minutes | Secures sign-in with Google and connecting Google or Shopify | 10 minutes |
| mp_x_oauth10 minutes | Secures connecting your X account | 10 minutes |
| mp_team_invite1 hour | Holds a team invitation while you sign up or sign in | 1 hour |
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.
Depending on your location, you may have the following rights regarding your personal data:
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.
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.
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.
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.
We may update this Privacy Policy periodically to reflect changes in our practices, technology, or legal requirements. When we make material changes:
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.
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.
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:
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.
Google user data is used exclusively to:
We do not use Google user data for any other purpose. Specifically, we do not:
We do not share, transfer, or disclose your Google user data to any third party, except:
We do not share Google user data with advertising networks, data brokers, or information resellers.
You can revoke Morning Pulse's access to your Google data at any time by:
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.
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.
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.
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:
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.
Shopify merchant data is used exclusively to:
We do not use Shopify merchant data for any other purpose. Specifically, we do not:
We do not share, transfer, or disclose your Shopify merchant data to any third party, except:
We do not share Shopify merchant data with advertising networks, data brokers, or information resellers.
You can revoke Morning Pulse's access to your Shopify data at any time by:
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.
Morning Pulse's handling of Shopify merchant data adheres to the Shopify API Terms of Service and the Shopify Partner Program Agreement.
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.
In Morning Pulse, go to Daily email → WhatsApp, then:
We record when you gave your consent and which version of the consent wording you agreed to.
Each brief contains:
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.
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.
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.
You can stop the WhatsApp brief at any time by:
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
You can ask us to delete your Instagram data in any of these ways:
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.
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).
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.