<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Clouditect - Medium]]></title>
        <description><![CDATA[Architecture, cloud, and real-world IT insights from a Solutions Architect. - Medium]]></description>
        <link>https://medium.com/clouditect?source=rss----36c883aeadb9---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Clouditect - Medium</title>
            <link>https://medium.com/clouditect?source=rss----36c883aeadb9---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 16 May 2026 02:50:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/clouditect" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[The Shopify App Could Read All Your Private Emails]]></title>
            <link>https://medium.com/clouditect/the-shopify-app-could-read-all-your-private-emails-0133432be585?source=rss----36c883aeadb9---4</link>
            <guid isPermaLink="false">https://medium.com/p/0133432be585</guid>
            <category><![CDATA[solutions-architecture]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[data-privacy]]></category>
            <category><![CDATA[oauth2]]></category>
            <category><![CDATA[technology-ethics]]></category>
            <dc:creator><![CDATA[Marcin Byra]]></dc:creator>
            <pubDate>Tue, 07 Oct 2025 07:15:34 GMT</pubDate>
            <atom:updated>2025-10-07T07:15:30.622Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A look at how a simple “track your order” feature can open a door to your entire inbox — and why more people should be talking about it. All because we often grant consent without thinking about what it means.</em></p><h3><em>What Is Shop?</em></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GgRd7d0ilxvjdaYfJn1o9w.png" /><figcaption>Shop app (Shopify) logo</figcaption></figure><p><strong>Shop</strong> is Shopify’s official shopping companion app. It helps you:</p><ul><li>Track online orders from multiple stores,</li><li>Get delivery notifications,</li><li>Discover and purchase directly from Shopify merchants.</li></ul><p>It’s convenient — and widely used.<br>If you’ve ever seen a <em>“Powered by Shopify”</em> checkout, you’ve already interacted with the same ecosystem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Cd47FUywHXvBP1Jp8ILYw.png" /><figcaption>Shop checkout view</figcaption></figure><h3>The Issue</h3><p>Recently, while ordering my favourite chili oil, I noticed something curious.</p><p>After checkout, the store suggested I <em>“track my order with Shop”</em>.<br>I downloaded it, entered my email, and — voilà — it automatically pulled in previous orders from other Shopify-based stores. Impressive. Seamless. Clever.</p><p>Then came the next step. The app asked me to <strong>connect my email account to track my orders</strong>. It appeared during the setup process, and you can see in my settings view below that the app still shows the missing access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kGj26_AbA7RJQpCHwEejxw.png" /><figcaption>Shop requesting consent to read your email messages</figcaption></figure><p>That’s when my protective instincts kicked in, just before clicking on the accept button. Why would it need <strong>access to my entire Gmail </strong>if my orders were already visible?</p><h3>What Happens Under the Hood</h3><p>Let’s look at how the modern authentication process works and what specific data the Shop app actually asks for.</p><h4>Modern authentication scheme</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t4zBRmakJ6AeDXk1dNt14w.png" /><figcaption>OAuth flow (simplified)</figcaption></figure><p>When apps request access to data from services like Gmail or Outlook, they use a secure standard called <strong>OAuth 2.0</strong>.<br>It redirects you to Google or Microsoft, where you can review and approve specific permissions (“scopes”) — for example:</p><ul><li>View your basic profile information</li><li>Read your calendar</li><li>Read your emails</li></ul><p>This diagram is simplified: to show the general idea, I’ve omitted token exchanges, additional requests, and redirects. Notice that in the consent screen above, Shop already has some permissions — listed below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oHuBItJPHKJK6KJDGgB4EA.png" /><figcaption>Basic permissions granted to Shop</figcaption></figure><p>That’s why it no longer asks for my email or profile data each time I use it; I’ve already granted those.<br>That’s the expected behaviour — but if I give this additional consent, it means the app will have ongoing access to my private emails.</p><p>OAuth is like giving a valet the key to your car. Useful in certain situations — but you shouldn’t hand over all your keys to anyone who asks.</p><h4>What the Shop App Asks For</h4><p>When redirected to Google, the Shop app requests permission to <strong>read all of your Gmail messages</strong>. That’s not hidden — it’s clearly shown in the Google consent screen.<br>And you always read and fully understand those screens… right?</p><p>Shopify likely requests this OAuth scope:</p><pre>https://www.googleapis.com/auth/gmail.readonly</pre><p>From <a href="https://developers.google.com/workspace/gmail/api/auth/scopes">Google’s Gmail API documentation</a>, it allows the app to:</p><blockquote>Read all resources and their metadata — no write operations.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ozA6X5RZzuL2crUT8sZ9ZQ.png" /><figcaption>A portion of the Gmail API scope list</figcaption></figure><p>This is the technical permission displayed in the consent screen during the OAuth flow.<br>Google marks such access as <em>restricted</em>, which means the developer must pass a verification process. That might sound serious, but it’s quite common; many apps go through it routinely.<br>Even if an app promises to use this only to detect order confirmations, the permission itself grants unrestricted access to every email.<br>That’s the critical distinction.</p><h4>Shopify’s Own Privacy Policy</h4><p>Shopify’s <a href="https://www.shopify.com/uk/legal/privacy">Privacy Policy</a> (as of October 2025) confirms that the company may:</p><blockquote>“collect, use, and disclose information to provide and improve our Services, including testing new features, improving performance, and developing new products.”</blockquote><p>Also, specifically for email integrations:</p><blockquote>Third parties: We receive information from partners who help us provide you with our services including the following:</blockquote><blockquote><strong>Email providers</strong>. If you use the Shop App and you connect your third party inboxes, such as Gmail or Outlook (according to their terms and policies and as permitted by applicable law), we receive information to identify shopping-related emails and display within Shop information about specific orders you have made, stores you have engaged with in the past, and other related information.</blockquote><p>The policy doesn’t explicitly describe <strong>how the Shop App processes data obtained through Gmail or Outlook integrations</strong>. As noted earlier, there’s no more granular Gmail API permission that limits access to shopping emails only — filtering must happen on the Shop side… or not.</p><p>The policy’s language is broad — understandable for a large platform, but concerning given the level of access users may grant. In practice, the boundaries of how email data is handled remain opaque to most users.</p><h3>My Take</h3><p>As a <strong>Solutions Architect</strong> working in a highly regulated environment, I’ve designed and reviewed integrations using OAuth and APIs like Microsoft Graph or Google Workspace.<br>Even when a system needs limited access — for example, to check calendar availability or pull meeting metadata — it can trigger major compliance discussions.</p><p>Why? Because <em>theoretical</em> access to personal data can be as risky as its actual use. Even if a vendor promises not to store or misuse data, once access is granted, it exists — and could be exploited or exposed in a breach.</p><p>So when a consumer app casually asks for permission to read all your emails “to improve your experience,” it’s worth pausing to consider what that really means.</p><h4>Mindset</h4><p>Most people, understandably, don’t overthink permissions.<br>We’ve all developed habits like:</p><ul><li><em>“If it’s in the App Store, it must be safe.”</em></li><li><em>“Everyone uses it, so it’s fine.”</em></li><li><em>“I trust Google to protect my account.”</em></li></ul><p>The app says it needs this to track orders; without permission, some features won’t work; it’s a big, reputable company — what could go wrong?</p><p>You’re one of millions of users, effectively anonymous, so you tap <strong>Allow</strong> without much hesitation. And because the app already shows you some order data even without that access, it doesn’t feel like a critical decision.</p><p>But ask yourself: Is this level of access essential — or just convenient (or profitable) for the company?</p><p>Even more telling: tracking already works without scanning your emails. Here’s my tracking view without granting consent:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AkQ1n6QTGQhH9zWiAHmwYA.png" /><figcaption>Shop tracking view</figcaption></figure><p>The only extra feature seems to be automated import of some orders that weren’t already added to the app but could be found in your inbox.<br><strong>You could spend 20 seconds adding them manually. Are you really willing to risk exposing your private emails for that?</strong></p><h4>Why This Matters</h4><p>Email accounts are often the single richest source of personal information in our digital lives:</p><ul><li>Banking and tax communication</li><li>Online purchase receipts</li><li>Work correspondence</li><li>Family photos and private messages</li></ul><p>Granting full read access — even to a reputable company — effectively hands over a copy of your digital identity.</p><p>To be clear: There’s no evidence that Shopify is misusing this data, and I’m not suggesting it is. I’m using this app simply to highlight a wider problem.</p><p>However, the potential exposure is significant, particularly if data were ever accessed improperly, breached, or repurposed.<br>It’s even more concerning when you realize you may have <strong>legally granted access to your private emails to a foreign company </strong>— virtually without restriction. That should raise the next question…</p><h4>Why Isn’t This a Bigger Discussion? Why people don’t care?</h4><p>Perhaps because we trust large, familiar platforms.<br>Perhaps because permission prompts have become so routine that we stop paying attention.</p><p>OAuth solved a complex problem — letting apps share data securely without passwords — and it made things easy.<br>Maybe <em>too</em> easy. We’ve become accustomed to convenience.</p><p>Most users <strong>would panic if an app asked directly for their Gmail login and password to read messages</strong> (which was exactly how it worked years ago). But when it’s wrapped in a polished consent screen, we rarely think twice.</p><h4><strong>What You Can Do</strong></h4><ul><li><strong>Read</strong> permission requests before approving them.</li><li><strong>Limit</strong> access to only what’s necessary for the feature you need.</li><li><strong>Revoke</strong> unused app permissions periodically (Google and Microsoft both allow this).</li><li><strong>Ask questions</strong> — transparency improves only when users demand it.</li></ul><h3>Final Thoughts</h3><p>Shopify’s Shop App is polished, popular, and generally trustworthy — but even reputable companies can make design choices that deserve scrutiny.</p><p>The concern here isn’t about bad intent; it’s about <strong>disproportionate access</strong> and <strong>lack of transparency</strong>. As users, professionals, and architects, we should ensure such permissions are widely understood and openly discussed.</p><p>Because the <strong>privacy of millions of users</strong> — and the risk of exposing all your emails — <strong>shouldn’t depend on whether someone took the time to read a consent screen.</strong></p><p>If a courier offered to pick up your physical mailbox key “just to check for delivery updates,” would you hand it over? Probably not. Yet many of us do the digital equivalent every day.</p><p><em>Written by Marcin — Solutions Architect sharing practical insights on cloud, architecture, and IT strategy. Also on </em><a href="https://www.instagram.com/clouditect"><em>Instagram @Clouditect</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0133432be585" width="1" height="1" alt=""><hr><p><a href="https://medium.com/clouditect/the-shopify-app-could-read-all-your-private-emails-0133432be585">The Shopify App Could Read All Your Private Emails</a> was originally published in <a href="https://medium.com/clouditect">Clouditect</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>