updated text

Author: LauraDuRy

src/routes/blog/post/How-to-put-privacy-first/+page.markdoc

@@ -23,7 +23,7 @@ With our recent announcement of GDPR compliance, we took a big step in becoming
 
 ## So, what did we remove?
 
-If you visit the Appwrite Console or website, you will see a cookie consent banner. However, you will see only two options for you to pick from, `Strictly necessary cookies` and `Product analytics.`We have removed all of our `Marketing` classified pixels, tags, and cookies such as:
+If you visit the Appwrite Cloud Console or website, you will see a cookie consent banner. However, you will see only two options for you to pick from, `Strictly necessary cookies` and `Product analytics.`We have removed all of our `Marketing` classified pixels, tags, and cookies such as:
 
 - HubSpot tag
 - Google Tag Manager
@@ -59,10 +59,9 @@ Our growth philosophy and rules enable us to grow without relying on tracking yo
 The above can simply be conveyed as having a good content and social media strategy, and the success of this can be analyzed in a privacy-friendly way. We can measure success in metrics like traffic, impressions, social reach, new accounts, etc. Here are some ways we keep the team informed:
 
 - **UTM data** helps us track attributions from different campaigns, mediums, sources, and specific content. We can tell whether a visitor is coming from a specific link or not, for which we currently use [dub.co](https://dub.co/), an open-source alternative to Bitly. This helps us determine whether sponsoring a newsletter was effective or if a piece of content brought us traffic. But that is about as far as we will go. As soon as you leave our website, we lose all your information and would like to keep it that way.
-- **Open source analytics alternatives.** We use privacy-friendly alternatives like [Plausible](https://plausible.io/about) to help us analyze our website and Console data. It is an open-source analytics platform with one of the highest [privacy standards](https://plausible.io/privacy) I have seen. It helps us get demographic and user behavior data in a privacy-friendly manner.
+- **Open source analytics alternatives.** We use privacy-friendly alternatives like [Plausible](https://plausible.io/about) to help us analyze our website and Cloud Console data. It is an open-source analytics platform with one of the highest [privacy standards](https://plausible.io/privacy) I have seen. It helps us get demographic and user behavior data in a privacy-friendly manner.
 - **First-party data.** We get a lot from users, like emails and names from authentication. We use it for login purposes, so you don’t have to enter your login details over and over again and add them to our CRM, HubSpot, for email communications. But with this data also comes great responsibility, and with our recent GDPR compliance announcement, we are not only upholding strict data privacy but also are certified with the European General Data Protection Regulation (GDPR) standards.
 - **Content performance.** As mentioned, you should be able to find information on Appwrite without any limitations. Many companies have gated content, where they set up forms to collect your data for you to get information or reports. We believe this restricts you from learning freely. Therefore, we focus on the performance of our content and see metrics such as `page view` and `time on page` as a measurement of success.
-- **Online reach.** Brand24 and Orbit are two tools we use to measure online reach. Both tools allow us to see and analyze community growth online. Brand24 focuses more on the standard online channels, such as X, LinkedIn, and YouTube, and the people influencing our reach there. Meanwhile, with Orbit, we focus on more (developer) community channels to understand performance on channels such as Discord, GitHub, and Dev.to.
 - **Search.** Many people search the internet daily, looking for solutions, and even after the introduction of ChatGPT, this is still the case. So, keeping track of our search results is another indicator of our tactics' success, as it’s a great indicator of interest shown in Appwrite and the industry. For now, we use Semrush and Google Search Console to give us this data, but we are interested in learning about open-source tools in this area.
 
 To return to our growth philosophy, we believe the dev community will find the information they need on their terms. We know that the developer journey is not one straight line and that people will find information on their preferred platforms when needed. We just need to ensure that we have content ready for you to find wherever you are on your journey. This instinctively eliminates the idea of running ads across platforms to convince you to use Appwrite. We merely use paid media or sponsored newsletters to let you know we exist, making pixels, cookies, and tags redundant in most cases.
@@ -73,14 +72,12 @@ But there is more to gain than just privacy-friendly data.
 
 As we often repeat, we are heavily focused on the developer experience. It is at the core of everything we do. Considering this, there are several reasons why we decided to remove most of the tags, pixels, and cookies from our website:
 
-- **Privacy:** As many studies show, people want to [control the information they share](https://venturebeat.com/data-infrastructure/report-94-of-consumers-want-control-over-the-information-they-share-with-companies/) with other parties online. By removing most of the tags, pixels, and cookies, we reduce the amount of personal data we collect from the Appwrite website and Console. And as we focus on collecting first-party data, we grant you that control.
-- **Performance:** Tags, pixels, and cookies can slow down a website's loading time. By removing them, we improve the performance of our website and the Console for you. And a [study from Akamai](https://www.akamai.com/newsroom/press-release/akamai-releases-spring-2017-state-of-online-retail-performance-report), shows that a two-second delay in web page load time increases bounce rates by 103 percent. So, improving performance is worth it.
+- **Privacy:** As many studies show, people want to [control the information they share](https://venturebeat.com/data-infrastructure/report-94-of-consumers-want-control-over-the-information-they-share-with-companies/) with other parties online. By removing most of the tags, pixels, and cookies, we reduce the amount of personal data we collect from the Appwrite website and Cloud Console. And as we focus on collecting first-party data, we grant you that control.
+- **Performance:** Tags, pixels, and cookies can slow down a website's loading time. By removing them, we improve the performance of our website and the Cloud Console for you. And a [study from Akamai](https://www.akamai.com/newsroom/press-release/akamai-releases-spring-2017-state-of-online-retail-performance-report), shows that a two-second delay in web page load time increases bounce rates by 103 percent. So, improving performance is worth it.
 - **Security:** This tracking technology can also track you across the web and collect intrusive data about you. By removing them, we are making our website more secure for you and preventing potential [data breaches](https://venturebeat.com/security/report-multiple-data-breaches-common-in-past-year/).
 
 Overall, it made much sense to go down this route and focus on delivering a better experience and enhancing trust with the community. And I think it’s fair to say that with the removal of marketing pixels, cookies, and tags, we didn’t lose anything; we merely gained.
 
 ## Building a privacy-friendly and open-source growth stack
 
 We still have the necessary tools to improve our product, the developer experience, and analyze our website traffic. That said, we will continue to explore the possibilities of moving towards a fully open-source and privacy-friendly growth tech stack. Not only do we feel it is the right thing to do, but it is also rooted in our culture. We want to treat you as we want to be treated by any vendors we use. For now, this has been the most sensible decision we could have made for Appwrite and the community. We are excited to take privacy further and further, so who knows where we will stand a year from now.
-
-If you are looking to build your privacy-friendly growth stack, go check out [this blog from Posthog.](https://posthog.com/blog/best-gdpr-compliant-analytics-tools)